Develop Bugs

[Q] Dualbooting different ROMs?

Is there a way to have 2 ROMs installed and get to choose which one you want to boot up everytime? I flashed Deck's 1.3 but I'd like to give MIUI a try, I'm too lazy to re-flash ROM, kernel, scripts, etc... If I don't prefer MIUI.

You could always backup your current ROM and flash MIUI, and after checking it out (for however long) just restore your setup if you're not feeling it. Or there is this;
https://market.android.com/details?id=com.drx2.bootmanager
I hear it takes up sizable space, but you might find it worth it. I tend to have a backup of CM7 and MIUI, just in case I want jump back for a bit or check something else out.

Have 5 diff ROMs (see sig) loaded using Boot Manager and lovin it

What I do is have a couple of different backups on my sdcard but if you plan on switching between your ROMs often I'd say go for the bootmanager
Sent from my Gruesomes Rom using XDA App

Bootmanager 3.01 is out now
Changes from v2.0 to 3.01:
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes

floydie7 said:
What I do is have a couple of different backups on my sdcard but if you plan on switching between your ROMs often I'd say go for the bootmanager
Sent from my Gruesomes Rom using XDA App
Click to expand...
Click to collapse
same here. i usually make a back up and put it in a folder with the name and date - if i haven't gone back to it after a few weeks, i just delete it.
if i find myself going back and forth - bootmanager
works awesome

devnulldroid said:
Bootmanager 3.01 is out now
Changes from v2.0 to 3.01:
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
Click to expand...
Click to collapse
Is there a link to a thread explaining how to do this? I can't seen to get the search tool to work today

sitlet said:
Is there a link to a thread explaining how to do this? I can't seen to get the search tool to work today
Click to expand...
Click to collapse
Here is the Boot Manager Manual that explains what the program is and how to use it and all of its features.

Bootmanager = AWESOME.
You need to have some patience setting everything up, but once you get everything working it takes 2minutes to boot into a different ROM.
Sent from my PC36100 using XDA App

I took Boot Manager for a test drive last week. It was nice and all....but one thing I found to be very irritating was that my SD card wouldn't mount when I had it plugged into my computer. I also received errors, while in my SD ROMs, and the boot.img for my phone ROM failed to load. As did the boot.img for ALL of my other ROMs except the one I was in. Unfortunately. the one I was in was not a ROM that impressed me at all. But I couldn't go back to my default ROM so I ended up having to reflash the whole damn thing. Really irritating for me and it was a total deal breaker. I can't take a chance of Boot Manager doing that during an extremely critical time.

Ok, first mistake you made was flashing roms while plugged into a computer. That is why the boot.img were not created properly.
Second, anytime there is an issue with booting into slots or back to phonerom, boot into recovery, select install zips from sd, then select bootmanager directory, then select phonerom directory, then flash the update.zip, then reboot.
All fixed and back to original rom
Sent from my PC36100 using Tapatalk

Boot Manager is a good app...lets you install 4 additional ROMs plus your phone rom.
you should check it out, some of the roms dont work, but you can google which ones do work. Lets you Nandroid to SD as well.

eggsack said:
Ok, first mistake you made was flashing roms while plugged into a computer. That is why the boot.img were not created properly.
Second, anytime there is an issue with booting into slots or back to phonerom, boot into recovery, select install zips from sd, then select bootmanager directory, then select phonerom directory, then flash the update.zip, then reboot.
All fixed and back to original rom
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Wrong. I was at a hospital when my boot.img decided it wanted to not work. I'm not a noob when it comes to this stuff. ROMs were loaded onto my SD card, phone removed from computer, installed into Boot Manager. I could switch between the ROMs just fine for the first day or two. Then they just randomly decided they didn't want to load the boot.img files at all. The issue with my phone being attached to my computer was a completely separate issue. Whenever I did attach my phone to the computer while I was using Boot Manager it would not allow my computer to see it. Deal breaker for me even if I could reflash the phone rom. I'm not saying it isn't a useful app. But the spontaneity of the bugs is something I can't risk.

Boot manager is the way to go, also helps when trying to work on a rom that you are cooking/porting/or modding for yourself.

I have a habit of switching between MIUI, Cyanogen and often trying out random other ones. I'm gonna give Boot Manager a try. Thanks.

Bootmanager is the best app ever.
Sent from my PC36100 using Tapatalk

I can't install MIUI on any slot D:
Sent from my Classic EVO

Royalfox said:
I can't install MIUI on any slot D:
Sent from my Classic EVO
Click to expand...
Click to collapse
uninstall the app from the rom and fix permissions worked for me...i was stuck on this for a while too

