Database Develop

[RECOVERY]Unofficial ClockworkMod Recovery v4.0.0.2(WIP)

Hi
Clockwork Recovery v 4.0.0.2 for Galaxy Ace
v2:
- working nandroid backup/restore!
For now i've disabled backup/restore of boot and recovery partitions. Restore of DATA, CACHE and SYSTEM is working fine.
If you have JTAG and want to test restore of boot/recovery please PM me!.
- it's based on KPH firmware + root in adb (both in normal and recovery mode)
v1:
Tested:
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens). It'll be fixed - thanks to tj_style!!
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested!!!.
How to flash (v2):
1. Download file from here .
2. flash it as PDA with odin
Mirrors:
Multiupload (thanks to peeter123)
I've removed recovery.zip - it was recovery.img packed with zip, not update for apply using stock recovery.
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.

Where did you get this?

Lovetz said:
Where did you get this?
Click to expand...
Click to collapse
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.

PabloPL said:
I've build it from source using this tutorial Porting clockwork recovery to new device, with some changes. Then i've mixed recovery.img with those from samsung firmware.
Click to expand...
Click to collapse
You are elite, dude!;-) (Hackers)

This opens so many oppertunites to our Ace CyanogenMod being one of them. Have you got any further with these bugs? This is great. Thank you
Sent from my GT-S5830 using XDA App

awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!

I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua

PabloPL said:
Hi
Today i managed to run the newest Clockwork Recovery on my Galaxy Ace. It has some problem with graphics (as you can see on screenshots).
I've tested following options (and for me they are working):
- wipe Data/Factory reset
- wipe cache partition
- some options under advanced menu (to wipe)
- install zip from SDCard (tested on some file from UOT kitchen)
- reboot recovery
- mount USB storage (and other mount options) Better not try to format partitions from recovery yet - it could format them to ext4 for which we probably not have yet support in kernel.
Know bugs:
- poweroff sems to reboot phone
- problem with graphics (probably framebuffer is set to 24 or 32 bpp mode. There is also missing double buffer support in framebuffer - thats why we have 2 recovery screens)
I've also managed to create nandroid backup of all partitions (boot,recovery,data and system) but not tried yet to restore them.
Phone info
In recovery mode (sorry for terrible image quality)
I've attached packed recovery.img. it's based on KPH firmware + root in adb (in both boot and recovery mode) + su binary.
Remember, I am not reponsible if you brick your phone. You're flashing this on your own risk.Not all options are tested.
How to flash:
1. take KPH firmware
2. extract CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
- tar xvf CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
3. replace recovery.img with attached file
4. pack it back
- tar -H ustar -c boot.img recovery.img data.rfs system.rfs >ODIN_FILE.tar
- md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar
- mv ODIN_FILE.tar ODIN_FILE.tar.md5
5. flash it with odin
To move in recovery:
- Volume up/down to move.
- Home (center key) to select item.
- Back to move back.
Click to expand...
Click to collapse
GREAT JOB MAN!
Go ahead, you are on it!!!
CHEERS!

The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App

kills999 said:
awesome work!!!....it would be legendary if NANDROID backup works!!!!NO more bricking worries!!!
Click to expand...
Click to collapse
For now i've tested it only with creating backup of boot/recovery/data/system partitions and it generated without errors.
Jekle_Ace said:
The main thing is to get the install update zip feature as that really is the reason we use ClockworkMod and what we wanted it for.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine

PabloPL said:
I've tested installing update from zip on some theme from OUT Kitchen and it worked fine
Click to expand...
Click to collapse
Can you upload ready-to-flash KPH file with CWM integrated?

Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App

tj_style said:
I've successfully to porting the Clockworkmod Recovery too for Galaxy mini.
The problem with framebuffer it's been fixed too.
View attachment 623281
I just have the problem with backup & restore, also with flashing full rom from zip.
Are you get success with backup and restore?
since galaxy ace / mini is using different tool for read / write the bml partition. not like SGS that can using redbend_ua
Click to expand...
Click to collapse
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.

Lovetz said:
Can you upload ready-to-flash KPH file with CWM integrated?
Click to expand...
Click to collapse
I have PDA file for odin with it, but i've messed something with Superuser.apk and you must install it by hand (only Superuser.apk, su binnaries are fine). Maybe when i'll have some free time - i'm working and studying (now have exams) - i'll upload it, if someone won't do this before .
Jekle_Ace said:
Wiping partitions /system /data etc is very important without wiping it can cause many problems as I've done that many times with my ZTE Blade. But still I appriciate this greatly
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
For now i've tested wipe only on following options (and it worked fine):
- battery stats
- cache
- data (factory reset)
Sorry for double-postings

