[Official] Dual Boot Patcher [Mi Max 2 / Oxygen] - Xiaomi Mi Max 2 ROMs, Kernels, Recoveries, & Othe

{
"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"
}
DUAL BOOT PATCHER​
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Warning: This method requires one time factory reset.
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_data-slot.zip file will be created. For example,
Lineage-14.1-oxygen.zip
After patching would create a new
Lineage-14.1-oxygen_data-slot.zip
If you want to root secondary rom, then download Magisk 12.zip given below(Do not use other version, you can update that later from magisk manager app) and patch it like you did with rom
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk 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.
Secondary: 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.
Now Let's Start
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc on internal storage. So make sure you moved them or made their backup)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher.
6) Install patched rom as secondary on /system or on /data partition - it's your choice. There is lot of space for 3 roms in /system.
If you want to root secondary ROM and flash patched magiskv12.
7) Select your secondary ROM in ROM list and reboot.
Steps to be followed on Secondary Rom
8) Install Dual Boot Patcher.
9) Install MagiskManager.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
FAQ's (FAQ)
Do I need to wipe again for third or next rom?
No, wiping is only required for one time, you can flash as many roms(your device can handle) after that.
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".
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
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:
First backup all your data including Internal Storage, then boot to TWRP>WIPE>FORMAT DATA then type 'yes' and tap enter. Now reboot and retry DBP.
Source/Credits:
https://dbp.noobdev.io
@chenxiaolong
@bad_request (Thanks for the XDA Post And Guide)
@mario_R (For step by step guide and errors.)
Downloads: https://dbp.noobdev.io/downloads/ and Download latest files
~ Hit Thanks button below if I helped you ~

*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

Related

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

{
"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"
}
[/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
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...

			
			
			
			



			
			
			
			
			
			
			

			
		

	
		

			
[APP](DualBootPatcher) Dualboot/Multiboot for Infinix HOT 2
			
			
			
				
{
"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:
I have managed to add support for Infinix HOT 2 to the DualBootPatcher App and have compiled a test apk.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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.
Click to expand...
Click to collapse
Requirements:
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - in the download section.
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
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App ?
Before you start using the app, take note of these:
- Some ROMs will fail to install in the in-app zip installer. Unlike TWRP, all errors (even smallest ones) in the updater-script causes the installation to fail. You can either use a working updater-script from another rom or flash the patched zip in TWRP.
- Some roms like Infinix 5.1 make External Storage the default disk. That also removes the writing access to the Internal storage. So, any attempt to install a secondary ROM to /data/media will likely fail. The solution is to remove your external storage (SD Card), install the rom and put it back (unless you want to install to the external storage itself).
- Leaks happen if you use xposed in some roms.
NOTE: IF YOU DOWNLOADED THE APP BEFORE JULY 28, 2016; PLEASE RE-DOWNLOAD IT IN DOWNLOADS SECTION. IT IS A NEW VERSION WITH MORE SUPPORT AND FIXES.
NOTE 2: Before you start, it's important to change ro.product.device value to d5110_infinix in your build.prop, if you don't do this, you'll face errors. But if errors still happen, then flash it in TWRP.
If you have an Android 5.1 ROM as primary (the one you're currently using):
1) Download, install and open the app
2) 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!
3) Now swipe again and click on "Patch Zip". Click the big pink add (+) button and select the ROM you want to patch and use as Dual/Multiboot.
3) Select either "Infinix HOT 2/Infinix ROM" or "Infinix HOT 2/Android One" in the first drop down menu (according to the partition scheme you have, Infinix ROM partition have system on block 18; Android One have it on block 23). Then select the partition configuration (see more details below for this) in the next drop down menu. I suggest you choose either "Data slot" or "Extsd slot". Give a random number where it states "Enter an ID".
4) Click continue and select where to save the patched file.
5) 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.
6) The app will patch the zip. When done, go back to "ROMs".
7) Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
8) Locate the file you have patched in step 6. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like Cyanogenmod-12.1_20160724_d5110_infinix_data-slot-2.zip).
9) 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. But I didn't test that.
10) Upon finition, 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.
If you have Android 6.0 as primary (your current rom):
1) Download the apk file in downloads section
2) Follow steps above to patch the zip. Make sure you set kernel when the app asks you to. It is important to do that. You can manually set it by clicking on the three dots on the primary rom, scroll down and choose "set kernel".
3) Now when you finished patching it. Don't flash it in the in-app flasher.
4) Boot to TWRP recovery (TWRP 3.0.2 recommended). Don't wipe anything. Just click install zip and chose the patched zip. Wait till the end.
5) Now after the installation. Just reboot and install the apk file on the newly installed ROM and you can switch roms.
Warning: If you don't flash in TWRP while using Android 6.0, you can't switch newly installed roms!!!
Partitions Configurations:
These are places where you can install secondary roms. In our case, I'm affraid it's limited to DATA SLOTS and EXTSD SLOTS. Which means you can only install roms to your Data partition (pratically your internal storage) and your SD Card.
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. This one installs to the System partition slot.
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. Our HOT 2 system partition size is about 2.5GB on Infinix ROM. You can probably install two light ROMs (like cyanogenmod and its variants) to it. But I haven't tested it.
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. Our HOT 2's cache partition is about 250MB which is not enough to install a rom on.
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: Same as the above, but it installs the ROMs to your external SD. Make sure you have backed up your data first!
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:
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:
Download the apk file: DualBootPatcher_X510.apk (6.8MB)
WARNING: Do not use other builds other than this apk file. Official releases don't have Hot 2 support yet! I'm waiting for @chenxiaolong to add support for our device to the main repo so that it will be officially supported.
Sources:
My fork of DualBootPatcher with Hot 2 support: https://github.com/Nonta72/DualBootPatcher
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Known issues:
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@Anik_khan for the idea and inspiration :laugh:

			
				
