[OFFICIAL]DualBootPatcher[RN4/mido] - Xiaomi Redmi Note 4 [Snapdragon] ROMs, Kernels, Re

[OFFICIAL]DualBootPatcher[RN4/mido] - Xiaomi Redmi Note 4 [Snapdragon] ROMs, Kernels, Re

{
"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.

Related

[Multi boot-BETA][Apk][Condor][Patcher]

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?

[H918] Stock DeOdex Flashable ROM.

Hello! Here is a flashable ROM for the LG v20! This is STOCK, rooted, and deODEXd
(This ROM here is Stock ODEXd, and rooted for those who want that instead.)
This ROM can be used to restore your phone in the event of bootloops, crashing, accidentally wiping /system, broke your kernel, deleted a system app, or whatever... We finally have a way to fix our phone OS! So I hope this turns on the spark on you modders out there.
This zip will NOT wipe your data. It will wipe /system. It is not necessary (currently) to wipe /data for this, since we are all on the same exact base.
This ROM comes pre-rooted, comes with the insecure kernel (no mods done to kernel, just disabled the security bit). The kernel comes with no-verity, and no force encrypt. So if your /data was not already encrypted, you can flash without worry of encryption. If you do not wipe /data, it is highly recommended to at least wipe /cache and Dalvik cache.
Major thanks to @JesusFreke for smali+baksmali, also for debugging it to work with Nougat
Major thanks to @SuperR. for the kitchen )
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for mentioning someone should do it. Also, he supplied the stock System.img. /RealMVP
Also, a HUGE thanks to @nyfl2004. He very kindly fixed my updater-script, and repacked the ROM.
Below, you will find a download link, and instructions which contain ONLY the system.img. This IMG is flashable in TWRP. It is 100% stock, and it will simply convert (overwrite) your existing /system partition to a deODEXd partition.
Open WinRAR and check that the following items are 100% to this
{
"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"
}
Extract the RAR archive, and then right click the system_new.img --> Properties. Ensure that the SIZE field is identical to the SIZE from the .RAR file in the picture here, and in your file as well. Copy the file to your phone.
Please make sure you are on TWRP RC8 as provided by @jcadduono
do "adb reboot recovery" and Install > Install image > then find the .img file and flash. There is NO need to format data OR system. Simply flash and reboot. Might need to reboot again if you get stuck on the TMobile splash screen at first. ROM is already deodexed and ZipAligned. Also, the default Debloat (as provided by the kitchen) has been applied.
Basically flash this IMG over your current ROM to deODEX it. ↓
https://mega.nz/#!WANykaDb!mcx6Wm5NeNOw4aTeHyn5jcr2IQsywuHWSHegnZTqjZY ←LINK
IF YOU CAN BOOT TO TWRP, YOU CAN FIX YOUR PHONE! Instructions below
These instructions are only for people who are getting bootloops and have no way of using their phone. If you can get to TWRP, you can get your phone back up and running.
Almost always it's a corrupt /system, or perhaps you were/are encrypted.
Verify which version of TWRP you are on? If not on RC8, please flash that version.
Before starting, in TWRP, go to Settings --> and ensure that the box for "Use rm-rf...." is UNCHECKED
For the encryption, the only way to get around that is to Format Data. This will erase all your apps, and files (pictures etc). To do this (it will wipe all your things, and this is only to decrypt your data, so if you don't need to do this, don't) , go to TWRP --> Wipe --> Format Data --> follow on-screen instructions to erase your data.
Then do Wipe --> and swipe to do the Factory Reset. Now, go back to Wipe --> Advanced Wipe. Checkmark Dalvik, System, Data, Internal Storage, and Cache, and wipe those items (swipe to wipe).
Now, in TWRP, go to Mount, and make sure that System, Data, and Cache are all CHECKED. "Mount system as read-only" is UNCHECKED. Press the Back button. Go back into Mount and ensure System is still checked, and go back to the TWRP main menu again.
Now go to Advanced --> File Manager. Ensure that the system folder is empty. Press the back button. Inside of Advanced, click Fix Contents, and swipe.
Go back to the Wipe --> Advanced Wipe, and redo the format of all the aforementioned directories.
Flash the Stock ROM (deODEXd would be better IMO, but whichever). Just to be safe, also flash the no-verity.zip from the recowvery thread.
Then again, in TWRP, go to Mount, and make sure that System, Data, and Cache are all CHECKED. "Mount system as read-only" is UNCHECKED. Press the Back button. Go back into Mount and ensure System is still checked, and go back to the TWRP main menu again.
Now go to Advanced --> File Manager. Ensure that the system folder is NOT empty.
Back out and hit Reboot --> Boot to system.
A lot of these operations are redundant, but if you can still access TWRP, you should be able to fix the issue. The only way that you will have problems, is if you did a DD command and wrote something to a wrong path.
Others that can no longer access TWRP do have a still unfixable problem... But you should be good to go.
After doing all the steps, you should be able to boot.
It will first take you to the LG logo for a few seconds, and then it will reboot itself. You will see the BOOTLOADER NOT SECURE thing, and then the LG logo again. After a few seconds the TMO splashscreen will appear and do its chime sound. Give it a good 10 minutes, at which point it should take you to the Android OS page where you will have a progress bar. Once that progress bar finishes, your phone will be live. Please let me know what happens.
Debloat (Removed). Nothing yet

