[BOOTLOADER][SAFEBOOT] Ouya Bootmenu (mlq)

[BOOTLOADER][SAFEBOOT] Ouya Bootmenu (mlq) - Ouya Android Development

Thanks/Credits
Click to expand...
Click to collapse
Hal9k - for the inital ouya bootmenu and many great ideas
Dan Pasanen (invisiblek) - for great work on the recovery and initial porting efforts
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod (general) or #cyanogenmod-dev (only dev related talk) on freenode

alright so i installed it, and normal boot boots back into recovery

YoshiFan501 said:
alright so i installed it, and normal boot boots back into recovery
Click to expand...
Click to collapse
This bootmenu is flashed over your current bootimage (you will need to relocate your kernel (to /system/boot.img) if you not using a custom rom)
Click to expand...
Click to collapse
most probably because /system/boot.img is not found. you need to install cyanogenmod afterwards or relocate your bootimage if still on stock.

Is it possible to easily revert the Ouya to a fully stock state after this? Any unninstall method?

Fyi everyone, if you scroll down through the options in cmw a couple times you'll activate rainbow mode! I'm not sure if this is an ouya specific cmw mod or not cuz all my other devices have twrp but anywho ENJOY!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Is it possible to use this bootloader with the EternityProject Kernel 3.4.37 for OUYA and the OUYA-Enhanced Rom. I can flash the ROM from within Recovery, but how do I install their kernel for it to boot in ouya bootmenu? I just don't want to brick, thanks for your help!

Just wanted to be the first to tell you that it's working fine and I'm glad to finally give the ouya what it deserves: a custom ROM! Thanks dude!

Can someone post a step by step to move from ep bootlegger to this one?

So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.

new version
new version is available in the first post

firmtech said:
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
Click to expand...
Click to collapse
update the bootmenu to v2.0.2 and rename your alternate bootimage on /sdcard to "altboot.img" and you should be ready to go

milaq thanks for excellent work....
Can you add reboot recovery options in Ouya Failsafe menu to get the full recovery menu?
The power button(for choices) works only if ouya connected-hdmi to hdmi
If Ouya connected hdmi to dvi(Pc monitor) the power button does not respond!
So to go into recovery mode, you can use alt + printScn (SysRq) + i (if keyboard connected)
But now the Ouya goes into a Failsafe menu.

version bump again
krest said:
the power button does not respond!
Click to expand...
Click to collapse
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.

milaq said:
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
Click to expand...
Click to collapse
Yes, you're right....
Now it's working perfectly
In any case, it would be great if you added the reboot recovery options in Ouya Failsafe menu.
Thanks

Dual Boot
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again? Must restore balance in the household. The natives are demanding to have Amazing Frog back!

bootmenu v2.0.4
new version up.
see first post for details.
KJRob said:
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again?
Click to expand...
Click to collapse
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.

milaq said:
new version up.
see first post for details.
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
I appreciate the reply. I would love to have the know how to do the work but that is out of my knowledge base. Maybe one day I will. I can wait for the official Ouya store to hit android. The kids will have to wait as well. I love my KK device just the way it is.

milaq said:
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
It's doable but once its done both sides of the roms would have significant storage reduction... on another note the method would be completely ( and easily ) reversible to the actual installed rom.
The other route is like you said with usb storage which would probably be the better of the 2 options.
Although with all this said we know that the ouya storefront is coming in the form of an app and I guess the other option would be to "portablize" the current framework ( I did it with 519... could try with the latest one... but I never tried it on anything higher than 4.3 )

How do you revert back to factory settings? Every time I flash stock, it boots to this. Thanks and sorry in advance

Related