Whoa!! Amazing, great work bruh!!

			
				
Good work bro

			
				
Well done bro! Am so impressed and as well excited!
This is what I call development pals!
It took me quite some time to read through - how much more the time it took to make this work!
Great job keep it up....

			
				
Anik_khan said:
Good work bro
Click to expand...
Click to collapse
Thank you for the idea, the path and the inspiration
Bolumstar said:
Well done bro! Am so impressed and as well excited!
This is what I call development pals!
It took me quite some time to read through - how much more the time it took to make this work!
Great job keep it up....
Click to expand...
Click to collapse
Thank you.
We will prove Google that we may not have Kernel sources but we still can make our device great.

			
				
hey bro help me please?

			
				
anzer77 said:
View attachment 3825304
hey bro help me please?
Click to expand...
Click to collapse
Download the new apk file named DualBootPatcher_X510.apk
I have fixed that issue in this new version.
Please take time to read the whole OP if you didn't. It is important !!!

			
				
Nice App Bro

			
				
@Nonta72
I have some questions, please
1- Does the app use the same kernel for all roms? or it flashes the required kernel while switching roms?
2- If I'm using Android one 6.0 as a primary rom, will USB OTG work in the secondary rom?
3- Does the secondary rom read both internal and external storage?
4- can I use already installed apps like whatsapp, facebook.. etc as shared apps? does this change the location of apps and its data?
5- Just want to make sure, flashing universal OTA updates for android one rom (the zips that is made by Joseph GodSlave on facebook group) works it it is patched for primary rom?
6- If I want to try multiboot then unistall it & remove everything back to the original state, how can this be done?
Thanks for your time and this very useful app ^^

			
				
Mysteryagr said:
@Nonta72
I have some questions, please
1- Does the app use the same kernel for all roms? or it flashes the required kernel while switching roms?
Click to expand...
Click to collapse
Answer: Nope ... It flashes the kernel required by each rom when you switch
2- If I'm using Android one 6.0 as a primary rom, will USB OTG work in the secondary rom?
Click to expand...
Click to collapse
Answer: If the secondary rom supports OTG, then yes. Don't forget that only Infinix 5.1 kernel does support it.
3- Does the secondary rom read both internal and external storage?
Click to expand...
Click to collapse
Answer: Yes, all ROMs you install as Dual/Multiboot can read both storages
4- can I use already installed apps like whatsapp, facebook.. etc as shared apps? does this change the location of apps and its data?
Click to expand...
Click to collapse
Answer: Refer to the App Share section of the OP. And yes, you can share all user Apps data. But you need to install Facebook/Whatsapp or whatever on both (or all roms) to be able to use shared data.
5- Just want to make sure, flashing universal OTA updates for android one rom (the zips that is made by Joseph GodSlave on facebook group) works it it is patched for primary rom?
Click to expand...
Click to collapse
Answer: You don't need to patched a primary rom. Just wipe in TWRP and install it, reboot to it, install the dual boot app and patch a secondary or multiboot rom. You can patch it for upgrade, but you shouldn't do that (just to avoid errors).
6- If I want to try multiboot then unistall it & remove everything back to the original state, how can this be done?
Click to expand...
Click to collapse
Answer: If you want to remove multiboot, just delete the multiboot folder on where you installed your second rom. If you instaled the second rom on /system parition, then it will be at /system/multiboot. If you installed it on data partition then it will be on /data/multiboot. You need a root explorer for that. You might also need to remove any multiboot folder on your Internal Storage as well as Externa Storage.

			
				
