Hey guys the much awaited DualBootPatcher is here for our Condor don't believe me test out yourself
It can patch:
Custom kernels for multi support
ROMs so that they can be installed as secondary
Google Apps packages
SuperSU so that it can be used in other ROMs
xposed
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
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 partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
NOTE- It is highly recommended to install secondary roms in external sd slot
How To
1. Install the Multi Boot Patcher app
2. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
3. Now go to rom settings and click on "Update ramdisk" it will update ramdisk and after that reboot
4. Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
*FLASHING FROM RECOVERY NOT RECOMMENDED*
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
1.Install the app you want to share
2.Open DualBootPatcher and go to "App Sharing" in the navigation drawer
3. Enable individual app sharing
4. Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes 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.
FAQ's
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
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
Link :- https://snapshots.noobdev.io/
CREDITS
@chenxiaolong For the app
Me for porting it for you guys @princetrishi for the video
ORIGINAL THREAD
XDA:DevDB Information
Multiboot for condor , Device Specific App for the Moto E
Contributors
zeeshanhussain12
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: 8.99.12
Beta Release Date: 2015-11-14
Created 2015-11-14
Last Updated 2015-11-14
Reserved
How To Report Issues ?
Getlogs.zip: getlogs.zip
If a multi-booted ROM is unable to boot, logs will be needed for debugging the issue. Please reboot into recovery without shutting down the device (ie. no removing the battery u cant remove battery in moto e [emoji14] ) and flash the GetLogs zip. This must be done immediately following the boot failure because some logs will be lost after a reboot The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.
Also, state whether the ROM reboots or hangs at the moto logo or the ROM's boot animation. If the ROM reboots, please state whether it reboots into recovery or not.
NOTE- CM13 is supported
Installation Video
Thanks to YouTuber Starkdroid (@princetrishi) for making this awesome installation video!
Screenies [emoji10]
{
"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"
}
Awesome work, thanks for your hard work
And the VIDEO TUTORIAL IS HERE!!!
https://www.youtube.com/watch?v=NCk1tr6T76M&feature=youtu.be
worked
Thanks bro.... Worked for me...
Doubt
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Edit : I flashed gapps seperately...and it worked!!!
Steps for those who face similar problems while patching Gapps -
1. Switch the ROM from Dual Boot Patcher.
2. Reboot your phone. If you flashed correctly, you should be on the secondary ROM....
3. Reboot to recovery and flash gapps. No need to wipe cache/dalvik cache.
4. Woila! Gapps flashed successfully!
Hit Thanks Button if I Helped!!!
The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
You need to patch gapps too [emoji6] and flash it from the app itself
Sent from my Moto E using Tapatalk
The Keeper said:
No....I tried. It doesn't work. It fails.
Click to expand...
Click to collapse
Its working for me, make sure you patch for correct slot
Sent from my Moto E using Tapatalk
Hey...will this work with cm13 as primary rom?
can this work with cm13 as secondary rom?
ishu.aryan said:
can this work with cm13 as secondary rom?
Click to expand...
Click to collapse
Nop cm13 is not supported in both primary and secondary ROM , I m still working on that part mate
Adrao123 said:
Hey...will this work with cm13 as primary rom?
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk
Thanks for the port
I was waiting for lp support of multirom, and then you ported multiboot, this is far better than multirom..
The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash
viku1996 said:
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash
Click to expand...
Click to collapse
umm..okay...Thanks
It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk
Please be more precise and which ROM you are using?
Note - cm13 is not supported
Gowtham_j said:
It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk
I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".
Gowtham_j said:
I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".
Click to expand...
Click to collapse
It was working for my friend. Please upload ramdisk update log . it will be there in multiboot folder
Sent from my Moto E using Tapatalk
if i wanna flash xposed
then should i patch xposed zip too?
Related
{
"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 Lg G3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d851.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d851_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be 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.
Source code
device tree https://github.com/Skin1980/device-d850-multirom
kernel https://github.com/Skin1980/android_kernel_lge_msm8974ac
twrp https://github.com/Skin1980/Team-Win-Recovery-Project
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
@Tectas cause i used his ( awesome) source code for building the kernel
And sure... tnx to the guys who tested this ( will add the name later sorry)
...and all the people that now i forget
PLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
IMPORTANT: Need to be with a Kitkat stock Rom ( if you use my kernel ) or with a rom that have a kernel with the kexec hardboot patch.
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
If you want show me your love for this you can consider a small DONATION
Issues:
1- On boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.
Can't wait to try this!! Thanks!
deleted.
I'm happy with one ROM at a time lol but cool stuff going on right heeyah!
★2SHAYNEZ★
I installed as per the instructions, I was able to boot up with my existing Rom. I then went to advanced multi Rom and installed another Rom. I have a couple questions, for aosp roms how do I flash the kernel and or gapps? When I attempt it hangs add says a message about looking for boot loader. Also I never got a prompt about selecting the second Rom,perhaps didue to the kernel not flashing?
I saw a video where once you add the rom, go to List of ROMs, choose the ROM you just flashed, it'll open ANOTHER menu, choose "Flash Zip" and flash gapps THEN boot that ROM. it's tedious but beneficial.
I installed per instructions..will not load back into TWRP after..just sits on LG logo forever.
Sent from my LG-D850 using Tapatalk
oranget said:
I installed per instructions..will not load back into TWRP after..just sits on LG logo forever.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Once I installed the modified twrp. It takes like 6 minutes to get into recovery every time.
jasonpantuliano said:
Once I installed the modified twrp. It takes like 6 minutes to get into recovery every time.
Click to expand...
Click to collapse
Will take a look tomorrow
Sent from my SM-N910F using XDA Free mobile app
Thanks for this, though im curoius if their is a way to uninstall. its working but running very slowly when booting, like 10 times longer than usual. or maybe with an update, this can be fixed.
probs
Takes 10 minutes to boot now, and I get a secure boot error if I try to flash any primary rom + kernel panic if I try to install/boot any secondary rom. Followed all the instructions (other than kernel, as I use Rin kernel) and injected boot sector and what not... Only thing I can boot is my nandroid backup. How to fix this or uninstall multirom?
King Ramen said:
Takes 10 minutes to boot now, and I get a secure boot error if I try to flash any primary rom + kernel panic if I try to install/boot any secondary rom. Followed all the instructions (other than kernel, as I use Rin kernel) and injected boot sector and what not... Only thing I can boot is my nandroid backup. How to fix this or uninstall multirom?
Click to expand...
Click to collapse
Don't use inject... Flash multirom again
Sent from my SM-N910F using XDA Free mobile app
omaralkha99 said:
Thanks for this, though im curoius if their is a way to uninstall. its working but running very slowly when booting, like 10 times longer than usual. or maybe with an update, this can be fixed.
Click to expand...
Click to collapse
Will build a new kernel later
Sent from my SM-N910F using XDA Free mobile app
Skin1980 said:
Don't use inject... Flash multirom again
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
flashed multirom again, still getting a kernel panic in secondary ROM. I'm using Liquidsmooth 4.0 lollipop with Rin 1.6.5 as the main rom and OA855minus5 (which is an LG based ROM) as the secondary ROM with Rin 1.8.5, is there something I'm doing wrong here?
King Ramen said:
flashed multirom again, still getting a kernel panic in secondary ROM. I'm using Liquidsmooth 4.0 lollipop with Rin 1.6.5 as the main rom and OA855minus5 (which is an LG based ROM) as the secondary ROM with Rin 1.8.5, is there something I'm doing wrong here?
Click to expand...
Click to collapse
Flashing multirom again might solve the signature error... as for kernel panic can't help because I can't test it. Maybe a last_kmsg can help
Sent from my SM-N910F using XDA Free mobile app
Skin1980 said:
Flashing multirom again might solve the signature error... as for kernel panic can't help because I can't test it. Maybe a last_kmsg can help
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Ok, I'll give it a shot and let you know how it goes. I'll try to run Liquid as a secondary and stock as primary and see if it panics/boots then.
Nope, no buzz. Flashed multirom again, then flashed the stock rom as the primary rom, then flashed Rin kernel. Secure boot error on the primary ROM
Couldn't get to the secondary ROM b/c the secure boot error would just pop up right away on startup, preventing the multirom menu from popping up
King Ramen said:
Ok, I'll give it a shot and let you know how it goes. I'll try to run Liquid as a secondary and stock as primary and see if it panics/boots then.
Nope, no buzz. Flashed multirom again, then flashed the stock rom as the primary rom, then flashed Rin kernel. Secure boot error on the primary ROM
Couldn't get to the secondary ROM b/c the secure boot error would just pop up right away on startup, preventing the multirom menu from popping up
Click to expand...
Click to collapse
Flash multirom zip as last thing and don't use inject
Sent from my SM-N910F using XDA Free mobile app
Skin1980 said:
Flash multirom zip as last thing and don't use inject
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
now it's just going into fastboot mode whenever booted
King Ramen said:
now it's just going into fastboot mode whenever booted
Click to expand...
Click to collapse
Very strange... try to do again all the steps in 2nd post. Might works
Sent from my SM-N910F using XDA Free mobile app
Introduction
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi4i. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
Multiboot any number of Android ROMs
Restore nandroid backup as secondary ROM
Boot from USB drive attached via OTG cable
Warning!
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be 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
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.
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.
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
MultiROM for Mi4i, Tool/Utility for the Xiaomi Mi 4i
Contributors
haikalizz
Source Code: https://github.com/webhaikal/android_device_xiaomi_ferrari-twrp
Version Information
Status: Alpha
Created 2015-12-11
Last Updated 2017-06-07
Reserved
Downloads
MultiROM : https://transfer.sh/Lz0kx/multirom-ferrari.zip
Modified Recovery : https://transfer.sh/fILcp/recovery-mr-ferrari.img
MultiROM Uninstaller : Coming Soon
Supported Kernels
This kexec-less multirom
Reserved
FAQ and other notes
About securityIn 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.
Where can I find files from other ROMs?http://forum.xda-developers.com/mi-4i/general/index-xiaomi-mi4i-roms-kernels-toolkits-t3187438
Can I have different versions of Android working alongside? How to use Lollipop and Marshmallow at the same time?Yes. The systems are separated.
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.
The boot animation shows after a few seconds on primary ROMs, why?Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.
Can I use MultiROM without root?Yes, if you don't use MultiROM Manager app but flash everything manually
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs
My secondary ROM doesn't boot, what should I do?Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again
Will this work for cm13 and MIUI 7 as they have different partition tables.
sykomaniac said:
Will this work for cm13 and MIUI 7 as they have different partition tables.
Click to expand...
Click to collapse
Haven't tested with Miui but CM and CM works...
hello friends which is the best rom with reduce heating issue and best battery back up?
jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
Wrong thread Ask this question in Q&A thread please.
jai25993 said:
hello friends which is the best rom with reduce heating issue and best battery back up?
Click to expand...
Click to collapse
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
haikalizz said:
You can install it either from MultiROM Manager app or from this guide:
Click to expand...
Click to collapse
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Awesome ! Great job !! waiting for report of Miui / Polska / Pro + CM rom combination..
stiw47 said:
EDIT
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
It's safe though, the app still hasn't recognised our phone yet..
I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.
stiw47 said:
@jai25993: Please, don't spam the thread, your question have no any relation with this thread, you should ask this in Xiaomi MI 4i Q&A section.
I am a person who always prefered multi boot on computer, and who like to play with OS's. At this moment, I have four GNU/Linux distros, one Windows and one Android x86 installed on my laptop hdd, and can't belive that finaly can try similar things on my phone.
Thanks to dev(s), and God bless you
EDIT:
I installed MultiROM Manager app, and app said "ferrari is not suported":
Is it safe to try manually, is somebody try allready?
Click to expand...
Click to collapse
sorry dear i will be careful in next time
Push to github and link them ! Good job
haikalizz said:
I uploaded a new recovery image. Old one wasn't built with multirom... My mistake, sorry.
Click to expand...
Click to collapse
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?
stiw47 said:
I didn't try first uploaded (wrong) recovery image, but I think that new one, aka second uploaded, is not good. I was try to flash several times, either via Flashify, Rashr or fastboot, I downloaded again, and flash again via all above tools, everytime flash is succesful, and every time i got only black MI splash screen, when I try to boot to recovery (no recovery screen). If I execute "adb devices" in that moment, I got recognized device with number (List of devices attached *some number* recovery), and yes, it says is in recovery, but no recovery screen on phone.
Did you try your method? Is it working with you?
I am on Ressurection Remix if that is meather (I think no), and using TWRP Mi4i by magdag.
P.S. Can you be more specific in which order we should install a files? I think:
1. MultiROM .zip
2. Modified recovery
3. Sensei kernel
4. Second ROM
Am I wrong?
Click to expand...
Click to collapse
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.
haikalizz said:
You're right on the order. About the recovery, both versions didn't have UI... I'm guessing some ui scripts didn't compiled... Need to check.
Click to expand...
Click to collapse
So what now? Can we use this recovery without ui on some way via adb/terminal (or some other way, I don't know), or we should waiting for ui fix?
Don't know how to use it without the ui though, no harm trying. I've pm'ed the multirom dev for any info on this...
Account removal
Deleted
Is it whole this method usable at this moment. How? (without gui in recovery)?
I may have found an error in the TWRP compiled for multirom... Can't get a logcat to actually ensure it but compiling TWRP from omnirom works just it doesn't have the multirom features
{
"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
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,
AospExtended-4.2-mido.zip
After patching would create a new
AospExtended-4.2-mido_data-slot.zip
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.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually you can do it using the app.
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
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
YouTube Tutorial:https://youtu.be/T44ifBaHAWs
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>FOMATE DATA then type 'yes' and tap enter. Now reboot and retry DBP.
App sharing not working.
Source/Credits:
https://dbp.noobdev.io
DOWNLOADS
~ Hit Thanks:good: button below if I helped you ~
Thankyou for starting this useful thread.
drmuruga said:
Thankyou for starting this useful thread.
Click to expand...
Click to collapse
Welcome
i flash two rom,when into the primary rom, the system show the password was wrong
PrayerInc said:
i flash two rom,when into the primary rom, the system show the password was wrong
Click to expand...
Click to collapse
Boot to twrp and open filemanger, go to data>system and remove .key file(what ever you have used ex: pattern.key, password.key , etc)
One should not use any type of security lock on pimary rom.
its not working for me
varunangirash said:
its not working for me
Click to expand...
Click to collapse
What's not working?
What at "Slot ID"?
bad_request said:
Boot to twrp and open filemanger, go to data>system and remove .key file(what ever you have used ex: pattern.key, password.key , etc)
One should not use any type of security lock on pimary rom.
Click to expand...
Click to collapse
so i cant set fingerprint and password in primary rom, what about the secondray rom and others??? if they set fingerprint and password,what will happen??
why other type phone havent this problem???
Jack'O said:
What at "Slot ID"?
Click to expand...
Click to collapse
Slot I'd is just a name. Like you are using two ROMs on data slots , you can give different names to each slots.
ex: rr, aosp, miui, lineage, etc
PrayerInc said:
so i cant set fingerprint and password in primary rom, what about the secondray rom and others??? if they set fingerprint and password,what will happen??
why other type phone havent this problem???
Click to expand...
Click to collapse
Its a bug, you can try and test if it's working or not on secondary rom, as I don't use security locks I can't tell if it's working or not .
Not working
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom
varunangirash said:
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom
Click to expand...
Click to collapse
How much space has left on your device?
Sorry I have not been keeping pace with things here. But does it allow two miui roms to dual boot? The last I remember was that only aosp were supported, IIRC.
varunangirash said:
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom
Click to expand...
Click to collapse
Bro don't use Secondary/dual slot for rom installation
zenjedi said:
Sorry I have not been keeping pace with things here. But does it allow two miui roms to dual boot? The last I remember was that only aosp were supported, IIRC.
Click to expand...
Click to collapse
Yes you can but always use data slots.
yes first i installed in secondary then i reliazed that its not have sufficient space so i installed on data slot but when i switch to my second rom that is rr and primary is miui 8.2.5 its not booting.
---------- Post added at 10:42 AM ---------- Previous post was at 10:36 AM ----------
Please see this Ss and give suggestions
Trying to patch a .zip i get an advise to "set documents into settngs > installed apps"
and the file don't get patched of course, and all permissions are granted.
varunangirash said:
yes first i installed in secondary then i reliazed that its not have sufficient space so i installed on data slot but when i switch to my second rom that is rr and primary is miui 8.2.5 its not booting.
---------- Post added at 10:42 AM ---------- Previous post was at 10:36 AM ----------
Please see this Ss and give suggestions
Click to expand...
Click to collapse
Are you using official miui rom?
Jack'O said:
Trying to patch a .zip i get an advise to "set documents into settngs > installed apps"
and the file don't get patched of course, and all permissions are granted.
Click to expand...
Click to collapse
On miui roms you have to first enable documents app by going to settngs > installed apps
And then you can patch files.
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
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.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
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.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please:
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port
We will have to try soon... It's the perfect set up for flashaholics
Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk
I can't make it work
fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Superb, I missed it in this great smarphone
acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?
there is only one TWRP in your folder. can you point me to another. I'll try no worries
acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....
BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/
BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?
Read the update post if you are updating(click here to go there)
{
"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"
}
What is MultiRom?
MultiROM is one-of-a-kind multi-boot mod. 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. Roms are installed and managed via the 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.
Warning!
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is possible that something goes wrong and you will have to re-flash yours current Rom zips again. Make backups. Always!
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
Boot from USB drive Attached via OTG cable (untested)
Compatibility
Theoretically any ROM can be used as primary or secondary, but I only test the bellow scenario:
Nougat Custom ROM Primary and secondary OK
Marshmallow Stock secondary OK
All the other possibilities of ROM are untested, also important encryption wasn't tested yet.
Installation instruction:
Via The MultiRom Manager App:
This is the easiest way to install everything MultiROM needs... Just follow the Below Instructions:
Install the app (MultiROMMgr_Quark_xx.apk) From Download folder
Select MultiROM and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
Done.
You current rom WILL NOT be erased by the installation.
Manually via TWRP
Download the files
Install the Multi_ROM TWRP just like normal TWRP, check norma TWRP installation instructions in case of doubt
Flash MultiROM.zip in the primary ROM
Reboot to recovery and start using it
On secondary if Custom ROM and you have bootloop problem flash the Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to the secondary ROM
Download Folder Click here
Files description:
MultiROMMgr_APP_Quark_xx.apk MultiROM manager app adapt for Quark
multirom_twrp-X.X.X-mod_X-quark.img Normal TWRP image, but with a TWRP adapted for multiROM
multirom-XXXXXXX-vXX-quark.zip flashable zip of multiROM boot manager interface
multirom_uninstaller.zip flashable zip to remove multiROM boot manager interface and cleanup any secondary ROM
Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip flashable zip, if using latest version of my kernel or Nougat ROM released by bhb27 no need to flash this but if you not, this is temp fix for any custom ROM running old version of my kernel or not as a secondary ROM, eventually this won't be need but to day it is, need to re-flash this in case of a kernel change.
XXXX are related to version and dates
Credits:
Tasssadar -Developer of MultiRom
nkk71 - For his No-KEXEC workaround that allow multi_boot to work without complicated kernel modifications
TWRP and MultiROM source click here and read the README.md
App source click here
Developer donation link:
To donate via paypal click here
No other donation option is available.
Help and etc:
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom (top right corner menu) -> Add Rom -> Select the Rom's zip file or backup and click Confirm.
Switching ROMs (primary to secondary and vice versa):
To make the boot process faster I recomende to disable boot manager interface from showing on every time the device boot's and enable the "keypress-based boot", to enable it go to TWRP top right corner (Multirom menu on TWRP) > Settings > Auto boot > mark "keypress-based boot" and if you wanna to go to "boot manager interface" durring boot after the device vibrate press and hold volume up
Now to switch ROM the "boot manager interface" can be used just go there and click over the ROM you wanna to boot.
Or use the MultiROM manager app
On the app just open it slid left to right or click on left corner to open the tab menu > Manage ROMs > Click on the ROM > click BOOT
Warning!
Very importante always go back to primary ROM from a secondary before going to another secondary this is to prevent the boot.img of primary be override with the secondary and cause boot problems, in case that happens is always possible to restore a boot.img of primary using TWRP backup or flashing a boot.img that can be found on the ROM.zip of your current ROM
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 unless you wipe internal memory or format Data)
* 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 the Rom, follow these steps:
* Go to MultiRom -> List Roms and select the Rom you want to update.
* Select "Flash zip" and Flash the 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 Update something, for example a Kernel or a ROM, which is Distributed as a Whole boot.img (eg. ROM update zip), 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 - No Need to Explain this I Think!
- 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 a Developer Option.
In case of a problem related to this project use @bhb27 on a post on this thread.
If anyone test different combinations of primary+secondary and or encryption let me know on the thread.
When we think our phone is going to die... BAM!
THANK YOU!
@bhb27
Your skills will never cease to amaze me my friend, great work!! Now I want to buy another Quark :good:
Wow! Sounds really good. Great job @bhb27
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
johnbravado said:
@bhb27 I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.
On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
Click to expand...
Click to collapse
the multirom.zp doesn't change yours current ROM you did something that cause that, it is just the boot manager support.
on main twrp menu you manage yours primary ROM, on MultiROM menu the extra secondary, you can restore yours backup via normal twrp menu and all must be fine, inject the multiRom boot after restore before reboot.
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
This is nice. Kinda like having safestrap again from the Moto Droid Maxx I had before the turbo.
bhb27 said:
I push the manager app to download folder, it allow in android changes, direct boot, etc...
when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.
:good:
Click to expand...
Click to collapse
:good:
Seven android nougat!!
Links to all those?
Bumpn gums from my vzw DROID Turbo xt1254
---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------
Which is best? RR I'm sure haha
Bumpn gums from my vzw DROID Turbo xt1254
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
RSDamasceno said:
:good:
Seven android nougat!!
Click to expand...
Click to collapse
gangrenius said:
Links to all those?
Click to expand...
Click to collapse
I'm sure you are joking? You know they are all the Development section of this forum. Well, except for AOKP, which is over in the Development section of the split "Droid Turbo" forum.
But if you really are serious, then it's always a good idea to keep an eye on this thread:
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
That link is to the most recent post.
Rarely I speak before thinking and this was an occasion
Bumpn gums from my vzw DROID Turbo xt1254
z4ck1n said:
@bhb27 this is fantastic !! Thanks !!
Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.
Which partitions to backup before trying this ?
Click to expand...
Click to collapse
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Fantastic work
It's really great to see that devs are still working on quark. I'm also very excited to see Multi ROM for our device. It would be even more great if someone ports any Linux based OS to our device...
there is no need to flash Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to a secondary ROM if you have update your secondary to the latest version of the ROM or the kernel that I released...
It worked very well on my Maxx :good:
Thank you!
Is it possible to include the queue function for the secondary ROMs?
bhb27 said:
system and boot, for ROM only.
system, boot and data if you wanna keep apps and they data...
if you test stock ROM as primary let me know the result.
Click to expand...
Click to collapse
I don't want to mess with primary rom (current stock mm). Want to install this over it, without losing data.
My Data is to big to be backup ...
Few Questions
How does multirom work? Does it change boot sector record like normal desktop oses?
In multirom installation which partitions are impacted?
Where is secondary rom installed?