Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-hammerhead.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_hammerhead_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Tasssadar/android_kernel_google_msm/tree/android-msm-hammerhead-3.4-kk-r1-kexec
Donations
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
Downloads
1. Main downloads
MultiROM: multirom-20160207-v33-hammerhead.zip
Modified recovery (based on TWRP): TWRP_multirom_hammerhead_20160210.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 4.4): kernel_kexec_hammerhead_440.zip
Kernel w/ kexec-hardboot patch (Stock 4.4.1 and 4.4.2): kernel_kexec_hammerhead_441.zip
Kernel w/ kexec-hardboot patch (Stock 4.4.3 and 4.4.4): kernel_kexec_hammerhead_443.zip
Kernel w/ kexec-hardboot patch (Stock L preview): kernel_kexec_hammerhead_L.zip
Kernel w/ kexec-hardboot patch (Stock 5.0 preview (LPX13D)): kernel_kexec_hammerhead_50_lpx13d.zip
Kernel w/ kexec-hardboot patch (Stock 5.0 and 5.0.1): kernel_kexec_hammerhead_50_final.zip
Kernel w/ kexec-hardboot patch (Stock 5.1): kernel_kexec_hammerhead_510.zip
Kernel w/ kexec-hardboot patch (Stock 5.1.1): kernel_kexec_hammerhead_511-2.zip
Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1): kernel_kexec_hammerhead_601.zip
Kernel w/ kexec-hardboot patch (CM 11 (4.4 - 4.4.2)): kernel_kexec_hammerhead_cm11-9-3d91a2d569.zip
Kernel w/ kexec-hardboot patch (CM 11 (4.4.3 - 4.4.4)): kernel_kexec_hammerhead_cm11-12-7d4eef09ee.zip
Kernel w/ kexec-hardboot patch (CM 12.0): kernel_kexec_hammerhead_cm12-1-10f4294a6b.zip
Kernel w/ kexec-hardboot patch (CM 12.1): kernel_kexec_hammerhead_cm121-01-47b35a93b8.zip
Kernel w/ kexec-hardboot patch (CM 13.0): kernel_kexec_hammerhead_cm13-01-2c39db662.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Mirror: http://d-h.st/users/tassadar
2. third-party kernels with kexec-hardboot patch
franco.Kernel (r21 and newer) - http://forum.xda-developers.com/showthread.php?t=2508284
Chaos - http://forum.xda-developers.com/showthread.php?t=2551441
ElementalX - http://forum.xda-developers.com/showthread.php?t=2519607
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller-hammerhead-2.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
4. Flashable factory images ZIPs
I usually release flashable ZIP files based on new factory images from Google, so that you can have clean stock ROM as a secondary system in MultiROM. They are not rooted, no anything, except for occasional small tweaks to make rooting with SuperSU possible. You can find them in this folder on basketbuild or dev-host.
Changelog
Code:
MultiROM v33
=====================
* Updates for Android 6.0 compatibility
MultiROM v32c
=====================
* Add support for Android M preview (MPZ44Q). SuperSU 2.46 doesn't work on M
and breaks boot - don't flash it!
MultiROM v32b
=====================
* Fix pattern encryption password incorrectly reporting "invalid password"
when the pattern overlaps itself
MultiROM v32a
=====================
* Fix support for separate radio.img with secondary kitkat ROMs
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only, for
AOSP encryption only - does not work with CAF-based CyanogenMod as primary
ROM). See FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstabs
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
MultiROM v27a
=====================
* Fix freezes in the boot manager
* Add support for SailfishOS
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scripts
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25
MultiROM v25
=====================
* Add support for the Android L preview
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22c
=====================
* Fix graphics corruption with some custom kernels
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
[url]http://bit.ly/ut_sharing[/url] for more info.
MultiROM v22a
=====================
* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
MultiROM v22
=====================
* Fix Ubuntu Touch boot taking long time
* Fix Ubuntu Touch freezing on Google logo for some users
MultiROM v21a
=====================
* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
MultiROM v21
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Initial version
Recoveries:
Code:
10.2.2016
=====================
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
9.2.2016
=====================
* Update to TWRP 3.0.0 (big thanks to nkk71 for doing most of the work)
* Use Material theme made by z31s1g - thanks!
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
[url]http://bit.ly/m_su[/url] ) or newer!
30.6.2015
=====================
* Update to TWRP 2.8.7
* Add option to duplicate secondary ROM into "Swap ROMs" section
10.4.2015
=====================
* Fix Ubuntu Touch installation broken in previous update
6.4.2015
=====================
* Fix support for SuperSU 2.47 Beta and higher
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.1.2015
=====================
* Fix "Swap ROMs" feature after the last update
14.1.2015
=====================
* Update to TWRP 2.8.4
* Lots of ZIP compatibility fixes (e.g. for CM 12)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Remove
boot.img" on the List ROMs -> *rom name* page.
12.8.2014 - 1
=====================
* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
version
11.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
27.2.2014
=====================
* Support for system-image based (from the Manager app) Ubuntu Touch
installation
* Fix time in recovery
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
4.2.2014
=====================
* Update to support latest Ubuntu Touch testing builds
* Fix date and time in recovery
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
26.1.2014
=====================
* Fix radio in Ubuntu Touch
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
15.12.2013
=====================
* Initial hammerhead release
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
This looks awesome!!
Sent from My Nexus 5 ?.
Nice job! But why no 3rd-party kernels?
EDIT: I should have read more carefully
Sent from my Nexus 5 using Tapatalk
This looks legit finally multiboot!!
Failed to get root access in multiboot app on cm ROM
Sent from my Nexus 5 using XDA Premium 4 mobile app
I don't see the option to add a zip rom in modified kernel...
Edit : I think I know why, this must be because of my TWRP theme. Will remove it and try, then post a second edit.
Edit 2 : to those who are running a TWRP theme, remove it 'til it gets compatible. Else everything working fine here.
Sent from my Omniromed and Faux kerneled Nexus 5 using Tapatalk
It's like Christmas one week early
Very very nice i waited for this since Nexus4 days. Thx a lot!
Best regards
Craxx
Send from my Nexus 5 with Tapatalk
Thank you for all your hard work !
Envoyé de mon Nexus 7 en utilisant Tapatalk
This goes to show why nexus devices are in a class all of there own.Thanks for this amazing feature.
@franciscofranco already pushed r21 of his kernel with the Kexec-patch included. Nice work!
Sent from my Nexus 5 using Tapatalk
One question... Why do you use a OLD recovery? It is 2.6.3.0 and actual is 2.6.3.4.. Or is only the false version displayed?
Best regards
Craxx
Send from my Nexus 5 with Tapatalk
Excellent! That's what I was looking... now I can check different ROMS. Thank you.
Great to see you here, testing now!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Working fine for me! Thank you so much for this
oh my goodness, i wasn't expecting this coming so early to n5 *-* i used it so much on my ex nexus 4, now gonna use it on my n5!
Sent from my Nexus 5 using XDA Premium 4 mobile app
I asked to merge the Kexec-hardboot patch for Bricked Kernel.
No way.... Been looking for this thread every day for a the last month, can't believe it's here already
What data directories do roms you dual boot share? Does it create a partition for each rom, or do they share app data like if I have nova launcher on two roms will it save changes I make to my homescreen it will change on other roms I have running nova launcher? Or what about general files like DCIM or downloads, will they be consistent?
If this is a dev thread only and there exists a FAQ thread please forward me, I couldn't find one.
{
"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 for the Samsung Galaxy S4 (Qualcomm variants)
Brought to you by AntaresOne
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S4. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card
Warning!
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 (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel - Download the ZIP file and flash it in recovery or keep stock kernel (only for CM11-based ROMs after 6 August 2014 & CM12-based ROMs)
You current rom will not be erased by the installation.
Download links are in the third post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
3. Other systems (once ported to device)
Firefox OS and Sailfish OS are just another Android ROM under MultiROM's point of view, so add them as if it were Android.
Using MicroSD Card
During installation, recovery lets you select install location. 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 MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
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.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- 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 the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Alucard Kernel w/ kexec-hardboot patch - https://github.com/Alucard24/Alucard-Kernel-jfltexx
Googy-Max3 kernel w/ kexec-hardboot patch - https://github.com/googyanas/Googy-Max3-Kernel
Hulk kernel w/ kexec-hardboot patch - https://github.com/Tkkg1994/Hulk-Kernel
Imperium kernel w/ kexec-hardboot patch - https://github.com/Slim80/Imperium_Kernel_TW_4.4.2
KT kernel w/ kexec-hardboot patch - https://github.com/ktoonsez/KT-SGS4
CM11 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-11.0
CM12 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.0
CM12.1 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.1
MultiROM device tree - https://github.com/AntaresOne/multirom_device_samsung_jflte
Big thanks to Tasssadar for this awesome utility.
Thanks a lot to @daveyannihilation for the S4 template.
XDA:DevDB Information
MultiROM, multiboot for Galaxy S4 (Qualcomm variants) (GRUB-like), Tool/Utility for the Samsung Galaxy S4
Contributors
AntaresOne
Version Information
Status: No Longer Updated
Current Stable Version: 20151029-v32b
Stable Release Date: 2014-09-01
Created 2014-09-01
Last Updated 2017-05-19
Changelog
15/6/2015 - v32a
Update after 6 months!! read post #669
Modified TWRP:
Base updated to 2.8.6.0
Sacrificed crypto and embedded SuperSU installer to get an image that fits 10.5MB recovery partition size
Detailed changes here
MultiROM:
Base update to v32
Added support for 5.1.x Lollipop ROMs
Better support for 5.0.x Lollipop ROMs
Detailed changes here
16/12/2014 - v30c
Modified TWRP:
Base updated to 2.8.2.0
Better support for primary/secondary Lollipop ROMs install/update
MultiROM:
Better support for Lollipop-based ROMs
Fixed the ghost update found in previous build
26/11/2014 - v30
Modified TWRP:
Add partial support for block_image_update in secondary ROMs ZIPs (Lollipop's default flashable zip format)
MultiROM:
Assume fstab version 2 by default
Fix klog saving and text size on emergency reboot screen
Write fstab for fw_mounter as version 2
12/11/2014
Device source:
Disable TWRP event logging
Modified TWRP:
Build an updated image without event logging
4/11/2014
Modified TWRP:
Add back "Share kernel" option (same behavior can be obtained by pressing "Remove boot.img" under MultiROM>List ROMs>*rom name*)
30/10/2014
Modified TWRP:
Update to v2.8.1.0
25/10/2014 - v29
MultiROM:
Minor updates
Full MultiROM Manager support (this fixes the ghost update)
Modified TWRP:
Full MultiROM Manager support
Uninstaller ZIP:
Add support for other jf variants
2/10/2014
Add support for MultiROM Manager app
1/10/2014 - v28c
Device source:
Add MicroSD Card to init devices
Fixed device autoboot in recovery after a reboot/shutdown
30/9/2014 - v28b
MultiROM:
ROM boot from external SD (MicroSD card) is now supported
TWRP Recovery:
General update (branch master)
Removed "Share kernel" option
ROM Installation to external SD (MicroSD card) is now supported
Uninstaller ZIP added back and now working
16/9/2014
TWRP Recovery:
Better MTP compatibility
12/9/2014
TWRP Recovery:
Merge twrp28 branch (now has MTP connection inside to transfer files between PC and device)
6/9/2014
Device source:
Clean and update init devices
Add volume keys init (now you can select ROM/tabs also with volume keys)
3/9/2014
Fixed installation on other jflte devices
1/9/2014 - v28
Device source:
add power button init (needed to reboot device when "an error occurred" and to exit from pong game, available by clicking on Miri)
Downloads
1. Main downloads
MultiROM EXT4 (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849558
MultiROM F2FS (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849563
Modified TWRP (20151029-v2.8.7.0): https://www.androidfilehost.com/?fid=24052804347849556
MultiROM Manager App: Google Play Store (by default it will install the EXT4 version!)
2. Kernels for primary ROM (Internal) based on Android 5.1.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.1 ROMs:
AOSP 5.1 & Optimized CyanogenMod 12.1 from JDCTeam: Alucard is embedded and always up to date
Alucard AOSPv2 5.1 v1.3ba
Stock CM12.1 kernel (included in ROM's zip)
3. Kernels for primary ROM (Internal) based on Android 5.0.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.0 ROMs:
Optimized CyanogenMod 12 from me and @alucard_24: Alucard is embedded and up to date
Alucard AOSPv2 5.0 v1.1a
Googy-Max3 v1.3.0
Hulk Kernel v1.3.1
KT-SGS4-LP5.0
Stock CM12 kernel (included in ROM's zip)
Kernel with kexec-hardboot patch for Google Edition 5.0 ROMs:
Alucard GE5 v1.1a
Hulk Kernel GE5 v1.3.1
Googy-Max3 GE5 v1.2.3c
Kernel with kexec-hardboot patch for TouchWiz 5.0.1 ROMs:
Hulk Kernel TW5 v1.3.1
Imperium LL v2.0
4. Kernels for primary ROM (Internal) based on Android 4.4.x KitKat
Kernel with kexec-hardboot patch for AOSP/CM 4.4 ROMs:
(builds up to 6 August, including CM11 M9)
Alucard AOSP v2.7.2a
(builds after 6 August, including CM11 M10)
Alucard AOSPv2 v1.4r
Googy-Max3 CM v1.2.5
KT-SGS4-KK
Stock CM11 kernel (included in ROM's ZIP) - All CM11-based ROMs after 6/08 with this android_kernel_samsung_jf source
Kernel with kexec-hardboot patch for Google Edition 4.4.x ROMs:
Alucard GE v2.4d
Googy-Max3 GE v1.2.8
Kernel with kexec-hardboot patch for TouchWiz 4.4.4 ROMs:
Googy-Max3 v1.3.0 TW 4.4.4
Hulk Kernel v1.2 TW 4.4.4
Imperium v1.14 TW 4.4.4
Kernel with kexec-hardboot patch for TouchWiz 4.4.2 ROMs:
Alucard TW v2.3ga
Googy-Max3 v1.3.0 TW 4.4.2
Hulk Kernel v1.2 TW 4.4.2
Imperium v1.14 TW 4.4.2
5. Uninstaller
MultiROM uninstaller ZIP: https://www.androidfilehost.com/?fid=95747613655050515
Just flash this to disable MultiROM and delete all secondary ROMs.
Alucard-PWR-CORE dev thread by @alucard_24: http://forum.xda-developers.com/showthread.php?t=2590246
Googy-Max3 dev thread by @googy_anas: http://forum.xda-developers.com/showthread.php?t=2741181
Hulk Kernel dev thread by @Tkkg1994: http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
Imperium dev thread by @slim80: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/kernel-imperium-kernel-v1-0-t2910801
KT-SGS4 dev thread by @ktoonsez: http://forum.xda-developers.com/showthread.php?t=2297379
Useful tips
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.
What storage for ROMs is supported?
Internal memory (/data/media-/sdcard) is supported as well as MicroSD card (/external_sd).
How many ROMs can I have and where are stored?
You can have as many ROMs as you can fit in internal memory and MicroSD card. All the ROMs are stored in /data/media/0/multirom/roms (in case of internal memory) and /external_sd/multirom/roms (in case of MicroSD card) drive. These folders are 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.
I'm a F2FS user. Can I still enjoy MultiROM?
Yes, you can. Just flash F2FS version of MultiROM zip. NOTE: it is compatible only with full F2FS (so cache, data and system both at once), if you use a custom layout like F2FS for cache/data and EXT4 for system just edit the mrom.fstab file inside the MultiROM zip before flashing the first time or after with reflashing.
Can I have different versions of Android working alongside?
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, systems are separated.
Can I flash TouchWiz-based ROMs as secondary ROMs?
You can, but it's strongly unrecommended and not all the TW ROMs work if installed as secondary, plus are very bigger than other ROMs. I suggest to flash them only as primary ROM.
Can I configure boot menu to be showed only when I want?
You can. Boot in TWRP recovery, go under Advanced>MultiROM>Settings>Configure autoboot and set Keypress-based, then select a ROM to autoboot. In this way, if you power on your device boot menu isn't showed and the ROM you choose to autoboot is booted, but if you power on and rightly when you see "Samsung Galaxy S4" bootlogo you press and keep pressed Vol+ or Vol- button, boot menu is showed.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
nds850 said:
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
Click to expand...
Click to collapse
Alright I tried beanstalk like you mentioned and it rebooted into recovery the first time I tried booting in to it. It worked fine the 2nd time however. Currently have dirty unicorns, pa, and now bs. Sometimes when I click reboot on either one of these ROMs, it automatically reboots to recovery instead of multiboot. Don't know of this is a bug or not.
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 256 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
AntaresOne said:
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 128 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Cool. Thanks for the explanation. This multiboot is really awesome
I'm not sure I understand how you mean. I completely shut the phone off and wait for the RAM to reset. I then start the phone and in the MultiROM menu choose the ROM I want to use. The phone restarts and load to recovery. Does the RAM need to be cleared after choosing the ROM? If that is the case how do I do that?
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
BakaB said:
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
Click to expand...
Click to collapse
I would assume so. It should work on all jflte's. It works fine on my jflteusc.
@BakaB @bdog2015
Yes, it works on all jflte devices.
I337, I545, L720, M919, R970, I9505, I9507, I9508
Inviato dal mio GT-I9505
I have been trying to flash the MultiROM zip through TWRP Recovery and I keep getting the following errors:
Code:
assert failed: getprop("ro.product.device") == " jflte" | | getprop("ro.build.product") == " jflte "
But what's weird is that both the lines that script is looking for (ro.product.device & ro.build.product) both say jflte in my build.prop so I'm very confused. I'm running Alliance ROM v2.0 I9505XXUGNG2 with stock permissive kernel and TWRP 2.7.1.0
Any help/advice would be appreciated.
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Ok MultiROM is installed. After installing MultiROM I flash TWRP_multirom_jflte_20140901.zip through TWRP and then reboot recovery. When TWRP reboots, I don't have any options under Advanced for MultiROM. Recovery is now showing 2.7.1 in the top left whereas before it was showing as 2.7.1.0 so I know that the recovery has changed.
Have I done something wrong? When I reboot the phone I get the MultiROM boot screen coming up asking me to either let it boot into the internal ROM or touch to change, but when I boot into recovery I have no options for MultiROM. I am happy to upload any logs that might help to decipher the issue I am having.
Thanks for your help mate.
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Dude... I'm just an idiot. I had twrp holofied which wasn't showing the menus and buttons. This mod is AMAZING!!! Dude I have been looking for this forever, you are a king. I'm definitely gonna be using this from now on, thank you so very very much! [emoji4]
Alliance I9505
@daveyannihilation
Hahaha don't worry
Now just remember this
Inviato dal mio GT-I9505
Is the new build recommended or am I fine if everything is working for me?
bdog2015 said:
Is the new build recommended or am I fine if everything is working for me?
Click to expand...
Click to collapse
The only change in new build is the fixed installation on other jflte devices. If you installed the previous build without errors, no need to update [emoji1]
Inviato dal mio GT-I9505
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Motorola Moto G. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-titan.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_titan_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch - Not available yet
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS - Not available yet
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS - Not available yet
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Changelog
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
MultiROM v27a
=====================
* Fix freezes in the boot manager
* Add support for SailfishOS
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scripts
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25
MultiROM v25
=====================
* Add support for the Android L preview
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22c
=====================
* Fix graphics corruption with some custom kernels
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
[url]http://bit.ly/ut_sharing[/url] for more info.
MultiROM v22a
=====================
* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
MultiROM v22
=====================
* Fix Ubuntu Touch boot taking long time
* Fix Ubuntu Touch freezing on Google logo for some users
MultiROM v21a
=====================
* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
MultiROM v21
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Initial version
Recoveries:
Code:
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Remove
boot.img" on the List ROMs -> *rom name* page.
12.8.2014 - 1
=====================
* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
version
11.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
27.2.2014
=====================
* Support for system-image based (from the Manager app) Ubuntu Touch
installation
* Fix time in recovery
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
4.2.2014
=====================
* Update to support latest Ubuntu Touch testing builds
* Fix date and time in recovery
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
26.1.2014
=====================
* Fix radio in Ubuntu Touch
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
Credits :
@Brawn_Sg for multirom falcon port
@Picohackr hackr for the recovery
@tassadar for the entire multirom
@h2o64 for the OP
@luca020400 for helping me with TWRP
DOWNLOADS
Tested Configuration:
Primary Rom: PAC-5.0
Sec. Rom: CM12
Sec. Rom: CM11
Donations (Tasssadar)
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
XDA:DevDB Information
Multirom v32 Titan, ROM for the Moto G 2014
Contributors
LuK1337, luca020400
Source Code: https://github.com/multirom-titan
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Abandoned
Created 2015-03-03
Last Updated 2016-02-14
Reserved
DOWNLOAD
Bugs:
Sdcard may not work in secondary roms: fix
Your sdcard or USB storage partition must be formatted as EXT4 if you want to store roms on it.
Stock based roms are not supported.
Changelog:
2015-07-06
- Updated MultiROM to the latest source (2.8.7.0)
2015-06-19
- Added support for software encrypted /data (TWRP)
2015-03-30
- Source updated to v32
2015-03-30
- Multirom TWRP now uses LP kernel
2015-03-27
- Updated MultiROM to the latest source (2.8.6.0)
2015-03-15
- Fixed volume keys in boot menu
2015-03-14
- Added sdcard (EXT4) support
2015-03-02
- Initial release
MultiROM:
MultiROM v32
MultiROM TWRP:
MultiROM TWRP 2.8.6.0
KEXEC PATCHED KERNEL:
CM12.1
CM12: LP KK
CM11
Stock 5.0.2
MISC:
UNINSTALLER
It doesn't work for me
But it does for Luk xd
Good flash to anyone hahaha
THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??
deeplyyoung said:
THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??
Click to expand...
Click to collapse
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)
LuK1337 said:
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)
Click to expand...
Click to collapse
Except roms with supersu ( like aicp and blisspop ) as primary
Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..
ishubhamsingh said:
Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..
Click to expand...
Click to collapse
I'll build patched CM11 kernel later.
the best roms can not be primary
Awesome stuff multiboot finally, no more wiping nice setups
Thanks Luk
Sent from my XT1068
Wow....Just tried it....Works great....All I can say is hats of to you Luk
No blisspop as primary
Yuppies
Sent From My XT1068{LP} Using TapatalK
Multibooting cm12 and cm11 possible?
Does multirom doesn't work for other guys ?
Or I'm the only one ...
luca020400 said:
Does multirom doesn't work for other guys ?
Or I'm the only one ...
Click to expand...
Click to collapse
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working
slukk said:
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working
Click to expand...
Click to collapse
I said it wasn't working becuase in my device multirom doesn't work
I got it working before ( at the 1st attempt )
But my device ****ed it up ...
That's why I haven't released it ...
Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?
Vidhanth said:
Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?
Click to expand...
Click to collapse
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK
deeplyyoung said:
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK
Click to expand...
Click to collapse
Cm12 as primary with boot.img from OP
And cm11? Is that perfect? How do we switch booting roms?
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: joyeuse
Maintainer/Authors build: @Kry9toN
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel: https://github.com/Kry9toN/kernel_xiaomi_sm6250
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/uc?id=1XUIrTfSeQ6rgYfvb4_XO6NIIRnWZJOOj&export=download
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro
Contributors
Kry9toN, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Created 2020-08-10
Last Updated 2020-08-10
Great, will test it now !
dungphp said:
Great, will test it now !
Click to expand...
Click to collapse
Nice if you found bug please tell me
Kry9toN said:
Nice if you found bug please tell me
Click to expand...
Click to collapse
It work ! Needed unmount system, vendor then flash rom
Why do you need to crosspost here? https://forum.xda-developers.com/redmi-note-9-pro/review/recovery-pitch-black-recovery-t4145151
Thumbs up. Backup seems to work.
@Kry9toN
After installing Island backups only fail as you can read on
https://www.reddit.com/r/Android/comments/chhcm6/psa_twrp_backup_does_not_like_android_for_work/
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1256
Island is similar to Shelter and is used to isolate certain proprietary Apps. I won't delete it. I could send you my PBRP log, if you want to work on the problem. How about it?
heyadmwutanime said:
Why do you need to crosspost here? https://forum.xda-developers.com/redmi-note-9-pro/review/recovery-pitch-black-recovery-t4145151
Thumbs up. Backup seems to work.
Click to expand...
Click to collapse
My miss take for choose form
Hi,
i tried to install this version but failed. Please see my steps belwo:
1) installing recovery.img via "fastboot flash recovery recovery.img" worked fine
2) installing the PitchBlack-joyeuse-2.9.1-20200722-1350-UNOFFICIAL.zip file via twrp returned "ERROR 1"
3) after rebooting into system and then back to PBRP, PBRP was gone and defualt recovery came up
Is there anything i miss?
Try to unmount some partitions and then install/sideload the zip. Try both install (from internal memory) and adb sideload. I also wasn't able to install many zip files through Recovery. Either the custom recoverys aren't ready yet or the zip files aren't made for Android 10 AOSP.
Tried adb sideload as well but it doesnt start on device side. Its just loading or startign endless.
I wantred also to get hands on the logs but once i install magisk, its getting into bootloop. Also the filemanager cannot be installed from PBRP.
Maybe its jjust to early.
Flashing Magisk from recovery will get u to bootloop. Extract ur roms boot.img from rom zip and patch it with Magisk Manager app then flash it with adb in fastboot mode
Hi,
I unlocked the bootloader of my RN9 Pro, rooted by patching the .img file with Magisk, now I would like to install a custom recovery. Does installing PBR format data like Czech TWRP found in neighboring forum? And how to install it with the official Recovery, the latter is not familiar to me, I come from a Mimax2.
Thank you
dungphp said:
It work ! Needed unmount system, vendor then flash rom
Click to expand...
Click to collapse
Thanks! I spent hours trying to figure out why I couldn't flash anything, unmounting vendor fixed it instantly!
2x super with the same size.
A bug?
You can't use adb sideload it glitches and gapps aroma doesn't work
Please help me
I unlocked bootloader, then flash pitch black recovery but once I booted to recovery, I flash miui rom and then my internal data got encrypted. It's not encrypted anymore but I can't flash any custom rom using this recovery.
When I access fastboot mode, adb devices doesn't show any device. I previously flashed twrp for curtana.
I'm still able to access pbr but everytime I try to flash rom, here's the error message:
Updater process ended with ERROR: 7
An Assert failed. Please check the output above for more details.
Error installing zip file 'file-location-info-bla-bla-bla'
Updating partition details...
Failed to mount '/product' (No such file or directory
...done
Please help me solve this
Edit:
I solved it by flashing through fastboot
Guys i want to try it. I will flash it via fastboot. I dont want to lose my data. Am ı need to flash rom after installing pbrp?
Hmm, looks like this does not support dynamic partitions.
I run into an assertion error trying to install the xiaomi.eu 11.0.5 ROM.
cheers
afx
a.f.x. said:
Hmm, looks like this does not support dynamic partitions.
I run into an assertion error trying to install the xiaomi.eu 11.0.5 ROM.
cheers
afx
Click to expand...
Click to collapse
Make sure to unmount /system and/vendor before flashing
crisagler said:
Make sure to unmount /system and/vendor before flashing
Click to expand...
Click to collapse
Not mounted by default anyway...
cheers
afx
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction:
Team Win Recovery Project 3.x , or twrp 3 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.
Features:
Wiping, backing up, restoring, and mounting various device partitions, such as the system, boot, userdata, cache, and internal storage partitions are also supported. TWRP also features file transfer via MTP, as well as a basic file manager, and a terminal emulator. It is fully themeable.
Click to expand...
Click to collapse
Bugs:
You tell me!
Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Prerequisites:
1. Unlocked bootloader.
Instructions:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP, and you will have TWRP as your permanent recovery!
5. Enjoy!
Contributors:
hadenix
Version Information:
TWRP version: 3.5.x
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: @Hadenix
Downloads:
TWRP
Support:
Telegram Channel
Changelog
Code:
13-10-2021
Updated sources TWRP
Added support for encrypting firmware with OSS Vendor
Safetynet module update for MIUI
Added cleaning of Super partitions;
Added a backup and the ability to install images of the Super partition;
Fixed translations
20-06-2021
Fixed CPU temperature sensor
Synchronization with source code
Added support for MIUI firmware encryption on Android 11
Fastbootd is activated
And other minor edits and fixes
31-05-2021
Updated source codes to the current ones
Updated graphics
Removal of the LogCat log
a patch to prevent the replacement of twrp stock recovery (for of.MIUI)
install Magisk v23.0 and uninstall it
AVB protection removal patch (for OFIUI on 11 android).
script for full conversion of Super to RW partition (by brigudav)
script for mounting dynamic partitions in RW (by brigudav)
script for disabling forced encryption (by brigudav)
script for disabling partition logging (by brigudav)
installation of a module for Magisk to pass the SafetyNet test
16-02-2021
Fix adb sideload
Updated sources TWRP
Changing the interface of the top bar
31-01-2021
updated twrp sources
updated fstab
fix recent errors
removed some flags
made the sorting
17-12-2020
updated fstab
fix recent errors
now the date is being decoded by pin code
13-12-2020
removed unnecessary libs/files
removed some flags
made the sorting
fixed the status bar
updated twrp sources
updated fstab
26-10-2020
Fix Magisk Installation
Minor fixes that prevented the installation of MIUI firmware
25-10-2020
Update prebuilts to 12.0.7.0 stable
First release
@Hadenix
I'm using the EU rom, stable, i flashed your TWRP and now my K30 5G is stuck, wont boot into recovery or system, i followed your steps 1 by 1, and yes after flashing TWRP i booted to TWRP via Fastboot.
What to do ?
Thank you so much
Inpain said:
@Hadenix
I'm using the EU rom, stable, i flashed your TWRP and now my K30 5G is stuck, wont boot into recovery or system, i followed your steps 1 by 1, and yes after flashing TWRP i booted to TWRP via Fastboot.
What to do ?
Thank you so much
Click to expand...
Click to collapse
I did the installation from scratch and everything works for me
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
twrp-3.4.0_10-2-picasso-hadenix
17-12-2020:
updated fstab
fix recent errors
now the date is being decoded by pin code
vudungcom said:
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
Click to expand...
Click to collapse
try the latest version
vudungcom said:
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
Click to expand...
Click to collapse
if you put it clean, then you need to format the date, all data is deleted
Hadenix said:
if you put it clean, then you need to format the date, all data is deleted
Click to expand...
Click to collapse
Thank for suggestion but now i am using stable eu version n dont have time to do, when i want to change new rom, will use your TWRP
how can I decrypt twrp? i can't update my rom without decrypting. and i can't find any solutions for that. every time i want to update I need to formate everything. please help
sazzadbk05 said:
how can I decrypt twrp? i can't update my rom without decrypting. and i can't find any solutions for that. every time i want to update I need to formate everything. please help
Click to expand...
Click to collapse
You can type your screen passcode android
Hi I have a problem for your latest twrp twrp-3.4.0_10-2a-picasso-hadenix when I entered the pin code it
stuck on decoding FBE what shoud I do ?
31-01-2021
updated twrp sources
updated fstab
fix recent errors
removed some flags
made the sorting
The Twrp download link doesn't work
Avladis said:
The Twrp download link doesn't work
Click to expand...
Click to collapse
Redmi K30 5G / picasso - Browse /TWRP at SourceForge.net
Code name: picasso
sourceforge.net
Hello Sir and friends,
Thank you the updates.
TWRP 3.5 can flash GSI ROM now. I can mount /system partition in dynamic partition. I assume that we can flash GSI ROM with this updated TWRP with no need to use fastboot command line.
16-02-2021
Fix adb sideload
Updated sources TWRP
Changing the interface of the top bar