It says "clean up finished" and nothing happened. I press on Stop Install and try to boot ROM, but it says " there's no Rom installed"
Sent from my Classic EVO

Just swapped out OMFGB for latest MIUI utilizing Ext2 file system and running nicely on my EVO 4G. Every day I am more and more impressed with Boot Manager
Talk about a virtual world...

[RECOVERY] [10/17/12] TWRP 2.3.1.1 - TeamWin Recovery Project

[RECOVERY] [10/17/12] TWRP 2.3.1.1 - TeamWin Recovery Project
dan-htc-touch is proud to present TWRP 2.3.1.1 for the Galaxy Tab 8.9
now with ability to backup/restore/flash from usb dongle
Special credits:
Dees_Troy for a lot of porting help.
braway for helping me to get recovery image to init.
BLOWNCO for helping test
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
Shift and racks for graphics help on default theme
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.1, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
new in 2.2
onscreen keyboard for selecting recovery names
select locations from backup and flash menu's
What's new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.1.0 now features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
In the future we will be working hard to make TWRP easier for other developers to compile. We eventually plan to get a gerrit instance running to let anyone submit patches to the project. We may be looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
Zip files that install more data than free space is available will crash or hang recovery (AOSP issue) - Fixed with flashing zip in place
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
https://github.com/dan-htc-touch/android_device_samsung_SGHI957
DOWNLOAD:
goo.im/devs/damantea/Recoveries
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers

Looks really promising. Maybe now rom zip flashes won't lag like hell. Has this been tested and confirmed working specifically for the i957? It is quite different from the other 8.9s.
Sent from my SAMSUNG-SGH-I727 using xda premium

I have 957r, but built using 957 source. This flashes zips in place, no copy to ram first

Thanks for the work. I'll give this a try when I get some time. Hopefully later tonight. Hopefully my install scripts work with this recovery.

Scarchunk said:
Thanks for the work. I'll give this a try when I get some time. Hopefully later tonight. Hopefully my install scripts work with this recovery.
Click to expand...
Click to collapse
That's what I'm hoping
Sent from my SAMSUNG-SGH-I727 using xda premium

Might help to check the symlink part of your script, and make sure nothing is conflicting with files already there, not sure what else could cause the system lag

Sweet! It does install and come up, taking a backup of the device now.
Anyone else give this a try?
I didn't have any luck with goomanager, it force closed while trying to unsuccessfully download the recovery image. No idea, seemed like a lot of effort to flash a raw image to a partition, so at a root shell I did:
Code:
dd if=openrecovery-twrp-SGH-I957-2.1.4.img of=/dev/block/mmcblk0p22
YMMV might vary there, but it worked for me.
edit to add: adb works in recovery.. pre-OS root shell SCORE!
thanks for this!

twrp v2
Will twrp work with att sgh-i957 as this device is not listed on their website? Can someone give a detail instructions how to install this through GOO manager as someone posted?
I have a stock unit and I've read the forum but not clear on whether to use CWM Recovery or TWRP v2 do a nandroid. I have not installed or flashed anything yet. Just asking for informations before doing anything.
----------------
ATT SGH-I957

nrvate said:
Sweet! It does install and come up, taking a backup of the device now.
Anyone else give this a try?
I didn't have any luck with goomanager, it force closed while trying to unsuccessfully download the recovery image. No idea, seemed like a lot of effort to flash a raw image to a partition, so at a root shell I did:
Code:
dd if=openrecovery-twrp-SGH-I957-2.1.4.img of=/dev/block/mmcblk0p22
YMMV might vary there, but it worked for me.
edit to add: adb works in recovery.. pre-OS root shell SCORE!
thanks for this!
Click to expand...
Click to collapse
spidyman007 said:
Will twrp work with att sgh-i957 as this device is not listed on their website? Can someone give a detail instructions how to install this through GOO manager as someone posted?
I have a stock unit and I've read the forum but not clear on whether to use CWM Recovery or TWRP v2 do a nandroid. I have not installed or flashed anything yet. Just asking for informations before doing anything.
----------------
ATT SGH-I957
Click to expand...
Click to collapse
If goo manager does not work, try the dd method, or Odin flash this
http://db.tt/Tz3MFdDf
CWM and twrp backups only work for the recovery they were created in

I also couldn't figure out how to get Goo Manager to do anything useful. Should I zip up the .IMG file first?

Any problems with a full wipe from recovery? Backup and restore freeze free? Both problems existed in cwm, just making sure.
Sent from my SAMSUNG-SGH-I727 using xda premium

