Develop Bugs

[RECOVERY][nozomi] TWRP 3.0.0-0 touch recovery [2016-02-06]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.

Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?

anychange for locked BL?

Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?

eScapeeXc said:
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
Click to expand...
Click to collapse
You should take a look at the "Download - FOTAKernel Image" header. There's no need to install that stock kernel, you can also just push the recovery. The way described on the website requires you use Terminal Emulator but there's an easier way. (I also don't really understand which is the right version because there is 2.4.3.0 for nozomi and 2.4.3.0 for LT26i and afaik that's the same device).
Just install GooManager on your phone, select "Flash ROMs" and there should be a message asking if you have a custom recovery. Select to install one and the latest version of TWRP will be installed.
I'm using Stock+ kernel, that already had TWRP 2.4.1 recovery, after doing this with GooManager I have TWRP 2.4.3.0. If you're using any of the other .55 kernels it should be work as well.
mrkidvn said:
anychange for locked BL?
Click to expand...
Click to collapse
No idea.
darkerm said:
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
Click to expand...
Click to collapse
That's basically the same question eScapeeXc asked so the answer is the same .

Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app

Will:
dd if=/dev/zero of=/dev/block/mmcblk0p11
remove the recovery?
Is there a way to choose between the recovery from the kernel and this one on fota while booting?
How many space has the fota partition on our device?

algates said:
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
It needs a modified ramdisk. So it will not work.

Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Dees_Troy said:
More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Click to expand...
Click to collapse
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?

twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
Yes.

twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
[email protected] said:
Yes.
Click to expand...
Click to collapse
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.

Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
tosa.th said:
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.
Click to expand...
Click to collapse
I understand that. I am using latest FXP CM10 so it should work right?

i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?

R: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
raydekok said:
i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?
Click to expand...
Click to collapse
I read that FXP official kernel support external recovery from 3-4 release
But maybe raymanfx has not implemented this
Btw that recovery is a crap.. Try advanced stock kernel
Sent from my Xperia S using xda app-developers app

just flash this thru the current recovery?
and install rom again?

twk99 said:
I understand that. I am using latest FXP CM10 so it should work right?
Click to expand...
Click to collapse
I don't use FXP, so I don't know is it support elf extract.
Check with FXP team about their kernel if it does support then you are good to go.

reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?

Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Installing seems ok. But how can I uninstall twrp from fota?
Sent from my LT26i using xda premium

raydekok said:
reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?
Click to expand...
Click to collapse
quote myself. this worked but under mount he can not select mount /system.
under my phone i can. what would that be?

★ ☆[Recovery][Mod][Multi-Boot] MultiROM V22 | m7vzw [Unofficial][03-16-14]☆ ★

