WELCOME
Dual Boot Patcher
I am proud to present to you, Dual Boot Patcher for j510!
Code:
Disclaimer:
I am not responsible for any bricked devices lost data or national disasters. Use at your own risk
Features:
Run two or more roms on your device at the same time!
Able to patch rom zips, custom kernels, gapps, supersu zips etc
Clean Material UI
Boot UI which allows you to select ROM at boot
App Sharing between Roms
Backup and Restore roms
Note: If the app is saying that this device is not supported and you have j510, edit your build.prop to set ro.build.product and ro.product.device to "j5xnlte". Then reboot. The app should be working. Do this only if you have j510. If you set the values improperly, installing a dual boot zip will hard brick your device.
TUTORIAL:
NOTE:Make a full nandroid backup before proceeding!!
Install your first ROM normally(from TWRP). It is recommended that if you want to multiboot an AROMA ROM, you should install it first(as primary). If you want to make your current rom as primary, skip this step.
Download and install the apk provided in the attachments.
Download the second rom.
Open the Dual Boot Patcher app, in the left swipe-in menu, select ROM section
It will ask you to set the kernel for Primary Rom. press Ok
Then go to "Patch zip file" menu, and click on the red "add" button
Then select "Add flashable zip". It will ask you to select a rom zip. Browse to your downloaded ROM and long-press to select it.
It will then ask you where to install it. You can Either Install it in "Secondary" which will install the Rom in system partition(use this if you have enough space on your system partition( at least 1.1 GB for AOSP roms and 1.8 GB for Touchwiz Roms). If you dont have enough space on your system partition, install it in Data or ext sd slot.(Note that installing in Data will take up space from your internal memory. DO not select the "multi slots"! they are for other devices
Click on OK. it will ask you the location of target file, just click on select to use defaults.
if you have any additional zips(such as gapps or supersu) patch them all using the above method. Select the same setting you used for the ROM!
After you have added all your zips, Click on the tick in the upper right corner and the patching will begin!
After Patching is done, reboot to recovery. DO NOT WIPE ANYTHING. Just install the zips you just patched(they will have "Dual" or "Data slot" written in front of their names.
After installation is complete, click reboot, and it will reboot to your newly installed ROM. Set up the rom normally. After setup is complete, install the DualBootPatcher apk.
Now you can select whichever ROM you want in the app. Just select it and restart!
From now onwards patch every zip with dual boot patcher before installing!
Boot UI
If you want Boot ui, follow these steps:
Go to roms section of the app. Press the 3 dots next to your first rom then scroll down and select update ramdisk. then press ok. It will ask you to reboot. just press reboot later
Repeat the same with other roms
Then go to settings and select install Boot ui.
Download Apk
DualBootUtilities
If anything goes wrong with the DualBoot keep the utilities zip in your sdcard. You can flash it in recovery(AROMA only). It allows you to wipe any rom installed on your device or switch to any rom.
Download Utilities
UPDATES
Update1:
Performance Improvements
Now you can restore backup to primary and secondary locations too(previously gave error)
Update2:
Added j5xnltexx to supported device codenames
Performance improvements
This app is not mine. I added support for dual boot on J5 2016.
This app is licensed under GPL. As per its requirements, here is the source code:
https://github.com/RIPT1DE/DualBootPatcher
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Boot ui not supported ?
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
This not work either
Moshifan100 said:
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Click to expand...
Click to collapse
No changes to the master branch as I am keeping it in sync with the original developer's master. The changes are in branch j510fn_support.
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
Bro change ro.build.product and ro.product.device in build. Prop to j5xnlte.
Wizardlysense said:
This not work either
Click to expand...
Click to collapse
Also if the above doesn't work send me the update.log
__riptide__ said:
Also if the above doesn't work send me the update.log
Click to expand...
Click to collapse
Here
Wizardlysense said:
Here
Click to expand...
Click to collapse
Did you give storage and root permission?
__riptide__ said:
Did you give storage and root permission?
Click to expand...
Click to collapse
Yup
Wizardlysense said:
Yup
Click to expand...
Click to collapse
Ok. Then can you send me a copy of your build. Prop?
Guyz, this is perfectly working for me.
Just follow the instructions.
@Wizardlysense I have edited my post with further instructions. Try those. If it's still not working, we will and figure it out.
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Incredible! Just incredible! Works fine with a5ux and lineage os!
GlitchWolf said:
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Click to expand...
Click to collapse
What is the error?
doc_elias said:
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Click to expand...
Click to collapse
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
gzdc said:
Incredible! Just incredible! Works fine with a5ux and lineage os!
Click to expand...
Click to collapse
Same here.. Great Work! Amazing!
__riptide__ said:
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
Click to expand...
Click to collapse
Everything working fine.
Related
So I'm back from funeral, It was awful but death is a natural process of our daily lives.
This is a ROM for GT-I8190N
I need someone to test it.
Tweaks:
Code:
- many build.prop tweaks
- Battery tweak
- sqlite_optimize
- Darky ziaplign
- V6 120MB LMK Addon
- Adrenaline v3 Booster
- Bravia Engine
- xLoud Engine
Everything in leather.face's script is in this ROM
Mods:
Code:
Added: A custom power menu with Download and Recovery options.
Added: AOSP Lockscreen
Added: Long press back button to kill an app
Fixed: S-Beam not showing in the Settings menu (hopefully)
Fixed: NFC Service Force Close
Instructions
1. download the zip file
2. put the zip file onto your sd card
3. reboot into recovery
4. flash I8190NDXALL5-BenzROM-signed.zip file from your sd card
6. reboot
ROM is wipe for better compatibility. Backup your data before proceeding
Download Link - ROM <<< Click.
Thanks to Chainfire for his root.
Thanks to leather.face for his script.
Thanks to my country neighbour dariolob for his build.prop tweaks. They work great.
Benzonat0r said:
So I'm back from funeral, It was awful but death is a natural process of our daily lives.
This is a ROM for GT-I8190N
I need someone to test it.
Tweaks:
Code:
- many build.prop tweaks
- Battery tweak
- sqlite_optimize
- Darky ziaplign
- V6 120MB LMK Addon
- Adrenaline v3 Booster
- Bravia Engine
- xLoud Engine
Mods:
Code:
Added: A custom power menu with Download and Recovery options.
Added: AOSP Lockscreen
Added: RippleEffect Lockcsreen
Added: Long press back button to kill an app
Everything in leather.face's script is in this ROM
Instructions
1. download the zip file
2. put the zip file onto your sd card
3. reboot into recovery
4. flash I8190NDXALL5-BenzROM-signed.zip file from your sd card
6. reboot
ROM is wipe for better compatibility. Backup your data before proceeding
Download Link - ROM <<< Click.
Thanks to Chainfire for his root.
Thanks to leather.face for his script.
Thanks to my country neighbour dariolob for his build.prop tweaks. They work great.
Click to expand...
Click to collapse
i'll try this and report back later....basically just install from cwm recovery right? need to wipe cache and dalvic?
benz, i've installed the rom...unfortunately, the nfc failed to load....dialog box keep popping up with message "unfortunately nfc service had stopped"....had to restore nandroid backup.....hopefully this can be resolved..
Go to root explorer, navigate to /system/app or /system/framework and delete any .odex files you can find in there, but first give me the names of all .odex files in there.
Edit: I think I've found a solution.
Flash Odex-remove_I8190N.zip attached below and report back.
Benzonat0r said:
Go to root explorer, navigate to /system/app or /system/framework and delete any .odex files you can find in there, but first give me the names of all .odex files in there.
Edit: I think I've found a solution.
Flash Odex-remove_I8190N.zip attached below and report back.
Click to expand...
Click to collapse
so far so good....will report back after 3-4 days usage....thanks benz...:good:
You're welcome. It seems we've figured it out.
Benzonat0r said:
You're welcome. It seems we've figured it out.
Click to expand...
Click to collapse
one thing missing....the s-beam from the setting menu....roms seems smoother...
Thanks. I accidentally removed the string for S-Beam in res/values/strings.xml.
It'll be added again soon.
Edit:
Flash it via CWM/TWRP
http://www.4shared.com/zip/YMJIJtKg/CWM-Settings.html?
ROM updated, first post updated.
Benzonat0r said:
ROM updated, first post updated.
Click to expand...
Click to collapse
greatts benz....:good: guess this is the first custom roms for the N version.....the free space is hugeee...stock rom occupied around 500mb....this one around 200mb....the s-beam function not able to test right now,but the setting is there where it should be....
Flashed it without an issue, but for some reason it gets stuck on first page of setup wizard. Every time I click next it crashes and restarts.
Any advice for that?
Agyar said:
Flashed it without an issue, but for some reason it gets stuck on first page of setup wizard. Every time I click next it crashes and restarts.
Any advice for that?
Click to expand...
Click to collapse
try follow this sequence :
1-install the rom from cwm
2-install the odex zip file
3-reboot and set up phone
4-reboot recovery flash the cwm setting....
mine got stuck several time in the samsung initial setting.....the select language to be exact....
You don't have to flash Odex-remove anymore because the script now deletes /system/app and /system/framework directories.
Wait I'll update the ROM again
nazri5363 said:
try follow this sequence :
1-install the rom from cwm
2-install the odex zip file
3-reboot and set up phone
4-reboot recovery flash the cwm setting....
mine got stuck several time in the samsung initial setting.....the select language to be exact....
Click to expand...
Click to collapse
Thanks
Will try this. Got stucked on select language part also. When clicking next there it stucks.
Can you just give few more sentances of explanations for step 4?
Thanks again
ROM updated, download link updated.
Try it now.
Benzonat0r said:
ROM updated, download link updated.
Try it now.
Click to expand...
Click to collapse
benz,i apply the cwm cm10 black notification here http://forum.xda-developers.com/showthread.php?t=2119219 and the battery tweaks is missing, (the monitor battery usage function) can u look into it if u have the time...thanks.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Agyar said:
Thanks
Will try this. Got stucked on select language part also. When clicking next there it stucks.
Can you just give few more sentances of explanations for step 4?
Thanks again
Click to expand...
Click to collapse
op updated first page....just flash it...should be ok now....seems like only 2 people here owned the N version....huhu....
Flashed latest updae and now everything works!
Nice and smooth so far
Thnx for doing something for two of us
nazri5363 said:
benz,i apply the cwm cm10 black notification here http://forum.xda-developers.com/showthread.php?t=2119219 and the battery tweaks is missing, (the monitor battery usage function) can u look into it if u have the time...thanks.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
op updated first page....just flash it...should be ok now....seems like only 2 people here owned the N version....huhu....
Click to expand...
Click to collapse
You can flash the one from there, files are the same.
Agyar said:
Flashed latest updae and now everything works!
Nice and smooth so far
Thnx for doing something for two of us
Click to expand...
Click to collapse
You're welcome.
Hey benz My S3 mini turned out to be the N version so I'm going to flash this right now
Ota with these apps installed is impossible ! Full flash stock rom before ota
This is at your own risk !
I am not responsible for dead sdcards, thermonuclear war or you getting fired because the alarm app failed
If you point the finger at me for messing up your device, I will laugh at you
I am not responsible if your phone becomes a hipster and claims to have been modified before it was cool
I am not responsible for what you do with your computer, be it a laptop or a desktop/whatever and your phone as well
What are c-apps ?
https://cyngn.com/c-apps
Click the link to learn more
Requirements :-
C-apps package
Es file explorer OR aroma file manager
1) Install es file explorer (or boot to twrp, mount system in options, disable only mount system read-only and flash aroma file manager)
2) (Es file explorer users only) enable root explorer and mount system read-write
3) now rename /system/priv-app/dialer -> /system/priv-app/dialerx
4) similarly, rename /system/app/incallui -> /system/app/incalluix
5) (es file explorer users only) you may experience app crashes. Don't worry about them and reboot to twrp
6) flash c-apps package
7) (aroma file manager users only) mount system read-write in twrp options and disable the mount system read-only checkbox, then flash aroma file manager again and rename /system/app/incalluix -> /system/app/incallui (remove the x) and do the same to /system/priv-app/dialerx -> /system/priv-app/dialer (remove the x, do not change the case of the letters ! )
8) (aroma file manager users only) exit it and reboot to system
9) (es file explorer users only) follow step 7 after booting into android
10) (es file explorer users only) reboot your phone
11) now, disable these apps after booting into android (they do not work)
(I couldn't find the time to upload screenshots, coming soon !)
Edit :- screenshots added, check attachments
Truedialer works (partially, incallui doesn't work, dualsim works) but I prefer stock that is why I disabled it
Only use 1 dialer app or they may conflict !
Working :-
Cm account
Gallery
Email
Calendar
True caller service
Cm anti-theft
Screencast screen recorder
Etc etc
Audiofx is not working but maxxaudio tuner and audiofx are the same thing
Thanks, it works.
1. I couldn't find "disable only mount system read-only" in TWRP. Anyway, I flashed Aroma File Manager,
2. renamed said files, exited Aroma,
3. flashed C-Apps package,
4. again flashed Aroma, went inside /system to rename files, they were replaced by DailerNext and InCallUiNext, exited Aroma,
5. rebooted to system.
6. Found that stock apps have been replaced(Nevermind, I'm not fan of them anyway).
I followed TWRP procedure.
krishna442 said:
Thanks, it works.
1. I couldn't find "disable only mount system read-only" in TWRP. Anyway, I flashed Aroma File Manager,
2. renamed said files, exited Aroma,
3. flashed C-Apps package,
4. again flashed Aroma, went inside /system to rename files, they were replaced by DailerNext and InCallUiNext, exited Aroma,
5. rebooted to system.
6. Found that stock apps have been replaced(Nevermind, I'm not fan of them anyway).
I followed TWRP procedure.
Click to expand...
Click to collapse
If you followed the procedure correctly, that wouldn't have happened
Anyways, I'll upload the 2 stock apps the got replaced and a file that contains permissions that need to be applied to them
[email protected] said:
If you followed the procedure correctly, that wouldn't have happened
Anyways, I'll upload the 2 stock apps the got replaced and a file that contains permissions that need to be applied to them
Click to expand...
Click to collapse
I thought so, I couldn't find "mount system read-only."
@[email protected] check attachment for screenshot
krishna442 said:
I thought so, I couldn't find "mount system read-only."
Click to expand...
Click to collapse
I'll look into this
In the meantime, try reflashing twrp
krishna442 said:
I thought so, I couldn't find "mount system read-only."
Click to expand...
Click to collapse
The option is there, just checked....in the bottom left of the mount section
[email protected] said:
I'll look into this
In the meantime, try reflashing twrp
Click to expand...
Click to collapse
[email protected] said:
The option is there, just checked....in the bottom left of the mount section
Click to expand...
Click to collapse
Thanks, I did, and there's this option .
krishna442 said:
Thanks, I did, and there's this option .
Click to expand...
Click to collapse
Strange....
I'll add this information to the op so that if anyone faces the same issue, they'll know what to do
Thanks
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
install the apk i have uploaded manually working fine along with audiotunner
sahil chandel said:
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
Click to expand...
Click to collapse
Send me a detailed guide via pm (what did you exactly use, etc) and I'll add it to the op
And, maxxaudio tuner and audiofx are the exact same thing....no difference...both are from maxxaudio....same dev
sahil chandel said:
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
install the apk i have uploaded manually working fine along with audiotunner
Click to expand...
Click to collapse
I just tried it out
Didn't work
Stick with audio tuner on op2 its the same thing
[email protected] said:
I just tried it out
Didn't work
Stick with audio tuner on op2 its the same thing
Click to expand...
Click to collapse
its working install manually see screenshots
sahil chandel said:
its working install manually see screenshots
Click to expand...
Click to collapse
it isn't
just tried
and that does not look like official audio tuner
[email protected] said:
it isn't
just tried
and that does not look like official audio tuner
Click to expand...
Click to collapse
bro thats audiofx.apk.....not audio tunner i have both audiotunner & audiofx.apk look 2nd screenshot i used them combinely too during headphones....gives awesome bass combination
sahil chandel said:
bro thats audiofx.apk.....not audio tunner i have both audiotunner & audiofx.apk look 2nd screenshot i used them combinely too during headphones....gives awesome bass combination
Click to expand...
Click to collapse
my bad
it doesn't look like the apk in the c-apps package
[email protected] said:
my bad
it doesn't look like the apk in the c-apps package
Click to expand...
Click to collapse
use the app that i hv uploaded
its from teamsek cm12.1
krishna442 said:
I thought so, I couldn't find "mount system read-only."
@[email protected] check attachment for screenshot
Click to expand...
Click to collapse
Thanks
But that does not look like official twrp
http://twrp.me/devices/oneplustwo.html
[email protected] said:
Thanks
But that does not look like official twrp
http://twrp.me/devices/oneplustwo.html
Click to expand...
Click to collapse
Yep, even I just noticed it. Omg. I'm really getting dumb these days. Thanks a lot.
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.
Coolpad Note 3 and lite are now officially supported by DualBootPatcher
Steps to use DualBootPatcher :-
# Downlad and install latest DualBootPatcher
apk from here
https://dbp.noobdev.io/
# Open it -> Go to roms in option
Grant all the permission,set the kernal
and update the ramdisk in primary rom.
# Go to settings and install boot ui.
# Now go to patch zip file -> Add flashable zip
# Select the rom.zip , googleapps.zip ,
patches.zip , addons.zip which you want to
use as secondary rom.
Select your device , data slot , (ext sd slot not
tested).
And apply patch.
# After patch completes install all the zip files
you have patched from twrp.
# If u want to use inapp flasher of
DualBootPatcher,
flash this zip before u use the app.
https://mega.nz/#!xhgQERbL!5UEPeMbbHU9kxLBmWLpUpsosRk4lGmtr0S3pWgkbdeU
#Note : works only if your rom supports init.d or su.d
# After the flash completes, hit reboot ==>> u
will be in the second rom.
# To switch rom :- Methods(any one works )
1. Using boot ui :u get option to switch rom during reboot
2. Select the rom in the App and reboot.
3. Install the boot.img in internal -> mutiboot folder from recovery and reboot
# If something goes wrong :-
Go to recovery -> install boot.img of primary
rom.
Note : 1. Not all the roms are tested.
Do At Your Own Risk
2. Note 3 plus also added but not tested
those who are interested can test and
coment here
CREDITS:-
#Chenxialong : For the incredible app
@Uday Hegde (For this Guide)
@kuberrocks96 (personally tested on Coolpad Note 3 Lite)
UPDATE : WORKING ON COOLPAD NOTE 3 , LITE AND PLUS
Working On Coolpad Note 3 as well
Note 3 plus try..
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
RaghuStar said:
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
Click to expand...
Click to collapse
did u tried to flash from recovery..?
Uday Hegde said:
did u tried to flash from recovery..?
Click to expand...
Click to collapse
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
RaghuStar said:
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
Click to expand...
Click to collapse
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Uday Hegde said:
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Click to expand...
Click to collapse
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
RaghuStar said:
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
Click to expand...
Click to collapse
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Uday Hegde said:
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Click to expand...
Click to collapse
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
RaghuStar said:
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
Click to expand...
Click to collapse
sure bro
Thanks sir for the guide
yadavdharmendar said:
Thanks sir for the guide
Click to expand...
Click to collapse
All thanks to @Uday Hegde
Unable to dual boot RR with MIUI 8.1
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
unable to update ramdisk on cpn3. why?
ripon_b said:
unable to update ramdisk on cpn3. why?
Click to expand...
Click to collapse
may be ur using nougat rom.
its bcoz of special characters in board name.
to solve
backup your boot.img
unpack it using any boot.img unpack tool
edit boot.img-board using text editor
clear all the lines in that file
repack boot.img and flash
now it will not fail to update
abhishek_patil said:
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
Click to expand...
Click to collapse
use data slot or external sd card
I have tried that also..
abhishek_patil said:
I have tried that also..
Click to expand...
Click to collapse
u have log file of the error..??
Uday Hegde said:
u have log file of the error..??
Click to expand...
Click to collapse
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
abhishek_patil said:
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
Click to expand...
Click to collapse
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Uday Hegde said:
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Click to expand...
Click to collapse
Okay, i have following Questions.
1) Which software should I use to unzip img file.
2) I am unable to dual boot it with MM V010 on CN3L,
It showing same error posted by @RaghuStar.
3) Avoiding use of BootUI will prevent BootLoop?
4) Is there any effect of kernel version?
DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. 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.
Disclaimer:
Code:
Your warranty is now void.
I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM (Supported SM-G316HU. Such as Touchwiz Galaxy J3(Lollipop) & J100H(Kitkat), CM 11, 12, 13, MIUI, FlymeOS)
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What Can Be Done:
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
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (greatlte) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20171004-greatlte-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple . There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
Quote:
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Other How to ?
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".
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:
https://dbp.noobdev.io/downloads
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Galaxy ACE 4(SM-G316HU) Source:
https://github.com/chenxiaolong/DualBootPatcher/pull/1090
Known issues:
- You have to tell me !!!
Contributors
yshalsager, chenxiaolong, dbp007
Version Information
Status: Stable
[Reserved]
[Reserved]
ROMS
Which custom roms do have for this device SM-G316HU
please provide link @HWDEV
---------- Post added at 02:43 PM ---------- Previous post was at 02:07 PM ----------
can't update ramdisk
it shows 'failed to update ramdisk'
pulmit said:
Which custom roms do have for this device SM-G316HU
please provide link @HWDEV
---------- Post added at 02:43 PM ---------- Previous post was at 02:07 PM ----------
can't update ramdisk
it shows 'failed to update ramdisk'
Click to expand...
Click to collapse
Visit this link :
https://forum.xda-developers.com/ace-4/general/master-thread-samsung-galaxy-ace4-s-t3631541
HWDEV said:
Visit this link :
https://forum.xda-developers.com/ace-4/general/master-thread-samsung-galaxy-ace4-s-t3631541
Click to expand...
Click to collapse
Thats ok for roms
But what about failed to update ramdisk error
pulmit said:
Thats ok for roms
But what about failed to update ramdisk error
Click to expand...
Click to collapse
Give the screenshoots. & multiboot.log file.
HWDEV said:
Give the screenshoots. & multiboot.log file.
Click to expand...
Click to collapse
previously i was using rooted stock rom when it showed ramdisk error
then i used custom rom lineage os 14 the ramdisk updated successfully
i flashed secondary rom and it was flashed successfully
after flashing the secondary rom the device was not booting
so i wiped the system and flashed the custom rom
i will again use the app and try to resolve the issue