I haven't used my G-Tablet in a few months. Now it's rather sluggish and hesitates. Do these ROM deteriorate over time. I am using ICS.
My opinion is gtabs don't run well with anything other than froyo based roms. I've tried several jelly bean roms and they start out very nice but in a few days start to slow down. Every time I tell my wife I'm trying another rom she says "why bother ". I'm back on VeganTab ginger edition and everything works.
Sent from my VEGAn-TAB using xda app-developers app
How do i get back to Vegan Tab from Smoother Bean Ver 1.5 With Cyanogen Mod version 10 - 20121103 -unofficial -smba 1002, kernal version 2.6.39.4 Android version 4.1.2? I agree my Gtab worked great under vegan tab, but ever since I went to ICS it just bogs down. Is there a place that walks me thru the steps I need to take to get me back to vegan tab gingerbread? thanks!
laserbiz said:
How do i get back to Vegan Tab from Smoother Bean Ver 1.5 With Cyanogen Mod version 10 - 20121103 -unofficial -smba 1002, kernal version 2.6.39.4 Android version 4.1.2?
Click to expand...
Click to collapse
What's the output of this command on your gTablet? Open the Terminal Emulator app and type in the bits in bold.
Code:
$ [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 223380 32 223348 0% /dev
tmpfs 223380 0 223380 0% /mnt/asec
/dev/block/mtdblock3 204800 161528 43272 79% /system
/dev/block/mtdblock4 222208 31100 191108 14% /cache
/dev/block/mmcblk3p2 1187400 305504 881896 26% /data
...
$
Is there a place that walks me thru the steps I need to take to get me back to vegan tab gingerbread? thanks!
Click to expand...
Click to collapse
If you want to go back to a GB ROM, then I suggest installing CM-7.2 rather than VEGAn-Tab.
If you want VEGAn-TAB here is a link http://vegantab.gojimi.com/2011/08/26/vegan-tab-gingeredition-7-1-0-for-bootloaders-1-1-and-1-2/
Sent from my VEGAn-TAB using xda app-developers app
---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------
Another link for bl 1.1 http://www.slatedroid.com/topic/152...ition-stable-rc1-updated-411-g-tabletzpad-t2/
Sent from my VEGAn-TAB using xda app-developers app
Below is the output of the command you asked for. Thanks again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
laserbiz said:
Below is the output of the command you asked for. Thanks again
Click to expand...
Click to collapse
Ah, I see: you have a 350MB /system partition--you must've used the TeamDRH 350MB nvflash package, instead of the 250MB nvflash package as recommended in your ROM's OP page. Had you a 250MB /system partition, you could have skipped a step.
Which GB ROM do you want to install? I recommend CM-7.2; VEGAn-Tab has a few bugs which don't seem to be present on CM.
rajeevvp said:
Ah, I see: you have a 350MB /system partition--you must've used the TeamDRH 350MB nvflash package, instead of the 250MB nvflash package as recommended in your ROM's OP page. Had you a 250MB /system partition, you could have skipped a step.
Which GB ROM do you want to install? I recommend CM-7.2; VEGAn-Tab has a few bugs which don't seem to be present on CM.
Click to expand...
Click to collapse
Thanks again for your prompt response. Does what I posted show which boot loader tree I am on (1.1 or 1.2?) and does that even make a difference if I want to go to cm 7.2? Also is there a link to a idiots version(me) to 7.2 so that I can do the install with the best directions?
laserbiz said:
Does what I posted show which boot loader tree I am on (1.1 or 1.2?)
Click to expand...
Click to collapse
All nvflash packages from TeamDRH will install a 1.2 bootloader, so that's what you will be on.
...and does that even make a difference if I want to go to cm 7.2?
Click to expand...
Click to collapse
Yes, official CM-7.2 is only for bootloader 1.1, but, we'll fix that in step 3 below.
Also is there a link to a idiots version(me) to 7.2 so that I can do the install with the best directions?
Click to expand...
Click to collapse
Follow these steps:
1. Shrink /system and expand /cache on the NAND flash for GB ROMs.
Download, unpack, and run the batch file in Team DRH's 250 MB nvflash package whilst the tablet is in APX mode. This will shrink the /system partition to 250MB (100+ MB more than what's needed for CM-7.2 GB), and more importantly, expand /cache to ~170MB. This is important because /cache is where Market apps (and other data?) are downloaded temporarily before installation.
2. Boot into CWM, then format /cache and repartition the internal SD card.
The nvflash package will install CWM-5.5.0.4Beta15. After step 1 completes, boot into CWM (there's no need to boot into the VS stock ROM). Use the menu entries to a) format /cache and b) repartition the internal SD card. For step b) you can choose either 2048/0 or 4096/0 as the size of data/swap. Your choice.
3. Transfer and install the CM-7.2, GB Gapps, and 1.2 kernel zip files.
After step 2 is done, transfer CM-7.2 installation zip file, the Gingerbread Gapps zip file (20110828 package), and pershoot's last Gingerbread kernel for 1.2 bootloaders (the file with the `newbl' in the filename: boot-cm_2632.48_gb_newbl-oc-uv-xtra-vfp_fp-112411.zip) to the SD card on the gTablet.
Install the ROM first, then install the 1.2 kernel (overwriting the default 1.1 kernel), and lastly, the Gapps.
4. Boot into CM-7.2 (make sure you set the correct time) and complete installation.
"3. Transfer and install the CM-7.2, GB Gapps, and 1.2 kernel zip files.
After step 2 is done, transfer CM-7.2 installation zip file, the Gingerbread Gapps zip file (20110828 package), and pershoot's last Gingerbread kernel for 1.2 bootloaders (the file with the `newbl' in the filename: boot-cm_2632.48_gb_newbl-oc-uv-xtra-vfp_fp-112411.zip) to the SD card on the gTablet.
Install the ROM first, then install the 1.2 kernel (overwriting the default 1.1 kernel), and lastly, the Gapps."
=========================================
The above file highlighted in red does not seem to be available, every time I try to go to droid basement, it comes back with bad gateway....is there an alternative site for that file?
rajeevvp said:
Ah, I see: you have a 350MB /system partition--you must've used the TeamDRH 350MB nvflash package, instead of the 250MB nvflash package as recommended in your ROM's OP page. Had you a 250MB /system partition, you could have skipped a step.
Which GB ROM do you want to install? I recommend CM-7.2; VEGAn-Tab has a few bugs which don't seem to be present on CM.
Click to expand...
Click to collapse
I'm curious, I haven't tried CM-7.2, when I go to thread I see a lot of issues. With VEGAn-Tab it runs fine. I wanted to try CM-7.2 but doesn't look like it would be better. Why do you recommend one over the other?
laserbiz said:
The above file highlighted in red does not seem to be available, every time I try to go to droid basement, it comes back with bad gateway....is there an alternative site for that file?
Click to expand...
Click to collapse
It works fine now. Must've been a temporary website glitch.
striker59 said:
I'm curious, I haven't tried CM-7.2, when I go to thread I see a lot of issues.
Click to expand...
Click to collapse
There isn't a thread for the stable, official CM-7.2 on this board as far as I am aware. There is a thread for a CM-7.2 release candidate and repack. And, on that thread:
1. The last ROM update there was made more than 6 months before the stable 7.2 came out.
2. Most of the issues reported by the users seem to relate to older versions of the repack (starting from CM-7.1.0-RC1 onwards).
3. All the CM7.x ROMs there are all based on a) release-candidate code, b) idiosyncratic repacks, c) questionable tweaks.
If you have seen problems with the officially released CM-7.2, I'm happy to look into it.
With VEGAn-Tab it runs fine. I wanted to try CM-7.2 but doesn't look like it would be better. Why do you recommend one over the other?
Click to expand...
Click to collapse
Mostly bugs as I said:
1. This one you already know.
2. VEGAn-Tab-7.1 mishandles a long DHCP lease time as -1 seconds, causing periodic WiFi disconnects. (also here).
3. An older version of VEGAn-Ginger wrecks the Internal SD card partition table when you attempt to do a factory reset via the ROM. Don't know if this same bug exists on the current VEGAn-Tab-7.1. (You could confirm for me.)
4. Addition of an extra .jar file in the BOOTCLASSPATH causes bizarre problems with the correct working of updated su and other commands/apps. (Not reported on this board so far--ask for details.)
Additionally,
5. CM-7.2 is Android 2.3.7 versus the Android 2.3.5 of VEGAn-Tab 7.1.
6. If I recall correctly, the camera seems more stable in CM-7.2.
7. And, other bugs that I don't recall at the moment...
rajeevvp said:
All nvflash packages from TeamDRH will install a 1.2 bootloader, so that's what you will be on.
Yes, official CM-7.2 is only for bootloader 1.1, but, we'll fix that in step 3 below.
Follow these steps:
1. Shrink /system and expand /cache on the NAND flash for GB ROMs.
Download, unpack, and run the batch file in Team DRH's 250 MB nvflash package whilst the tablet is in APX mode. This will shrink the /system partition to 250MB (100+ MB more than what's needed for CM-7.2 GB), and more importantly, expand /cache to ~170MB. This is important because /cache is where Market apps (and other data?) are downloaded temporarily before installation.
2. Boot into CWM, then format /cache and repartition the internal SD card.
The nvflash package will install CWM-5.5.0.4Beta15. After step 1 completes, boot into CWM (there's no need to boot into the VS stock ROM). Use the menu entries to a) format /cache and b) repartition the internal SD card. For step b) you can choose either 2048/0 or 4096/0 as the size of data/swap. Your choice.
3. Transfer and install the CM-7.2, GB Gapps, and 1.2 kernel zip files.
After step 2 is done, transfer CM-7.2 installation zip file, the Gingerbread Gapps zip file (20110828 package), and pershoot's last Gingerbread kernel for 1.2 bootloaders (the file with the `newbl' in the filename: boot-cm_2632.48_gb_newbl-oc-uv-xtra-vfp_fp-112411.zip) to the SD card on the gTablet.
Install the ROM first, then install the 1.2 kernel (overwriting the default 1.1 kernel), and lastly, the Gapps.
4. Boot into CM-7.2 (make sure you set the correct time) and complete installation.
Click to expand...
Click to collapse
Awesome detailed post. Thanks so much.
I've bounced all around and ended up with 3 Roms I like. The 7.2 CM you recommend, the GTabCombover Rom and the G_Harmony Jelly Bean Rom that TJohnsonjr put together.
Related
This is a modified CWM-based recovery for the Motorola Photon 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3 formatting
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition.
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-photon3.img
Example:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Photon 4G. I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
I do NOT have a Motorola Photon 4G. I have based this recovery off the Photon kernel and Atrix resources as suggested by Calkulin. I do not SUSPECT there will be problems but again, I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
SPRINT USERS
Orange 5.0.2.7-photon3 / ZIP version.
MD5 0dc70209659fecbf7a2a01fe64b431af / a7fa2daf946557006931d33f3954e350
Cyan 5.0.2.7-photon3 / ZIP version.
MD5 440baa230638bd12dfd38b67977d3ac3 / 4da9f845f5d8ae0c37d0e1deaecd931c
Light green 5.0.2.7-photon3 / ZIP version.
MD5 b0791b6a4e0ea1a593d450518f309315 / f4afa4ca6f9616713ba436149df48c46
Dark green 5.0.2.7-photon3 / ZIP version.
MD5 5ef4862918169c1b4f9b0cbd60c70267 / 12acbe4adac62dc79e9a2b9ed1d0ea3b
Blue 5.0.2.7-photon3 / ZIP version.
MD5 cb1a4b2b48d18f535f5a3ce312e3ee81 / 53eee173392a8a821e45e8ddb1bbefd6
Red 5.0.2.7-photon3 / ZIP version.
MD5 f95a0adfb47ae2b995412b89d95f40fe / ca222e4891f756b5b4ad59fe06b6f0bf
Original ROM Manager/CWM installable zip thanks to SolidHelix. You must still be UNLOCKED and have already applied at least one version of this recovery via fastboot to use them.
Source is here.
A few notes:
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext2/3 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. I am not aware of any use of this partition on this phone yet.
Thanks to:
Koush and the CM team for CWM
Calkulin for pointing out the kernel
Everyone who has made unlocking the Photon possible
** Changelog **
2011-11-14 (5.0.2.7-photon3):
Minor bugfix update mostly
ext4 experimental support
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental
2011-09-23 (5.0.2.3-photon2):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-photon1.3):
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-photon1.2):
Changed fstab to ext3 since no kernel support yet
2011-08-17 (4.0.1.4-photon1.1):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-photon1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots (these show an Atrix, but the color is identical):
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
I doubt ext4 support works due to no kernel support. Disabled currently. Added in -photon3.
Soft keys to use as navigation may not work due to the kernel.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
Awsome!!!
Sent from my MB855 using XDA App
Sounds good. Will try.
Sent from my unlocked rooted Moho!
This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?
I like that there is a choice of colors. Well done!
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
Hold down volume down and power till boot. Volume down till you see android recovery, then volume up.
Also, as aaron130 said you can use quick reboot from the market.
Sent from my unlocked rooted Mopho!
Fricken Awesomeness
Sent from my Photon Blaster.
ahhh this is what im getting..it seems fastboot isnt working for some reason even tho i just rooted..some help please
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot devices
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot erase recovery
< waiting for device >"
edit: nevermind got it working ..thanks!
Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?
i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated
the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
the same way you boot into fastboot
when phone is off.......
1. press and hold power and volume down
2. when the phone displays fastboot release the buttons
3. use volume down to switch to android recovery
4. press volume up and boot into cwm
Im creating a backup as I type (speak)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jglee311 said:
This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?
Click to expand...
Click to collapse
Lokifish Marz said:
Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?
Click to expand...
Click to collapse
Calkulin's is based off my -atrix3 revision. This is slightly newer code (-atrix3.1 bug fixes mostly). It uses the same kernel as his. He PM'ed me to let me know how he got it to work on this phone and I simply used his advice to create the thread.
I haven't verified ROM Manager on this phone. It may need until Koush updates ROM Manager to say it supports this phone. I thought several times about editing that out of the second post but chose to leave it for now..
tim-tim said:
i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated
Click to expand...
Click to collapse
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.
romracer said:
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.
Click to expand...
Click to collapse
http://pastebin.com/uGakTEYu
Yay 4 Juggs said:
http://pastebin.com/uGakTEYu
Click to expand...
Click to collapse
Thanks, the table looks exactly like the Atrix (not surprising). If choosing "Format /sdcard" from the mounts and storage menu didn't work, I'll probably need /tmp/recovery.log after trying (but before exiting recovery - the file is lost then).
Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that
romracer said:
Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that
Click to expand...
Click to collapse
are the tools fixed such as being able to clear cache...nandroid...etc?
The JB XXLSJ leak and the latest XWLS8 official JB releases have introduced a new partition on /dev/block/mmcblk0p12 mounted to /preload.
This was required due to the fact that the /system partition just isn't big enough to hold all the extra apps the JB leak requires.
The problem with this is that with the exception of PhilZ Kernel and Jeboo, CWM backups in bith Siyah and DorimanX omit the backing up this /preload partition. If you regularly try out different ROMs and restore back, this can mean your ROM's getting a little out of step as it would have the /preload files from the ROM you last flashed, with all other files coming from the ROM you performed the backup on.
Currently, if you are on Siyah/Dori, the only way to backup/restore everything via CWM backups is to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) make your backup in PhilZ/Jeboo/Apolo recovery
and if you want to revert back to Siyah/Dori:
e) flash Siyah/Dori
f) advanced>reboot recovery
If you ever need to restore, and you are using Siyah/Dori then you will need to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) restore your backup in PhilZ/Jeboo/Apolo recovery
e) flash Siyah/Dori
f) reboot
NOTE: Later versions of PhilZ require you to specifically set the backup/restore of /preload. This is done in PhilZ CWM Recovery:
1. boot into PhilZ recovery
2. Philz settings
3. Special backup and restore
4. Misc nandroid settings
5. Toggle /preload processing (make sure this says /preload will be processed)
To get around this current omission in Siyah and Dori, I have written the following 2 CWM flashable zips:
GS2PreloadBackup
This will backup your current /preload partition.
The backup is made on a per-ROM basis to /sdcard/MyBackups/preload/[ROM-Name]/preload.tar. Therefore, if you backup on several different ROMs, you will get several ROM folders in this preload backup location, one backup per ROMGS2PreloadRestore
This will restore the /preload backup made by the above script for your current ROM.
So if you are on Siyah/Dori and want to make a full backup without flashing between PhilZ, you can now do the following:
1. Boot up into recovery
2. Make your CWM backup
3. Run GS2PreloadBackup.zip
Further down the line, if you ever wanted to restore this, then
1. Boot up into recovery
2. Restore your CWM backup
3. Flash GS2PreloadRestore.zip
The restore is sensitive to the ROM you are currently on, so it will only restore the /preload for you current ROM, provided you have run the backup script previously for the ROM of course.
Changing the backup location
By default, backups are made to the internal SD card in /sdcard/MyBackups as described above. You can change the backup location to the external SD card if required. This can be done by editing /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Within this file there is a line that tells the script where the backups are to be stored. Edit the following line as required:
BKP_LOCATION=int (backs up to INTERNAL SD Card, ie. /sdcard/MyBackups)
BKP_LOCATION=ext (backs up to EXTERNAL SD Card, ie. /storage/extSdCard/MyBackups)
Please note, that if you change the location between int/ext in MyWipeOptions.prop, your backups will not get automatically moved to the new location. You would have to manually move the current backup over to the new location if you do not want to potentially have two copies of the backups.
Test Mode
The script inside the zip file that does all the work is called GS2Hawker.sh. This can be called via adb shell/Script Manager etc. in order to perform a test dummy-run. The Test Mode goes through all the motions as per a standard CWM Recovery run, but it does not remove any files/folders in any way, and merely shows the commands it would have done.
eg. extract GS2Hawker.sh from the zip using 7Zip or similar
adb shell
sh GS2Hawker.sh PreloadBackup
sh GS2Hawker.sh PreloadRestore
Summary of Files Created/Used
1. /sdcard/MyBackups/HawkerLogs/GS2PreloadBackup.log.
2. /sdcard/MyBackups/HawkerLogs/GS2PreloadRestore.log.
These shows the activity log of what the script has done. This gets overwritten the next time you run the script.
3. /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Options file for all my scripts. Currently this contains the option for backup location, internal or external SD card. (See Changing the backup location above)
These scripts are of course only a temporary measure as I am in no doubt that both Siyah and Dori will both also include the /preload partition in their CWM Recovery scripts very shortly, but for now, I hope this might help one or two of you out.
Known Issues
Free space checking prior to performing the backup always returns free space on internal sdcard even when
backing up to external sd card.
For some reason, when I do a df (on Siyah, not sure about other kernels)
I get the following:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /mnt/.secondrom
/dev/block/mmcblk1p1 12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk1p1 30648992 17592608 13056384 57% /emmc
It appears /dev/block/mmcblk1p1 is mounted to /emmc AND /sdcard?????!!!!
All file operations on /emmc gets performed on the extenral sd card as expected (ie your backups WILL go to external), BUT when the df command is issued to check for available space, it is performed on /sdcard! Therefore, if the script is trying to find the space left on /emmc, and the device returned from the df command is /sdcard, then an error is presumed, an no space check performed.
Please Note
I use these scripts myself between many flashes of different ROMS, and are provided here, as-is, out of my passion for development. Although every effort has been made to ensure everything works correctly on my handset I cannot be held responsible if things get messed up, or if you put something in your user-definable files that you shouldn't have included. As with everything else on here, you flash anything at your own risk. I always recommend performing a full CWM backup before attempting to flash anything onto your device.
Current Versions
GS2PreloadBackup 1.05 (22/05/2013)
GS2PreloadRestore 1.05 (02/03/2013)
Note: If the latest versions quoted above do not appear in the download devhost site, then please be patient!
ApriliaM3 should soon be uploading them.
Downoad Here
Download Here
My HUGE thanks goes out to ApriliaM3 for hosting the scripts.
Please give him the thanks he deserves.
To Do
....
Work in Progress
....
Changelog
GS2PreloadBackup v1.05 (22/05/2013)
1. Extra free space checking. (See OP for known issues)
GS2PreloadBackup v1.04 GS2PreloadRestore v1.05 (02/03/2013)
1. Backups can now go to either internal or external SD Card. See Post #1 for details
GS2PreloadRestore v1.04 (22/02/2013)
1. Now restores /preload/symlink instead of whole of /preload for greater flexibility in dual-boot systems
2. Current /preload/symlink contents removed before restore giving a better snapshot for the restore point
GS2PreloadBackup v1.03 (22/02/2013)
1. Now backs up /preload/symlink instead of whole of /preload
GS2PreloadRestore v1.03 (22/02/2013)
1. Current /preload contents removed before restore giving a better snapshot for the restore point
2. Progress now given in Mb during the restore process
v1.02 (13/02/2013)
1. Numerous display updates
2. Log file now goes to /sdcard/MyBackups/HawkerLogs so that they are grouped with logs from my other scripts
v1.01 (31/01/2013)
1. Progress now given during backup operation of the size of backup complete
Thanks buddy:thumbup::thumbup:. I just wanted to get in first. :thumbup::thumbup:
Edit. I just ran a backup and it worked and so did the restore :thumbup:
In the meantime I'll leave this picture until I can post something constructive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.39
(DEFAULT PROFILE AND SETTINGS )
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36268094
2.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=34879811
3.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
4. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Nice guide
Sent from my GT-I9100 using xda premium
Thanks Hawker, great work.
Red you got a nice ass!
Edit. ... I have done a backup and ran the zip after it and it worked great.
Thank you!
Sent From My Galaxy S2 Running
AllianceROM Powered By DorimanX Kernel
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
ApriliaM3 said:
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
Click to expand...
Click to collapse
Thanks Pete.
I've updated the links in the OP to yours.
I'll let you know if I update the scripts at all.
Cheers mate!
:good:
Thank you, really usefull script.
deleted
Updated to V1.01
See Changelog for details
hawkerpaul said:
Updated to V1.01 (pending upload to ApriliaM3's host.....)
Click to expand...
Click to collapse
All done Paul.
hawkerpaul said:
Updated to V1.01
See Changelog for details
Click to expand...
Click to collapse
I have been trying to backup preload to my external sd card by modifying /sdcard/MyBackups/MyBakDevice.txt ( see screenshot)
But the backup is stil made on the internal and after every attempt the content of MyBakDevice.txt is set back to the default /sdcard
I'm I doing something wrong here
EDIT: Tried 3 times, same result every time.
Backup to external sd card not possible currently, so I'm looking into getting this working properly. For now, ignore any information relating to MyBakDevice.txt. All backup will go to internal sd card only for the time being.
Updated to V1.02
See post #2 for details
Updated GS2PreloadRestore to v1.03
See post#2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
This is awesome, thanks for your work!!!!!
May I ask something? (if not, ignore me)
Is it possible to not backup the full /preload partition but only the /preload/symlink part of it? I ask because it would be very helpful with this : http://forum.xda-developers.com/showthread.php?p=38209559
So, a user could backup /preload/symlink/... Then install a 2nd Rom, that will probably format /preload and just restore it easily with your File. This might be a very big step for Dual boot as it makes so many things easier!
Anyways, thank you very much for your efforts!!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
Click to expand...
Click to collapse
Thanks!
But in my /preload there is the /symlink part of my Sammy Rom (shorted to about 80mb) and the /system of 2nd Rom (MCM's 10.1)
The created Backup with your zip is about 390mb big so I figured that there has to be more than just the symlink stuff.
This could be solved, of course by a clean install of first Rom (Sammy), backup with your file, install 2nd Rom and then restore /preload.
But it would be easier if only /preload/symlink would be backed up and later restored.
But, important, I don't want to bug you, it's awesome as it is, seriously!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
Click to expand...
Click to collapse
Awesome, thank you very much!!!
If it's ok I will add a how-to to my thread and link to yours?
To me, this is an enormous step forward great!!
Sent from my GT-I9100 using xda app-developers app
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.
FIrst things first...
Code:
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about the tool you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Now that we have that done...
Repartition guide for
The GT-i9100
Introduction:
This script came a long way before landing here. It originally came from @forumber2 with his guide for the GT-i9300. It then went on to the Note 2 by @ninekaw9 and @smeet.somaiya before I decided to port it over to this lovely device.
Click to expand...
Click to collapse
What does the script do?
It basically removes the partitions present from your device and creates partitions with modified sizes.
TLDR: A flashable .pit file
Images
Result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Features
Adds more space for more apps.
Reduced cache partition for even more space for apps.
No need for a computer, fully flashable in CWM.
How To Install?WARNING: From this point onwards, this guide requires your fullest attention so that it will not brick your device. I tested this on my own i9100, and it is working perfectly.
Links will be provided at the end of the post.
This will wipe everything from your device! Please make a backup before proceeding. Don't say I didn't warn you.
There are two methods to flashing this script. Both works perfectly fine.
Method 1 If you're using 1.1 and above, steps 6-9 are not needed!
Download the two recoveries provided in the Download post below.
Reboot into recovery (CWM or TWRP needed)
Flash philz_touch_6.07.9-i9100.zip and reboot into recovery.
Flash the repartition-apps<xxx>-data<xxx>.zip (Note: It will hang at rebooting to recovery in 5 seconds. Just take out the battery and boot it to recovery.)
Flash kk-kernel-05-01-TWRP.zip and reboot into recovery.
Click on Wipe, then Advanced Wipe.
Tick Internal Data, then click on Repair or Change File System.
Click on Change File System, click on EXT4, then swipe to confirm.
Click on Change File System again, click on exFAT, then swipe to confirm.
Go back to Advanced Wipe, tick on
Dalvik Cache
Cache
System
Data
emmc
Then swipe to wipe the 5 partitions.
Next, click on Install and install your preferred ROM.
Reboot and enjoy!
Method 2 If you're using 1.1 and above, steps 5-8 are not needed!
Download TWRP and the "parted" file from the bottom of the post.
Using a root browser (Root Browser recommended), place the parted file you have downloaded into /system/bin and set its permissions to "RWXR-XR-X".
Reboot into recovery and flash kk-kernel-05-01-TWRP.zip and reboot into recovery.
Flash the repartition-apps<xxx>-data<xxx>.zip
Click on Wipe, then Advanced Wipe.
Tick Internal Data, then click on Repair or Change File System.
Click on Change File System, click on EXT4, then swipe to confirm.
Click on Change File System again, click on exFAT, then swipe to confirm.
Go back to Advanced Wipe, tick on
Dalvik Cache
Cache
System
Data
emmc
Then swipe to wipe the 5 partitions.
Next, click on Install and install your preferred ROM.
Reboot and enjoy!
XDA:DevDB Information
Flashable zip to repartition the S2, Tool/Utility for the i9100
Contributors
Irwenzhao, smeet.somaiya
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2015-02-01
Beta Release Date: 2015-02-07
Created 2015-02-01
Last Updated 2015-06-26
Reserved
Changelog
1/2/2015
First release!
7/2/2015
Beta 1.01 released!
Changelogs:
Edited the script to not reboot into recovery. Not sure if it works, not an experienced Edify coder.
Click to expand...
Click to collapse
8/2/2015
Mirrors added. Mirrors for beta build will be added at a later date. Thanks for all the support!
20/3/2015
Untested bugfix for 1.0 is out! Please report the results. If it works I'll label it as stable.
28/3/2015
I have tested the fix and it works perfectly. it has been labeled as stable. Enjoy even more memory now! Sorry for the long wait!
Updated steps!
Method 2 added and necessary files uploaded!
25/6/2015
Update 1.1 is here! Major update MUST READ!
This update eliminates steps 6-9. After using the script, you can install a ROM DIRECTLY, how cool is that?
Downloads:
Repartition .zip files
1.1
reparitition1.1apps4.5gb-data9gb.zip
reparitition1.1apps7.3gb-data6gb.zip
1.0
repartition1.0-apps4.5gb_data9gb.zip (Mirror)
repartition1.0-apps7.3gb_data6gb.zip (Mirror)
Recoveries
TWRP (Mirror)
Philz (Mirror)
BETA/MISC
parted (Mirror) (for Method 2)
Reserved
Notes, Warnings and some Random Stuff (MUST READ)
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
I will be updating this thread (probably) weekly, but I will provide support through my mobile device.
DO NOT use this on stock ROMs. You will brick your device.
Follow the guide CAREFULLY. Please.
Hey there,
First response it seems. I'll have to try this later as I haven't had to repartition my S2 and it sounds a lot quicker than using say ODIN for the job. Anyone had any issues yet?
omallz said:
Hey there,
First response it seems. I'll have to try this later as I haven't had to repartition my S2 and it sounds a lot quicker than using say ODIN for the job. Anyone had any issues yet?
Click to expand...
Click to collapse
No issues on my device so far.
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
Yeah, it's would be great to have a zip-file for coming back to stock partition also!
Thanks.
Sergey2510 said:
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
Yeah, it's would be great to have a zip-file for coming back to stock partition also!
Thanks.
Click to expand...
Click to collapse
You'll have to do that using a .pit file. I think it's required to flash stock ROMs.
Repartition sizes
@Irwenzhao Could you please explain the attached files of Repartition sizes ?
I mean.. what will be the configuration and new sizes category wise ..
and Kindly share/upload another way to download the attached files too.. getting this error from Dropbox
"Error (509)
This account's public links are generating too much traffic and have been temporarily disabled! "
Thanks
adnan7khan said:
@Irwenzhao Could you please explain the attached files of Repartition sizes ?
I mean.. what will be the configuration and new sizes category wise ..
and Kindly share/upload another way to download the attached files too.. getting this error from Dropbox
"Error (509)
This account's public links are generating too much traffic and have been temporarily disabled! "
Thanks
Click to expand...
Click to collapse
Apps<xxgb> means that there'll be xxgb of space available to install apps and Data<xxgb> simply means that there'll be xxgb of space available for your music/documents/files.
Too much traffic? I wasn't expecting this many people! Shall provide a mirror ASAP.
Irwenzhao said:
Apps<xxgb> means that there'll be xxgb of space available to install apps and Data<xxgb> simply means that there'll be xxgb of space available for your music/documents/files.
Too much traffic? I wasn't expecting this many people! Shall provide a mirror ASAP.
Click to expand...
Click to collapse
Thanks already waiting
Mirrors up. Mirrors for beta build will be provided at a later date.
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
jeffrey2121 said:
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
Click to expand...
Click to collapse
Must be another typo I did while writing the script on my phone. Will correct it when I have the time.
Stock or Samy Based ROM *Custom Partitions*
@Irwenzhao is it possible to flash stock ROM or OMEGA v61 etc on the customized partitions ???
adnan7khan said:
@Irwenzhao is it possible to flash stock ROM or OMEGA v61 etc on the customized partitions ???
Click to expand...
Click to collapse
Stock ROM NO. Third Party Touchwiz ROM is a yes.
when I perform the last step for the 5 options on advanced wipe, I get wipe failed. What does that mean?
Irwenzhao said:
jeffrey2121 said:
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
Click to expand...
Click to collapse
Must be another typo I did while writing the script on my phone. Will correct it when I have the time.
Click to expand...
Click to collapse
can you please upload screenshot of storage after you update or correct the script
Dropbox had locked the files
It will work with the stock rom 4.1.2?
Thank you. After following your steps, my storage now changed. for device and USB. awesome work..
I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
ghost zip is for AOSP/CM based roms only!
MOTO 4.x.x is for KitKat Stock/Moto based roms only!
MOTO 5.x.x is for Lollipop Stock/Moto based roms only!
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So did u notice any performance difference? CM12.1 is smooth and fast as it is so I can't imagine our baby might be even faster
Edit: OK I missed that part about a bit smoother etc I will give it a try though and report back
chaoslimits said:
I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any CM12.x based kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
This is for CM12.1 (and possibly AOSP) based roms only.
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
View attachment 3399179 View attachment 3399180
Click to expand...
Click to collapse
Can I use this mod for stock Android 5.1 ?
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
This is for only Cm12.1 based rom or for aosp based roms
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Megatron007 said:
This is for only Cm12.1 based rom or for aosp based roms
Click to expand...
Click to collapse
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
where screenshots from?
I doubt this will work for stock 5.1.
Click to expand...
Click to collapse
not boot on stock 5.1
chaoslimits said:
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
Click to expand...
Click to collapse
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
Restore "boot" from your nandroid. I stated that this was for CM/AOSP roms only
Zorge.R said:
where screenshots from?
not boot on stock 5.1
Click to expand...
Click to collapse
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
chaoslimits said:
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
Click to expand...
Click to collapse
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
mastarifla said:
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
Click to expand...
Click to collapse
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
I understand that it has to optimize apps, but it wasn't making it that far, it was stuck on the boot logo like other people have mentioned
I changed it back to EXT4 and restored the BOOT partition, and its back to normal
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
md07 said:
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
Click to expand...
Click to collapse
Not sure what you're saying. OP doesn't say it works on stock yet. I asked someone with stock, who was willing to test to try it. Also all V2 are for moto firmware not for CM or AOSP roms.
I'll load stock when I am able but TWRP flash logs would help me figure it out quicker. I'm 99% sure the boot.img isn't being rebuilt due to rramdisk name inconsistencies.
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
md07 said:
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
Click to expand...
Click to collapse
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
chaoslimits said:
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
Click to expand...
Click to collapse
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
md07 said:
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
Click to expand...
Click to collapse
Great! Please post if you notice any performance changes. I'm curious if it's a placebo or if there's real improvement
Confirm, v3 worked on stock 5.1, thanks for work!
I think in order for this to work on stock 5.1, the kernel has to support fsfs, which so far there aren't any custom kernel available on 5.1. It does however work on CM roms perfectly well although to be perfectly honest I don't see any difference except for the hassle of reformatting the cache partition back to ext4 everytime I want to flash stock.
Sent from my Moto X