PabloPL said:
Could You share what changed did you made to fix framebuffer problems ?? For now i've made some change found here to get 2 screens in recovery (was getting 4 before).
About backup, like i wrote, tested only creating. I have to set up correct size of all partitions in BoardConfig etc, Ace is my primary phone, so i don't want to brick it.
I've made some changes to recovery source (look into bmlutils/bmlutils.c - there are hardcoded paths to boot and recovery partitions, which on Ace are differend than those in code).
I've also used custom recovery_ui.c with custom key mapping.
Click to expand...
Click to collapse
Sure, You can see on my github soon. I'm not yet pushing to my github now.
because the project of Cyanogenmod port and Clockworkmod port for Galaxy Mini is pending now until i have the Galaxy mini back, you can see the progress in this thread.
I've add the double buffering to clockworkmod source, since Galaxy mini kernel doesn't suppot that.
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.

thx dude, i really need this.

tj_style said:
I hope we can colaborate to make clockworkmod is fully working, because the Galaxy Mini, Ace, Gio and Fit is using similiar environtment.
Click to expand...
Click to collapse
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.

PabloPL said:
It would be nice. As i see You have far more progress.
In my opinion it would be better to make it with only minimal changes (or even without) to android source (recovery etc), to keep it in synch with "mainline". Closer we keep(and less changes), longer we could have support.
Also getting rid of BML and use MTD (when we have sources for 2.3.4) would be great.
Click to expand...
Click to collapse
Yup, i'm waiting to someone borrowing the galaxy mini to me and also waiting samsung to get released the 2.6.35.7 kernel source.

The source will come after 2.3 is offically released but we may be waiting a few weeks for it
Sent from my GT-S5830 using XDA App

Great work mate. Maybe you can work together with nprussel who is also trying to run cwm on g ace
@formatting partitions, there is indeed no support for ext4 in kernel
Sent from my GT-S5830 using XDA App

Atrix Boot Emporium [V2.0 Released! 08 Nov 2012]

Welcome to... Atrix Boot Emporium!​
Powered by AROMA Installer with custom ICS theme!​
Test out different kernels for the same ROM or boot a second ROM hosted on SD card in a sleek, menu-driven environment. No need for fastboot or heavy installers.
Easy to flash via CWM, but... “I will let YOU DECIDE whether to wipe /data !” See Notes below.
Atrix-Boot-Emporium-V2.0-signed.zip: http://www.mediafire.com/?azassaimbbgmnxd
Checksum: ed9649db8b2990e3280d37b6a78104f7
Version 2.0 features:
Menus to select ROM location (EMMC or SD Card) and ROM family (GB, CM7 or CM10)
GB NottachTrix:
AT&T
Faux 1.00GHz
Faux 1.30GHz
Faux 1.45GHz
(D00 and 1100 were pulled to reduce zip size)​
GB MROM:
HW Voltage
SW Voltage​
CM7 MROM:
HW Voltage
SW Voltage​
CM7 Neutrino:
EE
GT
GT+​
CM10 (EMMC-only):
epinter Stock and OC1300
Th3Bill JB AOKP and JB MIUI​
Dual-boot support! Boot supported ROMs hosted on SD card. Here I assume that your SD-based ROM resides at the following ext3[4] partitions:
/dev/block/mmcblk1p2 (/system)
/dev/block/mmcblk1p3 (/cache)
/dev/block/mmcblk1p4 (/data)​
Instructions:
1. Download Atrix-Boot-Emporium-V2.0-signed.zip to SD card
2. Boot to CWM and "install/choose zip from sdcard".
3. Select Atrix-Boot-Emporium-V2.0-signed.zip
4. Install zip and follow instructions on the Welcome screen
5. Select ROM location: EMMC (internal memory) or SD (external memory)
6. Select ROM family: GB, CM7 or CM10 (CM9 and ICS not yet available)
7. Select kernel
8. Confirm and reboot (ignore “Status 0” error --- AROMA Installer bug)​
Note 1: Atrix Boot Emporium is not a ROM store. I only stock boots (sorry). Also, I don't have version numbers for the kernels. But you can look inside the zip and view the timestamps of the boot images. You can also verify kernel version by going to Settings > About Phone.
Note 2: I did not include boot images for ROMs that are new or frequently updated. I'll wait until things settle down a bit
Note 3: This is a powerful tool, so remember which ROM you have installed on EMMC (or SD if applicable), and try not to cross ROM families, e.g. don't boot to CM10 with a CM7 kernel or you will soft-brick. You MAY need to wipe data and/or reintall GApps, even if booting to a member of the same ROM family. Please Nandroid backup or at least Titanium backup system + apps beforehand.
Note 4: If you have problems booting a ROM hosted on SD even after wiping /cache and /data, try repartitioning /system, /cache and /data using my Smart Part partitioning tool, found here: http://forum.xda-developers.com/showthread.php?t=1651356 . Then reinstall ROM and reboot. This always works for me except for CM10 ROMs. For some reason I can't get them to boot off SD. Maybe a security / permissions issue.
Standard disclaimers apply.
Enjoy!
Credits: NottachTrix, faux123, Notorious544d, mmontouri, Th3Bill, epinter, amarullz (AROMA Installer), Koush (CWM Recovery) and any others I didn't mention (sorry).

