Related
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/Y7UC8UU2JE
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/YP1BIUOF60 (this rom includes busybox, the otacert fix, and a few other minor things)
I also put together an update. This will update you to the new 2.1 OTA leak "official" without wiping. Wipe your dalvik and that's it. Do a nand backup first though just incase! http://www.multiupload.com/3OPZCD6NRA
GrdLock said:
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/09DM1FI1D1
md5: 535c300411cd47acd319e667fee8cf16
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/5HH0H1M4T1 (this rom includes busybox, the otacert fix, and a few other minor things)
md5: 6d95e5e8846c6912fda42c54daa0cb34
I also made a kernel-only update that can be flashed without wiping anything: http://www.sendspace.com/file/5ptpmc
md5: cc4e95034dc7e8adaa776483251952bf
Click to expand...
Click to collapse
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
rvpartsguy said:
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
Click to expand...
Click to collapse
Yes, I built the otacert fix into the rom.
Thanks for all your work grid, and all the others that have worked on this. Just got a new refurb the other day and was going to tackle rooting this weekend, gonna make the task so much easier.
Can you please explain what was fixed? Thanks again for your work.
The current rom is a rooted rom using the new 2.1 leak that was just released today, which is SUPPOSEDLY the "official" 2.1 update from Verizon.
What setting should be used for the phone, HTC Sync, USB, Mount SD, or nothing?
Nothing. Just connect it to your USB, and enable USB debugging. Don't mount your sdcard.
Does the market work now?
(I recall hearing that the market wouldn't work because of the test/dev certificate that was in the leaked rom)
The market will work if it doesnt work now, itll work when the OTA comes out.
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
K0CAW said:
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
Click to expand...
Click to collapse
It includes my rom. You should be able to restore pdfviewer if you need it though. I can post the files in a bit.
Great. I was pretty sure that the apps could be reinstalled if needed, but wanted to confirm. I'm downloading the package now, so I'll keep you updated. I'm pretty excited about this, since I'm still at stock 1.5.
Issues, Well first It copied the PB image fine, it didnt reboot the phone i had to manually do it with vol -, now im on step two installing amons image, it transfers but it cant start files\flash_image, no such file or directory and then it cant chmod it cause its not there.
Could you copy/paste the command prompt text you're seeing? (you gotta right-click the cmd window and select Mark)
Installing Amon's Recovery Image.
1545 KB/s (3926016 bytes in 2.480s)
cannot stat 'files\flash_image': No such file or directory
Unable to chmod /system/bin/flash_image: No such file or directory
flash_image: not found
-
Finished
Your phone will now reboot and test the recovery partition.
Press any key to continue . . .
Ahh, crap...
http://www.sendspace.com/file/obtx2w
Download that file, put it in the \tools\files\ directory, then try again and let me know.
I think I got delete-happy removing some temp files and deleted flash_image by accident.
Worked great
I just went through the install.bat file and everything worked 100% just as promised. I have not installed any of the extras yet. Thanks for the great work!
flash_image was it worked a treat its in amon_ra now was trying manually and came across it missing, went to post it and you had just now
One suggestion before letting adb copy the 2.1 rooted img to the phone have it delete the PB so users dont accidently click on it. Just a lil cleanup to help things out. So far its flashing 2.1 rooted I will let you know about the first error, ill go back through it again and get it to recreate.
Greetings.
I am trying to install Cyanogenmod 7.0.2 on my HTC Tattoo (still has 1.6). This is the first time I've done this.
I am following the Cyanogenmod wiki page that shows you the whole process of rooting+flashing a new rom (since this is my first post I am unable to post outside links in this thread).
In the "Installing Clockworkmod Recovery" section, I get the following error when trying to flash the image:
flash_image: not found
I listed the files in /sdcard and saw that it was completely empty.
Can anyone tell me what I missed?
I copied the Clockworkmod image file to the root directory by connecting my phone to my PC through USB (USB Debugging was on) and copying the file there.
Please let me know how to solve this.
Thank you.
I was able to solve my problem and proceed with the attempt to flash Clockworkmod. Now I'm getting another error though:
error writing recovery: No space left on device
I have plenty of space in the SD Card (~2GB), but I'm assuming the problem is with the phone's internal memory. I don't know what I can delete.
Any thoughts?
Thank you.
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
CROpipe said:
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried to do as you said and installed both Rom Manager and Superuser. But now I have other issues...
1. On Superuser, it says there is a newer version of su and to update. I accept and get the following error:
An error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your binary.
2. So, I decided to ignore the update of su and just move on to Rom Manager. Here, I get an error like "su was not found in /system/bin". Well, su is in "/data/local/bin", as per the cyanogen wiki to root the phone. After this, any attempt to flash Clockworkmod fails.
3. To try to make it so Rom Manager has everything it needs, I followed the wiki again, but this time I tried to move the su file to /system/bin. I got the following error:
failed on './su' - Cross-device link
Any ideas?
Thanks in advance!
Hmm, i had the same problem when i was trying to Flash CM7...
Your phone is not rooted...
I know its very frustrating but no worries!
1.Download program from this thread ->http://forum.xda-developers.com/showthread.php?t=761507... you'll see the program in attachemnts and dl the first one.
2.Paste it in your's SD card , install it (use ASTRO MANAGER, to find the program)
3.Open the program and root the phone with 1 click
4. Then Superuser will ask you to allow it and click yes, and go to ROM MANAGER.
5.You will have to allow the Superuser here too.. Do it.
6.Flash Clockwork Mod recovery, and reboot into recoverymod.
7.Flash your Rom , flash Gapps(Google applications)
8.Enjoy
Thank you CROpipe!
Your instructions worked! I now have CM7 installed on my HTC Tattoo!
Here are the issues I found though:
1. When I was trying to download the ROM using ROM Manager, the list of ROMs was empty. Maybe it's because I was not using the Premium version...? I ended up downloading the ROM from the forum, copying it to the SD card and installing it that way.
2. I tried also to install GApps through Rom Manager. I was afterwards able to set up my google account, but I still had to manually download GMail, Google Maps, ... I'm not sure if this is actually how it's supposed to go... :-/
Anyway, thanks again for the help.
Yap that is quite allright Congrats on your new ROM ))
Hi all.
I had an Orange UK Hero GSM on the latests official stock ROM and looked everywhere for a simple way to get Cyanogen 7 on it...
Most the 'simple' ways I found involved typing in text in a command line window and the ones I tried (including the official CyanogenMod instructions) did not work...
With a lot of looking around I've found a simple way that involves no typing and only downloading 3 files! So here goes... but before I do, remember I am not responsible for any damage you cause to your device. I am sharing the method that worked for me...
1) Put the attached apk files and the CyanogenMod 7 zip in the root directory of your SD card in the phone. The CyanogenMod zip can be got from: here.
2) Install the Universal Androot apk
3) Run the app to root your device (using SU option 2.1-2.2)
3) Install the RomManager 4.3 apk
4) Run the app. Choose install Clockwork Mod Recovery to install the recovery
5) Choose install ROM and when the phone boots into CWM Recovery select to install your CM7 zip from your SD card.
6) Reboot and you've got CM7.2 on your Hero!
Let me know if this works for you and hit the thanks button if it does! This guide would have saved me a day of trial and googling if someone else had written it first! :cyclops:
Thanks to the makers of Universal Androot and Rom Manager... it's their work that made this job so simple!
Thank you!!
Thank you for sharing the almost extinguished Rom Manager 4.3.apk
I've been looking for it for almost 3 days.
Thank you!!
Chris
afr33s said:
Hi all.
I had an Orange UK Hero GSM on the latests official stock ROM and looked everywhere for a simple way to get Cyanogen 7 on it...
Most the 'simple' ways I found involved typing in text in a command line window and the ones I tried (including the official CyanogenMod instructions) did not work...
With a lot of looking around I've found a simple way that involves no typing and only downloading 3 files! So here goes... but before I do, remember I am not responsible for any damage you cause to your device. I am sharing the method that worked for me...
1) Put the attached apk files and the CyanogenMod 7 zip in the root directory of your SD card in the phone. The CyanogenMod zip can be got from: here.
2) Install the Universal Androot apk
3) Run the app to root your device (using SU option 2.1-2.2)
3) Install the RomManager 4.3 apk
4) Run the app. Choose install Clockwork Mod Recovery to install the recovery
5) Choose install ROM and when the phone boots into CWM Recovery select to install your CM7 zip from your SD card.
6) Reboot and you've got CM7.2 on your Hero!
Let me know if this works for you and hit the thanks button if it does! This guide would have saved me a day of trial and googling if someone else had written it first! :cyclops:
Thanks to the makers of Universal Androot and Rom Manager... it's their work that made this job so simple!
Click to expand...
Click to collapse
great great , good post
TWRP Recovery
For Galaxy Ace
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
Me: For compiling it for Galaxy Ace.
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
aurisltu said:
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
I think, I should remind you: Recovery is independent of ROM.
It can flash everything which the new kitkat update-binary allow.
If anything fails to flash, just replace /META-INF/com/google/android/update-binary file inside that zip from cm11 or omni4.4 and it will flash.
well im using this recovery for a while and its responding better than the normal recovery , plus the other features in it , thanks for you great work
keep it up
sent from my kitkat ACE
works great, but if formatting or installing and you accidentaly bump the back button it stops what it is doing, can also corrupt the partition, installs ALL roms from cm9 through to cm11 and all scripts/mods install too,, thanks for this version,, i didnt like the other versions they were a yuck colour, i like the black and gray theme
I just had some look today on your device's development forum and found that @Mardon has already made this recovery for your device (Because, I was confused as I didn't receive a single THANK on any of my posts).
Please note that my TWRP has no relation with @Mardon's TWRP. He has used omniarmv6 sources while I've used official omni sources and the androidarmv6 sources.
I've worked hard enough and researched on everything and have made this recovery. This build is the closest one to an official build unlike little buggy build of @Mardon: Bad colors (not official colors), maybe brightness settings are missing, maybe you can't flash some zips with that recovery, etc.
And...ofcourse, you won't be able to flash stock rom using this recovery because it uses samsung's crappy rfs.
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Thanks Bro for the recovery.
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Work fine bro.. good job.. :fingers-crossed:
Thanks for this recovery, really works great, with CM9 too!
Bhargav97 said:
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Bhargav97 said:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
not working ... failed with error: -1
GalaxyAce User said:
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Click to expand...
Click to collapse
Busybox is needed for flash_image command to work. If you are using any Stock Based ROM, I doubt you have Busybox. If you can't manage to get it done this way (I don't get, why?) then you can replace recovery.img inside any recovery flashable zip file (of recovery, i.e. CWM-x.x.x.x.zip) from the one given in the link of first post. Now flash that zip file using your current recovery.
kjub6 said:
not working ... failed with error: -1
Click to expand...
Click to collapse
What I said above, also applies to you.
Thank you
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
sdembiske said:
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
Click to expand...
Click to collapse
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Thank you ...
Viper The Ripper said:
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Click to expand...
Click to collapse
Yes, found that out - neither this nor Mardon's TWRP version worked on Mardon''s CM11 latest. Took the recovery.image file out of CWM-6.0.5.3-cooper and flashed it using terminal command:
su
flash_image recoveryonly /sdcard/recovery.img
Worked like a charm and all's well now. Would like to know though what settings you recommend on SuperchargerV6 on Mardon's CM 11 with your patch for it installed - have not successfully managed to get it past the Samsung boot screen at 50% Supercharged the two times I have tried.
Thanks again, Steve
Link to dowload
Hi Bhargav97,
I don't found link for to dowload, it's possible that can u send me this link?
Many thaks!
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.