Just note that if you add Google Assistant via buildprop you can't access smart world. Not that I care much but just a note.. It will not recognize your device as an LG device so it will not open.

Looking forward to this. Thank you

if the build prop is changed, does that mean that Google Daydream will work? I know the screen is not ideal, but I do kinda miss my Gear VR (former s7 edge owner).

cmart4 said:
if the build prop is changed, does that mean that Google Daydream will work? I know the screen is not ideal, but I do kinda miss my Gear VR (former s7 edge owner).
Click to expand...
Click to collapse
I'm not sure. I was only going to do that so that the Pixel launcher would work. But @Swizzle82 has informed us that this would break Smart (LG Smart). Might just leave the build.prop alone, and let the user decide to change. Either way, I have yet to make a package that will flash. Then I have to see if it boots lol.

System.img link posted in OP! Overwrites current /system, no need to format. Enjoy!

Tilde88 said:
System.img link posted in OP! Overwrites current /system, no need to format. Enjoy!
Click to expand...
Click to collapse
Thanks for your work much appreciated!
Sent from my Pixel XL using XDA-Developers mobile app

Thank you so much for your work.
Could you please list the apps you removed.

netgar said:
Thank you so much for your work.
Could you please list the apps you removed.
Click to expand...
Click to collapse
Added to OP!
I'll remove more unnecessary stuff tomorrow. I'm done for today. Pokemon Moon time for me!

I installed this and my phone reboots to TWRP as a matter of fact it does this with any system image I install. Any suggestions to help with this I have looked all over and I can't seem to find anything. I would love to go back to stock and start over but that seems difficult in itself.

crazyc78 said:
I installed this and my phone reboots to TWRP as a matter of fact it does this with any system image I install. Any suggestions to help with this I have looked all over and I can't seem to find anything. I would love to go back to stock and start over but that seems difficult in itself.
Click to expand...
Click to collapse
Have you flashed no verity (or SuperSU)? If not, this can happen. Something to do with the encryption. If you cant get anything to work as you say, I would flash the stock .ZIP that is in the recowvery thread, and ensure to fully unencrypt. You will lose any data in the system.
Also what TWRP version are you on?

Tilde88 said:
Have you flashed no verity (or SuperSU)? If not, this can happen. Something to do with the encryption. If you cant get anything to work as you say, I would flash the stock .ZIP that is in the recowvery thread, and ensure to fully unencrypt. You will lose any data in the system.
Also what TWRP version are you on?
Click to expand...
Click to collapse
I was successfully able to boot into the system!! I am going to set up my device and and go from there!! Crossing fingers I don't have anymore issues.

Thanks

Was looking through your debloat list and can't seem to find a lot of those in my system. You had att smart wifi in your Tmo system?

Swizzle82 said:
Was looking through your debloat list and can't seem to find a lot of those in my system. You had att smart wifi in your Tmo system?
Click to expand...
Click to collapse
No. Like i said, this is the default debloat list included in the kitchen. It bundles in known things throughout android devices. Custom debloat is next. But i work today, so idk if ill do anything.

Is there an easy way to get permissive, I flashed your rom which saved my butt but now I don't have permissive. I don't want to mess up the system or have to flash dirty recowvery again. Thanks in advance.

crazyc78 said:
Is there an easy way to get permissive, I flashed your rom which saved my butt but now I don't have permissive. I don't want to mess up the system or have to flash dirty recowvery again. Thanks in advance.
Click to expand...
Click to collapse
Look for SELinuxModeChanger
---------- Post added at 06:39 PM ---------- Previous post was at 06:27 PM ----------
Is this a backup or a rom to replace what we have after rooting?

vibrantliker said:
Look for SELinuxModeChanger
Click to expand...
Click to collapse
Google banned it from the Play store

crazyc78 said:
Google banned it from the Play store
Click to expand...
Click to collapse
Here..

vibrantliker said:
Here..
Click to expand...
Click to collapse
Thanks!!
---------- Post added at 01:03 AM ---------- Previous post was at 12:47 AM ----------
It's not working it says it can't get root access. I am rooted I checked the settings in SUPERSU and it granted the app access. Any other ideas? I read something that it hasn't worked since lollipop and it was difficult to work on marshmallow. Ugh I really don't want to root again. I just want Viper to work.

[TOOLS][All quark] MultiROM_TWRP [TWRP 3.1.1_Mod_3][MR 35][20171111]

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?

MultiROM for Lenovo K6 Power/Plus/Note

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:
Device tree-https://github.com/karthick111/twrp/tree/karate
MultiROM - https://github.com/multirom-dev

Downloads
Karate: https://www.androidfilehost.com/?w=files&flid=230440
Karatep: https://www.androidfilehost.com/?w=files&flid=230445

FAQ and other notes
Device encryption:
Encryption isn't supported right now. So decrypt your device before using this.
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.
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.

The thug arrived...

I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?

Thomas_xxxxx said:
I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?
Click to expand...
Click to collapse
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.

dr.bathman said:
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.
Click to expand...
Click to collapse
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.

Thomas_xxxxx said:
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.
Click to expand...
Click to collapse
But sadly not working.

dr.bathman said:
But sadly not working.
Click to expand...
Click to collapse
Hope some update will fix it.

after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?

raj2k8 said:
after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?
Click to expand...
Click to collapse
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device

firemax13 said:
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device
Click to expand...
Click to collapse
i flashed both zip n img but its not working even i tried both karate n karatep bt same problem.

I have LineageOS 15.0 installed as primary ROM. Then in recovery I added OmniROM as secondary, I tried to boot it via multirom boot menu but then screen went black, LED diode was turned on even disconnecting mobile from PC and it keeped connecting/disconnecting to PC around. I cannot even see MultiROM boot menu and I was only able to boot to recovery and reflash LOS 15.0 to have my mobile working. Could it be caused by selecting OmniROM as secondary ROM? In past I tried Paranoid android and it worked without any problem. I thought my phone was bricked but fortunately I managed to fix that.

Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.

Thomas_xxxxx said:
Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.
Click to expand...
Click to collapse
Even the magisk wont work on secondary. So please use only SU.

firemax13 said:
Even the magisk wont work on secondary. So please use only SU.
Click to expand...
Click to collapse
Why magisk and xposed dont work on secondary?

MultiROM does not work with LineageOS 15.1. Is it going to be updated?

How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.

nitesh9 said:
How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.
Click to expand...
Click to collapse
Then search it on google how to. Bro you can search but please search on google please.

firemax13 said:
Then search it on google how to. Bro you can search but please search on google please.
Click to expand...
Click to collapse
I am not a total noob (I know how to google). I searched on google and didn't found any relevant result.
Then I studied the the multirom uninstaller provided by devs of other devices and figured it out myself how to remove and restore the modified files manually.
However, it would have been easier if karthick had provided the uninstaller zip like other devs. (Would have been much helpful for newbies/noobs).

MultiROM for Redmi 3S/3X (land)

Downloads
Land: https://www.androidfilehost.com/?w=files&flid=230713

Great job, thx

Taking land to unchartered territories.
Great contribution to the community.. :good:

Thanks for ur efforts sir.[emoji56]
Sent from my Redmi 3S using Tapatalk

nice work sir
Sent from my Xiaomi Redmi 3S using XDA Labs

Can we install miui and any nougat rom or can we install any nougat with oreo, or do they need to be of same android version?

Many thanks Sir!
Now our device almost have as good device support as Nexus devices!(except for sailfish OS, which would be also great to have)

I installed multiyil.zip and multi twrp.img and tried to install a rom as secondary rom to usb otg . It is succeeded,and it is showing in list rom menu.but i can't reboot to secondary rom . Plz heLp me

shafeek_muhammed said:
I installed multiyil.zip and multi twrp.img and tried to install a rom as secondary rom to usb otg . It is succeeded,and it is showing in list rom menu.but i can't reboot to secondary rom . Plz heLp me
Click to expand...
Click to collapse
What's the problem what does is shoes when u select secondary ROM from option
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
deep2111 said:
Can we install miui and any nougat rom or can we install any nougat with oreo, or do they need to be of same android version?
Click to expand...
Click to collapse
U can install any ROM u want
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------

shafeek_muhammed said:
I installed multiyil.zip and multi twrp.img and tried to install a rom as secondary rom to usb otg . It is succeeded,and it is showing in list rom menu.but i can't reboot to secondary rom . Plz heLp me
Click to expand...
Click to collapse
Force kexec
Ss attached for hint

akshat2012 said:
U can install any ROM u want
Click to expand...
Click to collapse
Couldn't install MIUI as secondary, it showed this error and the rom failed to install and deleted itself

akshat2012 said:
What's the problem what does is shoes when u select secondary ROM from option
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
U can install any ROM u want
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Click to expand...
Click to collapse
There is no option or menu when I boot .!So it 9s always rebooting to primary rom

Sir I tried to install my secondary rom viper coral but after select from boot viper coral and then boot into recovery not into rom.... Sorry for my bad English..

Does beacon kernel support multi boot??

shafeek_muhammed said:
Does beacon kernel support multi boot??
Click to expand...
Click to collapse
Yes, you can use it with beacon kernel.

How to uninstall multirom?

Restore boot, recovery
Tedy Ramdani said:
How to uninstall multirom?
Click to expand...
Click to collapse
I have just restored boot, recovery
And everything seems normal
Land 3s prime
---------- Post added at 12:23 PM ---------- Previous post was at 12:18 PM ----------
chaubeyprateek said:
Force kexec
Ss attached for hint
Click to expand...
Click to collapse
Did as per instruction yet booting to primery ROM.

I can't get choose os screen @chaubeyprateek

Database Info

welcome