[MOD][Z2] MultiROM v33d

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
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.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Install the MultiRom Manager app from the store and install the recovery and multirom.
Reboot into MultiROM TWRP and flash the MultiROM installer --> Sould be done automatically.
Make sure you are on a Rom compatible with one of these kernels and flash it
In order to boot a secondary rom you MUST enable the "kexec workaround" option in the MultiRom settings found in the recovery.
That's it. You can now go to "MultiROM menu" (Top right corner in the recovery) to start flashing other ROMs.
Alternative installation method (if installation via the above method fails)
Download the files named multirom-<date>.zip and recovery-<date>.img from here.
You should use md5sum to validate the downloaded files using the provided xyz.md5 files in the same download location.
Copy the files to the sdcard of your device.
Use "adb shell" to open a shell on the device and use "su" to obtain root rights (adb must be set up on your computer, instructions are found on xda).
Adjust the following command and enter it in the shell: "dd if=/sdcard/recovery-<date>.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
Reboot into recovery (shutdown, then VolDown + Power).
Flash the multirom zip from the sdcard.
Enjoy.
Adding ROMs
Go to recovery, select "MultiROM menu" (Top right corner in the recovery) -> Add ROM. Select the ROM's zip file and confirm.
Using USB 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 "MultiROM menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to "MultiROM menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Install a stock rom as secondary
This only works if you are using MultiRom version 33c or larger (excluding 33x-z).
1. Existing primary stock rom
Use these instructions if you plan to move an existing stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
MAKE A BACKUP!
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
2. Fresh stock installation
Use these instructions if you do not have a stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
MAKE A BACKUP!
Install the stock rom via an install zip of via an FTF. NOTE: For the FTF method you need to shutdown the device and boot into download mode (VolDown pressed while connecting the USB cable; cable connected to the PC). Use for instance flashtool to flash ONLY the kernel, system, and cache image. In addition, you MUST select "Wipe apps_log"!
When the device reboots, let it boot up and finish the first time setup procedure.
Shutdown the device.
Start the device into multirom recovery (VolDown + Power).
Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
Select the option "Copy primary rom to secondary/internal" and start the operation.
Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
Reboot.
CHANGELOG
Code:
=== Version 33d (Bugfix release) ===
- Fix the apps_log issue for good (FINALLY).
- Support for LOS in combination with stock.
=== Version 33c ===
- Sync with XperiaMultiRom repository: cleaner implementation of some patches & extends the rom support w.r.t. old builds.
- Improved compatibility of custom N roms (AOSP init system) with stock roms: Allows to use stock roms as secondary rom.
- Bug fix: Set the version number in the Mrom binaries (for automatic updates).
=== Version 33b ===
- Small maintenance update to support "embedded/combined ramdisks" of secondary roms.
=== Version 33a ===
- Fixed booting Stock after starting secondary N rom.
=== Version 33z ===
- Fixed boot image injection of stock roms.
=== Version 33y ===
- New nokexec version 4 (previous: version 2).
- Support for AOSP 1.3.3 kernels (1.2.2 based kernels are also supported).
- Support for Android N (>= 7.0).
- Support for Sony Z2 stock roms as primary rom (I am investigating the installation as a secondary rom: it's installing, but not yet booting).
=== Version 33x ===
- Update Multirom from version 32 to 33.
- Update Multirom TWRP from version 2.8.7.0 to 3.0.2.
Detailed Xperia-Multirom Changelog
MultiRom
MultiRom Recovery
General Multirom Changelog
To be found here.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)
FAQs can be found here.
CREDITs
Tasssadar
Myself5
AdrainDC
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
I do not accept donations. But you may consider donation to Myself5 who did the original port, or to Tassadar who envisioned Multirom and did most of the implementation. We just jumped on the rolling train
Myself5:
Tassadar:
Thanks a lot to those who have donated!
XDA:DevDB Information
MultiROM for Sony Xperia Z2, Tool/Utility for the Sony Xperia Z2
Contributors
Myself5, Diewi
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2015-01-13
Last Updated 2018-01-23

DOWNLOAD
I still need to fix touch inside the MultiROM menu, for now you need to use the volume buttons to navigate.
https://diewald-net.com/files/public/MultiRom/sirius
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.

Reserved
General Informations about Kexec are coming here soon.

Multi-Rom Random Post
Random Reserve Post

This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.

gamer649 said:
This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.
Click to expand...
Click to collapse
CM12 needs to be the host rom
after that you can install all you want

gamer649 said:
This is some real good progress in the Z2 development. When I'm not using the XDA One app I'll properly check out this thread. Thank you so much for this. I'll throw a donation your way at the end of the month.
EDIT:
Personally I think the installation instructions are a little bit ambiguous. Or is that your aim for this early in development?
Like in step one, I am assuming you need to be on an L ROM running your L kernel?
Is the multiROM TWRP embedded into your kernel?
The multiROM installer is the file multirom-20150113-v30x-UNOFFICIAL-sirius.zip, correct?
When do we need to flash the recovery.img you have provided?
Are the files under the KK/ directory needed yet?
Sorry for all the questions, I'm curious and want to try this but I don't wanna make any errors in the installation.
Click to expand...
Click to collapse
you need to flash the recovery.img to the FotaKernel Partition. ATM my M5-Kernel-V2-L is the only host kernel supported (therefore you need to be on CM12 as the Hostrom), more are yet to come (I work on a KK host kernel already and @AndroPlus Kernel is going to get supported soon too). The KK folder is not needed ATM, you just need M5 Kernel, the recovery.img flashed to FOTAKernel (see Recovery Collection Thread on how to do this) and then just flash the multirom*.zip and you are ready to go.

Hi Myself5, thanks for making multiboot rom for Z2, i always wanted to try something like this but my bootloader is "unlock allowed: no" is there any hope to run this on a locked bootloader / stock kernel or should i just complety forget about multiboot forever ??
Thanks for the work.

ptmaniac said:
Hi Myself5, thanks for making multiboot rom for Z2, i always wanted to try something like this but my bootloader is "unlock allowed: no" is there any hope to run this on a locked bootloader / stock kernel or should i just complety forget about multiboot forever ??
Thanks for the work.
Click to expand...
Click to collapse
MR needs a kexec-hardboot patched Kernel to load any other rom's kernel. However, as you can't flash any modified kernel I guess this is not possible for you. Sorry for that.