Nonta72 said:
You can patch it for upgrade, but you shouldn't do that (just to avoid errors).
Click to expand...
Click to collapse
Thanks very much, just one point I didn't get it, updating primary rom (Android one) may cause issues?

			
				
Mysteryagr said:
Thanks very much, just one point I didn't get it, updating primary rom (Android one) may cause issues?
Click to expand...
Click to collapse
Well, if you have Android One as primary. Then I guess you can update it. It might require stock recovery as well.
But I never tried it.

			
				
Nonta72 said:
Well, if you have Android One as primary. Then I guess you can update it. It might require stock recovery as well.
But I never tried it.
Click to expand...
Click to collapse
Joseph the GodSlave makes universal OTA zips which can be flashed via custom recoveries
Thanks very much for this app :good: it is very cool, you can test ported custom roms without touching system partition which make it easier for rom porters

			
				
Mysteryagr said:
Joseph the GodSlave makes universal OTA zips which can be flashed via custom recoveries
Thanks very much for this app :good: it is very cool, you can test ported custom roms without touching system partition which make it easier for rom porters
Click to expand...
Click to collapse
Yeah, I made it personally for that purpose. But I later realized it would be useful for other people. So I uploaded it.

			
				
Please I don't get it. I have a custom rom alredy and it tells me this.

			
				
olalbinx said:
Please I don't get it. I have a custom rom alredy and it tells me this.
Click to expand...
Click to collapse
It takes more time to make things for you to use on your device than reading an OP!
You could have read the post before asking such silly question.
Your issue is fixed in the OP:
NOTE: IF YOU DOWNLOADED THE APP BEFORE JULY 28, 2016; PLEASE RE-DOWNLOAD IT IN DOWNLOADS SECTION. IT IS A NEW VERSION WITH MORE SUPPORT AND FIXES.
NOTE: Before you start, it's important to change ro.product.device value to d5110_infinix in your build.prop, if you don't do this, you'll face errors. But if errors still happen, then flash it in TWRP.
Click to expand...
Click to collapse
IF YOU DON'T READ THE OP, I WILL NOT ANSWER THESE KIND OF REPORTS. IF YOU DON'T HAVE TIME TO READ, THEN I SHOULDN'T WASTE MINE READING FOR YOU!

			
				
Followed everything but it didn't work.
Sent from my Infinix X510 using XDA-Developers mobile app

			
				
Mysteryagr said:
Followed everything but it didn't work.
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
You didn't probably follow everything!
Because you're on 6.0 and you have to flash the patched zip in TWRP.

			
				
Nonta72 said:
You didn't probably follow everything!
Because you're on 6.0 and you have to flash the patched zip in TWRP.
Click to expand...
Click to collapse
That what I have done 3 times with XUI from x551 and XUI from x554 on data slot
And third time on ext sd card...
It fails to switch.
Sent from my Infinix X510 using XDA-Developers mobile app

			
				
