Dual Boot Patcher - Dual boot any ROMs on your Galaxy Grand Prime VE
Huge thanks to @chenxiaolong for his wonderful app, bringing a new life to our device
Now let's get started!
This app 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.
Windows (GUI)
Double click DualBootPatcher.exe 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.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
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:
[LINK] Dual Boot Patcher
[LINK] DualBootUtilities.zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
doesntexits, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-21
Reserved
Reserved
Whats dual boot do?
Owen007 said:
Whats dual boot do?
Click to expand...
Click to collapse
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
naimrlet said:
That means you can install both rom and use it both. Its like when you install another OS on top of Windows
Click to expand...
Click to collapse
Oh ok like in windows gr8 thing. Mean I can have two os.
Owen007 said:
Oh ok like in windows gr8 thing. Mean I can have two os.
Click to expand...
Click to collapse
Like cm13 and 14.1on the same phone or touchwiz and cm
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
d1v1n3 said:
Not Working
it's a great utility bt needs fix. I tried dual booting cm13 but image verification failed when flashing the patched image then i looked up updater-script and removed code block of SHA verification. pathced zip flashed successfully this tym bt still i m not able to boot cm13. dual boot patch app says cant switch the rom then i tred dual boot utilities frm recovery but it also dnt let to continue after the device information screen is shown
Click to expand...
Click to collapse
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Find any lines with "/dev/block/bootdevice/by-name/XXXX", for example:
Code:
block_image_update("/dev/block/bootdevice/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
Change "bootdevice" to "platform/sdio_emmc", like this:
Code:
block_image_update("/dev/block/platform/sdio_emmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
The partitions path I used before for CM13 was for recovery usage only, and DBP seems couldn't find bootdevice path from /dev/block. Also, there's no need to remove system verification from updater-script
Cheers,
working perfectly
doesntexits said:
First, to work with CM13, you have to edit updater-script of the patched ZIP a little bit
Click to expand...
Click to collapse
Thank you so much. i am happy that u have fixed this in the new update of cm13 and yes it's working now. without updating the updater-script i've another question too. there is app sharing feature bt when i try to open that it says that mbltools not enabled and ramdisk needs update. it would be so nice if app sharing can be enabled. any solution for this?
waleeds1 said:
Like cm13 and 14.1on the same phone or touchwiz and cm
Click to expand...
Click to collapse
Any rom m8
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
I know mate. I was giving an example
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
Btw will it heavily affect the space as 8gb rom is really less with arround 3 gb left for use apps and after another rom it will be even less
Thanks for this man !
Can this work on g530h xxu,?
naimrlet said:
Any rom m8
Click to expand...
Click to collapse
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
waleeds1 said:
Is it safe to use this with the 8.0 ROM with Los 14.1 ?
Click to expand...
Click to collapse
Yes, of course. I use this app for the whole time to test new Oreo builds
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Thanks gonna try both of em now, Oreo and this because I was reluctant to switch from your los 14.1 to Oreo untill stable build for Oreo would have been released but now I'll try it.
remilia15 said:
Yes, of course. I use this app for the whole time to test new Oreo builds
Click to expand...
Click to collapse
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
waleeds1 said:
Can you tell me how much system space does the ROM needs as I am running out of system partition while flashing the ROM I have applied the screen shot of how much space I have, the system size is the free storage as I will be removing that ROM. You could look it in the patcher app
Click to expand...
Click to collapse
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
remilia15 said:
For convenience, better keep system partition more than 700MB free space. IMO, most of our N ROMs are more than 600MB big
Or you can install the secondary ROM on SD card or the data partition instead. DBP has that option tho
Click to expand...
Click to collapse
Thanks for the reply, I know it has that option but but I want it to be in system partition so that it doesn't take up other space and also to maintain stability.
Related
READ ALL OF THE OP BEFORE POSTING QUESTIONS
The Intro;
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager is not supported.
Recovery can now boot from NAND instead of the old SD Card boot method, to flash the rom, download the recovery with the partition layout you require, then flash as you would a standard NAND rom using DAF and MAGLDR USB Flasher. then select AD Recovery to load into recovery.
Click to expand...
Click to collapse
MAGLDR v1.13 IS REQUIRED, OLDER VERSIONS ARE NOT SUPPORTED, DOWNLOAD v1.13 HERE
Click to expand...
Click to collapse
Kind note to Devs;
Please stop posting modified flash.cfg files for use with CWM
CWM is designed to make it easier to flash roms without needing a windows PC, if you post a different flash.cfg in each rom thread then it defeats this purpose as a pc will be required for flashing each layout.
Stick to using the default partition layouts or use USB flasher
Click to expand...
Click to collapse
WARNING MESSAGES:
GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH RECOVERY
Click to expand...
Click to collapse
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
Click to expand...
Click to collapse
How to use;
For MAGLDR NAND Boot;
1. Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
2. Extract downloaded file and load magldr into USB Flasher mode.
3. Run DAF.exe and follow instructions
4. After completed and phone reboots, hold power key and select AD Recovery from list
5. Recovery will now load
Click to expand...
Click to collapse
For old style SD Boot;
1. download one of the partition files for SD Boot, if you don't know which one you need, use the 250M one or check with rom developer.
2. Extract downloaded zip to a folder of your choice
3. Copy contents of copy_to_sd_root (initrd.gz and zImage) to the root of your sd card
4. boot into magldr and select USB Flasher option while phone is connected to PC
5. Run DAF.exe included in the zip and follow onscreen instructions.
6. After complete, again boot into magldr and select "Boot AD SD" option
7. ClockworkMod recovery should load, you can flash a rom from here.
Click to expand...
Click to collapse
Video Tutorials;
How To Install Clockwork Mod Recovery On The HD2 (Courtesy of GFurr)
How to Install NAND Android on HTC HD2 with ClockworkMod Recovery? (Courtesy of jayceooi)
Click to expand...
Click to collapse
Downloads;
Latest;
-Download v1.3 150MB-
-Download v1.3 250MB-
-Download v1.3 400MB-
Old Versions;
-v1.2- DOWNLOAD
-v1.1- DOWNLOAD
-v1.0- DOWNLOAD - MegaUpload Mirror
Old Partition Layouts for SD Boot;
-150MB System-
-250MB System-
-400MB System-
Click to expand...
Click to collapse
Changelog;
v1.3;
-Supports AD Recovery in MAGLDR
-MAGLDR v1.13 REQUIRED Download HERE
-400MB Partition layout now works with 512MB LEO for roms with Data2SD
v1.2;
-Fixed SD-EXT Backup/Restore/Wipe
v1.1;
-Updated ClockworkMod to 3.0.0.5, now based on Gingerbread Source
v1.0;
- Initial Release
Click to expand...
Click to collapse
Q&A;
Q. Ive flashed v1.3 but cant access recovery anymore.
A. Make sure you are using MAGLDR 1.13 and are selecting "AD Recovery" instead of "Boot AD SD"
Q. Ive downloaded v1.3 but there is no copy_to_sd folder
A. Recovery no longer requires any files on the SD card, just flash it like a standard nand rom and select "AD Recovery in magldr menu
Q. Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
Click to expand...
Click to collapse
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
Click to expand...
Click to collapse
Notes for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
The cache partition is only 10MB so that recovery can still use it, to get cache to work in android, make a directory in data called cachemnt and on boot symlink /cache to /data/cachemnt, this does not apply when using 150M partition size
Click to expand...
Click to collapse
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
i think i just wet myself....thanks so much
RaiderX303 said:
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager support still has some issues. See below for features and how to use.
Because ROMs are not flashed using DAF, a set partition layout is required before flashing any ROMs using recovery, included in the download is DAF which is configured to create the required partitioning, just run as you normally would to flash a NAND ROM and you are set to flash a new ROM through recovery
WARNING: GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
WARNING: IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH THE PARTITIONING TO USE RECOVERY AGAIN
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
How to use;
1. Copy content of copy_to_sd_root folder to the root of your SD card
2. Power on phone holding power button to access magldr menu
3. Select "USB Flasher" option
4. Run DAF.exe and go through installer to set required partition layout
5. After reboot repeat step 2 to access menu again
6. Select "Boot AD SD" and recovery will load
Download;
-v1.0-DOWNLOAD
Changelog;
v1.0
- Initial Release
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
Request for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
You have to be ****ting me!!! Great work!!! Soon... Nandroid Got Your Back. LOL.
---
Sent from my HD2 DROID.
Great.
Sent from my HTC HD2
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
This is now officially an android phone. Finally get to back up Roms awesome!!!!
Rom manager support is an app that allows you to control the recovery from within Android and then reboot to recovery to run the commands
Sent from my Desire HD using XDA App
Hell Yes
How will I install roms and where will I get them I am confused!
mattfmartin said:
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
Click to expand...
Click to collapse
Rom manager is just the app that that you get from the market to flash without booting to recovery we could wait on that.
what the doctor
this is progress and what ive been looking to add
Just to clarify the instructions... Do we extract the Downloaded zip to the Root of the Sd Card then flash What ROM we will be using? Words in bold are my keys...
Thanks
EDIT: Scratch that.. I guess I should have opened the Zip first.
This is Bad Ass!!
Wow! My dreams have come true
Thanks!
Oh man, this is amazing! Any chance of Amon Ra at some point?
to cool
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Devs will need to release ROMs in update.zip format, there are none currently released although i am in the process of uploading one, you then copy the zip the dev provides to the root of the SD, and flash like you did on the G1
mattfmartin said:
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
Click to expand...
Click to collapse
you will be able to flash themes using recovery once theme devs create them
SWEET!!!!!!!!!!!!
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
+1 good question, are we clear to load nand roms already or do the devs have to modify what they have? I think I will wait until more clarification.
Edit: thanks for the clarification
APJG said:
Oh man, this is amazing! Any chance of Amon Ra at some point?
Click to expand...
Click to collapse
What do u want from me? LOL As a matter of fact if i read this correctly this is almost what i need, a way to flash android ROMs without the usage of a pc (USB port). Can anyone tell me if it is correct
jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Yeah, We need some ROMS converted to flashable.zip's... I'm goning to load up CW now just so I can see it. LOL
Okay these are the steps I took and put as simple as possible.Some steps may be skipped depending on if you have done them or not.These are written based off my setup and what i did.
Disclaimer:Me nor Tassadar or bigsupersquid are responsible for any damage done to your phone so use at your own risk.
Multirom Install:
1.Format through cwm your sd card to have an ext(Recommended 512 mb)
2.Download the two zips from bigsupersquid posted here:http://forum.xda-developers.com/showthread.php?p=20626123#post20626123
3.Place them both onto your sd card.
4.Boot into cwm and flash the cwm zip you downloaded from squid's thread.
5.Now reboot your phone and then boot again into cwm(It should have blue text if it flashed correctly and the multirom option)
6.Now I highly recommend you make a backup of your current rom just in case anything goes wrong.(I made a copy of it onto my pc as well.)
7.Now flash the other zip titled "Multirom..." and wait for it to install.Now reboot to see if it boots.If boots then everything has been done correctly.
Rom on SD Card setup/install:
For this I have install on phone the latest build of cm for oV and will be using the same rom to setup on sd card just for test.
1.Now here Make another backup of your current rom through recovery(Will be used trust me)
2.Now flash the rom you want to use on sd card.(If using a 2.3 rom then the sd card crom msu also be 2.3 and vice versa for 2.2 roms).Reboot phone(a must so dalvik is created correctly).(Make sure to do the appropriate steps fro flash rom like wiping etc.)
3.Reboot back into recovery.Go to multirom and select "Create from current rom". (flash the multirom zip again if it says folder not found)(ROM on the sdcard is placed in /sd-ext/multirom/rom/).
4.After it finished you can go ahead and restore the backup you made in step 1. and the reboot after finished and wait until boot manager shows up.
5.Select boot from sd card and it should boot into the rom you chose to install to sd.(If it doesn't then you did one of the steps wrong).
6.That's it you now have multirom booting enjoy it !
MultiROM recovery menu description:
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Thanks to Tassadar,bigsupersquid,everyone behind cm7 for optimus v and anyone else that contributed to this
Sounds awsome, gotta try the noob friendly lol....dont have patience for the more detailed one ;P
Sent from my LG-VM670 running ICS2.3.7 oc 806~825
any way to get link2sd to work with this. sdext doesn't appear to handle both multirom and link
what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.
Ventrue05 said:
what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.
Click to expand...
Click to collapse
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol
why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.
Ventrue05 said:
why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.
Click to expand...
Click to collapse
Some just like the choice of having two different roms customized differently with different apps and such.
DarkLG said:
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol
Click to expand...
Click to collapse
Plus you can partition a bigger space on your SD card giving you more room for apps
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
Hmm guess nobody has a answer to this...
eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.
tdmcode said:
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.
Click to expand...
Click to collapse
Something was not working right because a couple people using the multi recovery couldnt get rzrecovery to install. Not sure if they got IHO installed or not. I have a feeling something is not allowing flash_image to work properly with that recovery.
I just wanted to see what the devs of this recovery thought.
Tetris from recovery is worth it by itself! havn't installed a second rom yet but this is cool anyways
Dual Boot Patcher - Dual boot any ROMs on your Galaxy E5
Huge thanks to @chenxiaolong for his wonderful app, bringing this app
Now let's get started!
This app 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.
Windows (GUI)
Double click DualBootPatcher.exe 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
cm13-e53g.zip
would create a new
cm13-e53g_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.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
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:
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
XDA:DevDB Information
Dual Boot Patcher, Tool/Utility for the Samsung Galaxy E5
Contributors
@nepalbiraj, @chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
PRESS THE THANKS BUTOON IF IT WAS USEFUL TO YOU
Version Information
Status: Testing
Created 2017-01-23
Last Updated2017-01-23
UPDATE #NEW METHOD COMING
AND USING THAT U DONT HAVE TO MAKE ANY CHANGE IN ROM ZIP FILE EVERY TIME
AND A VIDEO ALSO I AM WORKING TO MAKE THE PROCESS MORE easily UNDERSTANDABLE
Pre requisite
1. unlocked bootloader
2. Root
3. Twrp installed
4. Pc
5. Or usb otg
My guide assumes
Primary rom - stock zenui rom or can be any rom u r using
Secondary rom - aoscp extended latest build
Dualboot means- installing roms on yoyr device without wiping your current rom, so rom called secondary rom can be installed on internal storage itself, or sdcard, usb
In this guide i have used sdcard for installing secondary rom
Steps
First we have to partition our sdcard so backup everything to pc as sdcard will be erased
.Install Aparted from playstore or download from attachment
.Open the app A parted. Grant root
.Goto tools tab select partition 1 it should be ur sdcard
Select delete from below and click apply
. now goto create and click add use this as fat32 size as u wish
. again click add now this will be ur system partition so use this as ext4 size min. 3000mb
. again click add ext4 for data partition and size should be something around 5000mb min. Max depends on ur sdcard space
. add cache partition ext4 size min. 100mb
.now apply the changes.
Now u have prepare ur rom zip file .
First unzip the rom
Just replace the attached boot.img with boot.img in ur rom zip file and same do with updater script
Location of updater script is metainf/com/google/android
And then repack the rom file into zip
Now flash the attached twrp recovery
Boot into new twrp goto wipe
Change file system
Select system, format as ext4
Go back select data and format as ext4
And do same with cache
Now what
Just copy ur new rom zip file onto sdacrd after formatting and flash it
Gapps simply flash
For switching roms
Just install flashify from playstore and flash the boot.img of the rom u want to use
I know above guide is not full fledged but if u get stuck anywhere just comment i am here to help
But if u are a developer u may have know the proces by ur own
Sorry for my bad english
Press thanks if i helped you. :good::laugh:
Thanks to rom developers coz without them there was no need of dualboot
And if u want to use another rom as dualboot just telegram me its boot.img and updater script
I will provide u the modified one
Id. ady692
https://drive.google.com/file/d/0B8O22xDxCq2FWm5KNThNaWtiOHc/view?usp=drivesdk
addy692 said:
Pre requisite
1. unlocked bootloader
2. Root
3. Twrp installed
4. Pc
5. Or usb otg
My guide assumes
Primary rom - stock zenui rom or can be any rom u r using
Secondary rom - aoscp extended latest build
Dualboot means- installing roms on yoyr device without wiping your current rom, so rom called secondary rom can be installed on internal storage itself, or sdcard, usb
In this guide i have used sdcard for installing secondary rom
Steps
First we have to partition our sdcard so backup everything to pc as sdcard will be erased
.Install Aparted from playstore or download from attachment
.Open the app A parted. Grant root
.Goto tools tab select partition 1 it should be ur sdcard
Select delete from below and click apply
. now goto create and click add use this as fat32 size as u wish
. again click add now this will be ur system partition so use this as ext4 size min. 3000mb
. again click add ext4 for data partition and size should be something around 5000mb min. Max depends on ur sdcard space
. add cache partition ext4 size min. 100mb
.now apply the changes.
Now u have prepare ur rom zip file .
First unzip the rom
Just replace the attached boot.img with boot.img in ur rom zip file and same do with updater script
Location of updater script is metainf/com/google/android
And then repack the rom file into zip
Now flash the attached twrp recovery
Boot into new twrp goto wipe
Change file system
Select system, format as ext4
Go back select data and format as ext4
And do same with cache
Now what
Just copy ur new rom zip file onto sdacrd after formatting and flash it
Gapps simply flash
For switching roms
Just install flashify from playstore and flash the boot.img of the rom u want to use
I know above guide is not full fledged but if u get stuck anywhere just comment i am here to help
But if u are a developer u may have know the proces by ur own
Sorry for my bad english
Press thanks if i helped you. :good::laugh:
Thanks to rom developers coz without them there was no need of dualboot
And if u want to use another rom as dualboot just telegram me its boot.img and updater script
I will provide u the modified one
Id. ady692
https://drive.google.com/file/d/0B8O22xDxCq2FWm5KNThNaWtiOHc/view?usp=drivesdk
Click to expand...
Click to collapse
Please comment below
How this guide can be improved
Upcoming support.
#dualboot patcher support
Wanna work together so that we make it comparatable with twrp...and users can use it directly
govind1233 said:
Wanna work together so that we make it comparatable with twrp...and users can use it directly
Click to expand...
Click to collapse
Yeah anytime
U can contact me on telegram @ady692
addy692 said:
Please comment below
How this guide can be improved
Upcoming support.
#dualboot patcher support
Click to expand...
Click to collapse
Awesome :good: Nice work buddy
prakharluv said:
Awesome :good: Nice work buddy
Click to expand...
Click to collapse
thanks @prakharluv
Totally based-off project MultiBoot by @chenxiaolong (the real MVP) has now been ported to Lenovo A7000-a. Check the Official Thread
Keeping all details short, I would like to warn people that neither Me nor the original developer is responsible for any damage that took place to your device.
Disclaimer:
Code:
/*
* Your warranty is now not void.
*
* We are not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
How to use the patcher
(taken from original-dev thread)
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
DareAOSP-N.zip
would create a new
DareAOSP-N_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.
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.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
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:
DualBootPatcher (Supported Devices)
DualBootApp (switch ROM when booted to Primary/Secondary ROM)
Source Code: GitHub Pull Request
Reserved. (till it gets OFFICIAL)
Damn bro, You're the best xD. Can't wait to try this
God _/\_
Awesome
Why? I dont know use dual boot
It works but sometimes no boot.img is created for secondary rom (needs to flash patched kernel)
Also the dualboot utilities always freeze after tapping next button
Currently dual booting cm13 by @HDHR and your Aospextend , no problems encountered so far.
Edit : also needs to patch device allocator for secondary rom to properly switch roms
So the DualBootPatch is now official.
Check Post #1 for more details
Rohan Taneja said:
So the DualBootPatch is now official.
Check Post #1 for more details
Click to expand...
Click to collapse
Hurray :laugh:
app problem
every thing is working only when I open ROM app stops working .
any solutions?
thank you