Database Users

[RECOVERY] JCSullins' Touchpad CWM6 v6.0.1.9 [2012-12-15] Edit: 1-31-13

DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet.
I take no responsibility or credit for the information.
The OP is primarily just quotes/links from JcSullins over at RootzWiki about his current CWM Recovery v 6.0.1.9.
This thread is NOT intended as a walk through of a first time install of Android/CM on the Touchpad. There are several threads on Xda and RootzWiki for that.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rootzwiki version of this thread
CONTENTS: (See RolandDeschain79's CWM6 Video)
Post 1 - JcSullins fixed CWM6, installable from Acme3 or Recovery. (Scroll down)
Post 2 - Background on file system corruption/inode errors with CWM5 and early TWRP recoveries.
Post 3 - Moboot 3.5 and Moboot 3.8 background and issues with TWRP recovery.
Post 4 - How to Clean Install / Dirty Install Rom Updates using CWM6 after first install with Acme3.
Post 5 - Basic info for using CWM Recovery.
Post 6 - CM9/CM10 First Time Install Links (not all inclusive)
NEW CWM6 Setting: Dedupe (.dup) vs .tar backups. See post 5 for how to change the setting and read Koush's Explanation.
The Fixed CWM6 (2012-12-15) From RootzWiki AcmeInstaller3 thread Post 204
JcSullins said:
OK, fixed CWM6 update package has been "officially released"
JcSullins CWM Recovery v6.0.1.9 Goo.im Download
(Mpg2 Edit: Use the 12/15/2012 version because the script is setup to work with BOTH AcmeInstaller AND a previously installed Recovery)
Any CWM users should upgrade to this version (including those who installed the CWM6 testing from a few days ago).
Note that it will remove any existing uImage.ClockworkMod or uImage.TWRP before install.
Click to expand...
Click to collapse
From Rootzwiki Post 209
jcsullins said:
You can install with whatever recovery you currently have installed.
The version number it shows is 6.0.1.9.
Two things to check that it is correct version:
1) Selecting "install zip from sideload" from main menu will give a "Not implemented." message
2) In the "Backup and Restore" menu, you will see "choose default backup format" at the bottom (not "choose backup format")
To make sure that all the filesystems are "clean", I would suggest doing the following after it is installed:
1) go to 'backup and restore', select 'backup' (might take a little while)
NOTE: DO NOT CONTINUE WITH NEXT STEPS IF BACKUP FAILS FOR SOME REASON
2) go to main menu and select "mounts and storage"
3) select "format /cache"
4) select "format /data"
5) select "format /system"
6) go to main main, then select "backup and restore", then select "restore" and select the backup you just made
Click to expand...
Click to collapse
Thread continues Rootzwiki Post 211
Mpgrimm2 said:
JcSullins, thanks for your previous post about cm6. I had just posted this earlier when i found this thread....
My understanding from your previous post is that a fresh format with the newer Cwm6 you just posted will correct any file system/inode corruption. Am I correct?
Click to expand...
Click to collapse
jcsullins said:
Yep, that's correct.
Click to expand...
Click to collapse