Hi and thanks for this beautiful feature. But I have a problem: I am on stock ROM 4.4.2 . Can I install a second ROM with a MultiROM remain on stock?

dalla96 said:
Hi and thanks for this beautiful feature. But I have a problem: I am on stock ROM 4.4.2 . Can I install a second ROM with a MultiROM remain on stock?
Click to expand...
Click to collapse
not yet. You need a MR compatible Host Kernel (it needs kexec-hardboot). Till now only my M5 Kernel for CM has it. Wait some weeks, I'm working with @AndroPlus to get kexec-hardboot going withAndroPlus Kernel

Double Post. Credits @tapatalk ...

Myself5 said:
not yet. You need a MR compatible Host Kernel (it needs kexec-hardboot). Till now only my M5 Kernel for CM has it. Wait some weeks, I'm working with @AndroPlus to get kexec-hardboot going withAndroPlus Kernel
Click to expand...
Click to collapse
OK thanks you very much

Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.

dkionline said:
Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.
Click to expand...
Click to collapse
no?
just install supported kernel, mod and the custom recovery.img

Just like all recoverys, otg stick doesn't mount... Please use Nut's recovery TWRP as base, that works ever. Is it normal that I can't touch anything really when the MultiRom Menu comes while booting?

Heyyy came across this and its awesome!!! So currently this mod works only for CM-based? Can I use a cm12 as a main and envi rom as my 2nd rom? D:laugh:
EDIT: Actually I tried flashing envi rom but it couldn't boot. My orginal CM12 rom boots fine though. Maybe I'm missing something. Do I need to flash kernels to the rom?

