Hey,
im wondering if LG G4 (h815) ist working with Dual Boot Patcher.
Any Experience?
I'm also interested in dual booting. Having CM13 with stock ROM also to take photos would be perfect.
Any ideas?
I'm also intersted in it
Best thing is to patch TWRP with Multirom and kernel developers implement that patch on their kernels.
But seeing the low development going on with G4(mostly because of bootloader) I doubt that we will have that so soon.
I'm interested too. It would be great to have this option ! I need stock rom for photos too and would like another rom like cm13 for daily use. I see that this is available for G3 so let's hope it will be developed for G4 soon too.
I have Dual Boot Patcher running on my rooted H815. Genysis as primary and CM13 installed using a data slot. I sent a log to the developer and he got it working within a few days.
bobblesop said:
I have Dual Boot Patcher running on my rooted H815. Genysis as primary and CM13 installed using a data slot. I sent a log to the developer and he got it working within a few days.
Click to expand...
Click to collapse
Hi mate,
That is nice to hear this. Will you share with us how you set it up? Which build you used and which options you choosed (like the one that you put the CM13 on the data slot) to sucessfully make it work ? I really want to be able to dualboot as you do. I tried to patch an AICP rom and to install it on the data slot but when I tried to flash it I received only errors (like dual boot failed to load recovery partition image and some more lines like this one). Thank you !
I installed the latest dual boot patcher app and set the kernel. I then patched the CM13 and Gapps zips for data slot 1. I didn't try flashing these within the dual boot app but did it from TWRP. That rebooted to CM13 so I installed the dual boot patcher app again and can now dual boot!
bobblesop said:
I installed the latest dual boot patcher app and set the kernel. I then patched the CM13 and Gapps zips for data slot 1. I didn't try flashing these within the dual boot app but did it from TWRP. That rebooted to CM13 so I installed the dual boot patcher app again and can now dual boot!
Click to expand...
Click to collapse
Hi,
I tried the same steps just like you and I still got errors. I uploaded the multiboot.log file so if somebody can help me to check it and tell me what I'm doing wrong. Thanks !
You might be better uploading the log to the original thread in the galaxy S4 forum. The developer seems to respond to most issues.
I tried with CM13 as main rom, patched kernel, patched ZIP of an official ROM as secondary, went to recovery to flash it but it gave an error :/.
If someone gets it working please write a mini tutorial
bobblesop said:
You might be better uploading the log to the original thread in the galaxy S4 forum. The developer seems to respond to most issues.
Click to expand...
Click to collapse
Maybe I will do this for sure. But first can you tell me which version of TWRP recovery are you using and exactly the number and name of the DualBoot app ? I'm starting to think that the errors come from my TWRP version. Is this possible ?
I have successfully flashed patched CM13 roms & Gapps using TWRP 2.8.7.0 and 3.0.0.0 I have used a few dual boot patcher app builds from mid February and have 8.0.0.r2304.g03481db-SNAPSHOT installed and tested at the minute.
I had trouble flashing aroma based installs before on my G3.
I have Dual Boot Yeah
First Rom : Stock MM 6.0
Second Rom : AICP MM 6.0.1 du 25/03/2016
Easy
no problem , no bug , just i haven't gapps installed
sorry for my bad english
Can somebody write a little tutorial for dual boot on G4?
I know that we must patch all the zips for the second rom but where to flash them?
On the system?With twrp or with dual boot patcher?
Create a new slot in internal storage?How?How big?
And how to switch between roms?
Thank you in advance ☺
Sent from my LG G4
Ok guys,
I've found a tutorial on some french forum and I translated it
Prerequisite:
LG G4 ROOTED with at least 5 GB of free storage
Have installed a custom recovery
A second custom rom + kernel (AROMA not supported)
Making a Nandroid Backup (not required, but recommended)
Download and install the application -> https://snapshots.noobdev.io/
Procedure:
1.First, install the Dual Boot Patcher application (DBP), and open one, and allow root permissions when prompted
2.In the application, in the upper left corner, press the 3 horizontal lines and then "ROMs"
3. Then press the three dots of primary Rom to view the settings and then click "Set the kernel" and click on "CONTINUE"
4. Return to the main menu of the application, and press "Patch zip file."
5.In the menu that appears under "Device and partition configuration," press the arrow and select "IgG4 (IgG4)"
6.Below, in the "Partition configuration", press the arrow and select "Data slot" then choose and enter the name of your second Rom (Secondary example). Please note, it may break you download an English dictionary in your keyboard so you can enter a name.
7.When done, press below on "Press to select a file to patch." Select the zip file of the secondary rom, then press "Touch to start patching"
8.A message confirms that the patch of the Rom went well. Go back into the menu and try "Patching a zip file", but select the kernel this time.
9.After the patching, press in the main menu to "ROMs" and then press the red round button at the bottom right, accept the message with "OK", then press again the red button that displays a "+"
10.Select the secondary patched rom. You will recognize as "secondary" to appear in its name. Reflash it by pressing "✓" in the upper right.
11. Do the same, but select the kernel file of the secondary rom patched. Reflash it by pressing "✓" in the upper right once it is selected.
12.Once done, press "Secondary (slot Data)" (or the name you gave your second Rom) then in the application menu press "Restart."
13.The second Rom starts, it can take up to 10 minutes. Once started, the application will install Dual Boot Patcher
14.Open one, then press "ROMs". Open the menu of secondary rom and press "set the kernel". It's finish !! You can enjoy the dual boot!
[emoji4] [emoji4]
{
"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"
}
Envoyé de mon LG-H815 en utilisant Tapatalk
herveonex said:
[emoji4] [emoji4]
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
How did you do it?
When I tap on Set kernel I get the message "Failed to set kernel"...
And where did you get 6.0.1 rom?
Sent from my LG G4
.Genisys + kernel superxe v1.8 is ok ,no failed
.6.0.1 is vanilla unicorn.
Envoyé de mon LG-H815 en utilisant Tapatalk
So if you're secondary flashing a CM13 ROM and a kernel, do you flash Gapps as well?
Related
Welcome to Multiboot backup & Restore
{
"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"
}
This is a multi-function utility app with the following features:
•BACKUP your existing multi Rom to your internal or external memory using an accelerated multi-core GZIP binary PIGZ.
•RESTORE a previously made backup to your multi ROM slot
•DELETE a Multi-ROM
•DELETE a Multi-ROM DATA only (factory reset)
• DISPLAY detailed info of your Multi-boot setup AND backups
•RE-PATCH a zip already patched with the patcher snapshot app to a specific ROM slot. Allowing Note4 recoveries to flash without freezing. This uses a ZIP binary which doesn't need to unzip and process everything inside. Making a copy of your zip will take time tho.
• Switch ROMS and reboot within the app
Things not working (yet)
•ONLY FOR DUAL Sorry since you can't fit a multi ROM in the NOTE 4s tiny cache partition I can't test this function. I have an S4 but it's in repair. Once I have it functional I will add multi support.
•RE-PATCHER ISSUES Since Chen updates the info.prop for regularly I am going to fine a way to edit the file as it is without needing to constantly update along with patcher snapshot.
FAQ
Please be aware this early release does not have much in the way of tutorials and limited safety checks be sure you make TWRP backups in case something goes wrong.
Patcher app Snapshot
My app is only a complain companion to this amazing piece of work! thanks to Chenxian for making this all possible.
Check out the patcher thread here:
http://forum.xda-developers.com/showthread.php?t=2447534
Latest snapshot link
Download the patcher snapshot here:
https://snapshots.noobdev.io/
DOWNLOADS
First app run will install a custom busybox and binary folder which will NOT interfere with any other system functions
Once installed you should see this message
The main screen shows you active multi boot information tapping the button above will toggle between ROM and backup info
You can toggle the storage path too and choose your external microSD or internal memory to make backups
Tap on the ROM slot you want to access. This brings up the operations menu which has real time info of backup/restore progress
You can cancel this operation or force close the app from the notification bar
You can select a patched file generated by patcher snapshot app and re-patch for a specific ROM slot.
Note 4 users must do this since AROMA won't work from recovery yet and the only other option is to use patcher snapshot app to make your install.
If your primary ROM fails to boot having a re-patched zip to flash from recovery is essential
My basic file manager allows you to select your file by long-presing. Then you select a slot and a re-patched zip will be created in the same folder as the original
You can also switch ROMs and reboot into it from within my app!
It is a stand alone app that will need to be installed once and can be quickly accessed later from your launcher independently as well as accessed within this app.
Enjoy! And please give feedback to help improve this app.
-rlorange
Reserved. ..
Tap on slot to backup, nothing happens.
todivefor said:
Tap on slot to backup, nothing happens.
Click to expand...
Click to collapse
Dual boot or a multi?
rlorange said:
Dual boot or a multi?
Click to expand...
Click to collapse
I can select dual, but slot no.
todivefor said:
I can select dual, but slot no.
Click to expand...
Click to collapse
I'm sorry I don't follow. Does the operations window appear?
todivefor said:
I can select dual, but slot no.
Click to expand...
Click to collapse
Dial only for this initial release
I updated the OP forgot to mention that lol
First Trial Run
@rlorange, I ran this (48) on my SPH-L720 (Qualcomm Variant), first on CM-12.1 , AntaresOne & Alucard24 then on TW 5.0 Kushan02. Both recognized all of my slots dual, slot-1, 2, both did a backup to my external sd. I ran it on TW 5.0 last so did the restore from there, everything appeared to work but after waiting a while had to flash kernel then restored backup booted. Here are a few screenshots from CM-12 & TW 5.0.
JhoonB51 said:
@rlorange, I ran this (48) on my SPH-L720 (Qualcomm Variant), first on CM-12.1 , AntaresOne & Alucard24 then on TW 5.0 Kushan02. Both recognized all of my slots dual, slot-1, 2, both did a backup to my external sd. I ran it on TW 5.0 last so did the restore from there, everything appeared to work but after waiting a while had to flash kernel then restored backup booted. Here are a few screenshots from CM-12 & TW 5.0.
Click to expand...
Click to collapse
Only Dual is supported atm sorry. Hang in there my S4 should be fixed soon so I can get multi working...
I'm glad they are being recognised at least
Is there any step by step faq for creating a patched ROM....
Or is this guide still valid ?
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
rlorange said:
Only Dual is supported atm sorry. Hang in there my S4 should be fixed soon so I can get multi working...
I'm glad they are being recognised at least
Click to expand...
Click to collapse
Hey
Is it possible to at data backup ?
Data works great on note 4 (ATM cmremix on primary and tw on data )
During backup of roms, the app makes *.tar.gz files of system and data, but did not do this for the kernel, why?
New World Order (NWO)
Fix the title
{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
Disclaimer
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 or PhilZ Touch or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
Thanks for the mention
@WinterR test the unofficial snapshot, please
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img
Now DualBootPatcher supports the L7 and L7II!!!
I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?
@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )
If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk
I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).
Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel
Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel
Thread closed as per OP request.
-XDA Staff
{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for LG G4. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still very experimental!
I've only tested this with stock M as the primary ROM and AICP M as the secondary ROM
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
The MultiROM Manager app does not currently support the LG G4
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (recovery_yourvarient.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
MultiROM (multirom-YYYYMMDD-vXX-yourvarient.zip) - download the ZIP file from second post and flash it in recovery.
Your current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
Untested on clark
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/Hashbang173/multirom/tree/master
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
kexec-hardboot patch - https://github.com/genesixx/android_kernel_lge_msm8992-mr
Device tree: https://github.com/genesixx/g4-common-mrom
Thanks
This port is based on the hard work of Tassadar, Geoff Levand, webgeek1234, Mike Kasick, 500 Internal Server Error, and many others. Thank you.
Thanks to @HashBang173 for all the help
Issues
* Does not yet support encrypted devices
* Please report
XDA:DevDB Information
MultiROM v33 for LG G4, Tool/Utility for the LG G4
Contributors
genesixxbf3
Version Information
Status: Beta
Created 2016-07-08
Last Updated 2016-07-14
Reserved
Download link : https://www.androidfilehost.com/?w=files&flid=51689
compatible only with LlamaSweet kernel R6 (alpha3) as first kernel available here http://forum.xda-developers.com/g4/development/kernel-llama-sweet-kernel-t3286514
Reserved
known problem:
green screen when booting secondary rom
I'm a noob with MultiROM, but there is no option in recovery for multiROM ?
azZA_09 said:
I'm a noob with MultiROM, but there is no option in recovery for multiROM ?
Click to expand...
Click to collapse
Have you flashed the recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
genesixxbf3 said:
Have you flashed the recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
Click to expand...
Click to collapse
Yep
azZA_09 said:
Yep
Click to expand...
Click to collapse
Have you rebooted to the new recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
genesixxbf3 said:
Have you rebooted to the new recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
Click to expand...
Click to collapse
Yea,ofc. Do you have Skype or something else? It's simple to tell you there what's wrong or not
azZA_09 said:
Yea,ofc. Do you have Skype or something else? It's simple to tell you there what's wrong or not
Click to expand...
Click to collapse
I use hangout
Envoyé de mon Nexus 6 en utilisant Tapatalk
Which kernel are you using for the stock Rom?
nicholasknicks said:
Which kernel are you using for the stock Rom?
Click to expand...
Click to collapse
atm kernel patch aren't working
Closing the thread until I get progress
Envoyé de mon Nexus 6 en utilisant Tapatalk
I'm getting closer ! now it just security ****
First I copy pasted his thread I send the patches required to make it compatible with Z play I post his thread here and download link linked to his thread
Original developer: chenxiaolong
I'm proud to present the first dual boot project for the Moto Z Play! 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
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 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.
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
{
"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"
}
Downloads:
https://forum.xda-developers.com/showthread.php?t=2447534
Can you please make one for xt1580 Droid turbo 2 aka X force
i'm a bit confused, the link to the downloads is just to a old thread for a S4 from 2013. Are you saying that if you install the files from the S4 post that you can dual boot the Moto Z play?
RunnersFoot said:
i'm a bit confused, the link to the downloads is just to a old thread for a S4 from 2013. Are you saying that if you install the files from the S4 post that you can dual boot the Moto Z play?
Click to expand...
Click to collapse
https://dbp.noobdev.io/
Thread is old but the link is updated.
RunnersFoot said:
i'm a bit confused, the link to the downloads is just to a old thread for a S4 from 2013. Are you saying that if you install the files from the S4 post that you can dual boot the Moto Z play?
Click to expand...
Click to collapse
I link the original thread, I added moto z play support , you can see updated Download link on his post.
Yes initial work is for S4 but now it support lot of devices.
and Yes you can dual boot using the app
Error while installing secondary rom
Hi all
I Have Lineage 14.1 as primary rom on moto z play. Installed dual boot patcher however getting attached error while installing secondary rom to secondary or multi slot partitions..need help
I set the kernel. It says "the ramdisk doesn't have any version of mbtool".
then clicked "update ramdisk" and rebooted. My phone only rebooted to twrp and refused to boot.
Fixed it by re-flashing Magisk.
Is mbtool necessary?
{
"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"
}
I am proud to present first Dualboot project For Oneplus 5. 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
What is DualBootPatcher?
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. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Oneplus 5 to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
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 (OnePlus5) 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-20170707-cheeseburger-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.
Click to expand...
Click to collapse
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
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.
Click to expand...
Click to collapse
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:
All Downloads HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r221.g4661ff8e"
Screenshots:
In screenshots tabNo Screenshots available i need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
One Plus 5 Support: https://github.com/chenxiaolong/DualBootPatcher/pull/642
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For OnePlus 5 (cheeseburger), Tool/Utility for the OnePlus 5
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r221.g4661ff8e
Stable Release Date: 2017-07-08
Created 2017-07-07
Last Updated 2017-07-08
Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" || abort("E3004: This package is for device: cheeseburger; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- This won't work on stock OOS because of encryption.
3- Here's perfect 100% Working guide by @prile97 Here
Changelogs:
- 07/07/2017
Initial Release
- 08/07/2017
We are Officially Supported, Pull Request Here
Featured on XDA Portal
Woww.. Itz so soon.!!!
Stuck in Boot screen after updating ramdisk and rebooting.
Oos 4.5.5 and latest magisk 13!
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
+1
I'll be getting my OnePlus 5 most likely monday by the FedEx date. I'm so glad to see this available for this device. I had some issues with my Nexus 6P and running this. I love to flash different roms to see all the different options and this will be fantastic.
stuck in boot screen after updating ramdisk.
edit: can't install xXx rom anymore.
So the app was randomly removed from the magiskSU root list and the app isn't requesting root access back at all. I cleared data, cache and uninstalled but it still won't request root access.
Flashing the patched ZIP through TWRP installs it but it won't boot the system, stuck on OnePlus logo power by Android.
Only fix is to flash the utlities ZIP and choose to boot from primary ROM again, I tried stock OOS, custom OOS with AROMA and also RR as secondary ROM but none worked.
Stuck in boot screen after updating randisk. Solved rebooting in TWRP and dirty flashing full Oxygen OOS flashable zip and Super Su in one shot. After this I loosed TWRP, there were stock one again, so flashed TWRP again.
From my OP5.
fmotta said:
Stuck in Boot screen after updating ramdisk and rebooting.
Oos 4.5.5 and latest magisk 13!
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
Click to expand...
Click to collapse
Interceptor777 said:
So the app was randomly removed from the magiskSU root list and the app isn't requesting root access back at all. I cleared data, cache and uninstalled but it still won't request root access.
Flashing the patched ZIP through TWRP installs it but it won't boot the system, stuck on OnePlus logo power by Android.
Only fix is to flash the utlities ZIP and choose to boot from primary ROM again, I tried stock OOS, custom OOS with AROMA and also RR as secondary ROM but none worked.
Click to expand...
Click to collapse
I need some logs. Please flash this and attach the log
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
Are you guys encrypted or decrypted? I had the stuck on boot screen after updating ramdisk while I was encrypted.
But I don't want to try again now that I am decrypted :crying: I
Here you are
fmotta said:
Here you are
Click to expand...
Click to collapse
Please test this build
https://transfer.sh/uyzD0/Android_GUI-debug.apk
Same as before. 5 fast vibrations and reboot to recovery.
Thanks for it.. But will wait for multirom..
fmotta said:
Same as before. 5 fast vibrations and reboot to recovery.
Click to expand...
Click to collapse
Can you try with any custom rom as first rom?
Good job mate !
I updated the ramdisk thing and after i managed to get out of the bootloop now i'm unable to use wifi and fingerprint sensor
Don't try this
wow! this is amazing work!
it's like what we used to do with multi-Rom @ Nexus devices... Bravo!
GMX1PT said:
Good job mate !
I updated the ramdisk thing and after i managed to get out of the bootloop now i'm unable to use wifi and fingerprint sensor
Don't try this
Click to expand...
Click to collapse
Can you explain more?