Mysteryagr said:
That what I have done 3 times with XUI from x551 and XUI from x554 on data slot
And third time on ext sd card...
It fails to switch.
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
Go to internal/multiboot/dual and see if there is a boot.img file inside that folder.

			
			
			
			
			
			


				
			
			
			
			
			

			
		

	
		

			
[MOD][AUGUST 1][Moto G 2015] MultiROM v33a [No Kexec Workaround]
			
			
			
				
{
"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
MultiROM is one-of-a-kind multi-boot mod for Moto G 2015. 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 Moto X Play
* 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_osprey_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.
MultiROM (multirom-YYYYMMDD-vXX-osprey-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 Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive (not tested yet)
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.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed 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.​
Source code
MultiROM - https://github.com/multirom-redmi2/multirom (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)
Device Tree - https://github.com/Multirom-Lux/android_device_motorola_osprey/tree/twrp-precommon​
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
​

			
				
Downloads
1. Main downloads
MultiROM: https://www.androidfilehost.com/?fid=24591000424951534
Modified recovery (based on TWRP): https://www.androidfilehost.com/?fid=24591000424949588
Multirom Uninstaller: https://www.androidfilehost.com/?fid=24591000424949587​
2. third-party kernels with kexec-hardboot patch (Not needed)​

			
				
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.​
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.​

			
				
Enabling no-kexec workaround
As of this version you need to manually enable the no-kexec workaround.
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.​
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.​
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above​
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support​
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.​
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.... has been for quite some time, but I kinda kept it hidden
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
What we (yes, we) have come to affectionately call the "lingering primary_boot.img" this should now be taken care of, as much as possible
.
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the kernel and names it primary_boot.img
This backup is created and/or used only under certain situations, for example (this is not an exhaustive list):
the last ROM was primary, and we want to boot a secondary ---> backup the primary boot.img, flash secondary one
.
the last ROM was secondary, and we're booting another secondary ---> just flash the secondary boot.img
.
the last ROM was secondary, and want to boot the primary ROM --> restore the primary_boot.img we backed up
.
^^ and here lies the problem, we cannot actually say if the backup we created is actually correct for the primary ROM.... ideally it is, but there are easy ways to break that UPDATE: not so easy to break it all, anymore
one very simple example (as mentioned in the FAQs) would be:
==> Reboot from secondary to recovery, flash new primary ROM/kernel ---> the backup of primary_boot.img will still be there, MultiROM will still think the last ROM was a secondary, and therefore restore the backup; which will result in a non-booting primary ROM since the backed up kernel doesnt actually belong to this ROM
this is what I call a "lingering primary_boot.img"
this is just one simple example, but it can happen for a variety of reasons... interrupted boots, some app/method flashed a new kernel, etc.
The solution for the "lingering primary_boot.img":
Delete (if it's there): /data/media/0/multirom/last_rom_was_2nd no longer used
Delete (if it's there): /data/media/0/multirom/primary_boot.img
Reflash or restore the correct boot.img for your primary ROM
New safe guards to avoid a "lingering primary_boot.img":
TWRP will restore the primary boot.img when entering recovery
MultiROM identifies whether the boot.img currently in primary slot is secondary, by checking the boot.img itself;
it no longer relies on a separate file (last_rom_was_2nd)
If the boot.img in primary slot is not tagged as a secondary, it is considered a new primary boot.img
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a full second boot but with the secondary boot.img in the real boot partition
MultiROM continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Small note regarding encrypted devices using the no-kexec workaround
Since I dont use encryption, I haven't tested this to much extent, but I believe that there is a BOOT PRIMARY ROM option, which you can choose to boot into Internal without decrypting the device first.
Please be aware that this should not be used, if: the last booted ROM was a secondary using the no-kexec workaround.
The reason is that the backup of the primary_boot.img, is stored in the multirom folder, so for the no-kexec to be able to restore it, it needs access to the /data partition:
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
It's not too much of a big deal, because when the no-kexec workaround encounters an error, it reboots to recovery (and since recovery will restore the primary_boot.img), another reboot would be fine.
I do however (until I address this particular issue), encourage you not to use the BOOT PRIMARY ROM option, but instead decrypt the device, and then select the Internal ROM to boot.
Will this remain a "beta" version?
Most probably YES it will.... MultiROM is supposed to work with a kexec-hardboot enabled kernel; since that does not exist (at this time), on arm64 devices, I am using a workaround; since it doesn't exist and doesn't work, just work around it, if possible ... (call it "non-linear thinking" thinking if you wish)
until such time as the original author sees fit, or I decide to rename as "stable" (imho it is), it will remain called a "beta"
I have extensively tested this on the HTC One M7, the M8, and the M9 and have not found any side effects, so as of version 33b (2016-04-16), I consider this a stable release.
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
OnePlus One (starting here) by @KINGbabasula
Sony Xperia Z5 by @Myself5
(possibly Samsung Note 4, unsure if that was continued or not)
Others; unofficial builds?

			
				
Credits to:
@premaca (For helping with bringup)
@squid2 (For TWRP trees)
@Hashbang173 (Guiding me with no kexec workaround)
@nkk71 (For kexec workaround)
@Flashhhh & @androidbaba (For testing)

			
				
@GtrCraft thanks man for bringing multiboot to osprey. Btw Which roms are supported as of now with this?

			
				
sagar27691 said:
@GtrCraft thanks man for bringing multiboot to osprey. Btw Which roms are supported as of now with this?
Click to expand...
Click to collapse
Every rom for osprey
Sent from my XT1562 using XDA Labs

			
				
GtrCraft said:
Every rom for osprey
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Won't work on merlin ??
Although i know merlin has just a few roms !!!!

			
				
gregferns said:
Won't work on merlin ??
Although i know merlin has just a few roms !!!!
Click to expand...
Click to collapse
No

			
				
GtrCraft said:
Every rom for osprey
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
ohk... great... thanks

			
				
Good work @GtrCraft
Sent from my MotoG3 using XDA-Developers mobile app

			
				
Nice, congrats on the release. :good::good:
I need to fix up that text regarding the no-kexec workaround, since "lingering primary_boot.img" is no longer an issue... at worst a "lost/missing primary_boot.img" could be an issue, but I have not encountered / heard of it yet

			
				
Nice 1 gt am so glad ur developing for osprey!!

			
				
Thank you very much for your precious development for osprey...
But is it possible to get touch instead of hardware keys to select Roms while boot.

			
				
awesome work guys
actaully i cant install rom on ext-sdcard (as formated internal ) as it says failed to fixup roms name while adding rom on ext-sdcard and second i cant install dirty unicorn rom
and last there is not showing all files on my internal and external storage in recovery even my roms for installing sorry for my bad english
again thank you all guys for doing a great job

			
				
samirza692 said:
awesome work guys
actaully i cant install rom on ext-sdcard (as formated internal ) as it says failed to fixup roms name while adding rom on ext-sdcard and second i cant install dirty unicorn rom
and last there is not showing all files on my internal and external storage in recovery even my roms for installing sorry for my bad english
again thank you all guys for doing a great job
Click to expand...
Click to collapse
Dont install roms on ext sd card
Sent from my XT1562 using XDA Labs

			
				
nkk71 said:
Nice, congrats on the release. :good::good:
I need to fix up that text regarding the no-kexec workaround, since "lingering primary_boot.img" is no longer an issue... at worst a "lost/missing primary_boot.img" could be an issue, but I have not encountered / heard of it yet
Click to expand...
Click to collapse
Yeah, pm me if you have anything new
Sent from my XT1562 using XDA Labs

			
				
Arcade said:
Thank you very much for your precious development for osprey...
But is it possible to get touch instead of hardware keys to select Roms while boot.
Click to expand...
Click to collapse
The testers told me touch does work
Sent from my XT1562 using XDA Labs

			
				
GtrCraft said:
The testers told me touch does work
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Touch is not working. I mean touch is working in multirom twrp but once you switch on the phone it gives option to chose which one we have to install there touch is not working I am able to choose only by using harware volume keys...
Anyone else facing similar problem. If I m only one who is facing this what is gone wrong help me fix it please.

			
				
Arcade said:
Touch is not working. I mean touch is working in multirom twrp but once you switch on the phone it gives option to chose which one we have to install there touch is not working I am able to choose only by using harware volume keys...
Anyone else facing similar problem. If I m only one who is facing this what is gone wrong help me fix it please.
Click to expand...
Click to collapse
Yes +1
Touch not working while selecting which ROM to boot
Everything else works perfectly though
Thanks @grtcraft for your efforts
Sent from my MotoG3 using XDA-Developers mobile app

			
			
			
			
			
			
			
			



			
			
			

			
		

	
		

			
[MOD]MultiROM for Galaxy A5 (SM-A500)
			
			
			
				
{
"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
MultiROM is one-of-a-kind multi-boot mod for Galaxy A5. 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 Galaxy A5
* 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) Flash Modified TWRP with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature
2) Flash MultiROM zip in TWRP
3) enjoy
MultiROM has 3 parts you need to install:
Modified recovery Download the Modified TWRP for MultiROM
Patched kernel *OPTIONAL* : Not Needed
MultiROM download the ZIP file from second post and flash it in recovery.
Downloads:
Modified TWRP for MultiROM: https://www.androidfilehost.com/?w=files&flid=110082 Since the recovery image was too big for recovery partition, I used LZMA compression instead of LZO for the kernel, which saved about 3 MB
MultiROM: https://www.androidfilehost.com/?w=files&flid=110089
MultiROM Uninstaller: https://www.androidfilehost.com/?w=files&flid=110117
If you get force closes on secondary nougat ROMs:
Flash the rom, open /sdcard/multirom/roms/rom_name/system/build.prop on primary, or on TWRP with "vi" editor
and change:
Code:
ro.sys.sdcardfs=true
to
Code:
#ro.sys.sdcardfs=true
Then reboot.
DO NOT reboot the rom before changing build.prop line otherwise you will still get force closes!
You current rom will not be erased by the installation.​
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive (not tested yet)
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 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.
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 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.​
How does Kexec workaround works
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx branch cm-13.0-mrom
Kernel w/ kexec-hardboot patch: NOT NEEDED​
Credits
A big thanks for:
@nkk71 For kexec workaround and for helped me in IRC
@Tasssadar For MultiRom Source Code
That made this possible
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris​
Click to expand...
Click to collapse
​
XDA:DevDB Information
MultiROM for Galaxy A5 (SM-A500), Tool/Utility for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-09-10
Created 2016-09-10
Last Updated 2016-09-10

			
				
Reserved

			
				
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:

			
				
-CALIBAN666- said:
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
Click to expand...
Click to collapse
He he thanks

			
				
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.

			
				
-CALIBAN666- said:
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
Click to expand...
Click to collapse
No, it will br untouched, but a backup waste only 5 times, at massimum, so, if you have some free space make a backup, but as I said, it will be untouched

			
				
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks

			
				
supertiger1234 said:
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
Click to expand...
Click to collapse
Sure

			
				
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Edit: I'll choose your PacRom ;D

			
				
supertiger1234 said:
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Click to expand...
Click to collapse
CM is pure android, rr has lots of feature regarding the personalization, so, if you want a rom wich is pure android, get the cyanogenmod, otherwise, if you like to personalize your android get the resurrection remix. Oh you installed multirom, so you can install both of them (you can install more than 2 roms) and decide which one is better for you
EDIT: if you use pac-rom you have to move this as primary, because it has a bug that won't boot if you set it as secondary

			
				
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Edit: when i choose rr from the list, the device just reboots to multirom menu. hmm

			
				
supertiger1234 said:
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Click to expand...
Click to collapse
Not, try to reboot to recovery and then reflash

			
				
DeadSquirrel01 said:
Not, try to reboot to recovery and then reflash
Click to expand...
Click to collapse
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick

			
				
Mmm, maybe i have to remove preload from the fstab. Now i'll do and notify once it's done

			
				
Works on my A500M with Stock 6.0.1 and CyanogenMod 13, thank you very much for port this mod to Galaxy A5

			
				
supertiger1234 said:
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Click to expand...
Click to collapse
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support

			
				
DeadSquirrel01 said:
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
Click to expand...
Click to collapse
Hmm, The errors fixed buut now when I choose my second rom, it reboots to multirom menu xD
The non-kecex link doesn't work. Is there something important there?

			
				
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug

			
				
DeadSquirrel01 said:
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
Click to expand...
Click to collapse
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx

			
				
supertiger1234 said:
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
Click to expand...
Click to collapse
Well, it's a problem of the zip of the ROM. move it as primary or wait until I create a working installer
EDIT: maybe try with this installer https://www.androidfilehost.com/?w=file-thanks&fid=24591020540824243&mid=71&download_id=vlofv1jeu8k8ubpcpd375ql164&tid=1473585621&hc=c6de356c2e1c646fcb44f52216b36595df13152b92265bbb693814053fe5ca85

			
			
			
			
			
			
			
			
			
			



			

			
		

	
		

			
[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 Here​Cheers ! 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 Here​Cheers ! 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??

			
			
			
			
			
			
			
			
			
			

			
		

	
	
	



	
	







			

		



		

			
Categories

			
		


		

			
Resources