TheFerhatKing said:
Just like all recoverys, otg stick doesn't mount... Please use Nut's recovery TWRP as base, that works ever. Is it normal that I can't touch anything really when the MultiRom Menu comes while booting?
Click to expand...
Click to collapse
... Both your questions would be answered if you would have red the OP. I use @[NUT]s Device trees for TWRP already don't know why OTG is not working for you. A recovery log would be cool (After attaching the USB use adb to get it by using the command)
Code:
adb pull /tmp/recovery.log
The touch, as clearly written above the download link, is not yet working, I still need to fix this.
earthtk said:
Heyyy so currently this mod works only for CM-based? Can I use a cm12 as a main and envi rom as my 2nd rom?:laugh:
Click to expand...
Click to collapse
No as AndroPlus Kernel now has kexec-hardboot too you can use either stock or CM12/based (I'm working on a CM11 compatible Kernel) as the host Rom and any Z2 Rom you want as secondary Rom this is because secondary Roms need no patching (exept whats done when installing my MR itself) so you can use any Rom you want.
dkionline said:
Are we Need to mod the ROM for that? Are that only work with Z2 ROMs?
I would test it soon as possible with androkernel.
Click to expand...
Click to collapse
as you can read above, you only need to mod the host Rom (the Rom which is actually installed to the place it "belongs to") by installing a kexec-hardboot compatible kernel. And yes, OFC it does only work with Z2 Roms, this Mod is just for booting a Rom from a different place, not to magically make every Rom compatible with the Z2

I had read the whole op but not what was written over the download link sorry . But I didn't found where you said that you used Nuts device trees. I'm gonna do a log for you

TheFerhatKing said:
I had read the whole op but nut what was written ovet the download link sorry . But I didn't found where you said that you used Nuts device trees. I'm gonna do a log for you
Click to expand...
Click to collapse
Yeah, well you couldn't knew this, thats true Just checked again and discovered that I just mentioned him at the credits, not why. Sorry for that Looking forward to the log

[MOD] Multirom for Shield Portable

Reserved
Downloads
1. Main downloads
MultiROM: multirom-20150801-v32-UNOFFICIAL-roth.zip
Modified recovery (based on TWRP 3.0.0.0): twrp-multirom-20160526-UNOFFICIAL-roth.img
Kernel w/ kexec-hardboot patch (Stock 5.1 update 106) [flashable zip]: roth_kexec_boot_stock_106.zip
Kernel w/ kexec-hardboot patch (Stock 5.1 update 103) [flashable zip]: roth_kexec_boot_stock_103.zip
Kernel w/ kexec-hardboot patch (CM 12.1) [flashable zip]: roth_kexec_boot_cm_12_1.zip
MultiROM Manager: MultiROMMgr-debug.apk
2. third-party kernels with kexec-hardboot patch
None yet
Nicely ask your kernel developer to merge kexec-hardboot patch (patch for roth).

Reserved
Notes
I finally made this work. However, it is still not well tested. Three things to note:
1. The touchscreen does not work in the boot selection. Neither will the d-pad. So, I've had to set Y as up, B as down, and A and power as confirm.
2. The recovery is sideways. This is because that's the native orientation of the display. TWRP 3 no longer has rotation code, so I can't rotate the display to landscape.
Also, I have yet to make a Linux rom boot using this. That's mostly because I haven't got the guest atags patch working on Fedora's kernel (haven't tried and personally don't really care about others). If and when I make it work, I'll try to make an mrom installer for it. Sound and graphics acceleration don't work, but everything else seems really solid. Kudos to @Gnurou for coding as much as he has and getting most of it merged into the upstream kernel.
Changelog
20160526
Updated recovery to TWRP 3
20150905
Updated the Stock 106 zip to include the volume fix.
20150905
Added kexec patch for Stock 106.
20150801
Found problems in the kexec patch. Synced those to match Tassadars hammerhead patch and voila, stuff started working better... CM 12.1 and Stock 103 boot great as secondaries now.
20150723
With the release of official update 103, this seems to work pretty well. Some basic testing with stock as primary didn't show any problems. However, I haven't tested much. I've removed older kexec images since they would just cause problems anyway. I've also added multirom manger, which on a rooted system should set up everything in only a few taps.
20150604
Disabled adb in multirom completely. For some reason this breaks adb/mtp/etc in all roms, primary and secondary. Also, by doing a primary backup and restore to secondary, the stock rom boots as a secondary. Unfortunately, it seems to have all the same problems that it has as primary when multirom is enabled. On the bright side, CM seems to work perfectly fine as primary and secondary now.
20150528
Updated TWRP to latest upstream. Removed exfat-fuse support as well to allow it to fit. This means ROMs cannot be installed to external SDs or usb harddrives formatted as NTFS or exfat. ext2/3/4 and fat32 should work. However, inserting multirom into the stock image still breaks many things, so using multirom is still not recommended. I am hopeful that the eventual android 5.1 update will work better with multirom.
20150423
Updated multirom to fix force close of the play store on stock internal. Didn't work.

Thanks for this! I now have grid gaming AND cm! Again thanks for your work on the shield.

Updated TWRP and Multirom. Still wouldn't call it truly usable, but at least it's workable now. Stock console mode and the play store break when multirom is in use. That's the obvious symptoms. Also noticeable is the internal sd not mounting... I still don't know how to fix it, but it seems part of the init scripts are either failing or plain not running. If you play with this, you'll want to keep a backup of a pristine boot.img around. That's what I'm doing when I want stock for a set top box. But now that adb is working in ROMs, I don't know of any problems using this with CM 12.1. That has me hopeful that if Nvidia ever gets it in gear and releases the update, this will all fall into place.

Tassadar updated the multirom TWRP to 2.8.7.0, so I ran builds. Still waiting on Nvidia before continuing with multirom research and implementation... Build in the second post.

Build updates and a success story. I can boot through the multirom boot menu to stock 103 without problems. I need to do more testing, but it looks like this is safe to use now. However, backup and restore in twrp seems broken with update 103. To the point a restored system will not boot.
Edit: Fixed the backup / restore problem. Link updated. Manager will be updated shortly.
Edit 2: Botched the kexec build apparently. Running a new one now and will update once actually tested this time.
Edit 3: Fixed the kexec kernel. But my previous CM 12.1 build won't boot as a secondary, whereas it did on the old kernel. Will have to debug this.

Does multirom work if the Shield's primary rom is KitKat? (Update 101) I haven't updated to Lollipop.
I noticed you don't have any kexec kernels for KitKat..

Steel01 said:
Introduction
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
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
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-roth.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (twrp-multirom-YYYYMMDD-UNOFFICIAL-roth.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones listed below or third-party kernels which include the patch, you can see list in the second post. Flash it using TWRP.
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.
2. Ubuntu Touch
Not yet ported
3. Firefox OS
Not yet ported, but should be as easy as other Android ports.
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 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 FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/CM-Shield/multirom (branch pad_support)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree https://github.com/CM-Shield/android_device_nvidia_roth (branch cm-12.0-mrom or twrp_min_omni)
Kernel w/ kexec-hardboot patch - https://github.com/CM-Shield/android_kernel_nvidia_roth (branch cm-12.0-mrom-new)
XDA:DevDB Information
Shield Portable Multirom, Tool/Utility for the Nvidia Shield
Contributors
Steel01
Version Information
Status: Testing
Created 2015-04-23
Last Updated 2015-04-23
Click to expand...
Click to collapse
can you check the following tread http://forum.xda-developers.com/showthread.php?p=47964256#post47964256
they have a nice theme and its landscape mode and same resolution of the shield device
thanks

Small update.
Stock 103 boots fine as a secondary (using the copy primary to secondary function). That makes it a lot easier to experiment on the primary without having to flash back to stock anytime I want to do something not dev related.
Stock 101 does *not* currently boot as a secondary. If I set it up as primary, turn on adb, copy to secondary, then try to boot it, the logs show init blowing up all over itself. I have no idea why right now. Also, stock 101 won't work as a primary either, since things like the play store, console mode, and who know what else broke anytime I flashed a kexec kernel.
For some reason, multirom doesn't copy the boot image command line parameters into the secondaries kernel command line. This makes it difficult to disable selinux for porting purposes. I had to recompile the CM kernel with selinux disabled to get it to boot with the new blobs initially.
I expect I'll be able to fix the last point with a bit of research. At that point, dual booting CM and stock 103 should be completely feasible. I'm kinda stumped on the problem with 101, though. And since I don't plan to use it, I probably won't spend much time debugging the problem. If someone wants to look into that, I wouldn't mind helping them get started, though.
Edit:
 @paed808: No, I've removed the old kitkat kexec kernel for reasons stated above. I could boot into CM as a secondary with stock kitkat without problem; however, that broke stock so bad, I considered it unusable.

@Steel01 I just wanted to know just in case I accidentally enable Multirom while flashing a zip in TWRP. I don't want to use Multirom on my Shield Portable. I have a Nexus 7 for that. I just want TWRP, but this is the only TWRP for the NSP. If I accidentally enable Multirom what happens? Does it inject itself in the bootloader? If that fails, will it result in a brick?

paed808 said:
@Steel01 I just wanted to know just in case I accidentally enable Multirom while flashing a zip in TWRP. I don't want to use Multirom on my Shield Portable. I have a Nexus 7 for that. I just want TWRP, but this is the only TWRP for the NSP. If I accidentally enable Multirom what happens? Does it inject itself in the bootloader? If that fails, will it result in a brick?
Click to expand...
Click to collapse
Nah, it's really hard to brick one of these. Trust me, I overwrote the partition table and still was able to recover... (don't try that at home). As long as you don't flash the multirom zip, you won't even be able to access the multirom section inside TWRP and it won't inject itself during any other flashing.
The reason that this is the only truly working (and maintained) recovery on the Portable is because it has the screen rotation code. I couldn't get that to work properly for CWM (and agabren never released his code and won't respond to any contact about it) and upstream TWRP doesn't have it either. So, multirom TWRP is it. But as mentioned above, as long as you don't flash the multirom zip, it should act exactly like the upstream TWRP.
As a fun side note: There are two things that I currently know of that can brick a Shield device (Portable, Tablet, and TV)
1. Overwrite or delete the bootloader. That's the blob partition to fastboot. So yeah, be very careful when fastboot flashing that one.
2. Put something android doesn't recognize in the dtb partition. I actually didn't know this one until recently. The bootloader interacts with this partition during early boot, like before it hands off to boot.img. And apparently, that's the only way the bootloader will read a dtb and hand it off to the kernel. Yeah... so, I've been pretty lucky in my testing that I didn't brick my device by flashing something else there (like an upstream linux version, don't do that).
Interestingly, you can completely obliterate the partition table and the bootloader will still run. However, it won't be able to find the LNX partition to continue booting. But you can fastboot boot whatever you want (like Linux on an sdcard). Moral of the story: Don't let Linux 'fix' your internal GPT for you... You might have to pull favors with other Shield owners to undo that one. Well, I now keep a dd'ed copy of that GPT, just in case.

