Develop Bugs

[MOD][2014-01-19][Pre-Alpha Test] Use multiple ROMs: MultiROM Xperia M

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]☆ ★

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

TeamWin Recovery Project v2.8.7.0

Latest TWRP version for Optimus G [E975/F180X]
What is new in 2.8.7.0:
Code:
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)
Download:
TWRP v2.8.7.0
How to install:
Code:
- turn your phone into bootloader mode
- connect phone with pc
- using fastboot flash recovery "fastboot flash recovery recovery.img"
- reboot
Screenshot:
Credits:
Omni Team
Kevinjoa
XDA:DevDB Information
TW, Tool/Utility for the LG Optimus G
Contributors
DevSwift1
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Beta
Created 2015-07-18
Last Updated 2015-07-18

good job

Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...

M.M.K said:
Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...
Click to expand...
Click to collapse
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working

DevSwift1 said:
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working
Click to expand...
Click to collapse
Actually I have used your twrp. But only with reboot to recovery through running os!
Then it wont perform factory reset. But what if I get bootloop?anytime? Kdz...
I mean thats how G3 users enter to twrp! But we cant!
I hoped you could fix it Please try
Thank you anyway. I'm gonna flash your perfect rom with unlocked boot loader

Try Jollaman twrp.
Also Jollaman twrp is multirom compatible.
Enviado do meu Optimus G através de Tapatalk

Hey im new to this how i install this i used before to unlock boot via freegee?

the download link is broken

mi_guel69 said:
the download link is broken
Click to expand...
Click to collapse
Flashable zip - dont remember who made it sorry
http://www.multiupfile.com/f/02f8982a

Pls, fix link at the top. Thx

this is very old now... use this https://mirrors.c0urier.net/?dir=android/Dadi11/TWRP

