Related
Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Beta 1 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11beta1-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11beta1-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]
Downloads
2013-01-08 / 2013-01-19
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)
multirom-cm11beta1-20140119-c1905-test.zip (202 MiB, 1.2 GiB extracted)
Screenshots
See Screenshots
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree (used to build MultiROM Xperia):
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Beta 1 thread
XDA:DevDB Information
MultiROM Xperia M, Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-11-04
Changelog and technical information
Changelog
2014-01-08
Added option to update/rescan for ROMs
2014-01-07
First public test release
Technical information
It works by extracting the boot ramdisk to root and patching init.rc files after boot selection.
More to be added
Changes from the original MultiROM
This port is based on the original MultiROM by @Tasssadar, which is available for multiple devices including the Nexus 4, 5 and 7. However, since his original port did not account for supporting external SD cards, and also didn't handle most Xperia devices without a recovery partition, I've rewritten some part of his original MultiROM to handle these things.
Differences include:
All binaries are placed in the ramdisk altogether instead of the internal storage.
MultiROM Xperia does not mount the partitions before starting the real Android init. Instead, it generates a script and patches some files (including init.rc) to trick the target system to mount filesystem images (loop mounting loop devices).
One ROM can contain multiple user profiles (i.e. data, cache and persist).
The code to boot generic (non-Android) Linux ROMs is removed due to heavy rewrite of parts from the original MultiROM.
It currently only support using partition filesystem images, neither symlink nor bind mount is supported.
Reserved
Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks
aweosomeabhijeet said:
Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks
Click to expand...
Click to collapse
how did u get it work?
which model c1904 or c1905?
which sdcard?
Till now I've discovered a few bugs in this test release:
Sometimes, microSD card is not detected because the initialization is too long.
This varies between cards. A theory is that SDHC might take a longer time to initialize, which happens after MultiROM has scanned for partitions.
You can try rebooting a few times and if, by any chance, the card initialized right in time, you will be able to boot the external ROM.
I have a few possible solutions for this, and I will update to you when I've implemented a working solution.
USB OTG storage devices may not be detected properly. Needs investigation...
Thanks to @ansebovi for testing and informing about these.
i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?
ansebovi said:
how did u get it work?
which model c1904 or c1905?
which sdcard?
Click to expand...
Click to collapse
Flashed boot.img using fastboot.
Extracted ROM in the root of sdcard.
Rebooted. Selected sdcard>cm11>boot. And it booted
Model C1904
SanDisk micro sd 8GiB class4
Sent from my C1904 using xda app-developers app
I've added an option in the "Misc" tab to rescan for ROMs as a temporary measure. Flash the new boot image to get it. Please refer to the first post for download.
Sent from my Sony Xperia M (C1905)
GedeWK said:
i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?
Click to expand...
Click to collapse
Well, how to install gapps to the ROM? I need the play store
to do the tutorial I have to have the bootloader unlock?
alvinhochun said:
Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Alpha 2 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11alpha2-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11alpha2-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]
Downloads
2013-01-07
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)
Screenshots
See Screenshots
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree:
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Alpha 2 thread
XDA:DevDB Information
MultiROM Xperia M, a Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-01-09
Click to expand...
Click to collapse
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.
daruto80 said:
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.
Click to expand...
Click to collapse
u should not quote op on any thread...edit ur post..remove quote
and yes u need an unlocked bootloader
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
It's only for Xperia M at the moment since it is not completed yet.
If anyone feels like porting it to other devices I will surely appreciate, but for me I will wait till most of it is ready before porting to other devices.
Uploaded test package with unofficial CM11 Beta 1. Just extract it to SD card, just like the previous test release.
Although I don't expect daily usage on a pre-alpha test release, if you want to keep your data in CM11 Alpha 1, copy the `default` directory from cm11-alpha2 and replace the one in cm11-beta1.
Just a little update, I am coding as I type this, but you cannot expect the alpha release of MultiROM Xperia to be here in a short time 'cause there is a lot to do. You can still try the test packages at the moment.
Is the testing still in process? Because I can't wait to try this out. I hope it would be done sooner...
Booting all the 4 ROM(s)!
Thanks Alvin :highfive:
elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
XZ already have multi rom elias it has been done by mithun46
rebelos said:
XZ already have multi rom elias it has been done by mithun46
Click to expand...
Click to collapse
it is out dated , and it needs an app , says always unsupported rom , mithun stopped the developing for it ( he never replies on his thread nor on any question about the multirom )
aweosomeabhijeet said:
Thanks Alvin :highfive:
Click to expand...
Click to collapse
How were you able to get it to read ROMs? I'm currently having trouble and have tried almost everything. I compared the test zip and the FXP311 zip and found out that they are completely different.
★ ☆[Recovery][Mod][Multi-Boot] MultiROM V22 | m7vzw [Unofficial][03-16-14]☆ ★
Introduction
This is a port of Tasssadar's MultiROM.
MultiROM allows you to boot multiple ROMs on the same device (as well as, in theory, Linux distros, if there were any available for our device, or android-based operating systems such as Ubuntu Touch).
ROMs are flashed in the modified recovery, and upon booting the phone, you have a boot menu that will allow you to choose which ROM you want to boot.
You can also boot ROMs off of a USB drive connected via an OTG cable (**There are some limitations to this, keep reading for details**).
First of all, I would like to thank Tasssadar because this is 100% his work. If you enjoy MultiROM, feel free to donate to him.
I have just ported it to Kitkat for the Verizon HTC One.
MultiROM in action: http://www.youtube.com/watch?v=SCYh14Zwl3s
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.
Sense ROM Support
MultiROM is now able to boot Sense ROMs (as secondary only), but the process is a little more complicated.
See second post for step-by-step instructions (Big thanks to vroad for figuring this out). Still in testing on m7vzw.
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 you need to install:
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-m7vzw.zip)) - download the ZIP file from second post and flash it in recovery.
Modified recovery (recovery_mrom_YYYYMMDD.img) - download the IMG file from second post and use fastboot or an app such as FlashImageGUI or Flashify to flash it.
Patched kernel - You absolutely MUST have a kernel with the kexec-hardboot patch on the primary ROM for this to work.
My latest Aosb and Aicp builds both have this.
The primary and secondary roms can share a kernel if you want to install one that is not patched, but may work with the primary one.
You current rom will not be erased by the installation.
Download links are in the second post.
fastboot flash recovery recovery.img (or use Flashify from the Play Store)
flash the MultiRom zip to prep the device for multi booting
Flash an internal rom with a kexec hardboot patched kernel
For now, I recommend using two Aosp roms until Sense roms are further tested by me.
If you are feeling experimental, I will include a process for trying this now if you wish.
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 and proceed with the installation.
Note: In theory, FAT32, EXT4, and NTFS partitions should all be supported. However, using a FAT32 partition may result in a failed flash.
I have not tried NTFS. If you want to boot off of your USB drive, I recommend putting a dedicated EXT4 partition for booting ROMs.
Also, I was unable to boot off of a thumb drive without sharing a kernel with the primary ROM or using a patched kernel on the secondary ROM.
So if you are going to do this, any ROM you want to boot off of the USB drive ALSO needs a patched kernel.
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 a kernel which is distrubuted as whole boot.img, you have to use this option on it, otherwise you would lose MultiROM. (You will likely not need to use this option with most kernel installers)
- 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.
Source code
MultiRom - https://github.com/Tasssadar/multirom
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
kexec-hardboot patch - https://gist.github.com/Tasssadar/6733940
XDA:DevDB Information
Multi-Rom | m7vzw | Multi-Boot | Recovery, a Tool/Utility for the Verizon HTC One
Contributors
santod040
Version Information
Status: Testing
Current Beta Version: v22
Beta Release Date: 2014-03-16
Created 2014-03-17
Last Updated 2014-03-17
Reserved
Downloads
Modified MultiRom TWRP Recovery: DOWNLOAD
MultiROM m7vzw Zip: DOWNLOAD
My Aosp Kernel w/ kexec-hardboot patch: DOWNLOAD
Uninstaller: DOWNLOAD
Mount Disabler: DOWNLOAD (for Sense ROMs, see instructions below):
You don't need to flash mount-disabler onto primary ROMs.
You only have to flash mount-disabler onto Sense-based SECONDARY ROMs.
If you forget to flash it, Sense ROM's init will attempt to mount primary ROM's system/cache.
If something goes wrong and ROM doesn't boot, enter TWRP recovery and adb pull /proc/last_kmsg, which says why it didn't work.
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 (good thing HTC gave us a WHOPPING 32 gigs). 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 share kernel" when installing the secondary ROM, the systems are separated.
My secondary ROM doesn't boot if I share the kernel with the primary ROM.
Reinstall the secondary ROM, don't share the kernel this time, and flash the kernel you want to use to that ROM.
How to use Sense with MultiROM
Using Sense with MultiROM is complicated for a few reasons:
-The MultiROM boot menu doesn't show up with Sense ROMs for some unknown reason.
-Most Sense ROMs can't be flashed via the MultiROM menu because they mount partitions by explicitly using the mmc block. This causes the ROM to be partially install over the primary ROM. vroad has a pretty good explanation of why this happens:
Some users have already reported that ROMs with certain kind of updater-script will format system/data/cache of primary ROM slot, and overwrite to them, even though they have tried to flash onto secondary slot.
This is because these updater-script mount partitions with the name of block device(such as /dev/block/mmcblk0p34), not with mount points(such as /system).
-Sense ROMs also try to mount /system and /cache on boot, so the mount disabler zip is required for the ROM to boot properly.
To boot a secondary Sense ROM:
1. If you have an AOSP ROM already installed as your primary ROM, first go to Advanced > MultiROM > Swap ROMs and choose "move primary ROM to secondaries."
2. Install your Sense ROM as a primary ROM, just as you would with standard TWRP.
3. Go back to the Swap ROMs menu:
-If you had a previously installed AOSP ROM, choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
-Otherwise, choose "move primary ROM to secondaries"
4. Flash the Mount Disabler Zip to your secondary Sense ROM.
5. Insure that the primary AOSP ROM has a kernel with kexec-hardboot support as well as the MultiROM zip installed.
To update the secondary Sense ROM
1. Go to Advanced > MultiROM > Swap ROMs and choose " swap primary (Internal) ROM with secondary" and choose the Sense ROM you want to update.
2. Flash the ROM update to the primary ROM slot (just as you would with standard TWRP)
3. Go back to the Swap ROMs menu, and choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
4. Flash the Mount Disabler zip to your secondary Sense ROM.
If you do not follow these instructions properly, you will end up with a corrupted, half-Sense half-AOSP primary ROM and a secondary ROM that doesn't boot.
Kitk-Kat only. JB Sense ROMs most likely will not work.
Reserved
and one more....
Great work !! Was waiting for this for a long time...
mount disabler zip
Where do we find mount disabler zip, don't see a link to dl
kc6wke said:
Where do we find mount disabler zip, don't see a link to dl
Click to expand...
Click to collapse
Added to second post.
Just know that multi booting sense roms is still in testing, so results may vary.
So, If I am on rooted stock, can I install MultiRom and keep my stock as internal? Or do I have to use AOSP as internal and flash a new kernel? I'm assuming if stock was a necessity I would uninstall MultiRom, reinstall TWRP, then flash stock back.
jodaschmo said:
So, If I am on rooted stock, can I install MultiRom and keep my stock as internal? Or do I have to use AOSP as internal and flash a new kernel? I'm assuming if stock was a necessity I would uninstall MultiRom, reinstall TWRP, then flash stock back.
Click to expand...
Click to collapse
The internal rom must have a kernel with a Kexec hardboot patch.
The stock kernel does not have this.
Could I, given I have a backup on my computer, so I can still revert, Flash your kexec kernel over Stock,or do I have to go pure AOSP? Trying not to sound too ignorant...
jodaschmo said:
Could I, given I have a backup on my computer, so I can still revert, Flash your kexec kernel over Stock,or do I have to go pure AOSP? Trying not to sound too ignorant...
Click to expand...
Click to collapse
As of right now, as mentioned, multi booting sense roms on the m7vzw is still being tested and worked out.
This was initially intended for multi booting Aosp roms.
If you are not familiar with any of this or well adversed with messing up and recovering your device, I advise sticking with Aosp roms on this for now.
The kernel I posted is an Aosp kernel, it will not work correctly, if at all, on a Sense rom.
Makes sense. Cool, so I can update Carbon's Kernel, and work with what ever else. How does this fair for MIUI? I'm assuming it depends on the base rom?
jodaschmo said:
Makes sense. Cool, so I can update Carbon's Kernel, and work with what ever else. How does this fair for MIUI? I'm assuming it depends on the base rom?
Click to expand...
Click to collapse
Depends on the base rom and the m7vzw has no fully functional miui currently, so I would say it doesn't work with miui for now.
Yes you can update Carbons kernel and then add a secondary rom.
I would use another Aosp rom and just share the kernel across the two.
You do not need to share the kernel across the two, if you are certain that the secondary rom has a kexec hardboot patch.
I would assume they do not, unless stated specifically in the kernel threads OP, or ask that kernel Dev.
Hopefully the one I have posted works across enough Aosp roms, that it's fairly universal and fully featured.
santod040 said:
Depends on the base rom and the m7vzw has no fully functional miui currently, so I would say it doesn't work with miui for now.
Yes you can update Carbons kernel and then add a secondary rom.
I would use another Aosp rom and just share the kernel across the two.
You do not need to share the kernel across the two, if you are certain that the secondary rom has a kexec hardboot patch.
I would assume they do not, unless stated specifically in the kernel threads OP, or ask that kernel Dev.
Hopefully the one I have posted works across enough Aosp roms, that it's fairly universal and fully featured.
Click to expand...
Click to collapse
any update to this coming?? seems like a fun thing to have that and ive been trying it but it wont flash updated cm build and the kernel gives me black screen on the newer aosp roms ? lol
Alpha_wolf said:
any update to this coming?? seems like a fun thing to have that and ive been trying it but it wont flash updated cm build and the kernel gives me black screen on the newer aosp roms ? lol
Click to expand...
Click to collapse
It's a bit of work to keep current and I didn't see much interest to be honest.
So it's been on the back burner for a bit.
If I get some free time and find myself bored, I may bring it current again.
Just couldn't justify spending a lot of time on something that very few are interested in.
Sent from my HTC6525LVW using Tapatalk
santod040 said:
It's a bit of work to keep current and I didn't see much interest to be honest.
So it's been on the back burner for a bit.
If I get some free time and find myself bored, I may bring it current again.
Just couldn't justify spending a lot of time on something that very few are interested in.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
oh ok no prob if you do update id enjoy it lol be fun thing to have
Agreed! Especially if it would work with an internal sense rom. Anyone know if Viper kernel has kexec-hardboot patch?
Alpha_wolf said:
oh ok no prob if you do update id enjoy it lol be fun thing to have
Click to expand...
Click to collapse
Can someone please port this to sprint varient or lead me in the right direction , I have seen the op to port but still don't understand it willing to use and test my device for this
santod040 said:
Introduction
This is a port of Tasssadar's MultiROM.
MultiROM allows you to boot multiple ROMs on the same device (as well as, in theory, Linux distros, if there were any available for our device, or android-based operating systems such as Ubuntu Touch).
ROMs are flashed in the modified recovery, and upon booting the phone, you have a boot menu that will allow you to choose which ROM you want to boot.
You can also boot ROMs off of a USB drive connected via an OTG cable (**There are some limitations to this, keep reading for details**).
First of all, I would like to thank Tasssadar because this is 100% his work. If you enjoy MultiROM, feel free to donate to him.
I have just ported it to Kitkat for the Verizon HTC One.
MultiROM 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.
Sense ROM Support
MultiROM is now able to boot Sense ROMs (as secondary only), but the process is a little more complicated.
See second post for step-by-step instructions (Big thanks to vroad for figuring this out). Still in testing on m7vzw.
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 you need to install:
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-m7vzw.zip)) - download the ZIP file from second post and flash it in recovery.
Modified recovery (recovery_mrom_YYYYMMDD.img) - download the IMG file from second post and use fastboot or an app such as FlashImageGUI or Flashify to flash it.
Patched kernel - You absolutely MUST have a kernel with the kexec-hardboot patch on the primary ROM for this to work.
My latest Aosb and Aicp builds both have this.
The primary and secondary roms can share a kernel if you want to install one that is not patched, but may work with the primary one.
You current rom will not be erased by the installation.
Download links are in the second post.
fastboot flash recovery recovery.img (or use Flashify from the Play Store)
flash the MultiRom zip to prep the device for multi booting
Flash an internal rom with a kexec hardboot patched kernel
For now, I recommend using two Aosp roms until Sense roms are further tested by me.
If you are feeling experimental, I will include a process for trying this now if you wish.
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 and proceed with the installation.
Note: In theory, FAT32, EXT4, and NTFS partitions should all be supported. However, using a FAT32 partition may result in a failed flash.
I have not tried NTFS. If you want to boot off of your USB drive, I recommend putting a dedicated EXT4 partition for booting ROMs.
Also, I was unable to boot off of a thumb drive without sharing a kernel with the primary ROM or using a patched kernel on the secondary ROM.
So if you are going to do this, any ROM you want to boot off of the USB drive ALSO needs a patched kernel.
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 a kernel which is distrubuted as whole boot.img, you have to use this option on it, otherwise you would lose MultiROM. (You will likely not need to use this option with most kernel installers)
- 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.
Source code
MultiRom - https://github.com/Tasssadar/multirom
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
kexec-hardboot patch - https://gist.github.com/Tasssadar/6733940
XDA:DevDB Information
Multi-Rom | m7vzw | Multi-Boot | Recovery, a Tool/Utility for the Verizon HTC One
Contributors
santod040
Version Information
Status: Testing
Current Beta Version: v22
Beta Release Date: 2014-03-16
Created 2014-03-17
Last Updated 2014-03-17
Click to expand...
Click to collapse
kexec-hardboot patch for M7wlv CyanogenMod14.1 ？
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Intorduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S4. 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 external SD card. 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 image above. 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.
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned!
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card
And since i don't feel like ripping this stuff from AntaresOne's thread, go read it here (i'm lazy): http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/mod-multirom-v28-t2864469
This is basically the same, i've done some small modifications and development to get it working on I9295.
Installation
1. Via MultiROM Manager app NOT tested on I9295, propably won't work. Don't try! (But if you do, report )
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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel - Download the ZIP file and flash it in recovery or keep stock kernel (CM11/based ROMs with this android_kernel_samsung_jf source)
You current rom will not be erased by the installation.
Download links are in the second post.
TWRP
MultiROM TWRP can work without MultiROM installed. Obviously most MultiROM related features won't work so steer away from them.
When formatting partitions, especially /data, do keep backups handly, even from /sdcard. As /data and /sdcard are on same partition, formatting /data formats /sdcard. Note that factory reset doesn't actually format /data, it just wipes the directory clean. But when changing fs type on /data, /sdcard will be formatted also.
Credits
@Tasssadar for awesome application
@AntaresOne for jflte device tree to use as base and original thread
Known bugs
- none known currently
Source code
jactive device tree: https://github.com/spegelius/android_device_samsung_jactivelte/tree/cm-11.0-multirom
CM11 local_manifest for multirom: https://github.com/spegelius/manifests/tree/cm-11.0-multirom
MultiROM: https://github.com/Tasssadar/multirom
TWRP: https://github.com/Tasssadar/Team-Win-Recovery-Project
Downloads
https://drive.google.com/folderview?id=0BzJzDM42pkRvTkJVMGMxSVJiWkk&usp=sharing
Changenotes
MultiROM
multirom-20150215-v31-UNOFFICIAL-jactivelte
Changes:
All commits here: https://github.com/Tasssadar/multirom/commits/master since Feb 7, 2015
Supports new CM12 fstab scheme, needed for newest CM12 builds to work
20150207-v30-UNOFFICIAL-jactivelte
Changes:
All commits here: https://github.com/Tasssadar/multirom/commits/master since Jan 12, 2015
20150112-v30-UNOFFICIAL-jactivelte
Changes:
All commits here: https://github.com/Tasssadar/multirom/commits/master since Dec 03, 2014
20141203
initial release
TWRP
multirom_twrp_20150215_000001
Changes:
All commits here: https://github.com/spegelius/Team-Wi.../master?page=2 since Feb 7, 2015
TWRP 20150207_174341
Changes:
All commits here: https://github.com/spegelius/Team-Win-Recovery-Project/commits/master?page=2 since Jan 12, 2015
Fix reboot not working (credits for the fix: @d8389)
TWRP 20150112_202427
Changes:
All commits here: https://github.com/spegelius/Team-Win-Recovery-Project/commits/master?page=2 since Dec 18, 2014
20141218_215324
both Odin flashable tar and CWM zip available
merged changes from Tassadar's repo, TWRP version 2.8.20
disabled screen timeout for now. Need to look at the code more to understand why wake up doesn't work
I am surely gonna try this after I read more about it and the differences with DualBootPatcher
#GoodWork!
ZeroZorro said:
I am surely gonna try this after I read more about it and the differences with DualBootPatcher
#GoodWork!
Click to expand...
Click to collapse
Yes, this is quite nifty, i have CM12, CM11 and AOSP installed currently and latter two are running from my external sdcard (exfat). Granted, they are somewhat slower but for now those installations are only for testing. I ordered a miniusb to female usb adater so i can even install roms to usb stick . Not very handy in everyday use, but helps when you want to just test something...
Personally i use this modified TWRP quite lot now that it has f2fs and exfat support.
First attempt didn't work out for me....
Currently running WizCyan 4.4.2 ROM
When entering recovering mode and trying to install multirom-20141203-v30-UNOFFICIAL-jactivelte.zip from SD-card i end up with an error 7, no harm done...
Already made a nandroid backup of this rom so i think i'm gonna install patched recovery-image with Odin and after that multirom.zip through recovery.
That way i will be able to restore the Nandroid from the MultiROM menu, right?
@spegelius you say you have CM12 as primary ROM. I presume it's NOT the Dual? And it doesn't have to be patched before installing?
ZeroZorro said:
First attempt didn't work out for me....
Currently running WizCyan 4.4.2 ROM
When entering recovering mode and trying to install multirom-20141203-v30-UNOFFICIAL-jactivelte.zip from SD-card i end up with an error 7, no harm done...
Already made a nandroid backup of this rom so i think i'm gonna install patched recovery-image with Odin and after that multirom.zip through recovery.
That way i will be able to restore the Nandroid from the MultiROM menu, right?
@spegelius you say you have CM12 as primary ROM. I presume it's NOT the Dual? And it doesn't have to be patched before installing?
Click to expand...
Click to collapse
Did you install the TWRP? I haven't tried with CWM. Error 7 sounds like old recovery or something... not sure (had those problems with AOSP updater and some versions of CWM at some point).
I don't use dualboot, best not to mix it with this. Actually i think dualboot break multirom (need to flash multirom again after dualboot rom flash) and vice versa.
Haven't tried nandroid restore with MultiROM but i think it should be possible? Also if i got this right, if you restore your nandroid as an multirom installation, you'll have two instances of same rom; the main rom and the one installed from nandroid.
Just installed TWRP with Odin and after that MultiROM and it works...cause SuperWizCyan works great i'll leave it as Primary ROM for now and will install CM12 and StockROM on my SDcard...to be continued!
ZeroZorro said:
Just installed TWRP with Odin and after that MultiROM and it works...cause SuperWizCyan works great i'll leave it as Primary ROM for now and will install CM12 and StockROM on my SDcard...to be continued!
Click to expand...
Click to collapse
Hmm , i wonder if the latest CM12 installer works with MultiROM since it has custom partition format script which allows it to detect f2fs/ext4. Make sure you have backups before trying.
Okay, i even moved my Nandroid Backup to my PC before proceeding.....you can never be too careful!
Installing CM12 to my SD-card now.....
* I have to keep the screen 'alive' while installing CM12 with MultiROM, otherwise when the screen goes black...well i had to reset the phone....
* 2nd attempt it seems to work, no errors and after pushing the Reboot-button screen goes black again...> reset
* I can see the Boot-screen but touch-screen not working so trying to cancel Boot from Internal doesn't work so it auto-boots... >> found it ... Use Volume Buttons!
* But: i can see that CM12 is listed as 2nd ROM
* So now i have to find a way to get into the menu to choose ROM to boot
And... how do i install the GAPPS for this 2nd ROM? >> found it...you can do it within TWRP>MultiROM #cool
Also installed MultiROM manager apk hoping it would give me boot options but (obvious) it doesn't work on 9295 for now.
For testing purposes i set the 2nd ROM to boot in MultiROM setting (trough TWRP)....it seems that the black screen is a problem of TWRP, not MultiROM
Oh well... booting CM12 doesn't work for now...will post multirom_log soon
See attached multirom_log,txt
ZeroZorro said:
See attached multirom_log,txt
Click to expand...
Click to collapse
In the log there was mention about kexe-hardboot failing... Is WixCyan a TW rom? Is the kernel in it KEXEC-HARDBOOT patched? That patch is in CM11, CM12 and AOSP (and other CM11 derivates) since their kernels are the same base. For TW, you'd need some modified kernel.
So it works only for aosp and cm roms?
6783 said:
So it works only for aosp and cm roms?
Click to expand...
Click to collapse
No without patched kernel. It might work if the TW rom isn't the first rom, but instead a multirom.
Update: i'm there
Now i have SuperWizCyan as Primary (internal) ROM and SammyStockTW as secondary on my SD-card
I made it harder then needed cause i forgot to make a Nandroid with TWRP instead of CWM so i had to re-install CWM to get my 1st ROM back.
(If you really wanna know what i did, please ask, for now i will spare you the details )
For now, as you can see in the previous post, CM12 doesn't work for now....we'll wait and see and do some more testing!
But hey, it worked and so far so good.....1 thing i didn't read about is if there i going to be an option of app-sharing like DualPatcher does. App-sharing with data-sharing would be even better for my banking apps and Whatsapp to work on both ROM's.
Thanks again @spegelius !
ZeroZorro said:
Update: i'm there
Now i have SuperWizCyan as Primary (internal) ROM and SammyStockTW as secondary on my SD-card
I made it harder then needed cause i forgot to make a Nandroid with TWRP instead of CWM so i had to re-install CWM to get my 1st ROM back.
(If you really wanna know what i did, please ask, for now i will spare you the details )
For now, as you can see in the previous post, CM12 doesn't work for now....we'll wait and see and do some more testing!
But hey, it worked and so far so good.....1 thing i didn't read about is if there i going to be an option of app-sharing like DualPatcher does. App-sharing with data-sharing would be even better for my banking apps and Whatsapp to work on both ROM's.
Thanks again @spegelius !
Click to expand...
Click to collapse
Great, apparently there's KEXEC_HARDBOOT patch somewhere there or it's not needed .
For CM12, another installer zip is needed, which has the normal /system format and mount commands. I'll see if i get it done.
No app sharing, at least automatically. In the I9505 thread someone suggested moving the apps/data to sdcard or something...
Oh and the problem with screen timout is known, didn't remember to mention it. Screen timeout can be disabled in Settings.
Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of MultiRom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?
O-T said:
Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of mulirom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?
Click to expand...
Click to collapse
Yes, TWRP works without MultiROM. There are few checkboxes, like Inject MultiROM that need to be disabled when installing roms for example, but basic stuff works without multirom.
@spegelius
Ehhm, small correction for OP Installation - Modified Recovery:
It's a tar-file on your Gdrive, no zip-file for installation by recovery multirom_twrp_20141204_1838.tar.md5
Not tried Mobile Odin yet but I know PC Odin swallow tar-files.
About warning TWRP format of /data also include /sdcard. /sdcard is soft or hardlinked(?) to /data/media/0
Can the relationship between fstab of TWRP and mount points of S4A be a good place to start tracing, or is this all fuse managed?
Recovery.log of CWM 6.0.5.0 got me thinking:
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
Can mount points be somewhat off? (at least for CWM) . The reason is that delete dalvik cache take less than a microsecond, as if it has not been executed. Delete cache and zip install has been good.
Will update to TWRP using Odin from PC and follow up.
spegelius said:
In the log there was mention about kexe-hardboot failing... Is WixCyan a TW rom? Is the kernel in it KEXEC-HARDBOOT patched? That patch is in CM11, CM12 and AOSP (and other CM11 derivates) since their kernels are the same base. For TW, you'd need some modified kernel.
Click to expand...
Click to collapse
Yes WizCyan is TW ROM and should work....?
see: http://forum.xda-developers.com/galaxy-s4-active/development/rom-super-wizcyan-s5-style-t2874424
I'll ask @JASONRR if he can implement KEXEC-HARDBOOT in next version.
I have to do some clean install cause i can't restore my Nandroid Backups (all CWM-related). :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
*** Note I am not a MultiROM expert. I wanted to create a place to share and buried in @KINGbabasula's thread is not ideal. Per his request, I've made this thread...
*** Special thanks to @KINGbabasula for his original thread, and to @martinusbe and @nkk71 for entertaining my endless questions, and providing invaluable help when asked.
MultiROM is one-of-a-kind multi-boot mod for Oneplus One. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on YouTube. If you want, just search for "MultiROM installation" on YouTube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use TWRP (flash image file), fastboot or Flashify app to flash it.
Patched kernel - Your Primary ROM's kernel should have the no-kexec patch applied, but should be OK if not as MultiROM will check.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. If desired, you can go to Advanced -> MultiROM -> List ROMs, select your ROMcan flash individual zips, one by one, such as GApps or SU.
2. Ubuntu Touch (Note I have not tested this nor do I use Ubuntu Touch.)
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS (Note I have not tested this nor do I use Firefox OS.)
Firefox OS is just another Android ROM from MultiROM's point of view, so add it as if it were Android
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject current boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
MultiROM device tree - https://github.com/MR-op3/device_oneplus_bacon (branch mr)
MultiROM kernel - https://github.com/MR-op3/kernel_oneplus_msm8974 (branch mr)
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
[MOD][OPO] MultiROM v33e [WIP-TESTING][NOUGAT], Tool/Utility for the OnePlus One
Contributors
NoSpamDan, martinusbe, nkk71
Version Information
Status: Testing
Created 2017-02-12
Last Updated 2017-02-17
DOWNLOADS
Flashable MultiROM TWRP v3.1.1 Recovery img file: TWRP_multirom_bacon_20170711-07.img
Flashable MultiROM ZIP: multirom-20161206-v33e-UNOFFICIAL-bacon.zip
Flashable MultiROM Uninstaller ZIP: multirom_uninstaller.zip
Dark-themed MultiROM Manager App: MultiROMMgr-GZR-TBO.apk
(premaca's download folder)
You can thank @premaca and @martinusbe for much of this.
Previous versions:
Flashable MultiROM TWRP v3.0.3-0 Recovery:
multirom-20170711-v33e-UNOFFICIAL-bacon.zip
TWRP MultiROM:
TWRP_3.0.2-0_multirom_bacon_20161212-01.img
MultiROM ZIP:
TWRP_multirom_bacon_20170224-01.img
MultiROM Uninstaller:
multirom_uninstaller.zip
FAQ/FYI
Here are some common questions and answers with MultiROM:
I can't flash a different recovery on my device because the option is not there.
Most likely, the fstab file in the recovery needs to be fixed. You'll probably need to perform the fastboot steps in #2 below.
How to use fastboot to flash a recovery image to your device:
To flash back to another recovery:
Boot your device into fastboot mode.
Copy the recovery img file you want to flash to a place where you have fastboot installed. You probably did this already when you installed TWRP over your stock recovery so you could flash custom ROMs.
Open a terminal/command window in the directory where fastboot.exe and the recovery.img file are, and type: fastboot flash recovery recovery.img (where "recovery.img" is the actual name of the recovery file you want to flash).
None of my secondary ROMs will boot:
You probably need to run Restorecon on the secondary ROM to modify its selinux contexts. To do this:
In MultiROM TWRP, click the MultiROM options in the upper right corner.
Select "List ROMs"
Choose your ROM from the list
Click the "Run Restorecon" button
Reboot into that ROM
I am not seeing the boot menu from MultiROM to select a ROM.
Make sure you injected MultiROM into your primary ROM. To do this:
Flash the MultiROM zip file to your primary ROM.
Click the MultiROM options in the upper right corner
Select the "Inject boot sector" button
Reboot
If you still have trouble, see @nkk71's post here with more information.
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
can my 16GB-device work??
Great mod. Thanks NoSpamDan for keeping it alive!
SirSoviet said:
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
Click to expand...
Click to collapse
Going to need more details than that... and thanks for the log.
What ROM primary and secondary?
Did you inject the boot image on your primary?
Try flashing your primary as both a primary and a secondary and see if you can add another secondary. This is still in the testing phase but I have Slim7 as my primary and no issues with secondary ROMs. I don't normally even need restorecon on them when I test (unless it gets stuck at the kernel splash screen)...
EDIT: From your log:
Code:
[ 3.375133] multirom: kexec -u test has failed, kernel doesn't have kexec-hardboot patch enabled in config!
ceiven said:
can my 16GB-device work??
Click to expand...
Click to collapse
Sure, why not? You can use an external OTG drive to keep ROMs on. Depending on how much space your ROM & Data occupies will limit what you can do on such a small storage device.
SirSoviet said:
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
Click to expand...
Click to collapse
@nikhil18 forgot to enable KEXEC in V35. Use V34, it's enabled/working fine there.
NoSpamDan said:
Going to need more details than that... and thanks for the log.
What ROM primary and secondary?
Did you inject the boot image on your primary?
Try flashing your primary as both a primary and a secondary and see if you can add another secondary. This is still in the testing phase but I have Slim7 as my primary and no issues with secondary ROMs. I don't normally even need restorecon on them when I test (unless it gets stuck at the kernel splash screen)...
Sure, why not? You can use an external OTG drive to keep ROMs on. Depending on how much space your ROM & Data occupies will limit what you can do on such a small storage device.
Click to expand...
Click to collapse
So it seems that the latest version of LK has broken Kexec, so no need to worry about that. Just the No-Kexec workaround that's problematic.
I'm currently using HalogenOS, and any secondary rom won't work. I injected the boot image on the primary rom, otherwise I would be booting straight into the primary rom.
SirSoviet said:
So it seems that the latest version of LK has broken Kexec, so no need to worry about that. Just the No-Kexec workaround that's problematic.
I'm currently using HalogenOS, and any secondary rom won't work. I injected the boot image on the primary rom, otherwise I would be booting straight into the primary rom.
Click to expand...
Click to collapse
Well I edited my last response to include a line from your log indicating that the kernel does not have the kexec-hardboot patch.
NoSpamDan said:
Well I edited my last response to include a line from your log indicating that the kernel does not have the kexec-hardboot patch.
Click to expand...
Click to collapse
I know that, I said that the latest version of Lightning Kernel has broken kexec-hardboot. All that needs to be fixed is the no-kexec workaround.
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
JT1510365 said:
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
Click to expand...
Click to collapse
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
f41lbl0g said:
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
Click to expand...
Click to collapse
What roms would have it wouldn't rr remix rom nougat have it?
JT1510365 said:
What roms would have it wouldn't rr remix rom nougat have it?
Click to expand...
Click to collapse
I haven't used multirom in a while so I don't know.
JT1510365 said:
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
Click to expand...
Click to collapse
Great question... it's Nougat-friendly because you can install Nougat ROMs as secondary. The Developer Options problem is a bug...
As a work-around, you can install your problem Nougat ROM as a Primary, enable the Developer Options there, then move it to a Secondary slot...
f41lbl0g said:
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
Click to expand...
Click to collapse
Indeed, a secondary ROM needs this: https://review.slimroms.org/#/c/22989/
I'm running a marshmallow and nougat rom together with the last version of multirom?
NoSpamDan said:
Great question... it's Nougat-friendly because you can install Nougat ROMs as secondary. The Developer Options problem is a bug...
As a work-around, you can install your problem Nougat ROM as a Primary, enable the Developer Options there, then move it to a Secondary slot...
Indeed, a secondary ROM needs this: https://review.slimroms.org/#/c/22989/
Click to expand...
Click to collapse
For nougat compatibility, moving to latest @nkk71 multirom modified_twrp 3.0.3-0 is real better 2017-01-27:
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
BTW, MultiROM' OPs should clarify one for all that multirom.zip' s trampoline works fine with all unmodified recoveries twrp/cwm (primary rom install/update only): modified_twrp is only needed for managing 2nd roms.
Of course, using un-swapped unique modified_TWRP recovery is always much "cooler" (I didn't had much success explaining that to p880' users with : how to rom/kickflip and twrp/shuvit...), and NoKexec workaround is a more complicate behaviour.
Even after flashing v33e, Multirom manager says I'm running v33b... Is that normal?
oF2pks said:
For nougat compatibility, moving to latest @nkk71 multirom modified_twrp 3.0.3-0 is real better 2017-01-27:
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
BTW, MultiROM' OPs should clarify one for all that multirom.zip' s trampoline works fine with all unmodified recoveries twrp/cwm (primary rom install/update only): modified_twrp is only needed for managing 2nd roms.
Of course, using un-swapped unique modified_TWRP recovery is always much "cooler" (I didn't had much success explaining that to p880' users with : how to rom/kickflip and twrp/shuvit...), and NoKexec workaround is a more complicate behaviour.
Click to expand...
Click to collapse
I have a version of 3.0.3-0 built, but I couldn't get my multirom zip file to show the boot menu/boot sector. I did flash the zip and injected it but no luck. I have reached out to @nkk71 for ideas on this, but it might be best if he responds here when he has a chance.
For now, I'll put the new TWRP in Post #2 and here if you want to try it. Keep a previous version around just in case you need to fastboot flash it to your device: TWRP_3.0.3-0_multirom_bacon_20170213-01.img
iruiz2 said:
Even after flashing v33e, Multirom manager says I'm running v33b... Is that normal?
Click to expand...
Click to collapse
Yes, it's because it's pointing to @nkk71's repo, and it's also using his changelog I believe. I'll have to review, but manual installation is best for now. What the app is most useful for right now is managing your ROMs...
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS
Thank you for this! Will try tomorrow.
Ah man this is dope. Thank you bud!!!
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log
EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com
Anyone tested it with stock OOS13?
der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com
tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.
der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser