[Unofficial] [PATCHER] [APP] DualBoot Patcher APP for Exynos7870 and 7880

[Unofficial] [PATCHER] [APP] DualBoot Patcher APP for Exynos7870 and 7880 - Samsung Galaxy J7 Themes, Apps, and Mods

I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Click Here is the latest build
Modified Sources here: https://github.com/lzzy12/DualBootPatcher
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy J7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03

hi
tnx for dev
plz support j7y17lteM :crying:

Related

[MOD][Arm64]MultiROM for YU Yureka[v33][Beta 1]

FAQ's
1. Should I flash recovery only via Flashify app?
-Not essentially, You can flash it via recovery.
Boot to TWRP.
Install->Tap on Images(bottom right screen)>Locate and select your recovery.img
Flash to 'Recovery' partition.
Reboot back to TWRP(IMPORTANT).
2. Can I flash any other kernels?
-As of now NO. Only the given 'Dominator Kernel'
You can flash only 'kexec hardboot' supported kernels. Other kernels won't work.
Don't worry within few days, Devs are going to add support to their kernels.
3. Which roms can I flash?
-All Android 5.1+ roms can be flashed without any issues.
14 How to flash without Hardbricking?
-Follow the steps from OP and there are videos to make the things easy in initial pages.
Maximum it causes bootloops(softbrick), not hardbrick if you follow the guide.
5. Can I flash roms to ext-sd card and USB-otg? How?
-Yes you can flash them to ext-sd card and USB-otg.
Boot to TWRP.
Tap on Multirom.
Tap on ADD ROM
Select the right Location
Spoiler: Meomry Location SS
Flashing on ext-sd and USB otg takes some time, so be patient, don't freak out!
6. Where to find roms installed in my ext-sd and USB? How to boot into 'em?
-After flashing you'll be booted into MultiROM menu.
All your roms flashed on internal memory will be in Internal tab.
Others will be in External tab.
Spoiler: Screenshot
7. How to rename/remove/delete/wipe dalvik & cache or flash any other zips to existing rom?
-Follow
Boot to recovery.
Tap on MultROM
Tap on the rom which you want to remove/add zips.
You'll find all the options you need!
Spoiler: Screenshot
8. Is there any option of app sharing?
-NO. This is entirely different from mboot. You need to install separate apps in each ROM.
9. "Unable to flash, I'm getting errors" / "Executing updater script failed" / "Rom is not booting" ????
-Please provide logs. It'll be located in /data/media/0/multirom/last_kexec. log
It'd great if you can provide the screenshots.
Press VOL DOWN + LOCK KEY to take Screenshots.
Bugs
This is just a beta build so bugs are expected some of bugs the bugs which I am aware of are
* Roms above 5.1 are working (5.1 roms are also working)
* Ported roms are not working however roms ported as taking 5.1 gets boot
If you found any just report me
Video
Check this video for proper installation :
https://youtu.be/aAYSLt8zjNE

RESERVED

excellent work....
finally multi rom recovery is here.....
thanks bro...

@Men_in_black007, in muliboot app, when I click on rom, I get the error "could not determine the boot partition because this device's codename 'YUREKA' is not recognized." no matter which ROM i flash.
Please let me know if there is a work around for this.
I have tried flashing cm12.1 latest nightly , MIUI V7 developer edition v6.3.24, cm 13 latest nightly as primary ROMS.

Reserved
Reserved...
Trying it. Exited.:highfive:

there is no multirom option in advanced....please help

No link for Uninstallation.

Do we hav to keep the given kernel installed for using multirom? Or can we change it once secondary rom is installed?
Sent from my AO5510 using XDA-Developers mobile app

Dominator kernel isn't working with new official cm13 nightly builds.. Please fix...

purig said:
Dominator kernel isn't working with new official cm13 nightly builds.. Please fix...
Click to expand...
Click to collapse
Yes, it won't work until gets updated with new source.

What is the android version of this rom??is it AOSP based??thank you!!

Yureka + ?
Men_in_black007 said:
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. 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.
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
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:
MultiROM (multirom-YYYYMMDD-vXX-tomato.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (twrp_mrom.img) - download the IMG file from second post and use fastboot or Flashify app 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.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 676mb of space.
Using USB drive
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 easily 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.
Downloads
1. Main downloads
MultiROM: multirom-20160220-v33-UNOFFICIAL-tomato.zip
Modified recovery (based on TWRP): recovery_mrom.img
Kexec-harboot kernel : Dominator-v2.4-2016-02-16-0953-UB.zip
2. Third-party kernels with kexec-hardboot patch
Yet to come!
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Credits
@abhishek987
@TheStrix
This port is based on the hard work of @Tasssadar, @500 Internal Server Error, Geoff Levand, @webgeek1234, Mike Kasick, @Hashbang173, and many others. Thank you.
XDA:DevDB Information
MultiROM for YU Yureka, Tool/Utility for the YU Yureka
Contributors
Men_in_black007, abhishek987
Version Information
Status: Testing
Created 2016-02-23
Last Updated 2016-02-23
Click to expand...
Click to collapse
Sir can I use this in my yureka plus?

where is multirom apk??

[MOD][MultiROM][v33][Beta 1]

Reserved
DOWNLOADS
1. Main Downloads
Multirom :- multirom-20160615-v33-UNOFFICIAL-kenzo.zip
Multirom recovery:- recovery.img
2. third-party kernels with kexec-hardboot patch
no need with kexec workaround
Uninstaller :- multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.

Reserved
FAQ's
1. Should I flash recovery only via Flashify app?
-Not essentially, You can flash it via recovery.
Boot to TWRP.
Install->Tap on Images(bottom right screen)>Locate and select your recovery.img
Flash to 'Recovery' partition.
Reboot back to TWRP(IMPORTANT).
2.Can I flash any other kernels?
-yes you can flash any roms
3.Which roms can I flash?
-All Android 5.1+ roms can be flashed without any issues.
miui is not supported
4.How to flash without Hardbricking?
-Follow the steps from OP and there are videos to make the things easy in initial pages.
Maximum it causes bootloops(softbrick), not hardbrick if you follow the guide.
5.Can I flash roms to ext-sd card and USB-otg? How?
-Yes you can flash them to ext-sd card and USB-otg.
Boot to TWRP.
Tap on Multirom.
Tap on ADD ROM
Select the right Location
Flashing on ext-sd and USB otg takes some time, so be patient, don't freak out!
sd1 = usb otg
mmcblklpa = sd card
6.Where to find roms installed in my ext-sd and USB? How to boot into 'em?
-After flashing you'll be booted into MultiROM menu.
All your roms flashed on internal memory will be in Internal tab.
Others will be in External tab.
7.How to rename/remove/delete/wipe dalvik & cache or flash any other zips to existing rom?
-Follow
Boot to recovery.
Tap on MultROM
Tap on the rom which you want to remove/add zips.
You'll find all the options you need!
9."Unable to flash, I'm getting errors" / "Executing updater script failed" / "Rom is not booting" ????
-Please provide logs. It'll be located in /data/media/0/multirom/last_kexec. log
It'd great if you can provide the screenshots.
Press VOL DOWN + LOCK KEY to take Screenshots.
10.How to disable auto boot / change rom name / hide roms / brightness of Multirom menu?
-Follow
Boot to recovery.
Tap on MultiROM.
Tap on 3 dots on top right of screen.
Select settings.
Here you find all the customisations for MultiROM menu.

BUGS
- Miui is not supported
Credits @nkk71 for his no kexec workaround @Abhishek from yu forums @TheStrix for cm
NOTE :- All the devs are requested to help in improving this project as it is still in beta stage

Reserved for future....who knows what crazy post will be made here
Good job @zeeshanhussain12

VIDEO GUIDE (SOON WILL BE KENZO SPECIFIC)

Awesome.... Thank you
Sent from my SHIELD Tablet using XDA-Developers mobile app

yes,it looks so good
Sent from my Hol-U19 using XDA-Developers mobile app

Shahan_mik3 said:
Reserved for future....who knows what crazy post will be made here[emoji14]
Good job @zeeshanhussain12
Click to expand...
Click to collapse
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Sent from my Redmi Note 3 using XDA-Developers mobile app

Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...

This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?

nice to see you here buddy @zeeshanhussain12.

ayush321 said:
Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...
Click to expand...
Click to collapse
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk

Filip013 said:
This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?
Click to expand...
Click to collapse
miui gives error while flashing as secondary. i have not tried Xiaomi.EU roms. i have ported DualBootPatcher too i have it in my drive . it doesn't work well with sd 650 as qcom changed base directory in mm and lp. the current problem is with dtb nearly every rom is using different source which have different dtb, it is causing problems. we just have to wait for one official source or use the roms which is built with same trees

zeeshanhussain12 said:
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Can you tell me which roms are currently working with multiROM...

Reserved
Waiting for miui support
Sent from my Redmi Note 3 using XDA-Developers mobile app

Hadi al-Haiqal said:
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Click to expand...
Click to collapse
Haha Eos was the best and can't be replaced

zeeshanhussain12 said:
[/CENTER]
Introduction
MultiROM is one-of-a-kind multi-boot mod for Redmi note 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. 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, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the redmi note 3
* 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 messing with boot sector and data partition. 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
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) 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 (If you want to use Kexec) - 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 (TWRP_multirom_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch. we dont need patch kernel with the no kexec workaround
MultiROM (multirom-YYYYMMDD-vXX-wt88047-signed.zip) - download the ZIP file from second post and flash it in recovery.
You 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
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 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 MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
XDA:DevDB Information
[MOD][MultiROM][v33][Beta 1][kenzo], Tool/Utility for the Xiaomi Redmi Note 3
Contributors
zeeshanhussain12
Source Code: https://github.com/multirom-nexus6p
Version Information
Status: Beta
Beta Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2016-06-15
Click to expand...
Click to collapse
Awesome Work buddy! Keep going!

@War_machine28 said:
Awesome Work buddy! Keep going!
Click to expand...
Click to collapse
Please don't quote the whole op...

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Xiaomi Redmi 4A (rolex)

{
"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 the first dual boot project for Xiaomi Redmi 4A (rolex). 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 Xiaomi Redmi 4A (rolex) 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 "rolex" 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 lineage-13.0-20170307-UNOFFICIAL-rolex.zip_dual).
- 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.r201.ge0c23176"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Xiaomi Redmi 4A (rolex) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/639
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@dennis46419 for testing and screenshots
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/UltraDevsApps/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: Build 2
Beta Release Date: 2017-07-03
Created 2017-07-04
Last Updated 2017-07-04

Changelogs:
- 04/07/2017
Initial Release
- 07/07/2017
We are Officially Supported, Pull Request Here

Thaaaaaaaaaaaaaaaaaaaaaaaank u so much <3

Thank you so much. Going to try it asap. Thanks again
Sent from my Redmi 4A using Tapatalk

vaglan said:
Thank you so much. Going to try it asap. Thanks again
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
After updating ram disk and reboot stuck on twrp. Won't reboot to system. Had to restore. Any ideas??. Should i flash rom from that point on skipping all steps described???.(patch zip,sagit,etc???)
Sent from my Redmi 4A using Tapatalk

vaglan said:
After updating ram disk and reboot stuck on twrp. Won't reboot to system. Had to restore. Any ideas??. Should i flash rom from that point on skipping all steps described???.(patch zip,sagit,etc???)
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
Tried again this time didn't reboot after updating ran disk. Did everything as described everything seemed to work fine. Then i reboot and stuck again in recovery. Apparently does not reboot to system
only boots to recovery again. Try please and be more specific in your description. Ensure your device is set to .... sagit???.Is that right?. Big thank anyway
Sent from my Redmi 4A using Tapatalk

vaglan said:
Tried again this time didn't reboot after updating ran disk. Did everything as described everything seemed to work fine. Then i reboot and stuck again in recovery. Apparently does not reboot to system
only boots to recovery again. Try please and be more specific in your description. Ensure your device is set to .... sagit???.Is that right?. Big thank anyway
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
make sure your device is set to "rolex"
sorry it's my mistake

We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/639

Of course I did. Reboots directly to twrp and stays there
Sent from my Redmi 4A using Tapatalk

vaglan said:
Of course I did. Reboots directly to twrp and stays there
Click to expand...
Click to collapse
Don't try with miui official as first ROM
Try to use EU rom instead

I am on developer miui. Thanks anyway. I'll probably try with mokee as first room
Sent from my Redmi 4A using Tapatalk

Does it let us pass SafetyNet? (play Pokemon GO and use Snapchat)

CuteFluffy said:
Does it let us pass SafetyNet? (play Pokemon GO and use Snapchat)
Click to expand...
Click to collapse
If you can bypass it in your rom then yes. It does not affect anything on safety net

yshalsager said:
Don't try with miui official as first ROM
Try to use EU rom instead
Click to expand...
Click to collapse
I'm stuck on recovery too What I have to do,to not lose my data?
Yeah I know I had to do a backup...

Kajzer4321 said:
I'm stuck on recovery too What I have to do,to not lose my data?
Yeah I know I had to do a backup...
Click to expand...
Click to collapse
Flash utilities zip and change your rom to primary

yshalsager said:
I am proud to present the first dual boot project for Xiaomi Redmi 4A (rolex). 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 Xiaomi Redmi 4A (rolex) 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 ?
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 "rolex" 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 lineage-13.0-20170307-UNOFFICIAL-rolex.zip_dual).
- 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:
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
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.r201.ge0c23176"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Xiaomi Redmi 4A (rolex) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/639
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@dennis46419 for testing and screenshots
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/UltraDevsApps/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: Build 2
Beta Release Date: 2017-07-03
Created 2017-07-04
Last Updated 2017-07-04
Click to expand...
Click to collapse
Hello sir when i had updated the ramdisk and reboot my device it will not boot , it is always going into the recovery please help what to do .
Thanks in advance

Lineageosmod said:
Hello sir when i had updated the ramdisk and reboot my device it will not boot , it is always going into the recovery please help what to do .
Thanks in advance
Click to expand...
Click to collapse
First don't quote the whole op again.
You should use Xiaomi EU rom or multi rom. Because global or China rom won't work because of force encryption

yshalsager said:
First don't quote the whole op again.
You should use Xiaomi EU rom or multi rom. Because global or China rom won't work because of force encryption
Click to expand...
Click to collapse
EU ROM? MULTI ROM? where can i get these roms? link plz

defy_owner said:
EU ROM? MULTI ROM? where can i get these roms? link plz
Click to expand...
Click to collapse
https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
https://multirom.me/index.php?m=app&a=view&id=76&app=roms

Is there a way to change booting system inside the recovery??

[Official] Dual Boot Patcher [Mi Max 2 / Oxygen]

*Reserved

**Reserved

Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.

drmuruga said:
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
Click to expand...
Click to collapse
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool

I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.

jbmc83 said:
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
Click to expand...
Click to collapse
Yes , this tool working great , my problem is known to roms .
Patch roms and files in data slot not secondary slot in which is only one room can boot as secondary. Data slot for multiple roms flashing. And I never update ramdisk which leads to boot into recovery instead of system .

What's the use of dualboot we have only two ROMs to download.. Lol!

Now we should have at least two stable roms to taste this

nikz106 said:
What's the use of dualboot we have only two ROMs to download.. Lol!
Click to expand...
Click to collapse
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!

jbmc83 said:
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
Click to expand...
Click to collapse
+1 to this.

Mgphyo126 said:
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
Click to expand...
Click to collapse
Anyone?

mario_R said:
Anyone?
Click to expand...
Click to collapse
Twrp >> wipe >> format data..
And it's ok now. ??

when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!

DON'T set lock screen !!
you will end up locked away from your primary rom
----------
in my case the primary was globerom and secondary was lineage os
---------
if you already locked from your rom you can boot twrp and open terminal and write
cd data/system
rm *.key
and reboot

kalawy said:
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
Click to expand...
Click to collapse
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Kapil Tapsi said:
If you want to root secondary rom, then download latest magisk and patch it like you did with rom
Click to expand...
Click to collapse
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide

mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Click to expand...
Click to collapse
I figured that out ... the hard way :crying:

mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
Click to expand...
Click to collapse
Thanks mario_R for the guide and trick. I did it hassle free as I already had my internal decrypted. But I noticed some people having problem with installation.

it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??

app share have a high chance of breaking secondery rom

[RECOVERY] [TREBLE] [RETIRED] TWRP with Tissot Manager (Treble & Dual boot support)

RETIRED! No longer supported or being developed. @Giovix92 is now the lead dev, please use his TWRP for full compatibility with modern kernels/ROM's - https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
Old thread below:
-----------------------------------
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing, Dual boot repartitioning and other power-user tools with integrated Aroma Installer-powered GUI screens that I call Tissot Manager.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know!. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready with dual-boot ROM patcher;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Option to install a payload ROM in the current slot, rather than the inactive one;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Adds a "Tissot Manager" Aroma GUI to TWRP Advanced Menu (bottom-right button), which is the tool used to repartition the device for Treble and Dual boot, as well as some other nifty stuff:
Has the option to shrink System OR Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink System, you will keep max size Userdata - however it will be incompatible with non-Treble ROM's (they will crash on installing with Error 28 due to System being too small). It will Erase system, requiring you to reinstall a ROM or restore a ROM backup.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Dual boot requires Userdata shrink and works by splitting into userdata_a and userdata_b. The partition split size is customizable during the repartition process.
Adds a "Patches" section with the following current options:
Patch the current Vendor for dual-boot capability (only required if automatic patching wasn't possible). See the 'About Dual-boot' section below for more information.
Enable an insecure ADBD on boot for the current slot (i.e. enable debugging and remove authentication requirement). Useful for ROM hackers/porters.
Patch the current slot to enable/disable forced userdata encryption
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-boot.img-3.2.1-with-Tissot-Manager-x.x.zip:
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches (Aroma Installer powered GUI - a fully guided and interactive process).
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack. Reminder - check out my full guide for learning and instructions on all things Treble.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
About Dual-boot
Dual-boot on this device is relatively simple. As you know we have Slots - boot_a and _b, system_a and _b and vendor_a and _b (for Treble). This repartition splits userdata into userdata_a and _b too. You can simply change your Slot in TWRP reboot menu to change which ROM to boot.
This is designed for developers and testers - NOT for daily use. There are some significant issues with dual boot systems:
Any kind of security lock (PIN, fingerprint, etc.) set on one ROM will cause the other ROM to believe it has security too, but constantly fail with unlocking. This is reportedly because security info is stored on persist, which is shared between each slot (and not compatible with differing ROM's).
Because Userdata is split, so is Internal Storage. In TWRP, when changing slots, the MTP will remain mounted to the old slot - it must be manually disabled and renabled (Mounts menu) to update to the new slot.
I will not fix these issues - dual-boot is not designed to be for general/daily use and there may be more minor issues that I don't know about. It's intended for developers only.
In order for a ROM to be dual-boot compatible, the fstab file (information given to Android about partitions to mount) needs a small modification. This TWRP can try to do this patching automatically when you install a ROM, or it can be done manually in Tissot Manager's Patches menu (as well as single-boot patch to e.g. revert a ROM backup from a dual-boot state).
You will see in the install log if a dual-boot patch attempt is successful in the flash text output.
Automatic dual-boot patch occurs only if necessary when:
Flashing an AIO Treble ROM ZIP with TWRP
Flashing a vendor.img in TWRP "Install Image" mode
Automatic dual-boot patch does NOT work when:
Flashing a vendor.img via fastboot
Restoring vendor in a TWRP backup
Any other way of flashing a vendor
In any of these cases, you can manually patch Vendor for Dual Boot in Tissot Manager's Patches menu. You can also remove dualboot support the same way. It will detect the dualboot state of the current Vendor slot and present the available option. If you find that it doesn't actually change after patching, the Vendor is incompatible (please report it to me). RR AIO Vendor is tested OK.
Download
All downloads (and source code) always at:
https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
...or via DevBB Downloads section.
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/CosmicDan-Android/android_system_update_engine_tissotmanager-mod
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk. The void kernel included in RR AIO does not have this problem and can therefore be safely used without Magisk (for e.g. GSI compatibility).
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work. It will definitely not work if you have shrunk system.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ROM ZIPs with a shrunk System (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Credits and Thanks
- @mohancm for the original TWRP port, I used some flags from his DT
- @ghpranav and @mountaserhalak for the RR device tree that this is built with (and random help)
XDA:DevDB Information
TWRP with Tissot Manager (Treble & Dual boot support), Tool/Utility for the Xiaomi Mi A1
Contributors
CosmicDan
Source Code: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot
Version Information
Status: Stable
Created 2018-05-29
Last Updated 2019-11-24

Reserved

Screenshots (click for slightly larger non-cropped version)
Screenshot of new TWRP button:
_______________
Main menu (stock partition map detected):
_______________
Repartition choice type when coming from stock:
_______________
Repartition wipe warning/disclaimer if chosing to shrink Userdata for Treble:
_______________
Main menu (Shrunk Userdata type Treble partition map detected):
_______________
Repartition wipe warning/disclaimer if chosing to restore Stock from Shrunk Userdata Treble mode:
_______________
Example of Repartition processing screen:

Good job! :good:

Nice work!
Did you tested treble roms with this? Aex now have treble support

Omg, you are the best man. @mohancm also huge thanks to u man, great devs in our XDA.

I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!

Chikoow1 said:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Click to expand...
Click to collapse
This is just the repartition part, one step of Treble. You still need a Vendor pack. But yes, this enables Treble ROMs and the ROMs require repartition.
ddaggebi said:
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Click to expand...
Click to collapse
1. If you do, it will wipe partition map back to stock. So you will need to repartition with Treble Manager TWRP again. But you can make a backup of stock ROM in TWRP and just restore it after the repartition. It should work.
2. Don't know. Needs testing.
3. Yes! I forgot to add this to the FAQ.

Has this tpwr f2fs support and working?
Since Los support It i would like ti have

@CosmicDan
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?

Filip013;76586434 [user=1844875 said:
@CosmicDan[/user]
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Click to expand...
Click to collapse
It's indeed not intended to be compatible with stock ROM, but your mileage may vary, and as @CosmicDan said, it might work good enough or it won't. You can only try to see the results yourself.
This whole Treble thing is meant mainly for custom ROMS, since stock will never be Treble compatible (still, anything could happen)

I've just updated the TWRP with Treble Manager to 1.1 which fixed a semi-important bug.
Also, I've released a guide for those who find the Treble conversion/install process confusing - check it out. If you can, keep TWRP and Treble Manager specific questions in this thread, but ask your general questions and help over there - I will update the guide as I get feedback

CosmicDan said:
FAQ
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) Untested. Please report your results. But Treble is really not about Stock, you will likely encounter more problems down the line or it may turn out to be completely incompatible.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest/only way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (untested - if you get bootloop when using stock, it means you do) or Magisk (also untested, may still get bootloop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ZIP's on ROM's with a shrunk Userdata (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Unable to mount '/vendor' (Invalid argument)" red error in this TWRP
A) You can safely ignore it. It just means you have not repartitioned your device for Treble yet, so it can't mount the /vendor image.
Click to expand...
Click to collapse
Ay!
Have just finished testing about OTA on stock after Treblizing!
Result?!?
OTA works perfectly on stock after shrinking data to Treblize! Hurrah! ???
Process I followed:
1) Treblize by shrinking data
2) This is important: flash stock ROM in fastboot using MiFlash! When flashing for the first time, select "clean all and lock"! No other standard options working! I couldn't even boot stock using other options!
I've tested by fastboot flashing April build and then updating it to May OTA!
*** On a note: clean all will erase everything on your phone including your personal data!
If you use "save user data" then stock can't even boot! This may caused by the encryption!
BTW, after everything I just restored my non-Treble RR backup and everything works perfect! Just Treble Check app can't check that it's Treblized!
But don't worry! Treble partition table still remains! Fastboot flash can't touch that and can't recognize that it actually exists! Which to me is a good thing!
@CosmicDan, give me a thanks buddy! I deserve this!

SomratMJX said:
-snip-
Click to expand...
Click to collapse
Don't quote the whole OP and please use a smaller font size.

Change slot doesn't work... Others are okay as far as i have seen

dback31 said:
Don't quote the whole OP and please use a smaller font size.
Click to expand...
Click to collapse
Just thought it's too important to highlight! Nothing else!

Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Reboot to fastboot and change the slots with
fastboot set_active b

Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Use the latest TWRP 1.1! Works fine for me!

SomratMJX said:
Just thought it's too important to highlight! Nothing else!
Click to expand...
Click to collapse
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this

dback31 said:
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
Click to expand...
Click to collapse
Ha ha ha! It's related to OP buddy!
Anyways, I am too lazy to quote a certain part of the OP!

Database Develop

welcome