@Steel01. Thanks for the detailed explanation. Now I know what "blob" and "dtb" are. I thought just the boot.img was the bootloader, as it is on most Android devices.

Alright, I think this is finally ready for prime time. CM 12.1 and Stock 103 should work as primary or secondary without problem. If you see a problem, please report it. If you've got an older version installed, you'll want to reinstall almost everything: multirom, secondaries, kexec, etc. TWRP and the primary rom should be fine as is, though.
I was able to get Stock 101 to boot as a secondary. However, it's still not all there. The internal sd stuff doesn't all mount, causing all kinds of ugly problems, not the least of which is the Play Store crashing. I can manually run 'start sdcard' as root to get /mnt/shell/emulated mounted, but the links under /storage don't come up. At least at that point, the store works and it seems streaming and all that is fine. However, the main internal sd path (/storage/emulated/0) remains empty. So, not really a fully usable setup.
Edit:
Okay, so that was weird. I left my Portable booted into 101 for a bit. When I came back, all the internal sd mounts were correct. Eh? Maybe stuff refreshed after a bit and picked up the sdcard bind mount? Slightly confused, but it seems there is a way to make this work. Will probably look into this more eventually.

Does this break miracast, or is it a problem with lollipop? I edited system/build.prop and added persist.debug.wfd.enable=1 which allowed me to see my miracast adapters but it just disconnects and fails to pair. Running 103 stock rooted with your multimod recovery set up, but only internal stock rom with modified kernel. I can however cast the scrren through netflix app, thats it, hulu doesnt see them and i cant mirror screen. Thanks for any info!
Sent from my SAMSUNG-SM-G900A

the miracast its a problen with lolipop, but for you use the multi rom with last cm you need the shield using the update 103 with is lolipop