★ ☆[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 ？

[MOD][APR 20][Moto X Play] MultiROM v33 [No Kexec Workaround]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto X Play. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.​
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch.
MultiROM (multirom-YYYYMMDD-vXX-lux-signed.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/multirom-lux/multirom (branch master)
Device Tree - https://github.com/Multirom-Lux/android_device_motorola_lux/tree/twrp-precommon​
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
​

Downloads
1. Main downloads
MultiROM: https://www.androidfilehost.com/?fid=745425885120704569
Modified recovery (based on TWRP): https://www.androidfilehost.com/?fid=529152257862699607
Multirom Uninstaller: https://www.androidfilehost.com/?fid=745425885120704570​
2. third-party kernels with kexec-hardboot patch (Not needed)​

FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.​
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.​

No-kexec workaround (version 4)
As of this version you need to manually enable the no-kexec workaround.
Actually, depending on the developer, (s)he may have already enabled it. Nonetheless, you can still choose to override the settings:
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.​
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.​
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above​
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support​
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.​
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
​
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the boot partition and names it primary_boot.img
In version 4 of the workaround, this backup is created and used only when booting a secondary ROM. When a secondary ROM is selected it's boot.img is flashed to primary slot, upon booting into the secondary ROM, the primary_boot.img is restored.
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a normal second boot but with the secondary boot.img in the real boot partition
MultiROM restores the primary_boot.img and continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
Moto G 2015 by @GtrCraft
Moto X Play by @GtrCraft
OnePlus One (starting here) by @KINGbabasula
OnePlus 3 by @martinusbe
OnePlus X by @martinusbe ... (alpha status)
Sony Xperia Z5 by @Myself5
Sony Xperia L by @STRYDER~007
Sony Xperia SP by @Adrian DC
Xiaomi Redmi 2 by @premaca
.
(possibly Samsung Note 4, unsure if that was continued or not)
Others; unofficial builds? (if you are, kindly let me know, and I'll add you to the list)

Credits to:
@premaca (For helping with bringup)
@squid2 (For TWRP trees)
@Hashbang173 (Guiding me with no kexec workaround)
@nkk71 (For kexec workaround)

Successfully booted from RR to xosp by using multirom. But multi ROM manager app not working. When I reboot , I can change to secondary ROM .VERY VERY THANKS FOR THIS MULTIROM. You've done a great work.

drmuruga said:
Successfully booted from RR to xosp by using multirom. But multi ROM manager app not working. When I reboot , I can change to secondary ROM .VERY VERY THANKS FOR THIS MULTIROM. You've done a great work.
Click to expand...
Click to collapse
Multirom app doesn't work for Moto X Play

What are the roms can be used in multirom?
All m x play roms or cm based or aosp based, any specificity? ( sorry for my english)

drmuruga said:
What are the roms can be used in multirom?
All m x play roms or cm based or aosp based, any specificity? ( sorry for my english)
Click to expand...
Click to collapse
Any rom, as long as you use the no kexec workaround
Sent from my XT1562 using XDA Labs

GtrCraft said:
Enabling no-kexec workaround
Click to expand...
Click to collapse
Great work :good:
May I recommend possibly linking to the original post, because
(1) it's incomplete... but should do for the moment (yeah, it's a sloppy write up, but better than nothing)
(2) once certain things are updated, a copy/paste wont include them
Glad it's working for you, and if it is working properly, then perhaps i need to add it to that post
Happy MultiROM-ing

nkk71 said:
Great work :good:
May I recommend possibly linking to the original post, because
(1) it's incomplete... but should do for the moment (yeah, it's a sloppy write up, but better than nothing)
(2) once certain things are updated, a copy/paste wont include them
Glad it's working for you, and if it is working properly, then perhaps i need to add it to that post
Happy MultiROM-ing
Click to expand...
Click to collapse
Please tell where I will find the correst post. And yes everythibg is working perfectly. No lingering boot.img or broken boots
Sent from my XT1562 using XDA Labs

GtrCraft said:
Please tell where I will find the correst post. And yes everythibg is working perfectly. No lingering boot.img or broken boots
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
No worries, the original no-kexec-workaround info is still here http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
If I update any information, it will still most likely be there (unless I end up doing on the HTC 10)
(in which case i would update the info)
post updated to include Moto X Play, nice work :good::good:
lingering boot.img was deprecated btw, there are other ways to "break" things.... but it's a lot more difficult now

After installing Multiboot system ringtone volume shoot up to high at beginning later it comes down to normal value.
Has anyone faced this issue. I tested it in two Rom and confirm it. The issue is noted on internal ROM. @GtrlCraft
Sent from my XT1562 using Tapatalk

b00tbu9 said:
After installing Multiboot system ringtone volume shoot up to high at beginning later it comes down to normal value.
Has anyone faced this issue. I tested it in two Rom and confirm it. The issue is noted on internal ROM. @GtrlCraft
Click to expand...
Click to collapse
What?
Sent from my XT1562 using XDA Labs

I have tested it in Stock Rom as well as in another rom. This issue is seen when I boot into internal ROM.
When any alert -message or phone ring.
First ring is way too louder then gradually sound become normal. The sound is so loud that I think the speaker would die
@GtrCraft

b00tbu9 said:
I have tested it in Stock Rom as well as in another rom. This issue is seen when I boot into internal ROM.
When any alert -message or phone ring.
First ring is way too louder then gradually sound become normal. The sound is so loud that I think the speaker would die
@GtrCraft
Click to expand...
Click to collapse
That is not a multirom issue, never seens that happening anyway

I have tested it on stock ROM...
Sent from my XT1562 using Tapatalk

logcat of ring - Stock
Hi,
Please find logcat at http://pastebin.com/PuZfHb4q
@nkk71

b00tbu9 said:
Hi,
Please find logcat at http://pastebin.com/PuZfHb4q
@nkk71
Click to expand...
Click to collapse
dunno what i'm looking for / at,
but have you confirmed:
booting that particular ROM
flashed with MultiROM TWRP
but not injected does not produce this issue?
.
booting that particular ROM as a secondary slot also does not produce this issue?

nkk71 said:
dunno what i'm looking for / at,
but have you confirmed:
booting that particular ROM
flashed with MultiROM TWRP
but not injected does not produce this issue?
.
booting that particular ROM as a secondary slot also does not produce this issue?
Click to expand...
Click to collapse
Booting a ROM from multi Rom twrp with out injected does not produce any issue. Second ROM on MultiRom does not have the issue...
I tried Stock Moto as well as another Rom as primary in both the case high volume issue is noted.
Sent from my XT1562 using Tapatalk

[MOD][OPO] MultiROM v33e [WIP-TESTING][NOUGAT]

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

[TOOL] DualSix - Dual Boot for OnePlus6/6T [25.03.20]

DualSix - Dual Boot for OnePlus 6!
Before You go further, keep in mind that it's mostly recommended for advanced users! And those who can calmly read instructions, preferably twice!
What does this tool do? And what are the benefits? DualSix allows You to boot two ROMs at the same time! You can flash OOS on one slot and AOSP on another or MIUI or GSI etc. How awesome is that? It also gives You as secure virtual mSD Card that will never get encrypted so Your files will be always safe!
How is this Tool different compared to Zackptg5 version for OP7 Pro? Well.. let's be honest.. he's a great Developer and his skills in making scripts and other stuff are a lot better than mine so his version of Dual Boot is definitely better but since he doesn't have OnePlus6 and 7 Pro received great feedback + people wanted me to resurrect DualSix which I made 2 months ago, I decided to finish the project and release it. It will most likely be the last "big project" for this device before 8 Pro.
Now short Q&A:
Q: Can I use on mido, raphael, x00td, vince etc?
A: No! Only use it on OnePlus6 and 6T.
Q: Can I use it with EPR?
A: No. You can't use them on top of each other.
Q: What ROMs does it support?
A: Ports (soon), AOSP ROMs and GSIs.
Known Issues
Storage Settings in ROMs might report incorrect storage size
Currently only 128GB is supported
Shared Storage is sadly only accessible by using any root explorer (/data/media/0/SharedStorage)
This directory is accessible in TWRP as Micro SD Card (keep important files there)
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
MAKE SURE YOU HAVE LATEST OPEN BETA / OOS STABLE IN BOTH SLOTS!
Also make sure You're not currently using EPR!
It is recommended for You to keep most important files in Shared Storage / MicroSD Card.
It won't get corrupted if something goes wrong.
If You mess up and end up without DualSix TWRP. You can also use Emergency DualSix TWRP from Emergency files!
1. Run RUN_BEFORE_DUALSIX.bat/sh in Fastboot Menu.
2. Boot into TWRP of Your choice.
3. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6.zip
4. Flash Dual Six for Your storage
5. Reboot into recovery
6. Format all new partitions (Data A, Data B, Shared Storage/MicroSD Card)
7. Reboot recovery again, confirm that new TWRP log shows no red error messages
8. Now follow ROM specific guide below
-------- Ports ---------
Because ports are slightly more difficult to patch
Future ports will come with separate DualSix flasher.
REMEMBER. FORCE WIPE ONLY WIPES CURRENT SLOT.
YOUR SECONDARY ROM WILL BE FINE.
--- Once that happens follow ---
1. From fastboot, run flasher.
2. Most flashers auto reboot, if that happens, just boot into TWRP (even if You see boot animation))
3. Now when You're in TWRP, copy Dual Six ROM Patcher to Your MicroSD Card Storage
4. Flash Dual Six ROM Patcher
5. Done! Now reboot into the ROM and once it boots, You can root.
------- AOSP ROMs / GSIs --------
1. Flash AOSP_ROM_NAME.zip
2. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6/op6T.zip
3. Reboot Recovery
4. Flash Dual Six ROM Patcher
5. Flash GApps (if needed)
6. Reboot and enjoy!
Note: if AOSP ROM / GSI stays on boot animation for longer than 10 minutes, flash a permissiver.zip.
You should apply same guide for both slots.
Download:
DualSix v1.1 - Mar25
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to support this and other projects, buy me a coffee!
https://www.paypal.me/protodevnano
Credits
MounirHero - for 6T support
eng.stk - for his amazing TWRP
CosmicDan - for his sgdisk guide that helped me with EPR and DualSix
My group for motivating me to resurrect this project!
OnePlus for creating this amazing phone!
​
XDA:DevDB Information
DualSix - DUAL BOOT for OnePlus6 & 6T, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0, MounirHero
Source Code: https://github.com/engstk/android_device_oneplus_enchilada
Version Information
Status: Stable
Created 2020-03-24
Last Updated 2020-03-24

