Hello all.
I've compiled the latest ClockworkMod recovery for the Tattoo. In addition to the normal features it has, this is using a custom smaller font, so the text fits better on a QVGA screen.
If you're already rooted, you can flash it with "flash_image recovery recovery.img" (after running "su" first) from a terminal shell prompt, or from adb shell.
v2.5.1.8 is the last version included in CyanogenMod 6 sources
v3.0.0.5 is the new recovery from CyanogenMod 7 sources
How to flash instructions
Credits:
CM Team/Koush
KalimochoAz
NForce2506.02.2011 - Repack of 3.0.0.5 with advanced backup and wipe all function. Wipe all will completely format and erase all partitions.
Can you please tell me, in what way exactly is this Recovery better than Amon-RA?
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
arco68 said:
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
Click to expand...
Click to collapse
Is possible to add Ps3 Jailbreaking?
francians said:
Is possible to add Ps3 Jailbreaking?
Click to expand...
Click to collapse
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
arco68 said:
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
Click to expand...
Click to collapse
I asked a couple of weeks ago, but no answer.. I realy like clockworkmod and I'm afraid to change recovery.
Thanks. Good job!
Amazing recovery
Thank you very very much for this recovery. ROM Manager now works properly. BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
sunitknandi said:
BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
Click to expand...
Click to collapse
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
ClockworkMod recovery for the Tattoo isn't added to ROM Manager yet. Until now Tattoo owners had to use the Wildfire/Buzz recovery. I'll contact the author and ask if he can add this recovery for the Tattoo, so it's available from ROM Manager.
Downloading images
arco68 said:
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
Click to expand...
Click to collapse
If I knew where the images were hosted, I could fetch them through PC.
sorhe said:
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
Click to expand...
Click to collapse
Press menu button and select "manually installed clockworkmod" or similar option.
sunitknandi said:
Press menu button and select "manually installed clockworkmod" or similar option.
Click to expand...
Click to collapse
That doesn´t help!
With clockworkmod recovery I cannot flash some roms which flashed fine with maverick recovery. The installation aborted with this error:
E:Board does not support mtd utils.E:Failure at line 420:
write_raw_image PACKAGE:boot.img BOOT:
The rom is actually flashed, and only boot.img not. So I can boot the rom after manually flash the boot.img.
Is there any way to include mtd utils future in this recovery, or must to return to maverick?
I think it's a bug in clockworkmod. They changed some detection routines in the latest versions, which seems to have broken flashing to mtd when rom is using update-script instead of updater-script. I've heard that 2.5.0.9 is the latest which it worked correctly with. I'll look into it at some point unless they release a new version which fixes it.
clockworkmod 2.5.1.4 seems to be already out!
arco68 please could you take a look here: https://github.com/klutsh/android_bootable_recovery
or here: https://github.com/klutsh/psfreedom-kernels-patch
could you add psFreedom support?
edit: please fix also the font size for the tattoo screen
I suppose it can be done, so I'll take a look. Thanks for the links.
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
arco68 said:
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
Click to expand...
Click to collapse
I think is very hard find what's missing to make it works.. can you do it?
I know you are workin' also on a wonderful rom, but also psfreedom is a nice project that need a skilled man
I see the kernel patches for the Tattoo is no longer there. When he adds a working patch I'll try again.
Related
ClockworkMod Recovery 3.2.0.0
Note:
Amend scripting (update-script) is no longer supported, was deprecated by Google in Android 1.5. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Current version: 3.2.0.0-(01.06)
Recovery_Optimus_2x_3.2.0.0-(01.06).zip
MD5: 1e97b2c8a0d4b84e11ec2f31e51f83ca
SHA-1: 2f7cd8cdf8e239886e31497dcffc9e5026606155
Installation:
Unzip the archive
Plug-in the USB cable and select enable the "debug mode"
Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
Done!
If you want to thank me, click the Thanks button.
Old versions:
Recovery_Optimus_2x_3.2.0.0.zip
Changelog: http://goo.gl/MAuLi (2011-05-30)
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!
All Ok with this version!! no /cache umount
Perfect ....
As always one step ahead....
When entering Recovery menu, device vibrates all time long. =/
Good to see you here. Gonna try tomorrow!
Sent from my LG-P990 using XDA App
Just installed. This version is perfect. Thanks.
how come i cant find it in rom manager?
Sorry for a noob question, but with previus version I cannot install CM7 #31.
Can I install this rom now?
ranrick said:
When entering Recovery menu, device vibrates all time long. =/
Click to expand...
Click to collapse
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
initrd said:
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
Click to expand...
Click to collapse
Yeah, 3.0.2.8 didnt work either. Only 3.0.1.4 works without vibrations.
Works like a charm.
Anyway to add this aswell: http://forum.xda-developers.com/showthread.php?t=1098745
So you have 2 option.
Internal Sd and External Sd?
That would be awesome!
USB mount doesn't work. Is it me?
Recovery shows 3.2.0.0 but the app still reports it as 3.0.2.8 - is this for compatibility?
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
75markus said:
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
Click to expand...
Click to collapse
yep. same thing (like at 3.1.0.1)...
just made a nandroid restore and recovery can't mount /boot during restore.
It's probably why we can't ( for exemple ) flash a CM rom ( after nandroid stock rom ) play with it and if you want to return to stock rom using your backup you get a bootloop
Quite common (and annoying), that. Happens each time I've restored a CM NANDroid, have to restore, then reflash CM.
hi. just a noob question
can i use this recovery to flash all the roms for the optimus 2x. like modaco, cm7 and other modaco based custom roms. ?
i been reading the forums and there are so many recoveries. im kinda confused.
Yes you can.
There are only 2 types of recovery in reality, this type (external SD) and the one I built for internal SD use. If you're not sure what you need, pick the external one (unless you don't have an SD card).
bit of a noob..but cant seem to be able to install it. can someone give me a guide to install this with a mac thanks in advance
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Wildfire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. Can be installed with unrEVOked. Installs and works well according to users in this thread. Off-mode charging works according to t0mas_.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-buzz.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-buzz.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Flash like a normal ROM ?
Use it with unrevoked then custom recovery in the menu and use the image file in the zip
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Well my phone was installed and works well ...
t0mas_ said:
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Click to expand...
Click to collapse
No idea. It depends on the CM7 3.2.0.0 recovery source code. I didn't change anything, and I'm quite sure j_r0dd didn't touch this.
cse.10100 said:
Well my phone was installed and works well ...
Click to expand...
Click to collapse
Great! Updating the OP.
thanks, i'll try this out when i find time
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
aggourodolmas said:
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
Click to expand...
Click to collapse
Well, the recovery image itself doesn't touch superuser, but unrevoked will. I belive that you might be downgrading the superuser binary, but (at least for CM7) a reflash with the same zip without wiping anything should restore the superuser binary that was included in your ROM. It should work on other ROMs as well, as long as they're not wiping /data or /sd-ext while flashing for some reason. Make a nandroid backup before you consider flashing this recovery, that's my advice.
Can anyone confirm if this supports off mode charging?
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
Not sure where to look, but maybe one can search for this in some type of changelog for the official cwm repository.
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
works for me
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
rseke said:
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
Click to expand...
Click to collapse
You need to use unrevoked to flash the .img file.
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
rseke said:
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12548919&postcount=26
Unrevoked 3.14 can be found in the same thread on the first page.
Thanx for fast reply and for help.
I have one problem now,mu super user app not working how can i fix that,i cant enter to superuser app to update su binary,force close.
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
Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff
Taken and modified from official thread at Flo
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Manual installation
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni
Reserved
Great work
Sent from my LG-P880 using Tapatalk
Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..
Nice work, could I ask you to prepare multirom uninstaller also?
It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.
Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...
I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.
Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880
love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release
Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?
Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff
For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .
not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?
Introduction
MultiROM is one-of-a-kind multi-boot mod for LG G2. It can boot any Android ROM. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Click to expand...
Click to collapse
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Click to expand...
Click to collapse
Before you begin
This is in alpha stage. If you have the D805/6 model, use the recovery for D802. This should work on both LGD and JDI panels, but you may get some glitches. I'm working on a panel detection script which will be included in the next versions of recoveries.
Also, some ROM combinations don't work properly. You will get stuck on lg logo or MultiROM error message. It's because of the locked bootloader! It won't load the secondary ROM's kernel. We have to wait until there is a way to unlock it.
Click to expand...
Click to collapse
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-v28-UNOFFICIAL-G2.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_codename_YYYYMMDD.img) - download the ZIP file from second post and flash it in recovery.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Click to expand...
Click to collapse
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Click to expand...
Click to collapse
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Click to expand...
Click to collapse
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Click to expand...
Click to collapse
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Click to expand...
Click to collapse
Source code
MultiROM - https://github.com/PatrikKT/multirom-g2
Modified TWRP - https://github.com/PatrikKT/Team-Win-Recovery-Project
g2-common device tree - https://github.com/PatrikKT/device_lge_g2-common
Click to expand...
Click to collapse
Credits
@Tasssadar for the original work on MultiROM
@dr87 for letting me use his device tree and his kernel and helping out with some things
@savoca for his loki scripts
@arcardinal
@reas0n for testing
and everyone else I forgot
Donations
All this stuff would not be possible without the original work of Tasssadar. If you like his work, consider sparing him a few bucks on paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
And as of me, I don't want any donations. I do all of this for free. Just press that thanks button
Click to expand...
Click to collapse
This thread was used as a template
Downloads
1. Main downloads
MultiROM: multirom-20140921-v28b-UNNOFICIAL-G2.zip
Modified recovery (based on TWRP): TWRP_multirom__YYYYMMDD.zip
MultiROM Uninstaller: multirom_uninstaller.zip
Mirror: http://d-h.st/users/patrik.KT/MROM-G2
Click to expand...
Click to collapse
2. Kernels with kexec-hardboot patch
Render Kernel (for AOSP ROMs) - http://forum.xda-developers.com/lg-g2/development/kernel-render-kernel-aosp-lg-roms-t2803929
Dorimanx (for stock-based ROMs) - http://forum.xda-developers.com/showthread.php?t=2725023
VanirAOSP - http://forum.xda-developers.com/showthread.php?t=2494756
More coming soon!
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Nicely ask your kernel developer to merge kexec-hardboot patch.
Click to expand...
Click to collapse
Changelog
Code:
MultiROM v28b
=====================
* Fixed loki_tool for VS980
MultiROM v28a
=====================
* Larger UI
MultiROM v28
=====================
* Initial version for G2
* Support for devices with locked bootloader, which need loki
Recoveries:
Code:
21.09.2014
=====================
* Fixed loki_tool for VS980
15.09.2014
=====================
* Fixed installing zips without changing updater-script
14.09.2014
=====================
* TWRP 2.8.0
13.09.2014
=====================
* Initial G2 release
* Used SlimKat kernel source
reserved
happy testing, guys!
NOTE: this TWRP can be used as usual TWRP, it's similar to dr87 custom TWRP, but on SlimKat kernel.
Thanks guys you did it! How to uninstall?
Sent from my LG-D802 using XDA Premium 4 mobile app
TheFerhatKing said:
Thanks guys you did it! How to uninstall?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll make the uninstaller too. Until then, if you want to uninstall, just flash the ROM zip again and remove /data/media/0/multirom folder.
Okay thanks, just tested it a bit and it looks nice but the MultiROM UI is very small is it normal?
Sent from my LG-D802 using XDA Premium 4 mobile app
I'll make it bigger in the next version
Odoslané z môjho HTC Desire 601
Today is a good day!!!!
Looks fantastic! Thanks for your hard work. This will help out tremendously with this community Alot of us use our phones for work and play and cannot keep flashing back and forth. Now if we can get Ubuntu on here then we will really be cooking with fire. lol On my N72013 I had Ubuntu (Desktop) and my daily driver rom. I was able to do all sorts of high level IT work using Ubuntu then once I was don just change back over. This will open alot of doors for the G2. I am glad I got here when I did. AOSP really seems to be exploding contrary to CarbonRom dropping us. Though I understand why.
I am uploading new builds now that will support Multirom!
I love you XD multirom is the best tool for android! Which version of g2 is supported? d802?
EDIT: I've just that only version supported is d802!!!!
Good job guy!
Thanks for your awesome work
Sent from my LG-D802 using XDA Premium 4 mobile app
Cool~
Do you know if you'll be able to port this to d800?
Great achievement guys, you have breathed new life into our aging G2.
Been using Multirom from Nexus 4 days. Last used it on my HTC One(M7).
The best utility to have for the Flash-a-Holics like me.
Hope to see it soon for the Sprint variant LS980
I'm sure this will go in xda portal. Good work and thanks. I will try it later.
I just installed the multirom. It just ROCKS!!!!
I have installed pardus hd rom classic 7.7. Which rom can I use for second?
Is there any uninstaller available??
I used it with my nexus 4 its excellent I was wondering can I boot with my otg stick a ROM cause I have the 16gb with 10gb avaible
t-shock said:
I just installed the multirom. It just ROCKS!!!!
I have installed pardus hd rom classic 7.7. Which rom can I use for second?
Is there any uninstaller available??
Click to expand...
Click to collapse
If it's a stock based ROM, then you should install a stock based secondary ROM too. There are (sometimes) issues with booting stock-based and AOSP ROMs. The uninstaller is on the way. until then, you should be able to get rid of it by flashing the kernel you have and removing /data/media/0/multirom folder.
Ismail.A said:
I used it with my nexus 4 its excellent I was wondering can I boot with my otg stick a ROM cause I have the 16gb with 10gb avaible
Click to expand...
Click to collapse
Yes, you can. But it will be a bit slower. Read the OP...
I'm building the recovery images for d800, d801, d803, ls980 and vs980. The rest (d805, d806 and f320*) will be supported later.
EDIT: D800/1/2/3 builds are up. LS/VS980 and F320* coming in a few minutes
patrik.KT said:
If it's a stock based ROM, then you should install a stock based secondary ROM too. There are (sometimes) issues with booting stock-based and AOSP ROMs. The uninstaller is on the way. until then, you should be able to get rid of it by flashing the kernel you have and removing /data/media/0/multirom folder.
Yes, you can. But it will be a bit slower. Read the OP...
I'm building the recovery images for d800, d801, d803, ls980 and vs980. The rest (d805, d806 and f320*) will be supported later.
Click to expand...
Click to collapse
Thanks but only stock based rom that I found is with aroma.
I tried to replace some lines that you suggest to the script but it won't install.
Any suggestion??
t-shock said:
Thanks but only stock based rom that I found is with aroma.
I tried to replace some lines that you suggest to the script but it won't install.
Any suggestion??
Click to expand...
Click to collapse
Send me a link to the ROM's thread. I will check what line you should change
BTW as I said in the previous post, the d800/1/2/3 builds are up. Also the new twrp 2.8.0 is used from now.