[RECOVERY][UNOFFICIAL]TWRP 3.1.0-0 touch recovery For LG G3(D851)-Only [2017-03-16]

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.
SCREENSHOT IS IN ATTACHMENT
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_b...863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
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!
DOWNLOAD:
Download TWRP for D851 from here : twrp-3.1.0-0-D851-Unofficial.img
TWRP MATERIAL THEMES :
here => https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584​
CREDIT :
TeamWin Recovery Project
Android Matrix Development [https://web.facebook.com/groups/1024872487548231/]
Obaid Muneer
Nickron Davis
Sandeep Sethi
DroidPeepz_Inc.

Seems to work okay but when I try to use aroma I get a reboot.

cidxtc said:
Seems to work okay but when I try to use aroma I get a reboot.
Click to expand...
Click to collapse
Okay, I will look into it.
Thanks for notifying me

iykeDROID™ said:
Okay, I will look into it.
Thanks for notifying me
Click to expand...
Click to collapse
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.

cidxtc said:
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.
Click to expand...
Click to collapse
If you don't mind, can you upload that older cm14 kernel?
Thanks

iykeDROID™ said:
If you don't mind, can you upload that older cm14 kernel?
Thanks
Click to expand...
Click to collapse
Everything is on my pc which is dead right now.

cidxtc said:
Everything is on my pc which is dead right now.
Click to expand...
Click to collapse
Sorry about that bro.
Anyway i still try my best

error
Installed but does not start recovery

flako72 said:
Installed but does not start recovery
Click to expand...
Click to collapse
please make sure device is D851

iykeDROID™ said:
please make sure device is D851
Click to expand...
Click to collapse

I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%

RockNRoll Mullet said:
I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%
Click to expand...
Click to collapse
Do you have any recovery installed?

No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.

RockNRoll Mullet said:
No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.
Click to expand...
Click to collapse
I have used the 3.1 twrp and had no issues. Not sure what happened but sounds like you might need to restore a stock rom via tot or kdz files and a pc. Then root and flash twrp.
FYI if your restore to stock all files on internal storage will be deleted so backup any pics/files to your pc before restore.

Witch kdz file should I use. Will down grading from RR 7.1.1 to lollipop or marshmallow be a problem? Will lollipop be be easier to reroot?

I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.

iykeDROID™ said:
I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.
Click to expand...
Click to collapse
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.

cidxtc said:
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.
Click to expand...
Click to collapse
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon

iykeDROID™ said:
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon
Click to expand...
Click to collapse
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices

cidxtc said:
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices
Click to expand...
Click to collapse
Thanks.
I compile new kernel for use each time i want to work on it

[TWRP][JOAN][V30/V30+/V30S][UNOFFICIAL] 3.2.3-7 Oreo final

Hi!
!!! First things first: big phat huge !!!THANKS!!! to the full TeamWin Team, SGCMarkus (initial twrp tree), Phoenix591 (for inspiration), Dees Troy (for his trees), z31s1g for his brilliant theme and Captain Throwback (inspiration, too) !!!
For Pie ROMs you should use 3.3.1 recovery, either OrangeFox (based on TWRP with many very useful additions, with Magisk module manager being only one of it :good: ), or good old TWRP itself. 3.3.1 needed for decryption of pie ROMs!​
Feature list:
- capable of installing treble and/or vendorized ROMs
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you have to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings are independent from your encryption settings)
- Time and date is showed correctly, independent of /data
- some extra partitions (see below)
- Oreo 3.2.3-7: compiled with (modified) 8.1 TWRP branch
- Oreo recovery: Decryption of AOSP up to 8.1 and stock ROMs userdata is working (cherrypicked stuff for bringing that up), so, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't there anymore
Pie is not decryptable for the moment, neither with old Oreo recovery nor with newer PIe recovery: this is being worked on. Encryption changed in Pie, this needs some extra "love"
- everything working: backup, restore, decryption, time, mtp, adb, installing of treble or vendorized builds, themeable, .........
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or via diskdump (this already was available but then broken at some point of time, sry for that! ).
- Same for OP image
Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
Also, if you want to restore an older backup, don't restore 'firmware' from it!!! This will break your WLAN, at least, and you have to flash a modem.img to get it back working.
For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a ROM which has encrypted userdata, when you'd installed any other ROM in between. or formatted data There are some points to remember when restoring, a little guide is available in 3rd post, and some tipps too.
Some instructions:
How to flash?
If starting fresh with an unmodified phone, this thread should help you installing it
When you already have TWRP installed, you can flash this recovery from within TWRP:
- Tap "Install"
- Tap "Install image" button, located down right
- Locate your downloaded image and select it
- Select "recovery" from the list which shows up then
- Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
fastboot flash recovery <twrp-image-name.img>
When you experience errors or sth isn't working as it should in your opinion:
When an error occurs, pls supply me a log from TWRP, taken immediately after the error showed up. You can use the "Copy to SDCard" option (advanced options) in TWRP for this. Grab this file then and upload its content to pastebin.org.
I can't help without as much detailed info as you can supply. This should include at least following information: phone model, used TWRP image (exact name of image), task you wanted to do (which ROM e.g.).
There's now an optional version of TWRP available, which contains the inclusion of internal storage in data backups (IntSD version). Exclusions (folders which won't be backed up): TWRP, Movies, Music and Download folders. These won't be included in backups, as they can be really big.
With the recovery including internal storage you can backup to internal and external storage, no matter. The data_image recovery can backup its data image to external sd only, of course.
If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).
DOWNLOADS:
Oreo and Pie capable 3.2.3-7 TWRP:
Download links (always the latest and newest only; one version for all):
File name: TWRP-3.2.3-7-DataIMG.img (default)
MD5sum: aac1525f9bd85d6efbc0fb65bda4a904
MAIN Download: AndroidFileHost - TWRP-3.2.3-7-DataIMG latest
File name: TWRP-3.2.3-7-IntSD.img (non-default, includes main part of internal storage in data backup)
MD5sum: 23113ad33772a5f783dcabd09fa97ebb
MAIN Download: AndroidFileHost - TWRP-3.2.3-7-IntSD latest
Some additional words to different versions;
I personally use internal w/ sdcard backup, all my pics and almost everything possible app related on my phone is on external SDcard. Some data always remains on intSD (e.g. whatsapp, the Android folder which contains settings and app data too, k-9 mail folder and others), this needs to be in a backup for me. This is, what the intSD version does: but it leaves out the big folders (download, music, movie and TWRP).
As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.
All you need to compile this yourself:
[url]https://github.com/seader/android_device_lge_joan-twrp[/url]
[url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
[url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
[url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with encryption cherrypicks and the stuff added. encrypt-8.1 branch = intSD version, master branch = DataIMG version)

Features:
- Treblelized / vendorized: one recovery for all
- Time and date working, getting this from persist partition
- decryption working for both stock and AOSP up to 8.1; Pie is being worked on [break atm ]
- additional partitions available
- "data_image" (default) and "internalSD included" (non-default) available
- Checkbox for leaving out lockscreensettings when restoring data partition (available in main settings and restore settings; in supported themes in main settings only!)
- TWRP app removed
Changelog:
21. April 2019, TWRP 3.3.0-00, new Pie recovery:
- Newest sources used, pie branches everywhere
- tiny menu structure overhaul
- almost all the stuff from Oreo recovery back in, except:
-- decryption
-- data image function
-- inclusion of internal sdcard in backups
-- everything else is working and included (special partitions, time and date working, all the default functions working, exclusion of lockscreen settings when restoring, TWRP su and app removed)
08. Dec. 2018, TWRP 3.2.3-7, old Oreo recovery:
- OP image flashing function added
- Sources update
Older:
09. Nov. 2018:
- treble ROMs are now installable
- brought back modem partition, fully working (remember to NOT restore the "firmware" partition!)
02. Nov. 2018:
- switched from prebuilt kernel to inline kernel building for easier future updates in terms of pie / treble
- removed modem/firmware partition from backup list
- included some QCOM optimizations for buildtime
- excluded TWRP app, install prompt for this app shouldn't pop up anymore (not tested by me)
- disabled logcat
26. Oct. 2018:
- increased compatibility for some scripts / flashable zips
25. Oct. 2018:
- added optional recovery with internal sd content added to data backups (the "data_image" version is the one you already may have installed, like 3.2.3-4-f, just renamed and containing the fstab edits)
- little fstab changes regarding modem / firmware: pls update
18. Oct. 2018:
- removed decrypt files from RAMdisk and added a link to firmware instead
- added possibility to leave out lockscreen-db* files while restoring
- added data_image option; read post #3 pls
15. Oct. 2018
- added decryption of stock and AOSP based ROMs
12. Oct. 2018, pt. 2 (succesful)
- finally fixed the OP mysery... A typo from my side, sry!!
12. Oct. 2018, pt. 1 (failed)
- Added versioning, TWRP now is 3.2.3-1
- re-sorted partitions list
- OP partition won't cause an error anymore on phones where it doesn't exist; sry, didn't know, that US998 doesn't have a OP partition! In addition, it doesn't look for me like there is an equivalent partition on these phones...?
11. Oct. 2018:
- fixed some warnings
- added some additional partitions
- made OP flashable and backupable
- made vendor 'removable', so no warnings anymore for non-vendor devices
- included logcat
- added local_manifest, patch for timefix and a little description in readme
How to (re)boot to TWRP?:
If your phone is rooted:
- Magisk has options to reboot to different targets like bootloader or recovery, but this menu is a little bit hidden: you can access it by starting Magisk.Manager, going to the "Module" menu, tapping on the three dot menu on the top right. Then select your target
- If a terminal emulator is installed, open it, type "su" followed by enter and type "reboot recovery"
- You can do the same with an adb shell, open a shell and type the commands from above, they're the same
- There also are apps for rebooting to recovery or other targets. Just search around in PlayStore
- The good old "button dance" When phone is powered off, press the volume down key and power button at the same time. When a first sign of life is seen on display, immediately release the power button, but just to instantly press it again. A menu will show, which wants you to do a factory reset: do it You have to confirm this two times, and afterwards TWRP will boot without performing a factory reset. TWRP is compiled with a flag which recognizes this procedure and hinders the bootloader to pass the command for factory resetting.

Some additional infos:
- vendor partition: it's there for everyone (no more present in TWRP 3.3!). It is flagged as removable, so it can be leaved in fstab without producing errors. Ppl w/o a vendor partition (which you need to create via script when you want to flash treblelized AOSP builds) shouldn't let themselves get confused about that, it's an additional entry like external sdcard or USB OTG.
- kdzwriter: still untested (and no more present in 3.2, in 3.3 it never was), respectively tested with 21h kdz, which told me "not applicable for this device". I for know mark this as non-working. I'll leave it in this recovery, for future updates and other testers with other kdz file (no more inside).
- data image backup: chose SDCARD for backup location, and enable compression otherwise it's an ~55gb image lol. (<= it IS an 55gb image, no matter of compression. Compression doesn't work for images! So prepare for a huuuge file, and think about your filesystem on sdcard (can it handle big files? For AOSP you can chose ext4 or exfat, for stock exfat only)). This option includes internal sdcard, which is in /data/media. This can be used to do a real full backup with absolutely everything needed (incl. /sdcard/Android folder, your music, vids or anything else e.g.).
- time: when it goes wrong again, just delete the /persist/time folder from within recovery, boot up android and reboot to recovery. Should be "fixed" now. This folder isn't present in 3.3: here you can try to delete "/persist/.twrps" file (you need to re-setup TWRPs settings then) and the folder "/data/vendor/time", followed by a reboot to ROM and then to recovery again. May ned one or two reboots more to ROM or TWRP to get TWRP recognize the time correctly.
Encryption:
There's something you need to remember when restoring encrypted backups, after you have flashed another ROM (which differs from the one to restore): your secure startup settings. Write them down or have them in mind, you need it. Steps for restoring an stock or AOSP data partition encrypted backup:
- format data
- first restore your ROM only partially, means only boot and system (and only that)
- boot into your ROM you've restored
- go through the setup manager and afterwards hop into security and encryption settings
- encrypt your phone exactly the same way it was in your backup you want to restore encrypted userdata from; for 3.3 recovery it's only needed to set up any encryption config, you can put in what you want for yourpin / pattern / passwd
- if it is encrypted already, you only have to redo security settings. Use the same settings as in the backup, means pin/pattern/pw need to be the same *and* secure startup too, if you've chosen it before (see above for pie and 3.3 recovery: you can use anything. Youcan try this with oreo too, maybe it works too)
- reboot to recovery again and restore your encrypted data partition (from the backup you've already restored system and boot from)
- now you're good to go You should tick "Don't restore lockscreen settings" for leaving out the lockscreen.db* files. Otherwise you have to delete them manually to be able to get into your ROM, because lockscreen settings will prevent it. Lockscreen settings btw. are independent of encryption settings. It's the same pattern/pin/pw used, but another building site.
If you want to encrypt your AOSP ROMs userdata (only possible if you are on android up to 8.1), you can use the attached fstab file (it's for LOS 15.1 non treble), either as an example or to overwrite the existing one. Have a look at the line which contains "userdata". The fstab file is located in /system/vendor/etc/. Unzip the attachment (it is no flashable zip), put it in the correct location and overwrite the original file. Reboot your phone, then go into security settings, you should now be able to encrypt it.
This TWRP can't handle decryption of AOSP 9.0 encrypted data atm, you need 3.3 TWRP for that. There changed something from 8.1 to 9.0 which means the new stuff needed new recovery, which is included with 3.3 recovery.
Additional stuff:
- Recommended theme (original thread): [THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
Edited versions of this theme, with menu entries added:
Black and Dark theme versions available here. There are two version of each: one showing "incl. internal" and one without, both have the lockscreen settings exclusion checkbox included. You'll now find this menu entry in main settings page only, it was there before too, but there was an additional entry when restoring a backup. This is gone in this theme as it didn't fit the way I wanted it to fit Pick the one you need.
Included storage: version for recovery "IntSD"
Without storage: version for recovery "DataIMG"

can i just update it by flashing it in the twrp 3.2.1-02 treble as img?

seadersn said:
reserved #2
Click to expand...
Click to collapse
What's the difference between the AFH file and Mega file?
Sent from my LG-H932 using XDA Labs

black metallic said:
can i just update it by flashing it in the twrp 3.2.1-02 treble as img?
Click to expand...
Click to collapse
yes, and then reboot to recovery again
TWRP can simply be updated that way.
BROKEN1981 said:
What's the difference between the AFH file and Mega file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Im 99.9% sure thats a mirror, incase AFH is slow again.

SGCMarkus said:
yes, and then reboot to recovery again
TWRP can simply be updated that way.
Im 99.9% sure thats a mirror, incase AFH is slow again.
Click to expand...
Click to collapse
I figured as much. I had a night that AFH wanted 3 hours to download TWRP. A Google speed test gave me 78mbps.
So yeah, seems Mega is the way to go
Sent from my LG-H932 using XDA Labs

First, thanks for this. Second, what's the difference b/w the earlier "tfp" img and this "tfp-kdz" img?

joarce said:
First, thanks for this. Second, what's the difference b/w the earlier "tfp" img and this "tfp-kdz" img?
Click to expand...
Click to collapse
Stated in op. This image allows for writing of some stuff from kdz files.
Sent from my LG-US998 using Tapatalk

jip, thx

SGCMarkus said:
yes, and then reboot to recovery again
TWRP can simply be updated that way.
Im 99.9% sure thats a mirror, incase AFH is slow again.
Click to expand...
Click to collapse
cool, can i still use treble and wipe tge vendor?

I don't know if I understand it correctly. Pls correct me If I'm wrong.
The benefit of KDZ Writer is that we can update system from KDZ in TWRP.

Thanks will try this

Running it now (H932). Thank you.

seadersn said:
So, here it is: a new (the third for v30...?) thread for an already existing recovery.
Click to expand...
Click to collapse
Actually the 4th, but thank you!
First one was "H930" (which confused US998 users when they got bootloader unlock and root), 2nd one was for "US998" to counteract the H930 confusion -- but really should have been "V30" or "JOAN". @SGCMarkus then made one which not only was Oreo compatible but was "unified". Now this is 4th.
The unification thing is important. I saw over in Moto Quark threads (Droid Turbo, Moto Maxx, Moto Turbo -- all the same phone) where one initial forum was split into two because Droid Turbo at first didn't have bootloader unlock and root, the OTHER Quarks (Moto Maxx, Moto Turbo) jumped ahead in development. Then a year later when Droid Turbo got bootloader unlock and root, thanks to Sunshine, the CM dev at the time generously modified his kernel to include Droid Turbo (which was in a different "dead" forum by then). Thus all the Quarks were unified in development and could all run the same ROMs, same TWRP.
Whereas with one LG flagship phone (which I can't find right now), starting having split development. TWRP and dedicated ROMs for European (which again got bootloader unlock first, thanks to LG's mysterious ways) but then separate older TWRP and a few ROMs for the North America open market. Maybe that's improved now, which is why I can't find it, but I remember thinking "that's not right" and I didn't want that to happen to the V30.

Is the vendor partition mountable ?
Are trebleized ROMs flashable ?

Thanks for providing the new, current version of TWRP. V30 really needed an update for this. No more incorrect times/dates and Magisk giving an error due to false time/date.

Can you give a quick "dummies " tutorial on how to replace the old twrp with this new version using twrp?
Thx.

gimpy1 said:
Can you give a quick "dummies " tutorial on how to replace the old twrp with this new version using twrp?
Thx.
Click to expand...
Click to collapse
I put the new image on sd card. Booted to current TWRP. Flashed new image to recovery partition. Rebooted to system.
Mine took a few reboots to settle in. Couldn't get to it using reboot manager app. Was getting ready to do button dance, but tried reboot app one more time and it booted me to new TWRP. Everything's great now. I don't know if you're supposed to boot back to recovery after flashing the new image. That's what I didn't do.
Sent from my LG-US998 using Tapatalk

Krekos/CZ/ said:
I don't know if I understand it correctly. Pls correct me If I'm wrong.
The benefit of KDZ Writer is that we can update system from KDZ in TWRP.
Click to expand...
Click to collapse
jep, that's the intention of this tool. have a look at the pic in first post there's more to flash via kdzwriter.
FcBayernMinga said:
Is the vendor partition mountable ?
Are trebleized ROMs flashable ?
Click to expand...
Click to collapse
comes this evening, i need a bit of time for relaxing now, but i don't get it because of kids xD
Ballroomblitz said:
... I don't know if you're supposed to boot back to recovery after flashing the new image. That's what I didn't do.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
jep, this is needed! after flashing of new recovery reboot to recovery. :good: