DualBoot for Xiaomi-Redmi-5-Plus
Hi all, I´m not the maintainer but just sharing this useful app that I used in many devices and now our device is supported (I have 4/64 but must to work in the other variant)
DualBoot patcher is an open-source project initially running for Galaxy S4 developed by chenxiaolong (now is a large community) that allows install multiple roms simultaneously so many that storage can.
This is the main thread for discussion, bugs and help https://forum.xda-developers.com/showthread.php?t=2447534
You can download here the latest build https://dbp.noobdev.io
-getlogs for reporting issues, apk, Utilities (to switch to selected rom and wipe somethings from recovery if it´s necessary) and Windows to patch some rom from pc
Before any flashing session you have to backup all the important data from your device, I ever backup my EFS where is place IMEI and other files. (our oficial TWRP have this option) For strange reason cause my bootloader was unlocked from the seller I ever lost my signal flashing a main rom but just restoring backup the issue is solved.
Many users know how to run this app but for those who do not know here let you a simple and noob guide. Generally it runs properly using stock rom (the one that comes with the device, in this case miui) like primary rom and I ever used the other roms in data slot partition but it works also in secondary, etc or in ext-sd slot. I will use MiuiPro like primary and crDroid in data-slot. Is ideal to try roms without affecting our main daily-use rom. These would be the steps.
1- First of all install normally apk in your usual rom, open app and go to settings and check “Allow receiving intents”
{
"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"
}
2- You will be prompted to set kernel, tap in “set now”. You are ready with your first rom, now go to install a second rom.
3- Go to option “patch zip file” (you have to have a rom.zip in your sdcard)
4- Tap in “add flashable zip”
5- Browse to the zip rom and select it.
6- Select the slot where you´ll go to install your rom and put a name (don´t accept capital letters or spaces also some symbols)
7- When patch finishes you have to receive a “succedeed” message. Your patched zip will be placed in same folder that original.
8- Now go to main screen and select the icon in red to flash your zip patched from the same app (you don´t need to go to recovery but you can)
9- You will be prompted with a warning message, just tap “ok”
10- Tap “add patched file”
11- Browse to your zip patched and select, if confused what you should to select just compare date/hour (is a noob guide)
12- You will be prompted if you want to change or keep location, if you are ok tap in “keep it”.
13- You will see your zip selected with complete name to check if it´s right, proceed to flash it.
14- You have to see a suceeded flashing in green letters. If you have Gapps, mods like Magisk do the same steps till here.
15- Now go back and you will see in your main screen also your second rom, actually is checked, it means that if you reboot will do it in your other rom.
16- Now go to “reboot” options and tap it.
17- Now you are in the second rom, to can boot to primary repeat 1st and 2nd steps. To flash a third rom repeat process from 3rd step.
Some tips: Ever that you go to flash some mods or update some rom you have to patch it first. I didn´t try this option to change primary rom if existing others.
Ever that you flash something in recovery without patching it then you´ll go to flash it over your primary.
Ever keep DualBoot utilities in your sdcard, if device refuses to boot in secondary rom or any else you´ll have to flash it and a aroma installer will guide you to switch to your selected rom (if it´s able to, most of times to primary). Eventually if you want to simply reboot to your primary rom you can flash boot.img placed in /sdcard/multiboot directory.
good stuff!thanks dude!
ty, but can anyone port MultiROM?
How to revert back to stock i.e single /mono boot
Mohdjameel said:
How to revert back to stock i.e single /mono boot
Click to expand...
Click to collapse
If you want to preserve your first rom, main rom and use it like a single one, simply delete from DBP all the rest, go to wipe options and check all the boxes; In this stage your only rom runs without any dependency about DBP and you don´t need uninstall it but if you want uninstall you can do it without affecting this rom, then if you want also delete manually folder multiboot inside sdcard and if you want to delete all this stuff go to /data/multiboot and just erase it but this folder don´t affect nothing
SubwayChamp said:
DualBoot for Xiaomi-Redmi-5-Plus
Hi all, I´m not the maintainer but just sharing this useful app that I used in many devices and now our device is supported (I have 4/64 but must to work in the other variant)
DualBoot patcher is an open-source project initially running for Galaxy S4 developed by chenxiaolong (now is a large community) that allows install multiple roms simultaneously so many that storage can.
This is the main thread for discussion, bugs and help https://forum.xda-developers.com/showthread.php?t=2447534
You can download here the latest build https://dbp.noobdev.io
-getlogs for reporting issues, apk, Utilities (to switch to selected rom and wipe somethings from recovery if it´s necessary) and Windows to patch some rom from pc
Before any flashing session you have to backup all the important data from your device, I ever backup my EFS where is place IMEI and other files. (our oficial TWRP have this option) For strange reason cause my bootloader was unlocked from the seller I ever lost my signal flashing a main rom but just restoring backup the issue is solved.
Many users know how to run this app but for those who do not know here let you a simple and noob guide. Generally it runs properly using stock rom (the one that comes with the device, in this case miui) like primary rom and I ever used the other roms in data slot partition but it works also in secondary, etc or in ext-sd slot. I will use MiuiPro like primary and crDroid in data-slot. Is ideal to try roms without affecting our main daily-use rom. These would be the steps.
1- First of all install normally apk in your usual rom, open app and go to settings and check “Allow receiving intents”
2- You will be prompted to set kernel, tap in “set now”. You are ready with your first rom, now go to install a second rom.
3- Go to option “patch zip file” (you have to have a rom.zip in your sdcard)
4- Tap in “add flashable zip”
5- Browse to the zip rom and select it.
6- Select the slot where you´ll go to install your rom and put a name (don´t accept capital letters or spaces also some symbols)
7- When patch finishes you have to receive a “succedeed” message. Your patched zip will be placed in same folder that original.
8- Now go to main screen and select the icon in red to flash your zip patched from the same app (you don´t need to go to recovery but you can)
9- You will be prompted with a warning message, just tap “ok”
10- Tap “add patched file”
11- Browse to your zip patched and select, if confused what you should to select just compare date/hour (is a noob guide)
12- You will be prompted if you want to change or keep location, if you are ok tap in “keep it”.
13- You will see your zip selected with complete name to check if it´s right, proceed to flash it.
14- You have to see a suceeded flashing in green letters. If you have Gapps, mods like Magisk do the same steps till here.
15- Now go back and you will see in your main screen also your second rom, actually is checked, it means that if you reboot will do it in your other rom.
16- Now go to “reboot” options and tap it.
17- Now you are in the second rom, to can boot to primary repeat 1st and 2nd steps. To flash a third rom repeat process from 3rd step.
Some tips: Ever that you go to flash some mods or update some rom you have to patch it first. I didn´t try this option to change primary rom if existing others.
Ever that you flash something in recovery without patching it then you´ll go to flash it over your primary.
Ever keep DualBoot utilities in your sdcard, if device refuses to boot in secondary rom or any else you´ll have to flash it and a aroma installer will guide you to switch to your selected rom (if it´s able to, most of times to primary). Eventually if you want to simply reboot to your primary rom you can flash boot.img placed in /sdcard/multiboot directory.
Click to expand...
Click to collapse
Failed to determine device's codename?
liakaichen said:
Failed to determine device's codename?
Click to expand...
Click to collapse
I didn´t have this issue, if you are using a rom with a right build.prop for our device then it will detect ever with vince codename.
SubwayChamp said:
If you want to preserve your first rom, main rom and use it like a single one, simply delete from DBP all the rest, go to wipe options and check all the boxes; In this stage your only rom runs without any dependency about DBP and you don´t need uninstall it but if you want uninstall you can do it without affecting this rom, then if you want also delete manually folder multiboot inside sdcard and if you want to delete all this stuff go to /data/multiboot and just erase it but this folder don´t affect nothing
Click to expand...
Click to collapse
Yo mean that just by deleting multirom folder I can remove the dual boot ROM from system partition
Ryt?
How to swap between roms
Mohdjameel said:
Yo mean that just by deleting multirom folder I can remove the dual boot ROM from system partition
Ryt?
How to swap between roms
Click to expand...
Click to collapse
Nop, don´t confuse with multirom, this app has other method to can boot in a specific rom, not needed delete a folder to delete the rom, just I mentioned if you want to delete all the traces of this app i your device but if you want to just delete a rom (not the primary) open the app, then tap on three dots on the right side of the other rom and you will see the option wipe, tap on it and then all the partitions/files that you want to delete related to this rom including the rom itself.
If you want to switch to other rom then go to main screen and you will see that your actually rom is checked
just tap in any place on the rom wich you want to switch and it will be checked
then go to option reboot and is done
SubwayChamp said:
Nop, don´t confuse with multirom, this app has other method to can boot in a specific rom, not needed delete a folder to delete the rom, just I mentioned if you want to delete all the traces of this app i your device but if you want to just delete a rom (not the primary) open the app, then tap on three dots on the right side of the other rom and you will see the option wipe, tap on it and then all the partitions/files that you want to delete related to this rom including the rom itself.
If you want to switch to other rom then go to main screen and you will see that your actually rom is checked
just tap in any place on the rom wich you want to switch and it will be checked
then go to option reboot and is done
Click to expand...
Click to collapse
Thanks for the assistance
How to get an interface to swap into ROMs on boot
Why boot hi is not supported??
SubwayChamp said:
I didn´t have this issue, if you are using a rom with a right build.prop for our device then it will detect ever with vince codename.
Click to expand...
Click to collapse
I'm using Lineage 15.1 20180423version.will this room cause this issue?
I tried to dual boot aex 4.6 running7.1.2
And after I booted to that ROM it boot looped
Way to do?
Mohdjameel said:
How to get an interface to swap into ROMs on boot
Why boot hi is not supported??
Click to expand...
Click to collapse
Instead a BootSwapp or SwappRom app apart you can create a direct access icon to desktop and just tapping on it you swap to this rom.
SubwayChamp said:
Instead a BootSwapp or SwappRom app apart you can create a direct access icon to desktop and just tapping on it you swap to this rom.
Click to expand...
Click to collapse
Without reboot??
Mohdjameel said:
Without reboot??
Click to expand...
Click to collapse
Yes, if you reboot device without do nothing then it will reboot in the same rom like a normal reboot, it doesn´t need to display a screen to choose a rom to boot like multirom, instead of this when you are in for example your main rom then select other that you want to swap on in the next reboot and for this you can create an icon in your desktop and then just tapping on it automatically it will reboot to this rom.
SubwayChamp said:
Yes, if you reboot device without do nothing then it will reboot in the same rom like a normal reboot, it doesn´t need to display a screen to choose a rom to boot like multirom, instead of this when you are in for example your main rom then select other that you want to swap on in the next reboot and for this you can create an icon in your desktop and then just tapping on it automatically it will reboot to this rom.
Click to expand...
Click to collapse
Hey is that a bug I got ,that I couldn't unlock my passcode of primary ROM with the last unlocking passcode i.e my system forgot the passcode which I had set and won't let me unlock my device
Hey I want to dual boot Cr droid treble rom how do I do that
I am getting error
Destroying chroot environment
Bla ...bla
??
Please give me the links of ROMs that can be patched and installed through dbp
Mohdjameel said:
Playback give me the links of ROMs that can be patched and installed through dbp
Click to expand...
Click to collapse
In the first post is the general concept in how it works and which kind of roms run properly (till nougat that was when this thread was created)
Let call secondary rom to any other rom but the primary.
This would be the general picture;
You can use:
- Like primary any miui (stock rom) and any of the android pure (aosp, LO, aex, etc) based running nougat like secondary (more than one)
- Like primary any of the android pure (aosp, LO, aex, etc) based running nougat and any of the android pure (aosp, LO, aex, etc) based running nougat like secondary (more than one)
- Like primary any stock miui or any of the android pure (aosp, LO, aex, etc) based running nougat and only greatslon (called "aroma installer" in index of custom rom threads) custom miui rom based (of all the miui roms tested) like secondary.
- Like primary any of the treble/oreo based roms and like secondary I only tried aex rom and worked.
All this worked for me and If someone has some issue installing a rom in this scheme have to make sure of doing a clean flash.
Related
First of all i would like to thank ->Tsing Yi qingyi @http://weibo.com/1048297887 for his effort to make this possible!!
As some fellas request....I'm Just giving a detailed guide for the process to have Dual-System{Dual_Boot} in our little dragon @rmani :laugh:
DOWNLOADS:
1.HM1S-Sysrec.zip: http://pan.baidu.com/s/1jGzfP3o
2.M1S-System-Menu1.3-test.zip: http://pan.baidu.com/s/1qWDN5u8
if want it in a simpler way download 3
3.Mokke + Miui.zip: http://pan.baidu.com/s/1sjCyI3z
:good: @bhushan2k
MIRROR Link: https://drive.google.com/folderview...NrYmkzLTN3WmlONEczVnlzajg0emo3ZHM&usp=sharing
WARNING!! : Installation of Dual System is Complecated, include data loss and may brick your devices and i'm not responsible for any kind of Loss or Failure..!!
CAUTION!! : During this Process, Your Phone gets Factory Reset and all internal memory gets wiped!! Make a Backup of all internal data as well as a nandroid to extrnal sd!!
***//For Users coming from MIUI rom and want to have MIUI on one of the Systems continue from step 1-2 and read NOTE and in step 3 tick the checkbox promting special!
STEP1:
Flash HM 1S-Sysrec.zip...[after flashing, recovery gets rebooted].......In this Process Phones Intrernal Memory gets formatted and current ROM gets Factory Reset!
STEP2:
Flash HM 1S-System-Menu1.3-test.zip...Select English->Press Next->Accept and Press Next->Enter the function->Install and uninstall->Install the dual system.....This installs Dual-System and gets rebooted to recovery, meaning dual system got installed!!
**NOTE 1 : If you wish to install mokee+MIUI which was provided #3 in download section.....You can flash that mokee+MIUI.zip here, without proceeding further...and reboot!!
**NOTE 2 : Now we have two System partitions installed and we are on system1, which already have the previous Rom residual and System2 is Void!!
**NOTE 3 : If you want to have a fresh Installation of AOSP Rom on System1, you can directly flash a AOSP rom of your choice! or continue with previous rom!
STEP3:
Now that we have a Rom in System1 [MIUI or a AOSP]....so we need to install system switching software in it....
Flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System I-> Next [check special for MIUI users]...and reboot system!!
STEP4:
After the completion of boot process you will see a system changing app....open the app ->give root permissions and the phone gets rebooted and gets stuck at mi logo indicating we are in System2....Now Enter Reovery (Powr+VolUp same time)
STEP5:
Flash a ROM of your choice...."and dont reboot!"....after flashing rom again flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System 2-> Next....now reboot !!!.. which will take you to ROM installed in System 2 ....
STEP6:
After the completion of boot process, now that you are in System2, will see a system changing app as well ....open the app ->give root permissions and you will be able to switch to the other system/ROM........
////**Manual System switching process: **///
Flash HM 1S-System-Menu1.3-test.zip Follow the prompts to enter the main menu -> enter the function ->System Switching -> and select a System of your choice and proceed and Finally reboot !!!
***///Wanna change rom or try a new ROM keeping the other still///***
Stay on the System on which you want to try a new ROM....Reboot to recovery...
Flash HM 1S-System-Menu-Test1.3.zip and Follow the prompts to enter the main menu -> enter the function ->clear data->
Continuing which will wipes and factory Resets the current Rom....After proceeding further enter RECOVERY....
and Flash the ROM u wanna Try...and repeat #STEP5 and install switching software on new system!!(Hope U Understand)!!!
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
...for further questions comment below...............Give :good: if useful!!!....
Happy Flashing!!!
If anything Goes wrong...How to revert Back ?
Sent From My Redmi
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
can we use rom??and can i install custom kernel for both roms??
as9333 said:
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
2.cwm or twrp...u can try philz.. Dunno..
3.We can browse sys2 directories from sys1 & vice versa
how can i restore my data on my first rom? help me plz
chauhansonu104 said:
how can i restore my data on my first rom? help me plz
Click to expand...
Click to collapse
I don't think restoring nandroid data will work... Because....as u can see there are two two folders inside root/data/.......by restoring data from recovery will first wipes current root/data content and writes content from backup....so no dual-system!!! Hope you understand....tell me whether u have installed dual system? If so once see inside root/data /....u will get it!
sathyakaushik4 said:
can we use rom??and can i install custom kernel for both roms??
Click to expand...
Click to collapse
We can install gapps for system1 and system 2 separately....and can install custom kernels as well...!
very good tutorial.. thnx for this.. I tried on my own and couldnt manage.. will try again this time following ur simple steps..
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Great, Thanks for info, will try after my exams, one again Thank You Very Much.
@as9333
i guess we can switch between system 1 & 2 from recovery itself.. just flash the zip and explore through its aroma installer and see theres that option to switch...
as9333 said:
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
Note 1: Two Roms will be installed with two separate system partitions....all u can do things like installing custom add-ons or patches either being on system1 or system 2..use switching software to switch between system partition 1or 2...
Note 2: U can switch to system of ur choice from recovery...by flashing HM1s-system-menu.zip...there u will c an option to switch system...hope u understand if u had read the procedure with a bit of pathence!
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
N-Gavin said:
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
Click to expand...
Click to collapse
Read note2 of the above replied post...ur doubt will be clarified!!
bhushan2k said:
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
Click to expand...
Click to collapse
Mk+miui is not mandatory to download!!!.... Remaining 2 are <30mb...any ways u made it easy ...tnx for mirror!!
internal storage
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Hsmetric181 said:
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Click to expand...
Click to collapse
figured it out myself,for everybody else
won't format external sd card
and apps will be installed separately
Maybe some mistakes in step 2. The dev recommended unmount system, data and cache before installed Dual-System (doesn't matter really). Some user may need install it twice to success for unknown factors. And as I know on earlier versions, after you installed Dual-System, both partitions are empty. You need to flash a rom to system 1. But I haven't try v1.3 yet so I don't know if anything changed.
The tutorial seems so long but it's very reasonable to proceed.
1. (unnecessary for the 1st time) recover your phone's status - flash sysrec.zip
2. install the dual-boot system - flash into aroma and choose the option
3. flash a rom to current (1st) system - flash it in recovery
4. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
5. switch to system2 - switch directly in the aroma, or [ boot your phone to use the switcher app (after that plz press vol+ to enter recovery because system2 is empty now)]
6. flash another rom to current (2nd) system - just flash it in recovery, it will be in system2
7. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
now you have dual system installed.
For changing between systems, use the switcher (if installed) or change in the aroma installer.
For replacing a rom, switch to the rom you unwanted, and reboot to recovery and flash the new one.
For clear data, don't use recovery,it will clear both. Use the aroma (change to the system you want to clear data and choose clear current).
For miui user, special for miui is actually for miui 6 because /system/app can't get root permission in miui 6.
For uninstall, do it in aroma and then flash sysrec.zip
@pawanzZ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto X Play. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch.
MultiROM (multirom-YYYYMMDD-vXX-lux-signed.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/multirom-lux/multirom (branch master)
Device Tree - https://github.com/Multirom-Lux/android_device_motorola_lux/tree/twrp-precommon
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Downloads
1. Main downloads
MultiROM: https://www.androidfilehost.com/?fid=745425885120704569
Modified recovery (based on TWRP): https://www.androidfilehost.com/?fid=529152257862699607
Multirom Uninstaller: https://www.androidfilehost.com/?fid=745425885120704570
2. third-party kernels with kexec-hardboot patch (Not needed)
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
No-kexec workaround (version 4)
As of this version you need to manually enable the no-kexec workaround.
Actually, depending on the developer, (s)he may have already enabled it. Nonetheless, you can still choose to override the settings:
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the boot partition and names it primary_boot.img
In version 4 of the workaround, this backup is created and used only when booting a secondary ROM. When a secondary ROM is selected it's boot.img is flashed to primary slot, upon booting into the secondary ROM, the primary_boot.img is restored.
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a normal second boot but with the secondary boot.img in the real boot partition
MultiROM restores the primary_boot.img and continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
Moto G 2015 by @GtrCraft
Moto X Play by @GtrCraft
OnePlus One (starting here) by @KINGbabasula
OnePlus 3 by @martinusbe
OnePlus X by @martinusbe ... (alpha status)
Sony Xperia Z5 by @Myself5
Sony Xperia L by @STRYDER~007
Sony Xperia SP by @Adrian DC
Xiaomi Redmi 2 by @premaca
.
(possibly Samsung Note 4, unsure if that was continued or not)
Others; unofficial builds? (if you are, kindly let me know, and I'll add you to the list)
Credits to:
@premaca (For helping with bringup)
@squid2 (For TWRP trees)
@Hashbang173 (Guiding me with no kexec workaround)
@nkk71 (For kexec workaround)
Successfully booted from RR to xosp by using multirom. But multi ROM manager app not working. When I reboot , I can change to secondary ROM .VERY VERY THANKS FOR THIS MULTIROM. You've done a great work.
drmuruga said:
Successfully booted from RR to xosp by using multirom. But multi ROM manager app not working. When I reboot , I can change to secondary ROM .VERY VERY THANKS FOR THIS MULTIROM. You've done a great work.
Click to expand...
Click to collapse
Multirom app doesn't work for Moto X Play
What are the roms can be used in multirom?
All m x play roms or cm based or aosp based, any specificity? ( sorry for my english)
drmuruga said:
What are the roms can be used in multirom?
All m x play roms or cm based or aosp based, any specificity? ( sorry for my english)
Click to expand...
Click to collapse
Any rom, as long as you use the no kexec workaround
Sent from my XT1562 using XDA Labs
GtrCraft said:
Enabling no-kexec workaround
Click to expand...
Click to collapse
Great work :good:
May I recommend possibly linking to the original post, because
(1) it's incomplete... but should do for the moment (yeah, it's a sloppy write up, but better than nothing)
(2) once certain things are updated, a copy/paste wont include them
Glad it's working for you, and if it is working properly, then perhaps i need to add it to that post
Happy MultiROM-ing
nkk71 said:
Great work :good:
May I recommend possibly linking to the original post, because
(1) it's incomplete... but should do for the moment (yeah, it's a sloppy write up, but better than nothing)
(2) once certain things are updated, a copy/paste wont include them
Glad it's working for you, and if it is working properly, then perhaps i need to add it to that post
Happy MultiROM-ing
Click to expand...
Click to collapse
Please tell where I will find the correst post. And yes everythibg is working perfectly. No lingering boot.img or broken boots
Sent from my XT1562 using XDA Labs
GtrCraft said:
Please tell where I will find the correst post. And yes everythibg is working perfectly. No lingering boot.img or broken boots
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
No worries, the original no-kexec-workaround info is still here http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
If I update any information, it will still most likely be there (unless I end up doing on the HTC 10)
(in which case i would update the info)
post updated to include Moto X Play, nice work :good::good:
lingering boot.img was deprecated btw, there are other ways to "break" things.... but it's a lot more difficult now
After installing Multiboot system ringtone volume shoot up to high at beginning later it comes down to normal value.
Has anyone faced this issue. I tested it in two Rom and confirm it. The issue is noted on internal ROM. @GtrlCraft
Sent from my XT1562 using Tapatalk
b00tbu9 said:
After installing Multiboot system ringtone volume shoot up to high at beginning later it comes down to normal value.
Has anyone faced this issue. I tested it in two Rom and confirm it. The issue is noted on internal ROM. @GtrlCraft
Click to expand...
Click to collapse
What?
Sent from my XT1562 using XDA Labs
I have tested it in Stock Rom as well as in another rom. This issue is seen when I boot into internal ROM.
When any alert -message or phone ring.
First ring is way too louder then gradually sound become normal. The sound is so loud that I think the speaker would die
@GtrCraft
b00tbu9 said:
I have tested it in Stock Rom as well as in another rom. This issue is seen when I boot into internal ROM.
When any alert -message or phone ring.
First ring is way too louder then gradually sound become normal. The sound is so loud that I think the speaker would die
@GtrCraft
Click to expand...
Click to collapse
That is not a multirom issue, never seens that happening anyway
I have tested it on stock ROM...
Sent from my XT1562 using Tapatalk
logcat of ring - Stock
Hi,
Please find logcat at http://pastebin.com/PuZfHb4q
@nkk71
b00tbu9 said:
Hi,
Please find logcat at http://pastebin.com/PuZfHb4q
@nkk71
Click to expand...
Click to collapse
dunno what i'm looking for / at,
but have you confirmed:
booting that particular ROM
flashed with MultiROM TWRP
but not injected does not produce this issue?
.
booting that particular ROM as a secondary slot also does not produce this issue?
nkk71 said:
dunno what i'm looking for / at,
but have you confirmed:
booting that particular ROM
flashed with MultiROM TWRP
but not injected does not produce this issue?
.
booting that particular ROM as a secondary slot also does not produce this issue?
Click to expand...
Click to collapse
Booting a ROM from multi Rom twrp with out injected does not produce any issue. Second ROM on MultiRom does not have the issue...
I tried Stock Moto as well as another Rom as primary in both the case high volume issue is noted.
Sent from my XT1562 using Tapatalk
{
"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 a 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
https://www.youtube.com/watch?v=JDnDNxqfSaw
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.
IMPORTANT
1. I'm not responsible for anything, you do all this on your own risk.
2. Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
-> Download and flash the MultiROM recovery from the DOWNLOADs section using "fastboot flash recovery <path-to-recovery.img>
-> Use the recovery to flash the latest multirom zip from the DOWNLOADs section.
-> In order to boot a secondary rom you MUST enable the "kexec workaround" option (enabled by default) in the MultiRom settings found in the recovery: BEWARE that this workaround re-flashes the boot-partition every time you boot a secondary rom, so don't boot secondary roms too often, as it may brick your device on the long term! We still need to fix kexec such that exessive utilization is less risky
That's it. You can now go to "MultiROM menu" (Top right corner in the recovery) to start flashing other ROMs.
NOTE: The touch screen doesn't work if you use a MM/N ROM as a base/primary ROM.
ALTERNATIVE INSTALLATION METHOD
-> Download the latest TWRP multirom recovery from the downloads section.
-> Use a terminal emulator, obtain su, and use the following command Adjust the following command and enter it in the shell: "dd if=/sdcard/<name-of-recovery>.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
-> Follow the steps in the previous method to install multirom
ADDING ROMs
Go to recovery, select "MultiROM menu" (Top right corner in the recovery) -> Add ROM. Select the ROM's zip file and confirm.
USING USB DRIVES
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
UPDATING/CHANGING ROMs
1. Primary ROM (Internal)
-> Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
-> Go to "MultiROM menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
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 menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
-> Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
Multirom: https://github.com/XperiaMultiROM/multirom/
TWRP: https://github.com/XperiaMultiROM/android_bootable_recovery
CREDITS
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
Myself5
Diewi
XDA:DevDB Information
MultiROM v33x for Xperia Z1, ROM for the Sony Xperia Z1
Contributors
drakonizer
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Alpha
Created 2016-10-22
Last Updated 2016-11-02
Great job Dev
Hey @drakonizer i tried to flash the recovery bit I'm facing a black screen after rebooting in recovery. I'm on cm12.1 with m5kernel 11.2. I probably did something wrong but what?... I only flashed the recovery
Will 4.4 as primary work
benplay64 said:
Hey @drakonizer i tried to flash the recovery bit I'm facing a black screen after rebooting in recovery. I'm on cm12.1 with m5kernel 11.2. I probably did something wrong but what?... I only flashed the recovery
Click to expand...
Click to collapse
You should have flashed the TA update to enable booting directly to recovery. If not, the recovery won't work. Booting into recovery only works using the hardware button combo, and not from Android/adb.
pokepokepoke said:
Will 4.4 as primary work
Click to expand...
Click to collapse
It should, but I haven't tried.
So I have to flash stock ROM before?? If yes my device will wait before having multirom
benplay64 said:
So I have to flash stock ROM before?? If yes my device will wait before having multirom
Click to expand...
Click to collapse
You'll have to either flash latest stock completely out flash the TA update from the general section
drakonizer said:
You'll have to either flash latest stock completely out flash the TA update from the general section
Click to expand...
Click to collapse
So I can only flag the TA update with flash tool over cm?!
benplay64 said:
So I can only flag the TA update with flash tool over cm?!
Click to expand...
Click to collapse
Yes. It should work.
drakonizer said:
Yes. It should work.
Click to expand...
Click to collapse
Thanks you're the boss I will try it now
Updated recovery and multirom zip added with support for Android Nougat and custom stock kernels. Please try and report.
Also, OP has been updated. Looks like Multirom is pretty stable for daily use now. I personally tried it with N as primary and LP as secondary and it worked like a charm.
If users of amami/togari want me to port it for their devices, please PM me so that I can send you test builds. Once I deem them to be stable, I will open threads for them.
drakonizer said:
Updated recovery and multirom zip added with support for Android Nougat and custom stock kernels. Please try and report.
Also, OP has been updated. Looks like Multirom is pretty stable for daily use now. I personally tried it with N as primary and LP as secondary and it worked like a charm.
If users of amami/togari want me to port it for their devices, please PM me so that I can send you test builds. Once I deem them to be stable, I will open threads for them.
Click to expand...
Click to collapse
Friend, i am a little lost, but i need to do that. I need 5.1 for daily use and 6.0 for tests
I am feeling lost because i know how to use twrp to backup, restore, flash zips.... the basic. I am right now using 6.0 Ressurrection Marshmallow rom, with [email protected] 16.04#1 kernel.
I read but i am from brazil and my english isnt the best ones, thats why i am lost. My idea, is, use as primary the 5.1 rom to daily use... but i am lost HOW to start, what kernel should i use...
Please, can you help?
LinkRaf said:
Friend, i am a little lost, but i need to do that. I need 5.1 for daily use and 6.0 for tests
I am feeling lost because i know how to use twrp to backup, restore, flash zips.... the basic. I am right now using 6.0 Ressurrection Marshmallow rom, with [email protected] 16.04#1 kernel.
I read but i am from brazil and my english isnt the best ones, thats why i am lost. My idea, is, use as primary the 5.1 rom to daily use... but i am lost HOW to start, what kernel should i use...
Please, can you help?
Click to expand...
Click to collapse
Okay, I will describe it in detail once more, and hopefully this will be the last time.
-> You can have any ROM as primary, but 5.1 is preferred if you want touch screen support in the multirom menu (the OS choice menu).
-> Flash the latest TA update that enables the recovery partition. The thread is available in the general section.
-> Download the latest multirom recovery from the downloads section
-> Download the latest multirom zip
-> Flash the recovery using fastboot (fastboot flash recovery recovery.img)
-> Boot into recovery using POW+VOL DOWN and use it to flash the multirom zip you downloaded earlier.
-> Enter the multirom menu by tapping the icon on the top right corner of the recovery home screen.
-> Follow the menu to install your secondary ROM.
-> Once that's done, reboot, and you should see the multirom menu pop up
If you still didn't understand, there are multiple guides and videos on the internet. The process is pretty much similar for all devices, so you don't have to look for Xperia Z1 exactly.
drakonizer said:
Okay, I will describe it in detail once more, and hopefully this will be the last time.
-> You can have any ROM as primary, but 5.1 is preferred if you want touch screen support in the multirom menu (the OS choice menu).
-> Flash the latest TA update that enables the recovery partition. The thread is available in the general section.
-> Download the latest multirom recovery from the downloads section
-> Download the latest multirom zip
-> Flash the recovery using fastboot (fastboot flash recovery recovery.img)
-> Boot into recovery using POW+VOL DOWN and use it to flash the multirom zip you downloaded earlier.
-> Enter the multirom menu by tapping the icon on the top right corner of the recovery home screen.
-> Follow the menu to install your secondary ROM.
-> Once that's done, reboot, and you should see the multirom menu pop up
If you still didn't understand, there are multiple guides and videos on the internet. The process is pretty much similar for all devices, so you don't have to look for Xperia Z1 exactly.
Click to expand...
Click to collapse
Thank you for your time! I appreciate it. Two last questions. There will be difference between primary or secundary boot? as performance?
and if i want just to install the second boot ( keep the ressurrection marshmallow as primary) it can be done too?
Thank you and sorry
LinkRaf said:
Thank you for your time! I appreciate it. Two last questions. There will be difference between primary or secundary boot? as performance?
and if i want just to install the second boot ( keep the ressurrection marshmallow as primary) it can be done too?
Thank you and sorry
Click to expand...
Click to collapse
The only difference would be boot time.
Yes, you can use MM as primary, but touch on the multirom menu will not work and you'll have to use the volume buttons and power button to move and select.
Sent from my Xperia Z1 using XDA Labs
Hallo . Can i use this on stock base?
monnett said:
Hallo . Can i use this on stock base?
Click to expand...
Click to collapse
It should, no reason not to....why don't you try and tell me?
drakonizer said:
It should, no reason not to....why don't you try and tell me?
Click to expand...
Click to collapse
iam sorry . But i faced problem when flashing twrp on adb its say "too large"
monnett said:
iam sorry . But i faced problem when flashing twrp on adb its say "too large"
Click to expand...
Click to collapse
Sorry about that...it should be fixed now. Please re-download multirom-twrp-honami-02112016.img from the downloads section and try again.
Thanks!
Friend, i am still on MM Rom, 6.0 with the same kernel, now i want to make the lollipop as my secundary boot
i flashed the twrp of multiboot via fastboot mode. I´ve turned on my z1 (power + volume down) (Could see the new twrp menu) In the INSTALL option, flashed the zip file of multiboot. After that ( i did not reboot my devce) on the addRom menu, installed a lollipop rom (that i know that works with the same kernel as my MM rom)
but it starts the install thing and get a status FAILED and erase an incomplete rom... something like this. .. and i cant install it.... i´ve tested two different lollipop rom... am i missing something?
{
"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
*** Note I am not a MultiROM expert. I wanted to create a place to share and buried in @KINGbabasula's thread is not ideal. Per his request, I've made this thread...
*** Special thanks to @KINGbabasula for his original thread, and to @martinusbe and @nkk71 for entertaining my endless questions, and providing invaluable help when asked.
MultiROM is one-of-a-kind multi-boot mod for Oneplus One. 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.
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:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use TWRP (flash image file), fastboot or Flashify app to flash it.
Patched kernel - Your Primary ROM's kernel should have the no-kexec patch applied, but should be OK if not as MultiROM will check.
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. If desired, you can go to Advanced -> MultiROM -> List ROMs, select your ROMcan flash individual zips, one by one, such as GApps or SU.
2. Ubuntu Touch (Note I have not tested this nor do I use Ubuntu Touch.)
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS (Note I have not tested this nor do I use Firefox OS.)
Firefox OS is just another Android ROM from MultiROM's point of view, so add it as if it were Android
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 current 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
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
MultiROM device tree - https://github.com/MR-op3/device_oneplus_bacon (branch mr)
MultiROM kernel - https://github.com/MR-op3/kernel_oneplus_msm8974 (branch mr)
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
[MOD][OPO] MultiROM v33e [WIP-TESTING][NOUGAT], Tool/Utility for the OnePlus One
Contributors
NoSpamDan, martinusbe, nkk71
Version Information
Status: Testing
Created 2017-02-12
Last Updated 2017-02-17
DOWNLOADS
Flashable MultiROM TWRP v3.1.1 Recovery img file: TWRP_multirom_bacon_20170711-07.img
Flashable MultiROM ZIP: multirom-20161206-v33e-UNOFFICIAL-bacon.zip
Flashable MultiROM Uninstaller ZIP: multirom_uninstaller.zip
Dark-themed MultiROM Manager App: MultiROMMgr-GZR-TBO.apk
(premaca's download folder)
You can thank @premaca and @martinusbe for much of this.
Previous versions:
Flashable MultiROM TWRP v3.0.3-0 Recovery:
multirom-20170711-v33e-UNOFFICIAL-bacon.zip
TWRP MultiROM:
TWRP_3.0.2-0_multirom_bacon_20161212-01.img
MultiROM ZIP:
TWRP_multirom_bacon_20170224-01.img
MultiROM Uninstaller:
multirom_uninstaller.zip
FAQ/FYI
Here are some common questions and answers with MultiROM:
I can't flash a different recovery on my device because the option is not there.
Most likely, the fstab file in the recovery needs to be fixed. You'll probably need to perform the fastboot steps in #2 below.
How to use fastboot to flash a recovery image to your device:
To flash back to another recovery:
Boot your device into fastboot mode.
Copy the recovery img file you want to flash to a place where you have fastboot installed. You probably did this already when you installed TWRP over your stock recovery so you could flash custom ROMs.
Open a terminal/command window in the directory where fastboot.exe and the recovery.img file are, and type: fastboot flash recovery recovery.img (where "recovery.img" is the actual name of the recovery file you want to flash).
None of my secondary ROMs will boot:
You probably need to run Restorecon on the secondary ROM to modify its selinux contexts. To do this:
In MultiROM TWRP, click the MultiROM options in the upper right corner.
Select "List ROMs"
Choose your ROM from the list
Click the "Run Restorecon" button
Reboot into that ROM
I am not seeing the boot menu from MultiROM to select a ROM.
Make sure you injected MultiROM into your primary ROM. To do this:
Flash the MultiROM zip file to your primary ROM.
Click the MultiROM options in the upper right corner
Select the "Inject boot sector" button
Reboot
If you still have trouble, see @nkk71's post here with more information.
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
can my 16GB-device work??
Great mod. Thanks NoSpamDan for keeping it alive!
SirSoviet said:
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
Click to expand...
Click to collapse
Going to need more details than that... and thanks for the log.
What ROM primary and secondary?
Did you inject the boot image on your primary?
Try flashing your primary as both a primary and a secondary and see if you can add another secondary. This is still in the testing phase but I have Slim7 as my primary and no issues with secondary ROMs. I don't normally even need restorecon on them when I test (unless it gets stuck at the kernel splash screen)...
EDIT: From your log:
Code:
[ 3.375133] multirom: kexec -u test has failed, kernel doesn't have kexec-hardboot patch enabled in config!
ceiven said:
can my 16GB-device work??
Click to expand...
Click to collapse
Sure, why not? You can use an external OTG drive to keep ROMs on. Depending on how much space your ROM & Data occupies will limit what you can do on such a small storage device.
SirSoviet said:
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
Click to expand...
Click to collapse
@nikhil18 forgot to enable KEXEC in V35. Use V34, it's enabled/working fine there.
NoSpamDan said:
Going to need more details than that... and thanks for the log.
What ROM primary and secondary?
Did you inject the boot image on your primary?
Try flashing your primary as both a primary and a secondary and see if you can add another secondary. This is still in the testing phase but I have Slim7 as my primary and no issues with secondary ROMs. I don't normally even need restorecon on them when I test (unless it gets stuck at the kernel splash screen)...
Sure, why not? You can use an external OTG drive to keep ROMs on. Depending on how much space your ROM & Data occupies will limit what you can do on such a small storage device.
Click to expand...
Click to collapse
So it seems that the latest version of LK has broken Kexec, so no need to worry about that. Just the No-Kexec workaround that's problematic.
I'm currently using HalogenOS, and any secondary rom won't work. I injected the boot image on the primary rom, otherwise I would be booting straight into the primary rom.
SirSoviet said:
So it seems that the latest version of LK has broken Kexec, so no need to worry about that. Just the No-Kexec workaround that's problematic.
I'm currently using HalogenOS, and any secondary rom won't work. I injected the boot image on the primary rom, otherwise I would be booting straight into the primary rom.
Click to expand...
Click to collapse
Well I edited my last response to include a line from your log indicating that the kernel does not have the kexec-hardboot patch.
NoSpamDan said:
Well I edited my last response to include a line from your log indicating that the kernel does not have the kexec-hardboot patch.
Click to expand...
Click to collapse
I know that, I said that the latest version of Lightning Kernel has broken kexec-hardboot. All that needs to be fixed is the no-kexec workaround.
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
JT1510365 said:
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
Click to expand...
Click to collapse
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
f41lbl0g said:
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
Click to expand...
Click to collapse
What roms would have it wouldn't rr remix rom nougat have it?
JT1510365 said:
What roms would have it wouldn't rr remix rom nougat have it?
Click to expand...
Click to collapse
I haven't used multirom in a while so I don't know.
JT1510365 said:
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
Click to expand...
Click to collapse
Great question... it's Nougat-friendly because you can install Nougat ROMs as secondary. The Developer Options problem is a bug...
As a work-around, you can install your problem Nougat ROM as a Primary, enable the Developer Options there, then move it to a Secondary slot...
f41lbl0g said:
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
Click to expand...
Click to collapse
Indeed, a secondary ROM needs this: https://review.slimroms.org/#/c/22989/
I'm running a marshmallow and nougat rom together with the last version of multirom?
NoSpamDan said:
Great question... it's Nougat-friendly because you can install Nougat ROMs as secondary. The Developer Options problem is a bug...
As a work-around, you can install your problem Nougat ROM as a Primary, enable the Developer Options there, then move it to a Secondary slot...
Indeed, a secondary ROM needs this: https://review.slimroms.org/#/c/22989/
Click to expand...
Click to collapse
For nougat compatibility, moving to latest @nkk71 multirom modified_twrp 3.0.3-0 is real better 2017-01-27:
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
BTW, MultiROM' OPs should clarify one for all that multirom.zip' s trampoline works fine with all unmodified recoveries twrp/cwm (primary rom install/update only): modified_twrp is only needed for managing 2nd roms.
Of course, using un-swapped unique modified_TWRP recovery is always much "cooler" (I didn't had much success explaining that to p880' users with : how to rom/kickflip and twrp/shuvit...), and NoKexec workaround is a more complicate behaviour.
Even after flashing v33e, Multirom manager says I'm running v33b... Is that normal?
oF2pks said:
For nougat compatibility, moving to latest @nkk71 multirom modified_twrp 3.0.3-0 is real better 2017-01-27:
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
BTW, MultiROM' OPs should clarify one for all that multirom.zip' s trampoline works fine with all unmodified recoveries twrp/cwm (primary rom install/update only): modified_twrp is only needed for managing 2nd roms.
Of course, using un-swapped unique modified_TWRP recovery is always much "cooler" (I didn't had much success explaining that to p880' users with : how to rom/kickflip and twrp/shuvit...), and NoKexec workaround is a more complicate behaviour.
Click to expand...
Click to collapse
I have a version of 3.0.3-0 built, but I couldn't get my multirom zip file to show the boot menu/boot sector. I did flash the zip and injected it but no luck. I have reached out to @nkk71 for ideas on this, but it might be best if he responds here when he has a chance.
For now, I'll put the new TWRP in Post #2 and here if you want to try it. Keep a previous version around just in case you need to fastboot flash it to your device: TWRP_3.0.3-0_multirom_bacon_20170213-01.img
iruiz2 said:
Even after flashing v33e, Multirom manager says I'm running v33b... Is that normal?
Click to expand...
Click to collapse
Yes, it's because it's pointing to @nkk71's repo, and it's also using his changelog I believe. I'll have to review, but manual installation is best for now. What the app is most useful for right now is managing your ROMs...
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app
V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1."Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted."App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)"App > Installed" shows the currently installed version of the Magisk app
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations
Hello,
What about Knox with this method ??
Thanks
leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.
So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?
Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.
urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.
bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.
Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..