seems nice but how about listing the install steps?

dude u r awesome !

What exactly is this might I ask? I don't exactly know its function. I should be ashamed if it was something basic...

syngamer96 said:
What exactly is this might I ask? I don't exactly know its function. I should be ashamed if it was something basic...
Click to expand...
Click to collapse
^ this. I dont know either what exactly is this.. and the instructions aren't as clear as a noob like me would want

Is this a JB or ICS
Sent from my MB860 using xda premium

Not having downloaded or tried anything (yet), my initial guess is this is just a brand new way of dual-booting, no ROMs are included.

ranjithkumar1201 said:
Is this a JB or ICS
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is not a ROM , I guess its just some ways to flash kernels and such?
I'm confused.
Sent from that Atrix.

? Same as Cyanoboot ?

This is a Rom I think based on nochttatrix Rom. Gonna test it.
Sent from my MB860 using xda app-developers app

Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.

ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.
Click to expand...
Click to collapse
Yeah its compatible with Nottachtirx ROM. This is a kernel installer i flashed it. U can choose between different kernels. About the themen i didnt get any to choose or what every.

ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Click to expand...
Click to collapse
First thing the OP says is : Initial release features the original NottachTrix 1.3.1-compatible kernels and ramfix

ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.
Click to expand...
Click to collapse
This is strictly a custom boot image loader that I developed on my own. And the Welcome screen explicitly says: "Initial release features NottachTrix-compatible boot images".
Atrix-Boot-Emporium assumes that at least one ROM is installed on your device and features the six boot images found in the NottachTrix1.3.1 ROM. Emporium also features each of these six images with modified ramdisks to redirect the /system, /cache and /data filesystem mounts to SD card for dual-boot --- assuming the three "ext" partitions exist on SD and are of adequate size.
So if you flash the zip and follow instructions, you should find the original six NottachTrix1.3.1-compatible boot images and a corresponding six identical images adapted for SD-based ROMs (for dual boot).

So if I flash Nottatrix-ext to my SD and have ICS or CM7/9/10 on my phone, this zip will automatically arrange everything (creating folders with boot-images from both Roms) that I can switch between both? I was only able to that on Blur-based Roms until now - never got it working properly on Cm7.

In this initial release, the user selects a single boot image and that image is flashed to the boot partition, nothing else.
I was thinking that a subsequent release could feature a master menu where the user can select among GB (NottachTrix), CM7[9, 10] and ICS. Then a menu of boot images is presented for each class of ROMs.
The main idea behind the initial release was to enable quick selection of different boot images (e.g. OC kernels) for a particular ROM, in this case NottachTrix.
And it's already bailed me out of some trouble while on the road (no fastboot), lol.

Thank you, that´s awesome! Now I finally get the full purpose of this Release. Definitly I good thing - plz develop it further, I can get everything working with DualBoot except the boot.img thingies... That really bumped me every time.

Thanks for the feedback. I will look at my work schedule and see what I can do for the next release.