Working on my Shield portable using 103 and your CM Rom. Straightforward install but didn't know where to find CM Rom at first. One issue, downloads in CM were not accessible ( message cant open file) but were found in 103 downloads? Did I use wrong patch? Thks

Why an I not getting email updates to this thread... Sorry for the slow response.
Yeah, Google removed miracast support in Lollipop. I've never used screen casting, so I can't comment further than that.
Downloads in CM are not available? Do you mean that CM cannot access the internal SD download folder? If so, is the rest of the internal SD accessible? I'll check tonight when I can get my hands on my Portable.
You want the patch for whatever your internal ROM is. Though technically, you don't even need a primary ROM, that's what I'm have for testing right now. Everything is secondaries. In which case, you can use whatever boot image you want. Wouldn't recommend this for normal usage, though. The Portable is already short on space...

secondary Rom will only read offf of ext sdcard, not internal storage?
Edit: Storage now working. Don't know what changed. Rooted CM with Kingroot. 103 seems snappier than CM.

I was wondering if there was a permissions issue because it worked fine for me. But I'm using the newer cm build from later in the thread and not the stable one in the OP. And... Don't use root methods on CM... It's built in and in the developer options menu.

[MOD][D802] MultiRom V33 [WIP]

Downloads
Flash Order
MultiRom TWRP
Kexec Hardboot patched kernel (CM-13.0 BASED)
Multirom Installer
Click to expand...
Click to collapse
Downloads
MultiROM Installation Files:D802
Click to expand...
Click to collapse
Attention!
Flashing is at your own risk. You can't blame me if you didn't read everything correctly and or ended up getting softbricked.
Click to expand...
Click to collapse
Release only for D802 yet, Support for all G2 variants incoming soon
Click to expand...
Click to collapse

MultiRom status: it boots the second rom but it will eventually bootloop, could also be that I did something wrong or that I must change some variable still. I am trying to logcat it but can't get logcat to work even after editing ramdisk and last_kmsg is always gone so I gotta think of something for that.
Btw. I don't know how it works with loki and my TWRP MultiRom doesn't have extra temperature control and so on like Blastagators twrp has but I can say it's safe to use as I've used it already for sometime and didn't noticed too high temperatures
If someone has some advice or ideas too then he or she is free to be my guest and reply
Also if someone could acquire an logcat from an secondary rom that's also bootlooping that would be nice.
Files are still uploading
EDIT:
It took a bit longer to upload the files as my computer couldn't handle the my virtual machine anymore
Also Mokee comes to optimizing apps screen but then goes back to the boot animation, so that's an good sign

Thanks for this. I Will definitely try this later.

The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.

Wow! You are an hero!
This was the only regret from my previous nexus device!

jneto3000 said:
The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.
Click to expand...
Click to collapse
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:

Is it stable this version? Or is it as the old multirom?

matteo0026 said:
Is it stable this version? Or is it as the old multirom?
Click to expand...
Click to collapse
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low

wulsic said:
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low
Click to expand...
Click to collapse
Thanks! My dream is that i can edit all the partitions size that i can use all the space at the better. (now i can only use adb and edit it with shell)

wulsic said:
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:
Click to expand...
Click to collapse
I did as mentioned by you in the OP:
1. MultiROM TWRP
2. Kexec kernel
3. MultiROM zip
Then I reboot recovery and went to MultiROM option to install a secondary ROM, using Krexus and then XOSP. It says the ROM is installed fine but when I reboot device It boots up directly to primary ROM (which is crDroid).
What am I doing wrong?
I guess this topic would have more attention if it were in Android Development section, people might see this MultiROM topic and think this is the same old topic that already exists and is not working anymore.
Also, about the logcat not working, the only thing I know is about enabling adb on ramdisk, which I did here using Android Image Kitchen (the one you posted is not enabled yet) and replaced boot.img by the new one, but I couldn't test since the MultiROM did not work here yet.

I'm very excited about this multirom. The fact is that if anything goes wrong I might lose something. I still use the g2 as primary phone.
Soon or later I'll try also this mod.
Thanks @op for the effort.

[RECOVERY][OFFICIAL][kagura] TWRP 3.1.1-0 touch recovery [2016-10-08]

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.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
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:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
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
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.
XDA:DevDB Information
[kagura] TWRP 3.1.1-0 touch recovery, Tool/Utility for the Sony Xperia XZ
Contributors
AndroPlus
Source Code: https://github.com/TeamWin/android_device_sony_kagura
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2017-08-28

Now it's official!

Make a material version?
Sent from my F8332 using Tapatalk

Can someone post a detailed instruction please? I followed the TWRP instructions but kept getting stuck on "waiting for devices" on fastboot. I tried several different drivers suggested in other threads but none worked for me

@AndroPlus Do we need an unlocked bootloader for this?

Yes we do.

@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
edit: problem solved I installed your kernel with: sudo fastboot flash boot boot.img
and now I can boot into TWRP and LED during boot shows light. Seems to be a really great kernel.

paulle said:
@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
Click to expand...
Click to collapse
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).

AndroPlus said:
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).
Click to expand...
Click to collapse
Thank you, this method worked too.

@AndroPlus will that work with the dual Sim version F8332 also?

hanaheeno said:
@AndroPlus will that work with the dual Sim version F8332 also?
Click to expand...
Click to collapse
yes

Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?

hanaheeno said:
Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?
Click to expand...
Click to collapse
You have to enable oem unlock in developer options and run "fastboot oem unlock", then flash my custom kernel.
Because of strict security, we have to edit kernel to disable sony_ric and dm-verity to root if you want to custom /system.
If you can use system-less SuperSU you don't need to flash custom kernel.

Restore bug?
I just restored my backup and IMEI was gone. So the backup as such works fine besides the IMEI. Consequently I couldn't connect to the mobile network. I had to flashtool the original rom and restart the whole process.
Anyone else experienced such a problem?

I've repacked the 250 stock kernel with everything (except twrp, indeed). I use your recovery, and it works fine so far. But from system, I can't boot into twrp directly (e. g. from Titanium Backup or NeoPowerMenu).
For any help thanks in advance!

Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks

drakegao said:
Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks
Click to expand...
Click to collapse
See post #13 (3 posts above yours) - doing this does the trick

Klaus N. said:
See post #13 (3 posts above yours) - doing this does the trick
Click to expand...
Click to collapse
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool

drakegao said:
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool
Click to expand...
Click to collapse
Yes, indeed.

No boot in recovery
Problem: Unlock done and OK, flashed TWRP and OK. But I cannot boot in TWRP. Not with buttons, not with adb. I see only the message, that my device is unlocked.... The LED ist dark.
Today I flashed the kernel v4 and Ok, flashed TWRP again and ok, same result. No boot in recovery. Only the f***in message that my device is unlocked, Firmware is..... . 260 and a German xz single Sim.
Any Idea? Sorry for my poor English.

[MOD] MultiROM-20170825-v33c-UNOFFICIAL - TWRP 3.1.1 [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"
}
You use this tool at your own risk!!
I have tried to put as many safeguards as I can,
but I cannot be held accountable for any soft-bricks, hard-bricks, loss of data and/or information,
or anything else going wrong.
Introduction
MultiROM is one-of-a-kind multi-boot mod for Sony Xperia Z2 (Sirius). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
Click to expand...
Click to collapse
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 (actually the no-kexec workaround is messing with your boot sector), but it is possible that something goes wrong and you will have to flash factory images again.
Make backups. Always.
Click to expand...
Click to collapse
Installation
Manual installation
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 2 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-sirius.zip) - download the ZIP file from the download section and flash it in recovery.
Modified recovery (TWRP_multirom_sirius_YYYYMMDD.img) - download the IMG file from the download section and flash it in recovery.
Your current rom will not be erased by the installation.
Click to expand...
Click to collapse
Downloads
multirom-sirius
Click to expand...
Click to collapse
Stock 23.5.A.1.291 kernel with multirom and FOTArecovery support
Download link
Adding ROMs
1. Android
Go to recovery, enter the MultiROM section of TWRP (by clicking the icon in to top right corner) -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Click to expand...
Click to collapse
2. Ubuntu Touch this is NOT SUPPORTED
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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 the MultiROM section of TWRP (by clicking the icon in to top right corner) 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 the MultiROM section of TWRP (by clicking the icon in to top right corner) -> 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 corresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Source code
MultiROM - https://github.com/mohammad92/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device files - https://github.com/mohammad92/multirom_device_sony_sirius
Click to expand...
Click to collapse
Thanks
* TWRP team
* MultiROM team
* nkk71 for No Kexec Workaround
* AdrianDC
* XperiaMultiROM team
Click to expand...
Click to collapse

FAQ and other notes
Q: MultiROM Menu touch are buggy sometimes?
A1: I got it working by this patch and this modded input type
If you can get much better touch patch then you are a nice guy..
A2: Use volume keys to navigate and power key to select.
Click to expand...
Click to collapse
No-kexec workaround
Q: What is the no-kexec workaround?
A: The no-kexec workaround by nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
More info here
Click to expand...
Click to collapse

Changelog
Code:
MultiROM-20170825-v33c - TWRP 3.1.1-20170825
======================================
* Set default brightness to 200
* TWRP: Enable Sony RIC
MultiROM-20170812-v33c - TWRP 3.1.1-20170812
======================================
* Fix MultiROM Menu touch for Z2
* New implementation to handle external boot
on Ext4 / F2FS MicroSD or USB Drive in order
to allow access to the external storage for media,
through the storage 'external_multirom' path
* Include all recent improvements from TWRP 3.1.1

