Related
Hello!
I have been searching the forums here about custom roms, and so far, I saw two methods of how to install them.
Method1. update.zip
Method2. Backup/Restore or just advanced restore.
(both in xRecovery)
What's the difference?
If the developer of the rom stated do Method1, can we still do Method2?
Will it affect anything?
Thanks.
You cannot do the other method, it´s not possible, because they are completely different .
Method 2"restore" is like you make a backup trougth xrecovery and restore it. You can do a complete restore (recommended) or only system (your data will be not deleted, but in most cases you will have some problems)
Method 1 update.zip is a kind of script.
Fetz Braun said:
You cannot do the other method, it´s not possible, because they are completely different .
Method 2"restore" is like you make a backup trougth xrecovery and restore it. You can do a complete restore (recommended) or only system (your data will be not deleted, but in most cases you will have some problems)
Method 1 update.zip is a kind of script.
Click to expand...
Click to collapse
Thanks for that!
So you mean, Method1 is like, if you want to upgrade your rom?
Will doing Method1 erase all data?
It depends on a script. There is a file called update-script in every update and custom zip, you can view it in notepad++. If it contains FORMAT command it will wipe any partition that is named after the command. Most ROMs update zips only wipe system, which is a necessity, since you need to put new system in. Some ROMs, like doixanh's one, also wipe cache to get rid of old ROM's stuff. If there is a format data instruction, all your data and apps are gone.
Hello,
Can someone tell if it's wise to upgrade my Tytung R13 Kernel to R14 or Dorimanx kernel?
I like to have a better battery life.
How do I have to upgrade to a "better" Kernel without losing all my apps and settings?
Hope someone can provide me some answers.
Greetings Matthieu.
Put the Dorimax kernel zip file in the root of your SD.
switch your phone off
switch it on again holding down the power button until the menu comes up
select install zip from SD
navigate to the Dorimax zip and install that.
then reboot your phone!
(if you're using NAND Android!)
I use r14 with Tytung's Gingerbread ROM. Tried several earlier versions of Dorimax's kernel and had terrible luck with them. Lost app linkages mainly and Titanium Backup even though I was using the correct zip file created by a forum user on Tytung's thread. Going to the hidden phone menu I switched my phone to use GSM only and this reduced the battery drain from WCDMA preferred which is the default.
What ROM do you use? The original Tytung kernel thread and included file is for Tytung's ROM. For compatibility, somebody has suggested to replace the initrd.gz file with the one in your ROM before flashing.
You can try Tytung 14. It is good and stable. If you like to do some adventure and something exciting but a little dangerous, try Dorimanx. Dorimanx is a crazy developer. The speed of kernel and ROM updates is high. I will recommend to try Dorimanx kernel v3.3 and 4.1. Both of them work on my Typhoon ROM.
Hello,
Thanks for the answers. I use the NexusHD2 Gingerbread V3.2a rom with Tytungs R13 kernel.
I read something about the initrd.gz file. Do I have to do something with that file before upgrading to Tytungs R14 or is there a complete zipfile and can I install it just as mentioned in the second post without losing anything? Is the batterylife better with R14 or Dorimanx 4.1 instead of R13?
I am just a beginner and want to extend the usage of my HD2.
Thanks.
Greetings Matthieu.
Go to the kernel thread by Tytung http://forum.xda-developers.com/showthread.php?t=1258110. The kernel is just all you need.
The ROM you use is his work, too. Nothing have to be changed before flashing. Just do it. Have fun.
I am not sure if battery life if better in R14. You can try it. Flashing the kernel you will not lose anything. If you want to do some cleansing work, just wipe cache, Dalvik cache (in advanced setting), and fix permission. Do not wipe system/factory reset.
Thanks!! I hit the thanksbutton for you...
Is it also possible to just put a dorimanx 4.1 zipfile on my sd card and install it without doing extra actions (like installing extra files)? I am a noob with this so....
Greetings Matthieu.
Yes, in Dorimanx v4.1 the initrd.gz files from CM/MIUI/ICS are incl. in the kernel. While flashing you can choose your system. Though the file you are looking for, initrd.gz, is located in your ROM's .ZIP. just open it en you will find the file under /boot, extract initrd.gz en extract the Dorimanx .ZIP and place initrd.gz in the initrd-custom directrory. Last but not least you need to select all the exctracted files from the Dorimanx .zip (incl the initrd-custom folder with your custom initrd.gz) and make a new .ZIP!
Correct me if i'm wrong!? =P
can I flash Dorimanx kernal to sense roms?
Hi, I'm trying various kernels on my rom.
Therefore I'd like to backup my existing kernel.
I know TWRP can easily do this.
However for information I'd like to know manual adb method, or terminal commands.
Or is there a Zip file which I can run to automate the process
why not just keep the kernel zip file in your storage?
as a hobby, i test kernels, trinity kernel to be exact. i probably have 20-30 kernels in my storage at all times. when im want to run my favorite again, i just reflash it. i cant imagine why id want to back up a kernel.
Dual Boot for SGSA
So many devices are getting Dual Boot capability nowadays.So i decided to do same for our beloved SGSA.
EDIT : Guide Updated. Using slow sdcard as /system and /data was bad idea. Now secondary ROM work at same speed as primary ROM since we aren't using external SD card anymore
Read first three posts carefully before doing anything
Highlights:
No lags, bugs.Both ROMs works almost same
Stable. Booting of ROM is based on kernel. So as long as you stay on a kernel it'll keep booting ROM for which it is designed without interference with another ROM.
ROM can be switched by changing Kernel.
Stock ROM fully supported. Now you can feel speed of CM ROM with stability of stock ROM
Click to expand...
Click to collapse
How to use this:
Well, steps are quite easy.Just follow them one by one and you won't get any troubles.But please follow steps one by one, don't take shortcuts.
On PC extract ROM which you want to install as secondary ROM.
You'll get following files/folders there : META-INF, system, boot.img
Delete META-INF and boot.img
Download appropriate META-INF_*.zip from downloads section.Extract it and move extracted META-INF folder to location from where we deleted META-INF.
Navigate to /system folder and move folder named app to parent folder (i.e. if app folder is located at C:\blah\system\app then move it to C:\blah\app)
Select three folders (META-INF, system, app) and compress them to zip format.Push this file to device.
All above steps are mentioned in below video
Download appropriate Kernel from Downloads sections.
Flash that kernel using Universal Kernel Flash Tool or by writing in terminal dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
Power off your device
Now reboot into recovery by holding VOL UP + HOME + POWER (don't take shortcut here )
Ignore any warnings recovery shows.
Install the zip file which you pushed before as you install normally (Do not use Wipe options)
Download appropriate GAPPS package from download section (Do not install normal gapps.To know reason, read third post)
Reboot it.That's all (Keep in mind, first boot always takes long time)
If WiFi don't work on secondary ROM then flash appropriate modules from Downloads section
Read "Things to keep in mind" in third post.
Click to expand...
Click to collapse
How to switch ROM:
Flash kernels provided here to boot secondary ROM.
Flash native kernel (which comes with ROM) to boot primary ROM. (If you're using CM based primary ROM then take backup of stock CM kernel before flashing another kernel.)
Click to expand...
Click to collapse
How to change ROM:
Boot up your primary ROM.
Navigate to /data
Delete folder : /data/secondary_data
Now flash secondary Kernel and flash secondary ROM as you would.
or you can use my App for doing this stuff...
Click to expand...
Click to collapse
Using DualBoot App:
After installing secondary ROM as mentioned above, you can use my Dual Boot app to switch easily between ROMs. Additionally you can also use it for other options like sharing installed apps, factory reset secondary ROM etc. It will automatically download required kernel (Read third post). App is easy to use, just install it as Normal apk. You can also share this app with secondary ROM as mentioned below.
Wipe data/factory Reset - Factory reset secondary ROM
Share Apps with Primary - Share all apps of primary ROM with secondary ROM. This will reduce space used by secondary ROM. Use this option with CAUTION because some apps like Play store can FC. So it is better to use custom share apps option.
Revert Share Apps with Primary - This will remove all installed apps of secondary ROM
Custom Share Apps - Best way to share installed apps on primary with secondary ROM. Share as much apps as possible to reduce storage usage by secondary ROM.
Clean UP - Removes all files used in DualBoot mode
And more to come...
{
"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"
}
Click to expand...
Click to collapse
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
Technical info:
--> Mounted /dev/block/mmcblk0p4 as /system
--> Since it is smaller (300 MB) in size we're symlinking /system/app folder of secondary rom to /data/app
--> Using /data partition for both /data & /cache of secondary ROM
Click to expand...
Click to collapse
Future Plans:
An App so things become more easy (done)
Kexec support in kernel (WIP)
Click to expand...
Click to collapse
Sources:
Kernel Sources : Checkout TeamCanjica's repo
DualBoot App : Github
Click to expand...
Click to collapse
I'm writing an app for this.Once it is completed it would be much easier to do this thing
As usual, i don't take any responsibility of bricked devices, nuclear wars etc...
Downloads & Changelog
Downloads:
EDIT:
Since Dev-Host removed all my files i've re uploaded them to mediafire (Link to folder below). Since all files are removed from my account DualBoot app won't be able to download kernels. So manually download them and put them on sd card as instructed.
META-INF:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK) || Liquid Smooth 3.0
Click to expand...
Click to collapse
Kernel:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK)
Click to expand...
Click to collapse
Modules:
CM 11
Click to expand...
Click to collapse
GAPPS:
CM 10.1 || CM 10.2 || CM 11
Click to expand...
Click to collapse
Download META_INF, Kernels, GApps:
Mediafire Folder
Click to expand...
Click to collapse
DualBoot Application:
DualBoot v1.22
Click to expand...
Click to collapse
Changelog:
27/04/14 ---> Fixed FC problem on CM11, Kernel with OC support (same as TC's last release)
21/02/14 ---> Liquid Smooth 3.0 Support
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI v5 Support
21/01/14 ---> DualBoot App released, Updated META-INF folder for latest CM10.2 to fix errors
08/01/14 ---> Fixed bug with CM11 which was preventing it from booting second time
06/01/14 ---> CM11 support
04/01/14 ---> No need for external SD card.Both ROMs work at same speed, no more lagginess
11/11/13 ---> Initial Release
Click to expand...
Click to collapse
DualBoot App Changelog:
27/04/14 ---> Unsupported device problem fixed, Updated all kernel links
12/02/14 ---> Fixed AOSP, Removed app folder share (use custom app share instead)
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI support. Allows user to flash unknown kernel to use any ROM as Primary ROM
21/01/14 ---> Initial Release
Click to expand...
Click to collapse
Pros, cons, Tips, Future Plans
FAQs:
Q. How can i factory reset second ROM?
A. Boot into primary ROM and go to /data/secondary_data using any explorer and delete following folders : cache, data
Click to expand...
Click to collapse
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder.Now delete all contents of /cache folder.
Click to expand...
Click to collapse
Q. WiFi is not working on secondary ROM. What should i do?
A. Boot into secondary ROM's recovery and flash appropriate modules from downloads section
Click to expand...
Click to collapse
Things to keep in mind:
Wipe/data Factory reset from primary ROM will remove secondary ROM also.
Do not wipe cache partition after installing this mod (for both primary & secondary ROMs).
Don't touch anything other than install zip ( like wipe data/cache etc because they'll lead to unexpected results ) when using secondary ROM's recovery.
We're running out of space for /system partition in secondary ROM so please don't keep flashing random tweaks, mods which put files on /system partition.If it is emergency then use /preload partition and symlink them manually.
Do not install GAPPS for secondary ROM.Use only which i provided.
When CM based ROM is installed as secondary ROM then by default swap functionality is disabled on /preload (which TeamCanjica enabled).So stock ROM as primary ROM is compatible.
Ignore any warnings shown by secondary recovery.If you get any error then contact me.
Provided GAPPS are not full gapps it'll only install Play Store s that you can install other apps from market.
We have 2GB space in /data partition.I've been using this device for 9 months and it never took more than 1GB space on /data.But still if you're finding less storage then move some apps to sdcard.Still if you need more then contact me, we'll move some more files.
If you want to dual boot CM & stock ROM then it is necessary to install stock as primary because they're huge to be included on /cache partition.Although it is not impossible, if you're expert there, then you can create symlinks to make it work.But i won't support that way.So secondary ROM must be CM based.
Backup/Restore function won't work with secondary ROM
When wiping primary rom, it is impossible to save secondary rom unless you made backup.
Even though Dual Boot app downloads kernel automatically, it is advised that you download required kernels & manually and put them in proper folder ({internalsdcard}/DualBoot/) to avoid bad & corrupt downloads. In case if this happens & you phone don't boot up, don't worry, just flash stock kernel with odin & everything will be fine.
Click to expand...
Click to collapse
How to add Support for Unsupported ROM:
This tutorial will help you to add support for those ROMs which are based on already supported ROMs (like CM11, CM10.2 etc). This tutorial will teach you to create META-INF folder for particular ROM to avoid status 7 error. Please follow it carefully
Open META-INF\com\google\android\updater-script
Find and delete following code/ same code
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
Now find
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
& replace /dev/block/mmcblk0p3 with /dev/block/mmcblk0p4
Search for package_extract_dir("system", "/system"); & add this code after it
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/primary_data");
run_program("/sbin/busybox", "mkdir", "-p", "/primary_data/secondary_data/system");
delete_recursive("/primary_data/secondary_data/system");
package_extract_dir("app", "/primary_data/secondary_data/system");
symlink("/primary_data/secondary_data/system", "/system/app");
At the end of the script remove package_extract_file("boot.img", "/dev/block/mmcblk0p15"); or anything related to kernel flashing like write_raw_image etc.
Click to expand...
Click to collapse
Awesome...:good:
Wanted to try it but I have a 2gb memory card...
So I will have to Wait till my new memory card arrives:fingers-crossed:
i have a class 10 sd card..i ll try this as soon as i can..just a thing...AWESOME
Sent from my GT-I9070 using XDA Premium 4 mobile app
tried but not work. it just boot direct to recovery
wmfaiz said:
tried but not work. it just boot direct to recovery
Click to expand...
Click to collapse
Yep because you messed up with our param drivers.As i told before don't use any command like reboot recovery and don't use 4 way reboot (if your ROM supports) to enter recovery.This will keep you throwing into recovery.The solution is flash primary ROM's kernel then reboot normally.Use UKF to flash secondary kernel.Now power off your device and then use Hardware keys to enter recovery or if you've already installed secondary ROM then power on normally.
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
frapeti said:
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Thanks.I'm waiting for next build because last build has lzma compressed zImage.
dual boot?
cool...
I was used dual boot on my old device Galaxy Tab 2, very useful for testing a new rom before become it that rom as primary rom for daily use
great work
Update
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Many thanks for your hardwork man! For achieving dual boot on our device and keep on simplify the method of doing it. It is also happy to see that there is another app under developing to make things more easier, i will definitely try this out once i finished my exam!
Thanks a lot man :thumbup:
I will use it when you will add CM 11 compatibility.
BOOTMGR said:
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Click to expand...
Click to collapse
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
<O.T>
+1 to each thing in above post....
let me again tell u that you r really really AWESOME :angel: :laugh:
btw idea of debloating HJ is good ......personally i'm using heavily debloated HJ without any feature loss
BOOTMGR said:
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
I assume Primary ROM must be 4.0 or higher and not GB?
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
anantttt said:
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
Click to expand...
Click to collapse
Yeah it can be fitted as secondary ROM by debloating.But still some users will ask for some features.We can even use symlinks and can place it as secondary ROM without debloating it but it'll raise complexities.So it is better to use it as secondary ROM.
Odexing and placing them on /preload i also nice idead.But still i'll prefer to use it as primary ROM...
BTW,HarshJelly seems better than BOOTMGRjelly...:silly:
purplepizza said:
I assume Primary ROM must be 4.0 or higher and not GB?
Click to expand...
Click to collapse
Yeah.No support for GB (i'll think about it.If there won't be much difference (except baseband) between GB and JB we can also do it.)
darcik said:
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
Click to expand...
Click to collapse
Yesterday @Sami Kabir asked same question on FB group.Here is the answer.
Only apps can be shared between both ROMs not their data.The reason is that data of system apps and normal data apps both are stored under same folder (/data/data).So can't we share this folder? answer is no because namespace conflicts will arise there (Ex. package name for phone app is com.android.phone.It'll remain same for all android versions.It is possible that use have installed both ROMs of different API level.So if one phone app stores its data under /data/data then other won't be able to read it and you'll get FC)
Although it is possible to share apps between two apps.When i'll complete app, i'll provide an option for that....:good:
Cache partition
FAQs:
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder
Click to expand...
Click to collapse
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
CM11 Support
darcik said:
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
Click to expand...
Click to collapse
Yeah i forgot to write, you also need to delete contents of /cache folder or format cache partition.
That partition is like placebo.It is only used when upgrading android (that means generating dalvik cache (actually that partition was used to store dalvik cache but later on dalvik cache was also moved to /data partition so its useless now except time of generation of dalvik cache)
@all:
Added CM11 support.
Links are up.
Method remains same.
I've checked way to share apps between ROMs (and thus storage use will be much less).
I'll let user to choose whether to share apps or not which will be possible through DualBoot app.
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.