Atrix Boot Emporium V2.0 Released!​
Version 2.0 features...
Menus to select ROM location (EMMC or SD Card) and ROM family (GB, CM7 or CM10).
Includes boot images from...
GB NottachTrix
AT&T
Faux 1.00GHz
Faux 1.30GHz
Faux 1.45GHz
(D00 and 1100 were pulled to reduce zip size)​
GB MROM
HW Voltage
SW Voltage​
CM7 MROM
HW Voltage
SW Voltage​
CM7 Neutrino
EE
GT
GT+​
CM10 (EMMC-only)
epinter Stock and OC1300
Th3Bill JB AOKP and JB MIUI​
Dual-boot support! Boot supported ROMs hosted on SD card. Here I assume that your SD-based ROM resides at the following ext3[4] partitions:
/dev/block/mmcblk1p2 (/system)
/dev/block/mmcblk1p3 (/cache)
/dev/block/mmcblk1p4 (/data)​
See OP for details!

[HOW TO] DUAL BOOT for P990 & SU660 on BOTH Bootloaders v5.0

Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.​
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread

Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.​
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!

Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....

This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post

This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job

Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate

Nice ! Trying soon... :fingers-crossed:

SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.

i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?

what about ics and gingerbread on dual boot!?

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)

Nice man" I ll try it soon!

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.

I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!

Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:

And what about dual boot with linux?

tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.

sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).

tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...

How about flashing the second rom that have aroma installer??

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github

reserved
reserved against whatever need

reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.

On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).

bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...

Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.

bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:

bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...

bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.

bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal

xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)

reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.

bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e

andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.

Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.

cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...

Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

[RECOVERY]Safestrap 3.75 for unused partitions (/preinstall & /webtop)

This version of SafeStrap is based on SafeStrap 3.75 but has a lot of differences with it:
- there is not more the splashscreen during the boot, to enter in Safestrap you have to select BP Tools in the Boot Mode Selection Menu(VolUp&&VolDown+PowerOn)
- has been added a Safe Rom slot that uses the unused partitions:
/preinstall (~ 600mb) for /system
/webtop (~ 1,4gb) for /data
/cache is shared with the Stock Rom slot
- in this version you have 6 slots: the Stock Rom slot, the Safe Rom slot and the four virtual slots
- the Safe Rom slot is faster than any virtual slot and safer than the Stock Rom slot
If you are using the original Safestrap you can simply install this new version over it and you will still have your roms in the virtual slots.
This version of Safestrap works like any other version of Safestrap and you can use the Stock Rom slot and the four virtual slots as you are usually do, the only thing that is a bit complicated is to install an aosp rom in the new Safe Rom slot that i provided in it.
DOWNLOAD AND GUIDE TO USE THE SAFE ROM SLOT
HOW TO POST REQUEST FOR HELP:
You have to entirely read this thread, I do NOT answer redundant question.
I do not answer to requests for help in private, I have neither the time nor the interest in doing so.
Any doubts, questions or requests must be posted in this thread in order to answer a single time and help everyone.
XDA:DevDB Information
Safestrap 3.75 for unused partitions (/preinstall & /webtop) , Tool/Utility for the Motorola Droid 4
Contributors
Mentor.37
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2016-01-05

This thread is not about the ramdisks so do not ask about them.
In case of problems you can build the ramdisk as i explained in the main thread.

Super, i wait for some time for someone to make this. I'v tested this with cm12 to safe slot but blank screen. Some progress in this kexec problem ? Also SS revovery splash screen is not so but as turning of device and keys combo pressing.

I rechecked everything more and more times but seem to me that everything is ok, for now I do really have not idea on where could be the problem.

Solved
Good news, I understood where is the problem with the roms that use a kexec kernel and the problem was not in my modded recovery but in the rom's ramdisk. I'm now running the cm11 in my safe slot.
I will correctly describe how to run a kexec rom in my safestrap version in the next days, for now i'm a bit busy.

Mentor.37 said:
Good news, I understood where is the problem with the roms that use a kexec kernel and the problem was not in my modded recovery but in the rom's ramdisk. I'm now running the cm11 in my safe slot.
I will correctly describe how to run a kexec rom in my safestrap version in the next days, for now i'm a bit busy.
Click to expand...
Click to collapse
could the partitions be formated fs2fs ?
Regards

For now they can be formatted only as you can format the stock rom or any slot in the standard safestrap but should not be difficult add this option in safestrap but i can't ensure you that they will work, as far as i know the aosp roms require an ext3 or ext4 fs for /system and /data.
#Postedit
I have never used safestrap before this my project and for this i did not know it well, now i saw that the f2fs is the fs used for the virtual stlots and yes i can format these partitions as f2fs the first time that the safe slot is selected but for now i'm using the cm11 in this slot with the partitions formatted as ext3 and the rom is really really fast.