It`s awsome man ... great job .
أحسنت

Can you give kexec kernel too?

Thank you very much man!
Is there any problem if I want to install different Android versions? I want to keep Miui 8 (6.0.1) and try RR 5.8.4 (7.1.2).
Thanks in advance

itsnie said:
Can you give kexec kernel too?
Click to expand...
Click to collapse
No need for kexec kernel for this to work but I will try.
Adriano-A3 said:
Thank you very much man!
Is there any problem if I want to install different Android versions? I want to keep Miui 8 (6.0.1) and try RR 5.8.4 (7.1.2).
Thanks in advance
Click to expand...
Click to collapse
Not tested, but if there no bootloader change it will work.
I got my z2 few months ago but never tested all things yet as its not my daily device and got it to work on sony stuff as Im a samsung user for long time.

mohammad.afaneh said:
Not tested, but if there no bootloader change it will work.
I got my z2 few months ago but never tested all things yet as its not my daily device and got it to work on sony stuff as Im a samsung user for long time.
Click to expand...
Click to collapse
Ok. So welcome to Z2 space
I'll try and report the result.
=========================
Man I'm trying to install the new TWRP but no success.
If I try by current TWRP 3.0.0-2, only Boot option theres to flash your TWRP. This won't works since the file isn't a kernel. I tried it...
If I try to flash it by fastboot (fastboot flash recovery yourtwrp.img) it flashes but nothing changes, nothing at all.
Must your TWRP to be flashed in FOTA partition using dd commands?
My Z2's history: stock MM .291 > UB > kernel Abricot v8.1 > MIUI 8

Adriano-A3 said:
Ok. So welcome to Z2 space
I'll try and report the result.
=========================
Man I'm trying to install the new TWRP but no success.
If I try by current TWRP 3.0.0-2, only Boot option theres to flash your TWRP. This won't works since the file isn't a kernel. I tried it...
If I try to flash it by fastboot (fastboot flash recovery yourtwrp.img) it flashes but nothing changes, nothing at all.
Must your TWRP to be flashed in FOTA partition using dd commands?
My Z2's history: stock MM .291 > UB > kernel Abricot v8.1 > MIUI 8
Click to expand...
Click to collapse
Will try to make a script to my twrp img into the kernel.
Can you pull and upload the boot.img that contain twrp?

mohammad.afaneh said:
Will try to make a script to my twrp img into the kernel.
Can you pull and upload the boot.img that contain twrp?
Click to expand...
Click to collapse
Of course
Download the sony_abricot_kernel_v8.1.zip and extract sony_abricot_kernel_v8.1.img

mohammad.afaneh said:
No need for kexec kernel for this to work but I will try.
Click to expand...
Click to collapse
Yes i know but no kexec have some bug with this device, if power off from 2nd rom, i can't turn on my phone, i need to hard reset with power and volume up before turning on!
Also your recovery isn't working, simple i can't boot your recovery with key combinations "volume down then power"

itsnie said:
Yes i know but no kexec have some bug with this device, if power off from 2nd rom, i can't turn on my phone, i need to hard reset with power and volume up before turning on!
Also your recovery isn't working, simple i can't boot your recovery with key combinations "volume down then power"
Click to expand...
Click to collapse
Thanks for the feedback will try to fix it soon.

Adriano-A3 said:
Of course
Download the sony_abricot_kernel_v8.1.zip and extract sony_abricot_kernel_v8.1.img
Click to expand...
Click to collapse
Sorry for late response, I have done the script but boot.img size more than 20MB (zImage gzip format) we cant flash it.
Will try to build stock kernel with lzma or another compression soon. Also I need some free time to work on multirom for stock.
You can swap ROMs for now by installing AOSP on primary and stock on secondary.

mohammad.afaneh said:
Sorry for late response, I have done the script but boot.img size more than 20MB (zImage gzip format) we cant flash it.
Will try to build stock kernel with lzma or another compression soon. Also I need some free time to work on multirom for stock.
You can swap ROMs for now by installing AOSP on primary and stock on secondary.
Click to expand...
Click to collapse
I got it
But I prefer to wait your next release
I've been looking for Kali Nethunter and noticed that some flashable zips perform a kind of patch on bootimg. Maybe you get something that help you on your work

MultiROM-20170825-v33c - TWRP 3.1.1-20170825
======================================
* Set default brightness to 200
* TWRP: Enable Sony RIC

Stock 23.5.A.1.291 kernel with multirom and FOTArecovery support
Supports TWRP 3.1.1-20170825 only, link in OP
Download
Source code
android_kernel_sony_23.5.A.1.291
sony_23.5.A.1.291_ramdsik
android_device_sony_common
Thanks
* AdrianDC and sonyxperiadev team for init_sony and keycheck source
* Dees-Troy for extract elf ramdisk source
* pec0ra

Can i install from nougat? I'm using Carbon Xperia by M-Rom now n want stock custom rom for the second rom
Sent from my D6503 using Tapatalk

Database Develop

welcome