Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z Ultra. 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
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-vXX-DDMMYY-togari.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom-togari.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use third-party kernels which include the patch, you can see list in the second post.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of a ROM after first boot (with dalvik cache generated and connected to google account) takes more or less 700MB of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive (if USB drive partitions are not showed, disconnect USB drive and try again). 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 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.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kexec-hardboot patch for stock Sony kernel- https://github.com/Garcia98/kernel-amami/commit/4185df7caf40ac5aa6c7fc81d4098de58f9af19f
Touch patch for MultiROM menu- https://github.com/CyanogenMod/andr...mmit/907103b43eed80bd2bef89beb957d4052311ae67
XDA:DevDB Information
MultiROM for Xperia Z Ultra, Tool/Utility for the Sony Xperia Z Ultra
Contributors
Garcia98
Version Information
Status: No Longer Updated
Created 2015-01-18
Last Updated 2016-06-10
Downloads
1. Main downloads
MultiROM: MultiROM-v30x-180115-UNOFFICIAL-togari.zip
Modified recovery (based on TWRP): TWRP_multirom-togari_20150201-00.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 4.4.4): stock-kexec-boot.img
Kernel w/ kexec-hardboot patch (14.5.A.0.242): http://forum.xda-developers.com/showpost.php?p=60316498&postcount=131
You need to have kernel with kexec-hardboot patch only in your primary ROM!
2. third-party kernels with kexec-hardboot patch
* Validus LP kernel
* Resurrection Remix LP kernel
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: MultiROM_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Changelog
Code:
MultiROM v30x
=====================
* Initial release
Recoveries:
Code:
01/02/2015
==========
* Disabled screen timeout.
* Added filesystems tools.
* Latest TWRP updates and changes.
21/01/2015
==========
* Fixed the installation of block images OTAs through MultiROM.
* Latest TWRP updates and changes.
18/01/2015
=====================
* Initial togari release
FAQ and other notes
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.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
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./external SD card. 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.
Can I have different versions of Android working alongside
Yes.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
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.
Absolutely fantastic Garcia98.
Very to happy to see support for the Z Ultra.
Edit: To be clear, it does support 4.4.4 stock sony, but only with a third party kernel with the Kexec-hardboot patch?
Don't suppose you have build the stock 4.4.4 kernel with the Kexec-hardboot patch applied?
scoobydu said:
Absolutely fantastic Garcia98.
Very to happy to see support for the Z Ultra.
Edit: To be clear, it does support 4.4.4 stock sony, but only with a third party kernel with the Kexec-hardboot patch?
Don't suppose you have build the stock 4.4.4 kernel with the Kexec-hardboot patch applied?
Click to expand...
Click to collapse
If there's a custom kernel for stock ROM link me to it and I'll patch it
Wow. Awesome.
Mine say unsupported. I am using scrubber port 4.4.4 with this kernel http://forum.xda-developers.com/showthread.php?p=56411399
Can you patch this one?
Sent from my C6806_GPe using XDA Premium HD app
Garcia98 said:
If there's a custom kernel for stock ROM link me to it and I'll patch it
Click to expand...
Click to collapse
To be honest I use the stock kernel and was hoping you would be able to patch that for the latest stock rom?
Cheers
cameljockey1 said:
Wow. Awesome.
Mine say unsupported. I am using scrubber port 4.4.4 with this kernel http://forum.xda-developers.com/showthread.php?p=56411399
Can you patch this one?
Sent from my C6806_GPe using XDA Premium HD app
Click to expand...
Click to collapse
Well, I need a source built custom kernel, not just one with ramdisk modifications.
scoobydu said:
To be honest I use the stock kernel and was hoping you would be able to patch that for the latest stock rom?
Cheers
Click to expand...
Click to collapse
If in a week there's no stock kernel patched I'll try to release one
Z Ultra Google Play Edition?
@Garcia98, thanks for beating me to this! I started working on porting MultiROM to the Z Ultra GPE myself, and got as far as a kexec-hardboot-patched kernel that boots into the MultiROM menu with no touchscreen support and a non-booting TWRP recovery, likely because I used CM12 as my base instead of OmniROM. Instead of continuing to duplicate your efforts, I thought it might be simpler to ask if you would do a togari_gpe build for MultiROM/TWRP. It might be fairly easy to repack the recovery ramdisk into my CM12 boot.img myself and try to install them that way, but I'd like to see the GPE officially supported. My file hosting abilities are limited, otherwise I'd offer to do the build myself. That, and I don't have space for yet another Android build tree.
I'm going to attempt to submit a cleaned-up version of the kexec hardboot patch for every MSM8974 Xperia device I can (amami, honami, togari, togari_gpe, sirius, and possibly more) to Gerrit for inclusion in CyanogenMod. Whether said patch is ever merged is another story, but that could make things much easier for a lot of people.
gTan64 said:
@Garcia98, thanks for beating me to this! I started working on porting MultiROM to the Z Ultra GPE myself, and got as far as a kexec-hardboot-patched kernel that boots into the MultiROM menu with no touchscreen support and a non-booting TWRP recovery, likely because I used CM12 as my base instead of OmniROM. Instead of continuing to duplicate your efforts, I thought it might be simpler to ask if you would do a togari_gpe build for MultiROM/TWRP. It might be fairly easy to repack the recovery ramdisk into my CM12 boot.img myself and try to install them that way, but I'd like to see the GPE officially supported. My file hosting abilities are limited, otherwise I'd offer to do the build myself. That, and I don't have space for yet another Android build tree.
I'm going to attempt to submit a cleaned-up version of the kexec hardboot patch for every MSM8974 Xperia device I can (amami, honami, togari, togari_gpe, sirius, and possibly more) to Gerrit for inclusion in CyanogenMod. Whether said patch is ever merged is another story, but that could make things much easier for a lot of people.
Click to expand...
Click to collapse
Which are the differences between Xperia Z Ultra and Xperia Z Ultra GPE?
Garcia98 said:
Which are the differences between Xperia Z Ultra and Xperia Z Ultra GPE?
Click to expand...
Click to collapse
I don't remember where I heard this, but IIRC, the differences amount to little more than incompatible partitioning, so it may be possible to use your togari build with little more than a device check modification. EIther way, I don't think a new build using a togari_gpe Android device tree from, say, OmniROM 4.4, will be any more effort than selecting the appropriate lunch combination and waiting for it to compile. The kernel config is exactly the same on the GPE as it is on the Sony Z Ultra. I'll have to do some digging though - I set KEXEC_HB_PAGE_ADDR to 0x10000000, which is probably sub-optimal if not incorrect.
gTan64 said:
I don't remember where I heard this, but IIRC, the differences amount to little more than incompatible partitioning, so it may be possible to use your togari build with little more than a device check modification. EIther way, I don't think a new build using a togari_gpe Android device tree from, say, OmniROM 4.4, will be any more effort than selecting the appropriate lunch combination and waiting for it to compile. The kernel config is exactly the same on the GPE as it is on the Sony Z Ultra. I'll have to do some digging though - I set KEXEC_HB_PAGE_ADDR to 0x10000000, which is probably sub-optimal if not incorrect.
Click to expand...
Click to collapse
I think that if you could test if MultiROM works OK on togari GPE without any modification it would be superb as I don't find any big difference
Sent from my D5503 using XDA Free mobile app
Garcia98 said:
I think that if you could test if MultiROM works OK on togari GPE without any modification it would be superb as I don't find any big difference
Click to expand...
Click to collapse
Neither the MultiROM zip or the TWRP image will work without modification, and it should be significantly easier to build from source since at least in CyanogenMod's togari_gpe device tree, most of the code actually lives in the togari device repository, and subsequently gets inherited from togari in the makefiles. Omni has a similar setup from what I could see on GitHub. In other words, code changes on your end should very minimal, if not nonexistent - you just won't know until the build starts. If you don't do it, no worries - I will, it'll just take longer since it seems like I'll have to checkout an entire new Android build tree.
gTan64 said:
Neither the MultiROM zip or the TWRP image will work without modification, and it should be significantly easier to build from source since at least in CyanogenMod's togari_gpe device tree, most of the code actually lives in the togari device repository, and subsequently gets inherited from togari in the makefiles. Omni has a similar setup from what I could see on GitHub. In other words, code changes on your end should very minimal, if not nonexistent - you just won't know until the build starts. If you don't do it, no worries - I will, it'll just take longer since it seems like I'll have to checkout an entire new Android build tree.
Click to expand...
Click to collapse
Togari GPE device tree differs in nothing but name with togari tree, in fact it includes everything from togari tree so I'm 100% sure that this would work in ZU GPE if works in ZU
Sent from my D5503 using XDA Free mobile app
Garcia98 said:
Togari GPE device tree differs in nothing but name with togari tree, in fact it includes everything from togari tree so I'm 100% sure that this would work in ZU GPE if works in ZU
Click to expand...
Click to collapse
You're right about the device trees, and I don't see why it should require a rebuild, but repacking the recovery ramdisk from TWRP with a kernel from another boot image doesn't work, the red LED just blinks. The MultiROM zip might work with a device check modification, but I haven't checked, because TWRP is my priority.
battling to install on Validus rom
Hi,
I am trying to install this on my c6833 after doing a clean firmware flash and installing Validus Rom.
i followed the steps on OP (btw, flashing Multirom recovery file through Cyanogen recovery failed so I hotbooted Doomkernel to flash it with CWM and it worked)
however, when i fastboot flash the .img file, after that, the device doesn't boot. so i have to fastboot flash the Validus kernel again to get it to boot.
and after installing the app from playstore, a message in red says my device is not supported.
Any help would be deeply appreciated
thanks.
anybody managed to get this to work?
if so, which rom and how please.
my c6833 doesn't boot after fastboot flashing the .img file with flashtool.
don't install the recovery img. just flash validus and then multirom zip, the custom recovery will already be there. that's how i did it.
halifage said:
anybody managed to get this to work?
if so, which rom and how please.
my c6833 doesn't boot after fastboot flashing the .img file with flashtool.
Click to expand...
Click to collapse
planeinmountain said:
don't install the recovery img. just flash validus and then multirom zip, the custom recovery will already be there. that's how i did it.
Click to expand...
Click to collapse
Thanks mate
I am now on StoneUI-HD3 rom (4.4.4) with doomkernel, can i make a nandroid backup and then restore that backup as a secondary rom after flashing Validus?
Also, and lastly, can i just flash Validus from my recovery (after all the wipes of course) without flashing the rom's boot.img through flashtool ?
Thanks
you can flash validus from your current recovery no prob.
i don't know about restoring a nandroid in multirom. today is the first time i used it and i only instll cm12 nightly with it so far (which would not boot by the way).
halifage said:
Thanks mate
I am now on StoneUI-HD3 rom (4.4.4) with doomkernel, can i make a nandroid backup and then restore that backup as a secondary rom after flashing Validus?
Also, and lastly, can i just flash Validus from my recovery (after all the wipes of course) without flashing the rom's boot.img through flashtool ?
Thanks
Click to expand...
Click to collapse
{
"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 Nexus 6. 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
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-shamu.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_shamu_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 1 GiB of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Tasssadar/androi...ree/android-msm-shamu-3.10-lollipop-mr1-kexec
Donations
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
Downloads
1. Main downloads
MultiROM: multirom-20160207-v33-shamu.zip
Modified recovery (based on TWRP): TWRP_multirom_shamu_20160210.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 5.0 and 5.0.1): kernel_kexec_shamu_500.zip
Kernel w/ kexec-hardboot patch (Stock 5.1): kernel_kexec_shamu_510.zip
Kernel w/ kexec-hardboot patch (Stock 5.1.1): kernel_kexec_shamu_511-2.zip
Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1): kernel_kexec_shamu_601.zip
Kernel w/ kexec-hardboot patch (CM 12.0): kernel_kexec_shamu_cm12-02-50134cb9df.zip
Kernel w/ kexec-hardboot patch (CM 12.1): kernel_kexec_shamu_cm121-01-8f9e2418f2.zip
Kernel w/ kexec-hardboot patch (CM 13.0): kernel_kexec_shamu_cm13-01-677c36b09.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Mirror: http://d-h.st/users/tassadar
2. third-party kernels with kexec-hardboot patch
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller-shamu.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
4. Flashable factory images ZIPs
I usually release flashable ZIP files based on new factory images from Google, so that you can have clean stock ROM as a secondary system in MultiROM. They are not rooted, no anything, except for occasional small tweaks to make rooting with SuperSU possible. You can find them in this folder on basketbuild or dev-host.
Changelog
Code:
MultiROM v33
=====================
* Updates for Android 6.0 compatibility
MultiROM v32b
=====================
* Add support for Android M preview (MPZ44Q). SuperSU 2.46 doesn't work on M
and breaks boot - don't flash it!
MultiROM v32a
=====================
* Fix pattern encryption password incorrectly reporting "invalid password"
when the pattern overlaps itself
MultiROM v32
=====================
* First stable release for shamu
Recoveries:
Code:
10.2.2016
=====================
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
9.2.2016
=====================
* Fix confusing "Unable to mount..." error message
* Fix flashing of some kernels into secondary ROMs (e.g. Elite kernel)
6.2.2016
=====================
* Update to TWRP 3.0.0 (big thanks to nkk71 for doing most of the work)
* Use Material theme made by z31s1g - thanks!
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
[url]http://bit.ly/m_su[/url] ) or newer!
30.6.2015
=====================
* Update to TWRP 2.8.7
* Add option to duplicate secondary ROM into "Swap ROMs" section
6.4.2015
=====================
* First stable release for shamu
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.
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.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
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.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
At last, multirom is official for nexus 6!
Congrads Tasssadar!
Been testing this since its release. Always been awesome! Thanks Tasssadar. Been using MultiROM for awhile now.
So glad to see this finally get a thread. So thankful for your work Tasssadar. Innovative as well as functional, love it!
I've been waiting until our device got a thread to ask this question, anyone who knows, feel free to answer - Some ROMs require a wipe of /system in order to boot. I believe I understand the flashing instructions as I have read them numerous times - you factory data reset to clean flash, wipe cache to dirty flash. How would one boot a ROM that requires a wipe of /system into a secondary ROM slot? Or for those users who mess with a lot of /system stuff and like to wipe on every flash, is there a way to do this for secondary ROMs that I simply missed? Or should something about the way MultiROM is structured, i.e. "All ROMs are separate" from the FAQ, eliminate issues in terms of needing to wipe /system for secondary ROMs? I figure I would rather ask a question I don't need to than find out the hard way given this is not standard flashing and thus not inherently obvious.
Nice work, like with your previous Versions. This will be awesome to use especially with the 64GB variant!
Amazing work. Thanks for all of it. Hope you got your N6 RMA back!
@tassadar
I had this problem with the test releases also, but decided to keep it to myself since it was a test release, but the "key press to launch multirom" option in TWRP doesn't work. We obviously can't use volume down because that boots you into the bootloader, I've tried holding volume up while the phone is off and then pressing the power button, but it just continues to boot my rom.
brando56894 said:
@tassadar
I had this problem with the test releases also, but decided to keep it to myself since it was a test release, but the "key press to launch multirom" option in TWRP doesn't work. We obviously can't use volume down because that boots you into the bootloader, I've tried holding volume up while the phone is off and then pressing the power button, but it just continues to boot my rom.
Click to expand...
Click to collapse
That's exactly what testing releases are for - finding bugs and fixing them. Next time you spot something like that, report it right away, otherwise I might not even know about the problem
But somebody else reported the key-based autoboot not working, and unfortunately, on shamu, there is no way to tell if a key has been pressed before the kernel has booted up. I could add a short period of time when you could press the key and it would work, but then it would be the same as time-based autoboot. I will hide that option in next recovery release, so it doesn't mislead people.
Awesome work :good:
I'm waiting for miui / any other good custom ROM port for nexus 6
Atm we have only cm12 /stock based roms :3 .
Anyway thanks for bringing this to n6 :good:
Been running this a week or so works great for me, love being able to have a main rom and test out a bunch as a secondary.
Encryption on CM12?
Anyone else having trouble with encryption?
I had CM12 installed before today working fine with a pattern required on boot. Installed multirom, now I'm stuck at Multirom's pattern prompt, when I enter my pattern I get "Invalid Password" Wiped the device, including internal storage and reinstalled CM. Set a pattern again and it's stuck at the pattern prompt again.
So I'm gathering that if I want to run a ROM off a USB drive, I can format it to extX and then let the image size grow (or shrink) as needed, whereas if I use a drive formatted NTFS or Fat32 I have to decide up front the image sizes.
Did I get that right?
Following
YES!
Thank you Tass!!!
Quick questions: Would flashing kernels and other things normally be installed in the primary rom without any added steps? What about changing/updating the primary rom? Would wiping the phone wipe the primary rom only or all roms? Thanks
katyl said:
Anyone else having trouble with encryption?
I had CM12 installed before today working fine with a pattern required on boot. Installed multirom, now I'm stuck at Multirom's pattern prompt, when I enter my pattern I get "Invalid Password" Wiped the device, including internal storage and reinstalled CM. Set a pattern again and it's stuck at the pattern prompt again.
Click to expand...
Click to collapse
Ups, I forgot to fix it in MultiROM (had the same bug in TWRP's pattern entry, it's was fixed there but I forgot to do the same in MultiROM). Fixed in v32a.
demlv said:
So I'm gathering that if I want to run a ROM off a USB drive, I can format it to extX and then let the image size grow (or shrink) as needed, whereas if I use a drive formatted NTFS or Fat32 I have to decide up front the image sizes.
Did I get that right?
Click to expand...
Click to collapse
That's right.
C00lBeanz said:
Quick questions: Would flashing kernels and other things normally be installed in the primary rom without any added steps? What about changing/updating the primary rom? Would wiping the phone wipe the primary rom only or all roms? Thanks
Click to expand...
Click to collapse
Yes, just flash it as usual (in recovery, if you use fastboot to flash whole boot.img from some kernel, you'll have to flash MultiROM ZIP again or go to "Advanced->MultiROM->Inject curr. boot sector". Wiping your phone (if you mean going to "Wipe" and swiping the slider at the bottom for "factory reset") will wipe only primary ROM's data (it leaves /sdcard intact, and that's where the secondary ROMs are).
Tasssadar said:
That's exactly what testing releases are for - finding bugs and fixing them. Next time you spot something like that, report it right away, otherwise I might not even know about the problem
But somebody else reported the key-based autoboot not working, and unfortunately, on shamu, there is no way to tell if a key has been pressed before the kernel has booted up. I could add a short period of time when you could press the key and it would work, but then it would be the same as time-based autoboot. I will hide that option in next recovery release, so it doesn't mislead people.
Click to expand...
Click to collapse
Haha this is true! I just assumed you couldn't fix it if you didn't have a working N6, also don't remove that option because I don't know if you changed anything or not relating to that yet but I just saw an update in MRM and flashed it and now I can hold volume up to boot into MultiROM!!
Wow nice feature for N6! Are you planning to support more devices? E.g. Exynos Galaxy S III LTE? That would be awesome!
{
"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"
}
PREFACE
I've had this running for quite a while, but due to the amount of time I can dedicate to coding and testing, I've come to the conclusion of sharing it, even if it is not as ready as I would like it to be, and more changes are already on the way.
This is a beta version, so please treat it as such, and have your backup handy.Seeing the no-kexec workaround has been in use for quite a while, and also being used on other devices successfully, I consider it a stable release.
I also ask you to read every single word in the thread (well at least the first four posts), as I continue to elaborate on them.
As a community, it's easier to track down bugs, misbehaviours, etc. when working as a team, so your feedback will be greatly appreciated, but I kindly ask you to be very specific, every little detail counts, and the "it doesn't work" posts will not be taken into account.
Thank you for your understanding.
For your information, I have successfully tested and multi-booted:
ViperOneM9 3.5.0 (in primary)
MaximusHD 6.0.0 (directly to secondary)
ViperOneM9 3.5.0 (directly to secondary)
CM-13.0-20151210-NIGHLTY (directly to secondary)
Slim-himaul-5.1.1.beta (directly to secondary)
Notes:
* the supposedly "corrupted/inaccessible" external sdcard on Android 6 (Marshmallow) is not multirom related afaik.
* some of these ROMs take a long time to boot up, well above 10minutes, so patience
You use this tool at your own risk!!
I have tried to put as many safeguards as I can,
but I cannot be held accountable for any soft-bricks, hard-bricks, loss of data and/or information,
or anything else going wrong.
Introduction
MultiROM is one-of-a-kind multi-boot mod for HTC One M9 (hima). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port. 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
* 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.
Now seriously: Warning!
Beware of Dragons, Goblins, Gremlins and lingering primary_boot.imgDue to lack of kexec-hardboot kernel support, I am messing with your boot partition!
Since we lack kernels with kexec-hardboot patch on the M9, I'm using a workaround to bypass that restriction, and although tested successfully on the HTC One M7, HTC One M8 and HTC One M9, there are still several circumstances where things can go wrong.
If you are in doubt, either ask, or avoid it completely; MultiROM has always been a huge hack to begin with, and this is even more of a hack.
Always have a backup ready.
If you do get stuck [trying to (re)boot to primary] (i.e. starring at the boot animation, for a very long time) it is likely you have a lingering primary_boot.img (a gremlin), your primary ROM, should in fact be intact, but the workaround has "confused" the primary kernel, and has an incompatible one being used.
This is usually easily fixable by just restoring your "boot.img" from within TWRP->Restore.... there should be no need to restore everything else.
Please bear in mind, that some ROMs (particularly Sense based ROMs), can will take a long time to boot up, well above 10minutes, so patience!
Installation
Not supported at this time: 1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
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 (well, it should, but in this case it only has 2) you need to install:
Modified recovery (TWRP_multirom-YYYYMMDD-vXX-UNOFFICIAL-hima.img) - download the IMG file from second post and use
"fastboot flash recovery TWRP-multirom-20151210-v32a-beta1-UNOFFICIAL-hima.img"
(in download mode, for example)
Code:
C:ADB>fastboot flash recovery TWRP-multirom-20151210-v32a-beta1-UNOFFICIAL-hima.img"
target reported max download size of 800000000 bytes
sending 'recovery' (40248 KB)...
OKAY [ 2.883s]
writing 'recovery'...
(bootloader) HOSD CL#576582
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.475s]
finished. total time: 6.359s
C:ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-hima.zip) - download the ZIP file from second post and flash it in the MultiROM Recovery.
.
.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
We don't have a patched kernel, so I'm using a workaround.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch this is NOT SUPPORTED
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.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
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.
Screenshots here
Source code
MultiROM - https://github.com/Tasssadar/multirom (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device files - ....
Everything is here:
https://github.com/multirom-htc
https://github.com/nkk71
XDA:DevDB Information
MultiROM, Tool/Utility for the HTC One (M9)
Contributors
nkk71, Captain_Throwback
Version Information
Status: Stable
Current Stable Version: 33testbuild
Stable Release Date: 2016-11-15
Created 2015-12-10
Last Updated 2016-11-15
FAQ and other notes
HTC One M9 - Peculiarities / Bugs
There are no kexec-hardboot kernels for the M9, so you need to enable the no-kexec-workaround. Please refer to post 4 for details.
Deprecated info (used to be a problem in v1 of the workaround)
Potential problems resulting in lingering primary_boot.img:
* Reboot from secondary to recovery, flash new primary ROM/kernel (this may be fixable in inject.c, but my first attempt had unexpected results)
* Reboot from secondary, then fastboot flash boot boot.img
* While in secondary, use an app (MultiROM, Flashify, etc), which dd's the boot.img
* Others??
In short, do NOT try to mess/flash/etc your primary kernel if the last ROM you had booted was a secondary. ... this will result in a "lingering" primary_boot.img
.
A few notes about enabled adb in MultiROM boot menu: having adb enabled in MultiROM boot menu (TWRP->MultiROM->Settings->Enable ADB) may interfere with the ROMs "connection" (MTP, etc), possibly even prevent the ROM from booting (rarely, but I've seen it happen). Since this option is usually only used for debugging, I recommend to keep this option disabled.
.
Something not working, or you need help debugging
Please provide the following information:
a detailed explanation of the problem
.
the recovery.log (found in /tmp/recovery.log or by copying it to the sdcard and then copying it to PC)
.
the link to the thread and name of file (+ which version) you are having problems with
.
due to the large size of some of these ROMs, I may not have time to download and test them, so please also upload the updater-script (found in ROM.ZIP under /META-INF/com/google/android/)
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.About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Downloads
Current Test Builds
All Current Test Builds can be found on androidfilehost under MultiROM TEST BUILDS
You should be using these, not the ones mentioned below!
Definition of Test Builds: These are stable builds which I have and am using (and testing). They contain the most up to date fixes as mentioned in the changelog under <tba>.
The main reason I'm calling them "Test Builds", is because they have not gone through extensive testing as what I would usually do for a "release version". I think most people would call them release versions, but I tend to be more conservative.
.
The second reason, they get uploaded to AFH instead of directly here, is two fold:
I'm maintaining the M7, M8, M9 and HTC 10 MultiROM versions, and uploading to AFH is easier and faster for me.
Updating the actual threads and posts, is too time consuming every time I want to push an update.
Changelog and NO_KEXEC 4.1 Information can be found in the HTC 10 MultiROM thread.
1. Main downloads
Modified recovery (based on TWRP): TWRP_3.0.2-0_multirom_hima_20160723-01.img
MultiROM Main ZIP: multirom-20160723-v33d-UNOFFICIAL-hima.zip
Not supported at this time MultiROM Manager Android app: Google Play or link to APK
AndroidFileHost (mirror & old versions): https://www.androidfilehost.com/?w=files&flid=45256
Installation Note: if you were using the previous no-kexec workaround, please reboot to primary ROM first (to get rid of legacy files), then flash TWRP and multirom
2. third-party kernels with kexec-hardboot patch
None exist at the moment, hence the use of the workaround.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller-20160424-v33c-UNOFFICIAL-hima.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash [RECOVERY][Hima] TWRP touch recovery, but it is not needed - those menus don't do anything if MultiROM is not installed.
Changelog
Code:
MultiROM v33d
=====================
* Fix MultiROM Boot Menu touchscreen for Sprint
* Fix MultiROM Boot Menu boot to recovery & bootloader
MultiROM v33b
=====================
* Updates for Android 6.0 compatibility
* New kernel logging + history (needs to be enabled in TWRP)
* Added no kexec-hardboot workaround version 2
[I][B](needs to be enabled in TWRP)[/B][/I]
MultiROM v32a-beta1
=======================
* initial port for HTC One M9 (hima)
[B]* Note: encryption not supported at this time[/B]
Recoveries:
Code:
2016-07-23 (33d)
=====================
* Rebased on android-6.0 tree
- fixes TWRP progress bar
* Includes official TWRP commits up to Jun 9, 2016
* Add support for package_extract_file("system.img", <block device>)
2016-04-19 (33c)
=====================
* Fixed external sdcard ext4 partition flashing
[I]Note: booting from OTG may be broken[/I] :(
2016-04-17 (33b)
=====================
* Rebase to TWRP 3.0.2
* Use new stock theme made by z31s1g - thanks!!!
* New partition selector
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
[URL="http://bit.ly/m_su"]http://bit.ly/m_su[/URL] ) or newer!
* Fixes for several installer scripts using non-conventional methods
when installing systemless root
* Fix inject multriom checkmark not showing on startup
* New option to enable kernel logging + history for multirom
* New advanced options for no kexec-hardboot workaround version 2
[I](yes the Info page is missing)[/I]
[I]refer to [URL="http://forum.xda-developers.com/showthread.php?p=64248526&postcount=4"]post 4[/URL] for detailed info[/I]
* Add progress tracking in multirom 'restore' install
2015-12-11 (32a-beta02)
=======================
* fixed access to ext4 partition on external sdcard
2015-12-10 (32a-beta1)
=======================
* initial port for HTC One M9 (hima)
Enabling no-kexec workaround
As of this version you need to manually enable the no-kexec workaround.
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.... has been for quite some time, but I kinda kept it hidden
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
Note: the below needs to be revised as the "lingering primary_boot.img" is no longer an issue, however to do my affection for it, I can't just delete all references to it
What we (yes, we) have come to affectionately call the "lingering primary_boot.img" this should now be taken care of, as much as possible
.
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the kernel and names it primary_boot.img
This backup is created and/or used only under certain situations, for example (this is not an exhaustive list):
the last ROM was primary, and we want to boot a secondary ---> backup the primary boot.img, flash secondary one
.
the last ROM was secondary, and we're booting another secondary ---> just flash the secondary boot.img
.
the last ROM was secondary, and want to boot the primary ROM --> restore the primary_boot.img we backed up
.
^^ and here lies the problem, we cannot actually say if the backup we created is actually correct for the primary ROM.... ideally it is, but there are easy ways to break that UPDATE: not so easy to break it all, anymore
one very simple example (as mentioned in the FAQs) would be:
==> Reboot from secondary to recovery, flash new primary ROM/kernel ---> the backup of primary_boot.img will still be there, MultiROM will still think the last ROM was a secondary, and therefore restore the backup; which will result in a non-booting primary ROM since the backed up kernel doesnt actually belong to this ROM
this is what I call a "lingering primary_boot.img"
this is just one simple example, but it can happen for a variety of reasons... interrupted boots, some app/method flashed a new kernel, etc.
The solution for the "lingering primary_boot.img":
Delete (if it's there): /data/media/0/multirom/last_rom_was_2nd no longer used
[*]Delete (if it's there): /data/media/0/multirom/primary_boot.img
Reflash or restore the correct boot.img for your primary ROM
New safe guards to avoid a "lingering primary_boot.img":
TWRP will restore the primary boot.img when entering recovery
MultiROM identifies whether the boot.img currently in primary slot is secondary, by checking the boot.img itself;
it no longer relies on a separate file (last_rom_was_2nd)
If the boot.img in primary slot is not tagged as a secondary, it is considered a new primary boot.img
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a full second boot but with the secondary boot.img in the real boot partition
MultiROM continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Small note regarding encrypted devices using the no-kexec workaround
Since I dont use encryption, I haven't tested this to much extent, but I believe that there is a BOOT PRIMARY ROM option, which you can choose to boot into Internal without decrypting the device first.
Please be aware that this should not be used, if: the last booted ROM was a secondary using the no-kexec workaround.
The reason is that the backup of the primary_boot.img, is stored in the multirom folder, so for the no-kexec to be able to restore it, it needs access to the /data partition:
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
It's not too much of a big deal, because when the no-kexec workaround encounters an error, it reboots to recovery (and since recovery will restore the primary_boot.img), another reboot would be fine.
I do however (until I address this particular issue), encourage you not to use the BOOT PRIMARY ROM option, but instead decrypt the device, and then select the Internal ROM to boot.
Will this remain a "beta" version?
Most probably YES it will.... MultiROM is supposed to work with a kexec-hardboot enabled kernel; since that does not exist (at this time), on arm64 devices, I am using a workaround; since it doesn't exist and doesn't work, just work around it, if possible ... (call it "non-linear thinking" thinking if you wish)
until such time as the original author sees fit, or I decide to rename as "stable" (imho it is), it will remain called a "beta"
I have extensively tested this on the HTC One M7, the M8, and the M9 and have not found any side effects, so as of version 33b (2016-04-16), I consider this a stable release.
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
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)
Great worki @nkk71!
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.0
Delete
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.1
qriozum said:
Application "MultiROM" not working is HTCOne m9:
View attachment 3571948
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.1
Click to expand...
Click to collapse
Somebody didn't read the OP . . .
Didn't flar2 add hexec path to elementalx kernel??
Does your workaround affect performance or functionalities in any way?
Dear All,
This is a highly experimental build, it is not meant for people who want a one-click-does-it-all solution, please read the OP, in particular:
I also ask you to read every single word in the thread (well at least the first four posts), as I continue to elaborate on them.
Click to expand...
Click to collapse
Thank you
In case, I wasn't clear enough, this is an "experiment", it works for me (mostly, except some bugs I've mentioned), if you want to join, you are more than welcome (at your own discretion and risk), otherwise, I can fully understand you being not comfy using it.
nkk71 said:
Dear All,
This is a highly experimental build, it is not meant for people who want a one-click-does-it-all solution, please read the OP, in particular:
Thank you
In case, I wasn't clear enough, this is an "experiment", it works for me (mostly, except some bugs I've mentioned), if you want to join, you are more than welcome (at your own discretion and risk), otherwise, I can fully understand you being not comfy using it.
Click to expand...
Click to collapse
is there a method to uninstall the mod?
throcker said:
is there a method to uninstall the mod?
Click to expand...
Click to collapse
yes of course, plenty, probably the easiest would be:
1- reflash "normal" TWRP to get rid of this one
2- restore backup (actually you only need to restore the boot.img)
you can delete the multirom folder manually, until I post an uninstaller
nkk71 said:
yes of course, plenty, probably the easiest would be:
1- reflash "normal" TWRP to get rid of this one
2- restore backup (actually you only need to restore the boot.img)
you can delete the multirom folder manually, until I post an uninstaller
Click to expand...
Click to collapse
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
throcker said:
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
Click to expand...
Click to collapse
You are wrong.
throcker said:
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
Click to expand...
Click to collapse
Feel free to ask any kernel dev about any of the following:
* kexec
* kexec-tools
* kexec-hardboot
* kexec-hb-tools
on arm64
I did not create this to make things easier on myself, so either
1- feel free to correct me, and point me in the right direction
2- stick to the thread
Just for info: thinking/creating/coding and testing this ("make it easy") workaround
wasnt easy at all
Please stick to the thread, I think my information and feedback requests were specific enough, so can we stick with them.
Sent from my HTC One M9 using Tapatalk
Just installed this on Verizon m9. So far so good. I have Candy Six running as primary and FluentRom as a secondary. Thanks for this.
MultiROM TWRP updated to "TWRP-multirom-20151211-v32a-beta02-UNOFFICIAL-hima.img"
downloads and changelog are in the third post
(this fixes the external ext4 partition problem)
Thank for your work. I try it as soon as possible.
I apologize if I missed this in the thread, I read through but have a tendency to overlook things I'm actually looking for. Is touch working for you guys in the rom selection menu?
Just wondering, I don't mind using volume keys to select
Sent from my HTC One M9 using Tapatalk
grim489 said:
I apologize if I missed this in the thread, I read through but have a tendency to overlook things I'm actually looking for. Is touch working for you guys in the rom selection menu?
Just wondering, I don't mind using volume keys to select
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Ah yes, one of those bugs
touch generally works, but is dependant on how the kernel was built, as @Captain_Throwback mentioned, if SECURE_TOUCH is not specified then touch wont work
which ROM is that?
nkk71 said:
Ah yes, one of those bugs
touch generally works, but is dependant on how the kernel was built, as @Captain_Throwback mentioned, if SECURE_TOUCH is not specified then touch wont work
which ROM is that?
Click to expand...
Click to collapse
Oh OK I see, haha I'm on candySiX primary ROM and viper secondary. Thank you!
Sent from my HTC One M9 using Tapatalk
Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
- Decrypts Android 11
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
Treble & Non-Treble Support
No compatibility.zip error while flashing OxygenOS
A lot of customisations
Extremely beautiful UI ready to please your eyes.
Dev team is always ready to fix your problems
F2FS support
Screenshots
Screenshots at
https://imgur.com/a/Ai8KWX9
and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://orangefox.download/
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!
Congratulations
Now official.
Long live the Fox
Device: Oneplus 5T
8GB 128GB.
UI 10/10
Installation 10/10.
Keep it up
Nice to see this recovery for oneplus
Maitreya29 post: 84100659 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Click to expand...
Click to collapse
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
thkgop001 said:
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
Click to expand...
Click to collapse
I would recommend switching for stability purposes only. This recovery is beautiful to say the least and everything as far as I can tell works completely well. I am on crDroid Android 11 flashed with this recovery.
Maitreya29 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Enjoy!
Click to expand...
Click to collapse
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
thkgop001 said:
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
Click to expand...
Click to collapse
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Mr.Conkel said:
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Click to expand...
Click to collapse
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
thkgop001 said:
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
Click to expand...
Click to collapse
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Mr.Conkel said:
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Click to expand...
Click to collapse
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
thkgop001 said:
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
Click to expand...
Click to collapse
Well incase it was for further reference I would recommend using fastboot to flash Orange Fox with the recovery.img it flashes right over top of the current recovery so nothing can go wrong like that. Anytime no problem.
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
riki66 said:
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
Click to expand...
Click to collapse
Much needed, now that we have twrp supporting android 11 pin/password decryption. @Maitreya29
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Barkuti said:
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Click to expand...
Click to collapse
Welcome to the family!! Also yes stock roms kill any custom recovery only way to avoid this is with a custom rom of your choosing, the recovery is replaced upon booting into system, if you need to reboot into recovery or bootloader for any reason it should work just fine. This is a beautiful recovery I highly recommend! As far as roms there are plenty to choose from. Good luck, have fun and most importantly enjoy your new device!
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Barkuti said:
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Click to expand...
Click to collapse
If your looking from a daily perspective I highly recommend running Android 10 as A11 is still pretty rough around the edges and isn't as feature heavy yet. Although that will come in time. For now I would recommend crDroid A10 or Resurrection Remix A10 (A11 isn't out yet). I use Rr as a daily with MadKernel it works great. All these threads are relatively easy to find. But for stability over features always go with LineageOS. Cr and Rr hardly have any bugs but they do exist and you can run into a few issues. Just let me know if you need more information.
Cheers!!
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Barkuti said:
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Click to expand...
Click to collapse
If task switching is what your looking for then I highly recommend Resurrection Remix OS I use slim recents and its wonderful. Here's a screenshot for perspective. Mad Kernel is what I use it with but that isn't mandatory.
Mmm, but Slim Recents can be installed onto whatever ROM, doesn't it?
We'll see, we'll see.