Final version
I just uploaded the final version in which i also restored the capability to use the virtual slots.
If you are using my previous debug version or if you are using the original safestrap 3.75 you can simply install this new version over them and you will still have your rom in the safe slot or in the virtual slot.

Yes, i know that i told that the previous was the final version but i just uploaded a little update that fixes a problem in the layout of the new safe slot menu.

Mentor.37 said:
For now they can be formatted only as you can format the stock rom or any slot in the standard safestrap but should not be difficult add this option in safestrap but i can't ensure you that they will work, as far as i know the aosp roms require an ext3 or ext4 fs for /system and /data.
#Postedit
I have never use safestrap before this my project and for this i did not know it well, now i saw that the f2fs is the fs used for the virtual stlots and yes i can format these partitions as f2fs the first time that the safe slot is selected but for now i'm using the cm11 in this slot with the partitions formatted as ext3 and the rom is really really fast.
Click to expand...
Click to collapse
I was thinking to add fs2fs support to the kernel and see how it works, like otterx project.
thanks for your work !
regards

Thank you for great work. I'm now trying CM11 in safe slot. Everything looks great, it run very fast compared to cm12. I have one question: How can I edit cm12 ramdisk.img? I've tried "Android Image Kitchen 2.0" with no luck. Thanks for help.

In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is faster than the cm11 used in the same slot, i suppose thank to the ART.

Mentor.37 said:
In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is fastest than the cm11 used in the same slot, i suppose thank to the ART.
Click to expand...
Click to collapse
Excellent! It works like a charm! Now i can swap SD-card and internal storage etc... Thank you Mentor!

Thanks, Mentor.
This is a brilliant idea, and it works perfectly.
It seems crazy not to use this, if you don't need /preinstall or /webtop.

Mentor.37 said:
In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is fastest than the cm11 used in the same slot, i suppose thank to the ART.
Click to expand...
Click to collapse
Can you also add patch for cm 10.2.1 ?

Anyone can build by itself a ramdisk to use a rom in the Safe Rom slot with these passages:
1) unpacking the ramdisk.img with this command:
Code:
gunzip -c ../ramdisk.img | cpio -i
N.B.: for the roms based on LP the procedure is a bit more complex and i explained it some post above
2) editing the file fixboot.sh as explained in the main thread
3) repacking the new ramdisk.img with this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.img

Excellent work!

Mentor.37 said:
Anyone can build by itself a ramdisk to use a rom in the Safe Rom slot with these passages:
1) unpacking the ramdisk.img with this command:
Code:
gunzip -c ../ramdisk.img | cpio -i
N.B.: for the roms based on LP the procedure is a bit more complex and i explained it some post above
2) editing the file fixboot.sh as explained in the main thread
3) repacking the new ramdisk.img with this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.img
Click to expand...
Click to collapse
For some strange reason I cannot repack new ramdisk.img for cm 10.2.1

I have a problem - the safe slot is there but, it shows that it has 0 MB (0 MB Free) in Data. I still did try to install CM11 (M12) there. It did installed successfully, but after rebooting it stuck (at least I think it did) on the CM boot animation. It stayed there for good half a hour so I thought there is a problem. So i restarted and went back to stock (have CM12 there, I wanted to test a CM11 a bit if it would be snappier as it probably is more developed and than switch those two as CM12 has nightly updates and there is risk of bricking the phone with daily flashes)
Anyway is showing 0 MB in Data normal and /preinstall and /webtop are used anyway or is it wrong?
Thanks!

dutohlav said:
I have a problem - the safe slot is there but, it shows that it has 0 MB (0 MB Free) in Data. I still did try to install CM11 (M12) there. It did installed successfully, but after rebooting it stuck (at least I think it did) on the CM boot animation. It stayed there for good half a hour so I thought there is a problem. So i restarted and went back to stock (have CM12 there, I wanted to test a CM11 a bit if it would be snappier as it probably is more developed and than switch those two as CM12 has nightly updates and there is risk of bricking the phone with daily flashes)
Anyway is showing 0 MB in Data normal and /preinstall and /webtop are used anyway or is it wrong?
Thanks!
Click to expand...
Click to collapse
Both preinstalled and Webtop should have data in them, before you wipe them, what are total sizes?
Sent from my XT907 using Tapatalk