So far so good! Made several backups and restored two of them without issue.
Real encouraging!

nrvate said:
So far so good! Made several backups and restored two of them without issue.
Real encouraging!
Click to expand...
Click to collapse
Have you wiped anything like data system or cache yet?
Sent from my SAMSUNG-SGH-I727 using xda premium

orlandoxpolice said:
Have you wiped anything like data system or cache yet?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes, all three. Worked as expected. Didnt try wiping recovery or boot.y

nrvate said:
Yes, all three. Worked as expected. Didnt try wiping recovery or boot.y
Click to expand...
Click to collapse
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium

orlandoxpolice said:
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yep. Installs over cwm and as nrvate said, everything seems to be working as it should. Haven't tried installing any of the stuff I was working on yet. Haven't had the time, but I tossed on dannorom along with the stock kernel and I'm happy.

OK, I'm just dying of curiosity here. How are you guys flashing this .IMG file???
I tried with Goo.im, it won't see it. Renaming to .zip doesn't do anything useful either, it just reboots into recovery.
I couldn't flash the .img or renamed .zip in CWM.
What's the secret? Anybody care to share?
---------- Post added at 05:20 AM ---------- Previous post was at 04:30 AM ----------
orlandoxpolice said:
Ok last stupid question I promise. Safe to install over cwm I assume?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I just flashed TWRP over CWM using ODIN. Worked fine. Still no idea what the .img file is for, but TWRP is so slick I won't be moving back to CWM.

Indeed, no problems installing over CWM.
Digging TWRP alot!

ok, fixed a few things, removed reboot bootloader, added reboot download. as well as added ability to backup/restore to usb dongle, please test before i add to first post
http://db.tt/VxOwWios
usb dongle is called sdcard in mount section

When backing up is it safe to backup and restore boot?
Sent from my SAMSUNG-SGH-I727 using xda premium

Rom Manager with the Photon Q recovery works fine on the Razr M.

So you are Unlocked & Rooted.
Download the apk here
Just choose the setup for The Photon Q let it do its thing.
It is just a "stepping stone" to flash the newest from the same recovery.
It is 6.0.1.3 & works a lot slower than the newest 6.0.4.5 or TWRP from my goodies.
For the doubters I will say that, except the keyboard & digitizer input, the Q & the M are the same phone.
Atrix HD using RM also.
More
See method 4
Love TWRP? RM installs TWRP also. Just flash the zip from cwmr see housekeeping goodies.
The biggest news is that one can go from rooted stock to custom recovery with this. If you want TWRP OR Matt's CWMR just flash it from this recovery -see goodies below. Also the attached flash-able zip is a larger font CWM version from the Atrix HD forum.
This also allows you to take the OTA using 3 (or 4 if you have not unlocked yet ) phone "apps": Rom Manager, VooDoo rootkeeper, and the stockRECOVERY.zip (Motopocalypse.apk).
Get VooDoo on your SDcard from the Developer http://androidvnd.com/download.php?id=org.projectvoodoo.otarootkeeper
Now we have phone maintenance without a PC. More housekeeping goodies here. The bootloader unlock apk is there too http://forum.xda-developers.com/showthread.php?t=2327340
Steps to restore to the newest stock rom: I have a Mac and have to : ( using Parallels desktop & W7)
1. Data wipe from CWMR a must do or WiFi breaks. No more TWRP for me, I lost extSD cause of the box in normal selection.
2. Enter fast boot ...
3. Rsdlite & select the XML from Matts util...Reboots.
4. ByPass SETUP go settings/Dev. settings for USB debug.
5. Root w/ Matts.
6. Say no to logins & syncs.
7. VooDoo protect & unroot.
8. Check for update......yes yes...stock recovery... reboot
9. VooDoo restore root.
10. Login and DL RM.
11. RM with Photon Q recovery.
12. I keep ROM on extSD only... back home
CWMR is way faster and more space efficient than TWRP. Yet the blob folder can lead many to think otherwise.
Never use a space if you rename that date code label.
You never want to use internal SD for backup or anything else as it gets wiped in the often needed data wipe/reset. That is why a SD swap is so needed on our phone.
I keep RomMgr & VooDoo on my SD so I can skip all the logins and syncs If I have to restore w/ RSD.
Now I see why there are no supporters of RM on the Photon Q forum. ROM installations do not work well with the M (read Q also).
Help for general errors & what to do about them:
http://forum.xda-developers.com/showpost.php?p=43043608&postcount=1
The Q and the M are identical hardware and use the same emulated storage0.
But their digitizer screen input is the mirror of each other.
That is why the cwmr hard button version works but their official twrp will work but the screen input is mirrored.