What a wonderful thing....!
Thanks Jay! Can't wait to try this out!

Awesome!! Well Done Bro... [emoji16]
Sent from my RMX1971 using Tapatalk

Great job Jay, hoping 64gb comes soon! One of your ports on one slot and GSI on the other would be amazing!

DualSix TWRP not flashing or booting, OnePlus 6T
I cannot get the dualsix twrp to flash to my device. In twrp it says device not compatible and aborts the installation. I also cannot boot the emergency twrp image from the emergency files folder in fastboot mode, when I try it boots back to the rom. I have a OnePlus 6T 128GB model. My guess is that the twrp is only for the OnePlus 6 and that's why it's aborting? But the OP mentions it working on both the 6 and the 6T. I have tried with and without running the "RUN_BEFORE_DUALSIX_WINDOWS.bat" beforehand. Not sure what to try now.
edit: nevermind, the link hadn't updated yet when I first downloaded it earlier so I did have the twrp that was only for OnePlus 6, sorry about that

Nice, will try it when I have time

This is what I thought/hoped the stupid A/B partition nonsense was going to be.
NICE!!

Will this wipes all. Internal storage

Can't wait to try this. Awesome work

Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.

That's terrific ! This sounds promising !
I'll try to get OP6 OOS latest OB and Havoc OS 3.3 alongside

Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Edit: Posted a message in my channel where I test ROMs and confirm if they work or not