Background: File system corruption/inode errors
Background: File system corruption/inode errors from RootzWiki Acme3 thread Post 102
jcsullins said:
The "Fix Recovery" commit - http://review.cyanogenmod.org/26596 - fixed the building
of recovery as part of standard build process.
http://review.review.cyanogenmod.org/#/c/26704/ plus review.cyanogenmod.org/#/c/26705/
is the fix for the filesystem corruption. If you build a recovery for the Touchpad (or know
someone who does), please make sure you/they include these two commits.
Click to expand...
Click to collapse
jcsullins said:
This issue was initially discovered in the days of CM7 when I created scripts to resize the /data partition. Several people were having trouble
using them because the filesystems check (fsck) on /data would fail. After some testing, I discovered that ext4 filesystems created with make_ext4fs
from system/extras/ext4_utils would fail a "fsck -fn <block_dev>" check immediately after creation with numerous inode errors. As far as we knew,
there was never any "real" data corruption. The problem seemed to only surface when doing a fsck required for doing a filesystem resize.
The issue resurfaced when we needed to resize /system for jellybean installs. Luckily, with the jellybean version of ext4_utils, I was able to uncover
the real source of the problem (make_ext4fs assumed our kernel supported ext4_lazyinit when it doesn't) and the fix (see above).
I tested TWRP v2.3.1.0 for tenderloin and it had the issue. I contacted Dees_Troy about rebuilding a fixed TWRP. Turns out that the TWRP for
tenderloin is not built using the jellybean source, so the above fix would not apply. However, he changed TWRP to use mke2fs instead of make_ext4fs to work around the issue.
In short, TWRP v2.3.2.3 for tenderloin does not have the issue. It is the current version available from http://teamw.in/project/twrp2/75
NOTE: The link on that page says it's v2.3.1.0 when it's really v2.3.2.3 it downloads.
Click to expand...
Click to collapse

Moboot 3.5 and Moboot 3.8 background and issues with TWRP recovery.
By now you should also be using the latest CWM6 (12/15/12) or latest TWRP (2.3.3.0+) due to files system corruption issues. If you use Cwm6, I recommend Moboot 3.8 as well.
Twrp & Moboot 3.8 summary ...
Moboot 3.8 is still considered a "Testing" version but allows correct device S/n reporting to android OS needed for certain apps/games like Asphalt 7 etc. There are no issues reported (yet) when used with cwm6 because it has always used sdcard/clockworkmod/ for backups.
TWRP uses your device S/N (000000000 on Moboot 3.5) to create the folder where backups are stored, when you update to Moboot 3.8, TWRP will be looking at a new backup folder (ie 12345678) and won't see your previous TWRP backups. This is not an issue on all future backups (or if you started with Moboot 3.8). If needed you can use a file browser to move the old TWRP backup files to the new S/n folder and it has been reported to work.
(Note: I have not tried TWRP on the Touchpad, but I have used it on other devices).
JcSullins' Moboot 3.5 (Last stable version)
JcSullins' Moboot 3.8 (Testing version)
Moboot 3.8 has been setup to be flashed from either Acme3 or the installed recovery (ie CWM6).
For download links and more info, I created a dedicated thread: [INFO] on JcSullins' Moboot versions (& Version Poll)

Currently... If you have 'ever' installed (ie originally) with AcmeInstaller3 you don't have to use it or AcmeUninstaller anymore for regular installs or updates, you can use the latest Cwm6 or TWRP 2.3.3.0 using either the clean install or dirty install that I detail below. If you get your install all hosed up, Acme is still the best way to clean out all the garbage, by completely removing (AcmeUninstaller) and reinstalling android (AcmeInstaller3).
Using AcmeUninstaller/AcmeInstaller3 method works well and is considered the 'tried & true' method because of issues with prior recoveries.
Prior versions of Acme(1&2) created a system partition size of 300mb which was appropriate for cm7/9. Cm10 needs about 350mb or more so Acme3 is needed because it sets the size of partition to 400mb AND formats without all the corruption/inode errors that occurred when formatting with prior recoveries (cwm5 & TWRP 2.1.x) hence "tried & true".
Per JcSullins (See the OP) if you perform a format of the 3 partitions with Cwm6 (& implemented in TWRP 2.3.3.0) it will correct any corruption issues (so u don't need to rely on Acme for a correct format once it has set the correct partition size).
To summarize,
if your system partition was previously sized to 400mb with Acme3, then yes, formatting and flashing with CWM6 will work correctly.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note: Cwm6 12-15-2012 and Moboot 3.8 zips can be installed from your current recovery as well as being installed via Acme3. If you have already installed CM via Acme3 (provides 400mb system partition size needed for future installs of CM10), and have Moboot 3.8 (optional but recommended) and CWM6 (not optional, need this version or latest TWRP 2.3.3.0), then...
How to Clean Install / Dirty Install Rom Updates using CWM6 after first install with Acme3.
Step 1 (backup & format)
- Make a backup of your current CM9 install (See next post for details on using CWM6)
- Format/wipe ... system, data & cache (via Cwm6)
(ensures there isn't any file system corruption left over from prior recovery versions)
Step 2 Option 1 (clean install)
- flash CM9 and ICS Gapps zips via CWM6
(or CM10 & JB Gapps)
- Reboot, re-run CM setup
Step 2 Option 2 (Dirty install)
- "Backup and Restore" -> "Advanced Restore" -> select your CM9 backup -> "Restore data"
(advanced restore of cm9 data only)
- flash CM9 and Gapps zips via CWM6
(or CM10 & JB Gapps)
- Reboot, (should have all your apps and settings)
-------------------------------------------------------------------------------------------------------------------------
Some may disagree with me but I have never considered wiping Cache/Dalvik Cache a "Clean Install".
(using AcmeUninstall/AcmeInstaller3 would be a clean install too).
Clean Install vs Dirty Install Rom/Updates via Recovery: (After initial install with Acme3)
Generally, if your recovery is working right (each one has had issues at some point in it's development on every device I've had), the typical steps I've seen...
"Clean installing" a rom usually means to format the 3 basic partitions (& sometimes the /boot too depending on the rom/kernel script) and flash the rom as recommended by most devs to avoid issues (some rom installer scripts will handle the formatting for you, but shouldn't be assumed unless stated by the rom's developer. 9-14-13: See Attachment for example).
"Dirty Installing" a rom typically involves formatting the system & cache (sometimes only the cache :thumbdown: ) and flashing a rom to preserve /data partition with user apps & settings.
A cleaner method for this is to format all 3 partitions, flash rom, and restore only /data from a backup.
I've rarely seen dirty installs recommended by devs, but when I have seen them say it was "OK to try", it was done on the same rom/firmware base between incremental rom updates only (vs b/w CM7 - CM9 or CM9 - CM10, etc), and if you had a bug, you needed to go back and do a clean install before reporting it or expecting help. I will add that many people have been successful restoring their CM9 data after flashing CM10 & Gapps.

Basic CWM Recovery Info
CWM Recovery Backup, Format/Wipe, Restore, & Flash: ! MAKE SURE YOU READ THE NOTES IN THE OP AT THE TOP FIRST !
You CAN get into RECOVERY by: pressing [pwr] and selecting "boot ClockworkMod" from the bootloader (Moboot) when powered off.
You CAN get into RECOVERY by: holding [pwr], selecting "Reboot", then "Recovery" from within CM9/10.
Sdcard/clockworkmod/ (This is the folder CWM Recovery creates/uses.)
________________ /backup (recovery's backup of /system, /data, /boot.img, etc. are saved here by date. You can edit the filename.)
________________ /download (If you use CWM Rom Manager, it will place its downloads here. I've never used it.)
After the device has a Custom recovery, the recovery can be used to:
1) Flash/install .zip files:
- New/rooted kernels, including boot.img files (controls how the o.s. works with hardware)
- Roms (complete /system & /data file with kernel, custom apps, modded settings)
- Bootanimations (should be correct resolution)
- Other system improvements
- Themes (modify look of device/menus etc. Usually specific to each device (ie HP TP) & FW/Rom Base (ie CM9 vs CM10)
Must clear "dalvik cache" & may need to flash "deodexed template" or deodexed Rom, boot to system, before flashing each theme).
2) Make .tar(or dedup) backups of /system, /data, & /cache. Also backs up /boot ( boot.img or Kernel), and some versions may backup /recovery (recovery.img ), /wimax (wimax.img ) if available, that can be restored, usually together.
Note: Format the appropriate partition before restoring. (Usually format/wipe the first 3.)
It’s a good idea to make an initial backup right after you install the custom recovery. Then you can just format, restore the backup, if things get messed up.
3) Format/wipe the 3 main partitions and flash other partitions (depending on recovery version):
/system (o.s., system apps)
/data (google acct, app & phone settings, downloaded/installed apps)
/cache (used by o.s. to access info/apps, includes "/dalvik cache")
Android Partitions Explained
----------------------------------------------------------------------------------------------------------------------------------------
Controls:
[ Vol Up/Dwn ] = move or highlight selection
[ Home ] = select item/option
Note: On CWM Touch versions HW controls may still work.
How to Flash a Zip (Generally):
Place the .zip on the SDcard (or Sdcard/zip or similar folder of your choice)
Boot to recovery.
-> WIPE CACHE (habit of mine)
-> INSTALL ZIP FROM SD CARD -> CHOOSE ZIP FROM SDCARD
(navigate to where the zip is and select it)
-> REBOOT SYSTEM NOW (may need to "Go Back" to get to reboot option)
How to flash a rom (Generally):
- Make a backup in recovery first (/system, /data, /cache, etc.)
- Format/wipe the 3 partitions as appropriate.
(some Rom zips will do this for you, but may require a specific recovery coding such as “Edify” in CWM).
- Flash the Rom.zip (and any supplements like Gapps)
- Reboot to system, let it load, Verify functions
How to flash a theme (Geneally):
- Go to recovery, Wipe " Dalvik Cache ",
- Flash the " Stock Deodex Template" or Deodexed Rom (Depending on your version)
- Reboot to system, let it load, Verify functions
- Go To recovery, ADVANCED, Wipe "dalvik Cache"
- Flash the theme you want, ie GreenSteel.zip
- Reboot to system, let it load, Verify functions
Note: Anytime you wipe cache/dalvik cache it will take longer to boot the first time (ie Android is Updating).
Back up & Restore your file system with CWM recovery (DETAILED)
1 - (Enter Recovery)
-> BACKUP AND RESTORE -> BACKUP (This will separately backup: boot.img, /system, /data, /cache, wimax.img, etc)
Note: If you prefer the dedupe (.dup) backup format over .tar (default) and want to change the setting,
go to -> CHOOSE DEFAULT BACKUP FORMAT (before creating your backups)
* NOTE: you can stop here if you just want a backup*
2- (Format Manually through Recovery)
-> WIPE DATA/FACTORY RESET ( this will format the DATA & CACHE partitions for you in one shot )
-> MOUNTS AND STORAGE -> FORMAT SYSTEM
-> FORMAT DATA (Optionally there if needed, i.e. to restore only data partition)
-> FORMAT CACHE (Optionally there if needed)
4- (Restore Manually through Recovery)
-> BACKUP AND RESTORE -> CHOOSE YOUR BACKUP
-> RESTORE (This will restore all parts of the backup: /system, /data, & /cache, /boot [ boot.img or Kernel], /recovery [recovery.img], /wimax [wimax.img], SD-EXT if setup )
Note: If there is more than one, the numbers are a date/time stamp (ie: 2012-02-16.06.14.40 is Feb.16, 2012 at 6:14AM), so choose the appropriate one.
I typically change the name later, ie: "2012-02-16 CM9andApps".
(9-14-13 edit: Changing the name in newer CWM recoveries may create "MD5 checksum" errors and prevent a restore. Needs verified).
4.1- ADVANCED OPTION (Restore portions of backups individually, typically used to restore /data after Rom Update)
-> ADVANCED RESTORE -> CHOOSE YOUR BACKUP IMAGE ( /system, /data, /cache, /boot, /recovery, /wimax, SD-EXT)
-> RESTORE
5- (Reboot)
-> REBOOT SYSTEM NOW (may need to "Go Back" to get to reboot option)

CM9/CM10 First Time Install Links
CM9/CM10 First Time Install/Discussion threads
(XDA) Roland Deschain's How to install jcsullins CM10 Unofficial Build 20121216, with Sound, Camera & Microphone
(Also has Cm9 install info and zip packages with all current files.)
(Rootz) Nevertell's CM9 Install Directions in Post 19 of Newbie Questions thread
(@ NT, this is worthy of it's own thread or rolled into the OP of Travis' CM9 thread)
(Liliputing) How to install Android 4.0 or 4.1 on the HP TouchPad (CyanogenMod)
(This is a great guide and the one I originally used, but the linked install files for AcmeInstaller3, Cm9/10, Gapps, Moboot 3.8, & Cwm6 are out of date)
JcSullins' HpTouchpad Goo.im folder
(source for many current files: Cwm6, Moboot, Acme3, AcmeUninstaller, CM10.0 Experimental, etc)
Official CyanogenMod 9 HpTouchpad Downloads
(Click the "Nightly" link for now)
Latest Goo.im Google Apps Downloads
(Must match your CM base, ie CM9, CM10.0, CM10.1)
CM9/CM10 Support/Discussion Threads
(Rootz) Travisross69's [ROM] Official CyanogenMod 9 Nightly Build Discussion
(Rootz) Roland Deschain's How to install jcsullins CM10 Unofficial Build 20121216, with Sound, Camera & Microphone
(Xda) Imfloflo's [NIGHTLY] [ROM] CyanogenMod 9
(Xda) BigSimon's [ROM] [12/16] Unofficial CM10 Preview by Jcsullins Now with sound+camera

mpgrimm2 said:
one more post for me
Click to expand...
Click to collapse
What is this all about ?

Menthe is MIA on his JcSullins CWM6 thread since Dec 7th. I requested (Dec 20th) to take over the thread but the Mods recommended I just create a new one and they would merge it. I waited long enough and I think people may find the info useful if they don't want to use a pc/Acme3 to do all their rom updates/nightly's. I will duplicate this over at Rootz once I am all setup.

this is a lot of useful info. thanks for putting it together

Re: [RECOVERY] JCSullins' Touchpad CWM6 Recovery v6.0.1.9 [2012-12-15]
mpgrimm2 said:
Menthe is MIA on his JcSullins CWM6 thread since Dec 7th. I requested (Dec 20th) to take over the thread but the Mods recommended I just create a new one and they would merge it. I waited long enough and I think people may find the info useful if they don't want to use a pc/Acme3 to do all their rom updates/nightly's. I will duplicate this over at Rootz once I am all setup.
Click to expand...
Click to collapse
I'm sorry I'm a little lost I am new to this thread but I am NOT new to the touchpad nor xD a when did you have to use a computer to update CyanogenMod I didn't know people needed to do that because I just do it right through my touchpad. I am so glad I came to the threads because I thought only cm mod was available. Now only if I port gay bi sorcery over here this would be crazy it is the best rom out there it has more tweaks than every other ROM combined literally. It's so large and crazy it ca there is a central server for a lot of the mods an tweaks because it would be too large
Sent from my cm_tenderloin using xda premium

Crwolv said:
I'm sorry I'm a little lost I am new to this thread but I am NOT new to the touchpad nor xD a when did you have to use a computer to update CyanogenMod I didn't know people needed to do that because I just do it right through my touchpad. I am so glad I came to the threads because I thought only cm mod was available. Now only if I port gay bi sorcery over here this would be crazy it is the best rom out there it has more tweaks than every other ROM combined literally. It's so large and crazy it ca there is a central server for a lot of the mods an tweaks because it would be too large
Click to expand...
Click to collapse
Post 2 & 4 give a basic background on the issue. Basically, early recoveries were creating file system corruption when formatting partitions. It didn't always produce noticeable problems, but it was there. The workaround was to use AcmeInstaller3 from a PC for installs/updates and then restore a backup from within Recovery. Acme3 reformats the partitions correctly and would list/scroll all the file system errors before it fixed them (sometimes taking 15 - 20 mins to finish). Jc's CWM6 fixed the problem so it's ok again to do everything from recovery.
Remember you move to CM10, your system partition size needs to be @ 400mb (done initially with Acme3).
I'm not sure what the rest of your post is about.

Added Roland's Video and link to Koush's explanation of .dup vs .tar backup settings.

Just for grins and giggles (and with limited script reading skills), I decided to have a look at the installer script in TP CM9/10 zip package and found the following.
Code:
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/store/cm-system", "0");
mount("ext4", "EMMC", "/dev/store/cm-system", "/system");
This confirms the fact that the CM9/10 zip will format ONLY the system partition for you during install, so if u want a clean install all that is needed (for CM9/10, not necessarily all roms) is to do a "wipe data/factory reset" (formats /data & /cache) and flash the zip.
So if u are just upgrading from a prior CM "nightly" to the current one, you can do a simpler "dirty install" by wiping/formatting cache and flashing the CM zip to retain your data (this assumes u have no file system corruption from earlier recoveries on your data partition).
I still stand on my general steps for "clean" & "dirty" installs via recovery since there isn't a guarantee that the rom developer setup the installer to do any formatting for you like CM9/10 does. The extra format shouldn't hurt in the long run (before the TP is obsolete anyway).
Sent from my "Up all night, sleep all day" HP CM9 Touchpad

sorry, it's a badly written post
1. Have to include a changelog
2. whether it's beneficial...

stayfidz said:
sorry, it's a badly written post
1. Have to include a changelog
2. whether it's beneficial...
Click to expand...
Click to collapse
PLease explain this statement better.
Are you referring to my OP, the previous post above yours, the whole thread, etc. Did you read through the thread and the "background" section to know what was going on with the TP recoveries before JcSullins' fixed it (not me or my work) or just look for a download link?

mpgrimm2 said:
PLease explain this statement better.
Are you referring to my OP, the previous post above yours, the whole thread, etc. Did you read through the thread and the "background" section to know what was going on with the TP recoveries before JcSullins' fixed it (not me or my work) or just look for a download link?
Click to expand...
Click to collapse
Hi, to the whole post, we're not all geeks by nature
1. By the way, what this recovery fixes, adds?
thanks again

You don't have to be a geek to "read and understand what you are doing first" (first statement in the op) before modifying your device. All users are expected to read and learn even a little bit. No one is going to spoon feed it to you.
Perhaps I am wrong, but it sounds like you are not bothering to read through posts 1 & 2. This thread isn't hundreds or thousands of posts long. There is even a link to a video by Roland Deschain about this Cwm6 next to the "contents" and an explanation on .dup vs .tar backups by Koush after the "contents".
Myself and others will help, but you have to be willing to roll up your sleeves and read a bit then come back with a question if u still actually have one.
Sent from my "Up all night, Sleep all day" EVO3D!

This was informative. I had no idea that there was a file corruption problem with older recoveries. That would explain a lot of issues I had. Just completely wiped my Touchpad back to factory (webOS default) then used ACME 3 to get CM10 back on with CWM6. Hope that solves my random issues. Thanks!

All the goo.im links are dead. Any other way to get this?

buddhag33k said:
All the goo.im links are dead. Any other way to get this?
Click to expand...
Click to collapse
Yes, head over to RolandDeschain's thread and download one of the cminstall.zip packages, its included in there.
[ROM GUIDE] How to install Jcsullins CM10/CM10.1 Unofficial Builds
Edit: Goo.im appears to be doing updates. Some of the files are back.
.

[MOD][APP][UPDATED][AOSP/CM/MIUI/STOCK] Dual Boot for SGSA || No Ext SD Card

Dual Boot for SGSA​
So many devices are getting Dual Boot capability nowadays.So i decided to do same for our beloved SGSA.
EDIT : Guide Updated. Using slow sdcard as /system and /data was bad idea. Now secondary ROM work at same speed as primary ROM since we aren't using external SD card anymore
Read first three posts carefully before doing anything
​
Highlights:
No lags, bugs.Both ROMs works almost same
Stable. Booting of ROM is based on kernel. So as long as you stay on a kernel it'll keep booting ROM for which it is designed without interference with another ROM.
ROM can be switched by changing Kernel.
Stock ROM fully supported. Now you can feel speed of CM ROM with stability of stock ROM
Click to expand...
Click to collapse
How to use this:
Well, steps are quite easy.Just follow them one by one and you won't get any troubles.But please follow steps one by one, don't take shortcuts.
On PC extract ROM which you want to install as secondary ROM.
You'll get following files/folders there : META-INF, system, boot.img
Delete META-INF and boot.img
Download appropriate META-INF_*.zip from downloads section.Extract it and move extracted META-INF folder to location from where we deleted META-INF.
Navigate to /system folder and move folder named app to parent folder (i.e. if app folder is located at C:\blah\system\app then move it to C:\blah\app)
Select three folders (META-INF, system, app) and compress them to zip format.Push this file to device.
All above steps are mentioned in below video
Download appropriate Kernel from Downloads sections.
Flash that kernel using Universal Kernel Flash Tool or by writing in terminal dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
Power off your device
Now reboot into recovery by holding VOL UP + HOME + POWER (don't take shortcut here )
Ignore any warnings recovery shows.
Install the zip file which you pushed before as you install normally (Do not use Wipe options)
Download appropriate GAPPS package from download section (Do not install normal gapps.To know reason, read third post)
Reboot it.That's all (Keep in mind, first boot always takes long time)
If WiFi don't work on secondary ROM then flash appropriate modules from Downloads section
Read "Things to keep in mind" in third post.
Click to expand...
Click to collapse
How to switch ROM:
Flash kernels provided here to boot secondary ROM.
Flash native kernel (which comes with ROM) to boot primary ROM. (If you're using CM based primary ROM then take backup of stock CM kernel before flashing another kernel.)
Click to expand...
Click to collapse
How to change ROM:
Boot up your primary ROM.
Navigate to /data
Delete folder : /data/secondary_data
Now flash secondary Kernel and flash secondary ROM as you would.
or you can use my App for doing this stuff...
Click to expand...
Click to collapse
Using DualBoot App:
After installing secondary ROM as mentioned above, you can use my Dual Boot app to switch easily between ROMs. Additionally you can also use it for other options like sharing installed apps, factory reset secondary ROM etc. It will automatically download required kernel (Read third post). App is easy to use, just install it as Normal apk. You can also share this app with secondary ROM as mentioned below.
Wipe data/factory Reset - Factory reset secondary ROM
Share Apps with Primary - Share all apps of primary ROM with secondary ROM. This will reduce space used by secondary ROM. Use this option with CAUTION because some apps like Play store can FC. So it is better to use custom share apps option.
Revert Share Apps with Primary - This will remove all installed apps of secondary ROM
Custom Share Apps - Best way to share installed apps on primary with secondary ROM. Share as much apps as possible to reduce storage usage by secondary ROM.
Clean UP - Removes all files used in DualBoot mode
And more to come...
{
"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
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
Technical info:
--> Mounted /dev/block/mmcblk0p4 as /system
--> Since it is smaller (300 MB) in size we're symlinking /system/app folder of secondary rom to /data/app
--> Using /data partition for both /data & /cache of secondary ROM
Click to expand...
Click to collapse
Future Plans:
An App so things become more easy (done)
Kexec support in kernel (WIP)
Click to expand...
Click to collapse
Sources:
Kernel Sources : Checkout TeamCanjica's repo
DualBoot App : Github
Click to expand...
Click to collapse
I'm writing an app for this.Once it is completed it would be much easier to do this thing
As usual, i don't take any responsibility of bricked devices, nuclear wars etc...​

Downloads & Changelog
Downloads:
EDIT:
Since Dev-Host removed all my files i've re uploaded them to mediafire (Link to folder below). Since all files are removed from my account DualBoot app won't be able to download kernels. So manually download them and put them on sd card as instructed.
META-INF:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK) || Liquid Smooth 3.0
Click to expand...
Click to collapse
Kernel:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK)
Click to expand...
Click to collapse
Modules:
CM 11
Click to expand...
Click to collapse
GAPPS:
CM 10.1 || CM 10.2 || CM 11
Click to expand...
Click to collapse
Download META_INF, Kernels, GApps:
Mediafire Folder
Click to expand...
Click to collapse
DualBoot Application:
DualBoot v1.22
Click to expand...
Click to collapse
Changelog:
27/04/14 ---> Fixed FC problem on CM11, Kernel with OC support (same as TC's last release)
21/02/14 ---> Liquid Smooth 3.0 Support
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI v5 Support
21/01/14 ---> DualBoot App released, Updated META-INF folder for latest CM10.2 to fix errors
08/01/14 ---> Fixed bug with CM11 which was preventing it from booting second time
06/01/14 ---> CM11 support
04/01/14 ---> No need for external SD card.Both ROMs work at same speed, no more lagginess
11/11/13 ---> Initial Release
Click to expand...
Click to collapse
DualBoot App Changelog:
27/04/14 ---> Unsupported device problem fixed, Updated all kernel links
12/02/14 ---> Fixed AOSP, Removed app folder share (use custom app share instead)
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI support. Allows user to flash unknown kernel to use any ROM as Primary ROM
21/01/14 ---> Initial Release
Click to expand...
Click to collapse

Pros, cons, Tips, Future Plans
FAQs:
Q. How can i factory reset second ROM?
A. Boot into primary ROM and go to /data/secondary_data using any explorer and delete following folders : cache, data
Click to expand...
Click to collapse
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder.Now delete all contents of /cache folder.
Click to expand...
Click to collapse
Q. WiFi is not working on secondary ROM. What should i do?
A. Boot into secondary ROM's recovery and flash appropriate modules from downloads section
Click to expand...
Click to collapse
Things to keep in mind:
Wipe/data Factory reset from primary ROM will remove secondary ROM also.
Do not wipe cache partition after installing this mod (for both primary & secondary ROMs).
Don't touch anything other than install zip ( like wipe data/cache etc because they'll lead to unexpected results ) when using secondary ROM's recovery.
We're running out of space for /system partition in secondary ROM so please don't keep flashing random tweaks, mods which put files on /system partition.If it is emergency then use /preload partition and symlink them manually.
Do not install GAPPS for secondary ROM.Use only which i provided.
When CM based ROM is installed as secondary ROM then by default swap functionality is disabled on /preload (which TeamCanjica enabled).So stock ROM as primary ROM is compatible.
Ignore any warnings shown by secondary recovery.If you get any error then contact me.
Provided GAPPS are not full gapps it'll only install Play Store s that you can install other apps from market.
We have 2GB space in /data partition.I've been using this device for 9 months and it never took more than 1GB space on /data.But still if you're finding less storage then move some apps to sdcard.Still if you need more then contact me, we'll move some more files.
If you want to dual boot CM & stock ROM then it is necessary to install stock as primary because they're huge to be included on /cache partition.Although it is not impossible, if you're expert there, then you can create symlinks to make it work.But i won't support that way.So secondary ROM must be CM based.
Backup/Restore function won't work with secondary ROM
When wiping primary rom, it is impossible to save secondary rom unless you made backup.
Even though Dual Boot app downloads kernel automatically, it is advised that you download required kernels & manually and put them in proper folder ({internalsdcard}/DualBoot/) to avoid bad & corrupt downloads. In case if this happens & you phone don't boot up, don't worry, just flash stock kernel with odin & everything will be fine.
Click to expand...
Click to collapse
How to add Support for Unsupported ROM:
This tutorial will help you to add support for those ROMs which are based on already supported ROMs (like CM11, CM10.2 etc). This tutorial will teach you to create META-INF folder for particular ROM to avoid status 7 error. Please follow it carefully
Open META-INF\com\google\android\updater-script
Find and delete following code/ same code
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
Now find
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
& replace /dev/block/mmcblk0p3 with /dev/block/mmcblk0p4
Search for package_extract_dir("system", "/system"); & add this code after it
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/primary_data");
run_program("/sbin/busybox", "mkdir", "-p", "/primary_data/secondary_data/system");
delete_recursive("/primary_data/secondary_data/system");
package_extract_dir("app", "/primary_data/secondary_data/system");
symlink("/primary_data/secondary_data/system", "/system/app");
At the end of the script remove package_extract_file("boot.img", "/dev/block/mmcblk0p15"); or anything related to kernel flashing like write_raw_image etc.
Click to expand...
Click to collapse

Awesome...:good:
Wanted to try it but I have a 2gb memory card...
So I will have to Wait till my new memory card arrives:fingers-crossed:

i have a class 10 sd card..i ll try this as soon as i can..just a thing...AWESOME
Sent from my GT-I9070 using XDA Premium 4 mobile app

tried but not work. it just boot direct to recovery

wmfaiz said:
tried but not work. it just boot direct to recovery
Click to expand...
Click to collapse
Yep because you messed up with our param drivers.As i told before don't use any command like reboot recovery and don't use 4 way reboot (if your ROM supports) to enter recovery.This will keep you throwing into recovery.The solution is flash primary ROM's kernel then reboot normally.Use UKF to flash secondary kernel.Now power off your device and then use Hardware keys to enter recovery or if you've already installed secondary ROM then power on normally.

Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app

frapeti said:
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Thanks.I'm waiting for next build because last build has lzma compressed zImage.

dual boot?
cool...
I was used dual boot on my old device Galaxy Tab 2, very useful for testing a new rom before become it that rom as primary rom for daily use
great work

Update
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:

Many thanks for your hardwork man! For achieving dual boot on our device and keep on simplify the method of doing it. It is also happy to see that there is another app under developing to make things more easier, i will definitely try this out once i finished my exam!

Thanks a lot man :thumbup:
I will use it when you will add CM 11 compatibility.

BOOTMGR said:
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Click to expand...
Click to collapse
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???

<O.T>
+1 to each thing in above post....
let me again tell u that you r really really AWESOME :angel: :laugh:
btw idea of debloating HJ is good ......personally i'm using heavily debloated HJ without any feature loss

BOOTMGR said:
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
I assume Primary ROM must be 4.0 or higher and not GB?

Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space

anantttt said:
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
Click to expand...
Click to collapse
Yeah it can be fitted as secondary ROM by debloating.But still some users will ask for some features.We can even use symlinks and can place it as secondary ROM without debloating it but it'll raise complexities.So it is better to use it as secondary ROM.
Odexing and placing them on /preload i also nice idead.But still i'll prefer to use it as primary ROM...
BTW,HarshJelly seems better than BOOTMGRjelly...:silly:
purplepizza said:
I assume Primary ROM must be 4.0 or higher and not GB?
Click to expand...
Click to collapse
Yeah.No support for GB (i'll think about it.If there won't be much difference (except baseband) between GB and JB we can also do it.)
darcik said:
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
Click to expand...
Click to collapse
Yesterday @Sami Kabir asked same question on FB group.Here is the answer.
Only apps can be shared between both ROMs not their data.The reason is that data of system apps and normal data apps both are stored under same folder (/data/data).So can't we share this folder? answer is no because namespace conflicts will arise there (Ex. package name for phone app is com.android.phone.It'll remain same for all android versions.It is possible that use have installed both ROMs of different API level.So if one phone app stores its data under /data/data then other won't be able to read it and you'll get FC)
Although it is possible to share apps between two apps.When i'll complete app, i'll provide an option for that....:good:

Cache partition
FAQs:
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder
Click to expand...
Click to collapse
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.

CM11 Support
darcik said:
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
Click to expand...
Click to collapse
Yeah i forgot to write, you also need to delete contents of /cache folder or format cache partition.
That partition is like placebo.It is only used when upgrading android (that means generating dalvik cache (actually that partition was used to store dalvik cache but later on dalvik cache was also moved to /data partition so its useless now except time of generation of dalvik cache)
@all:
Added CM11 support.
Links are up.
Method remains same.
I've checked way to share apps between ROMs (and thus storage use will be much less).
I'll let user to choose whether to share apps or not which will be possible through DualBoot app.

Klte cm12.1 + twrp + f2fs?

Hi guys,
lateley I saw F2FS support in Nightlies changelog of CM12.1. Im using latest TWRP + CM12.1. So.. how to get there?
Do I need a custom kernel? What if CM13 will be released do I have to go back to EXT4 before and will this work without problems?
Do I need to fully wipe all my data or can I just convert without data loss?
Help appreciated!
Kind regards!
[Edit: ]
Should I convert every partition or just cache + system?

Looking at http://review.cyanogenmod.org/#/c/109990/4/rootdir/etc/fstab.qcom, F2FS is only supported for the data and cache partition.
CM12.1 for klte/klteduos supports F2FS, TWRP has options under "wipe" -> "advanced wipe" -> "fs options" -> "change fs" to format the partitions to use F2FS.
You should make a full backup and then change the fs type. Dont't forget to backup your internal sdcard as this is not included in the TWRP backup.
There's a nice howto: http://forum.xda-developers.com/xpe...rial-migrate-filesystem-to-f2fs-ext4-t3004755
Good luck!

Thank you very much!
I've made a backup of data and cache and tried to convert but TWRP won't let me change to F2FS as the option is missing. Do I need some custom TRWP or did I miss something as I am using the latest version. Also, if I change the data partition my userspace won't be touched, right? So the backup of my userspace which I can see when I plug my phone to PC is not necessary, just for caution, right?
Thanks in advance!
[Edit: ]
If CM12.1 has the F2FS options, the kernel should automatically support the new file system? In your link they say you need TWRP with mkfs.f2fs support, so I need to change something somehow?

ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/showthread.php?t=2777835).
Just changed my cache partition with it.
BTW, if you followed the howto, you should have read that you can also download the provided mkfs.f2fs and push it to the original TWRP recovery.
I think, you don't read and search carefully enough. All your questions are answered in this forum, you just need to invest some time.

meiser said:
ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/showthread.php?t=2777835).
Just changed my cache partition with it.
BTW, if you followed the howto, you should have read that you can also download the provided mkfs.f2fs and push it to the original TWRP recovery.
I think, you don't read and search carefully enough. All your questions are answered in this forum, you just need to invest some time.
Click to expand...
Click to collapse
Thank you, again!
I used the search function before, the problem ist that it's very specific as there are dozens of kernel and custom roms and I wanted to be on the save side as I really need my mobile. But you are right, the mkfs.f2fs problem should have been solved by reading better. So this is now solved!
Kind regards

ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/show....php?t=2777835)
Click to expand...
Click to collapse
As i see it can't format internal storage. Is there any solution?

[s5360][compiling kernel] in cwm can't format /system, /data... etc

Hello, today I tried to compile my own kernel, and everything went nicely, packed zimage and ramdisk to boot.img, but when you try to format the partition / system / data and / cache error pops up (picture 1).
And now what is the problem, whether in the config file? or just bad compiling a kernel?
PS: Here I give a configuration file pastebin*com/raw.php?i=UbBVsC8L
(picture 1)
hosting*danio*ml/1449124072.jpg

[TOOL][SCRIPT][A520X|A720X] Repartition tool for treble support

Repartition tool for A5 and A7 2017
Disclaimer
Code:
I am NOT responsible for bricked devices or any damage that may happen to your device.
Repartitioning is a dangerous process and may brick your device in the worst case.
Features
This script will set 64MB for your /cache partition and ~4.6GB for your /system partition (The size of /system may be smaller or bigger depending on which variation of A5 and A7 is used)
The script will create a new partition called "vendor" with a size of 300MB
Only /system and /cache will be deleted during the flashing process, your /data partition keeps untouched
Flashing the script for a second time after already having it flashed will delete the /vendor partition and restore your stock partitions
You will still be able to install any recent ROM (Note that A720S may be unable to install any recent ROM. Contact me if you have problems)
TWRP, SHRP and Orangefox are supported
Installation
Make a backup of all your partitions first in case something goes wrong. Repartitioning is a dangerous process!
Make sure to have the latest version of TWRP/SHRP/Orangefox installed before installing this script.
Download the Repartitioner from post #2
If you only want to patch your recovery but already have the /vendor partition, download the RecoveryPatch from post #2
Flash the installer zip and wait until it is finished. It will add the necessary partition, patch your recovery and automatically reboot you to recovery if the installation is successful.
After reboot, make sure that /system, /cache and /vendor are mountable. If not, format them. (See a How-To in FAQ in post #3)
Congratulations, your device now supports treble!
Downloads
Find them in post #2
Support and FAQ
Telegram Group
FAQ (Frequently asked questions)
Credits
Me for the time I spent on this
@corsicanu for his template script
@Reverant for the original repartition script
@osm0sis for AnyKernel
Telegram users for testing
XDA:DevDB Information
[TOOL][SCRIPT][A520X|A720X] Repartition tool for treble support, Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
Simon1511
Version Information
Status: Stable
Created 2020-09-08
Last Updated 2020-09-09

Downloads
v1.2
Repartitioner: Google Drive | Androidfilehost (Will resize your partitions AND patch recovery)
RecoveryPatcher: Google Drive | Androidfilehost(Will ONLY patch your recovery for treble support. Flash this if you upgrade from an older version.)
Changelog
Spoiler
v1.2
Spoiler
Removed TWRP version check
Added support for SHRP and Orangefox
v1.1
Spoiler
Fixed a typo that prevented the script from creating new partitions on A720F and korean A5 variants
v1.0
Spoiler
Initial release

Reserved
FAQ (Frequently asked questions)
I cant mount /system, /cache or/and /vendor. What do I do?
->In recovery, go to Wipe, Advanced Wipe, select the partition you have problems with and tap "Repair or Change File System". Choose "Change File System", choose EXT4 and confirm the process. Reboot to recovery again to complete the process.This may be slightly different depending on which recovery you are using.
Restoring my /system backup always fails! What do I do?
->This seems to be a general TWRP problem. To fix, wipe /system, reboot to recovery, install the ROMs zip you had installed before, reboot to recovery again and restore your backup.
I have an A720S and cant install any recent ROM! Why?
->A720S has the smallest /system partition of all A5 and A7 variants and Lineage and every other ROM currently has its stock partition sizes set. Just flash the repartition ZIP again to revert the changes and contact me so we can resolve this problem.
How do I upgrade from an older version to the latest?
->The latest version doesn't change anything in terms of partition size. Therefore, you don't need to upgrade unless you have any issues.
How do I patch my recovery to support treble?
->Download the "RecoveryPatch" ZIP from the download section above and flash it in recovery. It will patch your recovery to support treble. If you want to switch to non-treble recovery, flash the recovery IMG/ZIP or the RecoveryPatch ZIP again.

reserved

in a720f can't format or mount /system, /cache or/and /vendor
says unable to wipe them
error changing file system
After second time installing "repartitioner-v1.0-a57y17lte.zip" reverse process fails to restore /cache partition to first /cache

matkali said:
in a720f can't format or mount /system, /cache or/and /vendor
says unable to wipe them
error changing file system
After second time installing "repartitioner-v1.0-a57y17lte.zip" reverse process fails to restore /cache partition to first /cache
Click to expand...
Click to collapse
Did you have TWRP 3.4 installed before installing the repartition script?
If not, thats likely to be the cause.
Also, dont forget to format /system, /vendor and /cache after installation.

Simon1511 said:
Did you have TWRP 3.4 installed before installing the repartition script?
If not, thats likely to be the cause.
Also, dont forget to format /system, /vendor and /cache after installation.
Click to expand...
Click to collapse
yes I do all of them

matkali said:
in a720f can't format or mount /system, /cache or/and /vendor
says unable to wipe them
error changing file system
After second time installing "repartitioner-v1.0-a57y17lte.zip" reverse process fails to restore /cache partition to first /cache
Click to expand...
Click to collapse
Yeah same issue here,. A720F

deleted

Updated the script to fix A720F and korean A5 support.
Sorry for the circumstances.
Downloads can be found in post #2

UPDATE
repartitioner v1.2: Google Drive | Androidfilehost (Will resize your partitions and patch recovery)
RecoveryPatcher: Google Drive | Androidfilehost (Will ONLY patch your recovery for treble support)
Changelog
Removed TWRP version check
Added support for SHRP and Orangefox