Nobody believes me.
http://www.droidrzr.com/index.php/t...nager-works-on-the-xt907-sleeper-of-the-year/

Famous Dev's opinion.
http://forum.xda-developers.com/showpost.php?p=44055839&postcount=370

Well that's neat and all, but whats the point?

Leraeniesh said:
Well that's neat and all, but whats the point?
Click to expand...
Click to collapse
I never used it before. But it is very handy I think all the features work. I went and bought the premium app when I first got into android with the Dx2. Looking for a bluetooth ready cm based rom to install. Carbon is not yet ready.

while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8. Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3) AND can be manaually assigned to be recognized by ROM manager anyway.

tucstwo said:
while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8.
[I do not see any difference. The Q is also qHD.]
Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3)
[True, but this allows custom recovery with out a PC. Then one can flash any recovery they want.]
AND can be manaually assigned to be recognized by ROM manager anyway.
[I have found all of the housekeeping features work]
Click to expand...
Click to collapse
Thanks for the feedback.

OP updated.

FYI the more up to date Recovery for 3.4 kernels

Update
arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....
***********************************
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img

aviwdoowks said:
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img
Click to expand...
Click to collapse
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.

ej1911 said:
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.
Click to expand...
Click to collapse
These phones are siblings & this is a work around to have a working recovery for cm 4.3. The xt907 ver will not work!

All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.

ej1911 said:
All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.
Click to expand...
Click to collapse
In the above post
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134

Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app

ej1911 said:
Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
The same reason I use rom manager on our M.
It is very handy.
Xt897 stock recovery is way better than ours.
Handy.
I backed up from the home screen & then restored from home screen with the xt926 ver.
Some posters on rzr could not get our recovery to succeed w/ 907 versions.

I don't claim to be an expert. I have been playing with Android since 1.6, and have been using UNIX and Linux based systems for over 2 decades, so I do have a decent working knowledge.
In that time, most of the expensive devices that I have seen turned into paperweights were caused by either using incorrect tools or using the correct tools without fully understanding how to use them.
I'm not trying to get into an argument, but I would suggest any user that has an interest in modifying their device learn how to use the tools that are required to do so. A working knowledge of fastboot, adb, basic Linux commands, factory and aftermarket recoveries, and RSD(or the manufacturers flashing tool for your device is the bare minimum anyone should have before rooting.
As far as 4.3 recoveries, I highly recommend switching to CWM at this point before playing. Dhacker has some available to download or you can build the newest (regular and touch) at the cwm builder site.
Sent from my Droid Razr M using xda app-developers app

Be careful. I forgot this was my recovery & started to do a 2 step from twrp mgr. Backup & flash the miui alpha! In a panic I used the keys to abort.

arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....

[INFO] Recoveries for the Samsung Galaxy Ace II X

Work in Progress
List of Custom Recoveries for the Samsung Galaxy Ace II X
For all things rooting and installing, a custom recovery is often needed. New things are being developed day and night. Thus, I find it necessary for there to be a list of all the recoveries that are compatible with the Samsung Galaxy Ace II X. Some are better than others, though it is a matter of preference. Anyways, commencing the list...
1. ClockworkMod 5.5.0.4 - not my work
ClockworkMod recovery, usually abbreviated as CWM or CWMR, is a custom recovery based off of AOSP source, created by Koushik Dutta (known by the nickname "Koush").
Bugs - Mount USB doesn't work.
Download
2. ClockworkMod 6 - not my work
Bugs - Mount USB doesn't work, "dancing screen," SOME USERS REPORT THAT INSTALLING CWM6 CAUSES THE DEVICE TO BOOT INTO RECOVERY INSTEAD OF THE ROM
Download
3. TeamWin Recovery Project 2.6.3.0 - my work
TeamWin Recovery Project, often abbreviated as TWRP, is a custom recovery that has a fully touch-driven interface. Aside from the uniquity of being 100% touch controlled, it also contains an ubiquity of features. It has a built-in file manager, support for sideloading via ADB, support for backups and restoring backups, a completely theme-able interface, and more sorts of customization.
Bugs - Mount USB doesn't work.
Download
Changelog:
Release 2 - backported some features from TWRP 2.7, fixed color tint issue, implemented internal storage
Release 1 - initial release
4. TeamWin Recovery Project 2.7.1.0 - my work
Download
Bugs - None reported.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
Release 4 - Upgraded to 2.7.1.0 (customized to build on a JB-based tree: removed mouse support via USB OTG, removed text wrap for now), fixed internal storage
Release 3 - Fixed color tint issue
Release 2 - Fixed USB Mass Storage
Release 1 - Initial release *TWRP 2.7.1.0 has some mount issues. Don't use it.
5. TeamWin Recovery Project 2.8.1.1 - by @draekko
Check his post here for details and download links.
This list will be updated regularly as recoveries are updated, new recoveries are built, or for miscellaneous reasons. If there are any bugs I haven't mentioned for any of the recoveries, let me know and I'll add it to the OP.

Nice thread.
keep up the good work.

Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app

CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:

Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
AndroidAssassin said:
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
Seb269 said:
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Click to expand...
Click to collapse
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?

Codename13 said:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Click to expand...
Click to collapse
They are the same.

Bug report (TWRP 2.7.0.0)
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.

gregory678 said:
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
Click to expand...
Click to collapse
The latest release? I have no such problem. TWRP is configured so that the settings are stored on the external sdcard. So if you don't have one, your settings won't be saved. I considered setting the cache partition as the TWRP settings storage, but cache is often wiped when installing ROMs and packages. The same with system, data, et cetera. I've considered setting the recovery partition as a settings storage partition; however, whenever a new build of TWRP is installed, the recovery partition will be overwritten. I could try splitting the cache partition up so there is the cache partition and a new 12mb partition, but then there would either be errors when installing firmwares via Odin, or the new settings storage partition would be wiped. Unless you have any better ideas than the sdcard being the settings storage, don't complain. I'm not sure what's causing your issue - perhaps it's because you only insert your sdcard when you boot into TWRP? Enlighten me, and tell me a bit about your device setup (ROM, kernel, size of sdcard, etc).

OMG, I'm such dumb, I just noticed that settings file is hidden. I was wondering why it's always left empty folder after rebooting from recovery mode, now I discovered a hidden settings file in it, I'm Scherlock of the year . Sorry for bothering you, can someone delete these ashaming posts?

Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?

I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Jeremicus said:
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh then try installing a recovery again and booting into it.

Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk

I was thinking about the advantages of TWRP 2.7 over 2.6. I knew that if I looked in the commit history for 2.7 on Github, I would be bound to find the commits that brought in some of my favorite features of TWRP 2.7.0.0. That, along with I having just discovered that Github commits can be download as patches, will bring the best version of TWRP for us yet. So far, I've successfully backported haptic feedback (along with the settings for it) and a bit more. I've also fixed internal storage in TWRP. I plan to backport the smoother scrolling, USB Mass Storage (it only works in 2.7 at the moment because 2.7 added in a different way to handle and mount UMS. I'll backport the different way of handling and mounting UMS), and add in some other bits of fun. It's going to be really cool, and it really isn't time consuming, so I should be able to bring it to you all very soon.
AndroidAssassin said:
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
Click to expand...
Click to collapse
Just download Recovery Tools from the Play Store.

It dont have nething for ace2x
Sent from my GT-S7560M using XDA Premium 4 mobile app

Codename13 said:
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Click to expand...
Click to collapse
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:

husokal said:
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
Click to expand...
Click to collapse
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.

Codename13 said:
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Click to expand...
Click to collapse
Im sorry i dont know much things about SELinux
As i see 2.7.0.0 Forces SELinux which i dont know what can be problem about it.
and 2.6.3.0 Mount Storage not working.
So im using 2.7.0.0 for my stock. Cause i need this function sometimes.
Sorry for noob question but what can be problem about Enforcing SELinux for 4.0.4
Edit:
Got it! : http://forum.xda-developers.com/showpost.php?p=52013947&postcount=5392

There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.

s7560m said:
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
Click to expand...
Click to collapse
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
EDIT - It seems that there's also a new version of TWRP out. It seems to be quite minor, but I'll see if I can port it. It's been bumped up to version 2.7.1.0 now.

Codename13 said:
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
Click to expand...
Click to collapse
Definitely twrp is the best! Never had any issues with it whatsoever, and has a great ui. If you could though, it would be awesome to try and port philz touch and cwm touch as well, just in case those who like cwm want that touch feature, or like the theme and features of philz touch . And I really hope the usb mounting issue can be fixed, as it can save so much time, rather than downloading to my computer, transferring to phone external storage, and then booting into recovery. Those who are lazy don't want to do all of that lol. Anyways, keep up all of the good work, and hopefully these bug fixes and new recoveries are implemented in future notice!