ProtoDeVNan0 said:
Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Click to expand...
Click to collapse
I need access to your g drive to download

david72262 said:
I need access to your g drive to download
Click to expand...
Click to collapse
Oops. Never happened to me before. But fixed it. Enabled file access for everyone. Not sure why mobile uploads have different sharing options

Awesome man. Great going.

What the f*, I though nobody was gonna attempt to do this !
I'll have to try that

oscarmaldonado said:
Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.
Click to expand...
Click to collapse
I was wondering the same thing

Hi...Thank you very much for this mod.
I am willing to do this but i have a few questions regarding it
1st: after we flash this mod...can we go back to the original partition table and if so...could you explain what files to use and in which order.
2nd: if i want to flash OOS on slot a then my current boot slot would have to be active slot b because roms flash to opposite slots right?
3rd: if i have OOS on slot a and a custom rom on slot b...when i have an update for OOS i must be on active slot b and flash the whole OOS full rom zip and flash all the other files like magisk and recovery and patchers or is it a different way?
4th: can we set a password for slot b's rom or will it brick the device like the 7/7Pro' guide section?
5th: does the shared storage have a fixed size or is it dynamic...and if so, if we put photos and media there will the normal apps like gallery and music players be able to access them at all?!
6th: do we have to stay unencrypted?
7th: if we want to flash magisk to slot a....does our active slot has to be slot a or slot b?
8th: if i want to change rom on slot b...then what do i have to wipe to be able to clean install the rom i want?
i know i asked a lot of questions and some may be stupid but i would really like to try this with all the knowledge beforehand so i dont get myself into a perma-brick like the guys over at 7/7Pro's section
Thanks again for this mod and i hope you reply soon .

joepas said:
I was wondering the same thing
Click to expand...
Click to collapse
I tried, I couldn't get it to boot so I was able to revert it back by running DualSix Remover 128GB.zip in the same folder, reformatted everything and reinstalled OOS.

need help
can anybody tell me for certain how bad i just wrecked my phone. So I was on step 4. Flash Dual Six for Your storage, and after it flashed i hit the restart button on accident. My phone was stuck in the op6 3 dot bootloop. Then i might have put the nail in the coffin by fastboot flashing the images out of the 9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip. I’m pretty sure im autistic can anyone help me fix my phone?