{
"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. 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 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-device.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-fota-device.zip) - download the ZIP file from second post and use a recovery
to flash it into the FOTA partition (see TWRP 3 for more informations).
UNNECESSARY: Patched kernel - You can use those kernels on most Marshmallow based primary ROMs to add kexec boot support.
Kexec support is no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
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.
Recommended values are (not needed for ext4 storages) :
Cache : Keep default value
Data : Minimum 4000 for proper usage
System : 1500 to 2000 should be enough for most installs
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 Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/AdrianDC/multirom_core (branch master)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch master)
Device Tree - https://github.com/XperiaMultiROM/android_device_sony_dora (branch master)
Kernel - https://github.com/AdrianDC/kernel-sony-copyleft (branch master)
TWRP sources - https://github.com/AdrianDC/twrp_development_sony/commits/device_sony_dora (branch device_sony_dora)
MultiROM available for Dora also thanks to :- [MENTION]Tasssadar[/MENTION]
- [MENTION]nkk71[/MENTION]
- The XperiaMultiROM team
XDA:DevDB Information
MultiROM for Xperia X Performance, Tool/Utility for the Sony Xperia X Performance
Contributors
Adrian DC
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: No Longer Updated
Created 2016-10-08
Last Updated 2019-08-06
Reserved
Downloads
1. Main downloads
MultiROM for Xperia X Performance (Dora): https://mega.nz/#F!Ckd2HbwI!NFv3bh7J87lHTi3cujnV_g
Downloads mirror : https://basketbuild.com/devs/AdrianDC
MultiROM: multirom-2017MMDD-v33x-device.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-device.zip
Regular TWRP with my same sources: https://mega.nz/#F!DtsERIzb!OFINTFpTQ6CF85alkcIpgA
2. Uninstaller
MultiROM uninstaller: multirom-2017MMDD-uninstaller-device.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs.
Otherwise, reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM boot from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Reboot the phone
How to install only the recovery
(Option 1) Flash the ...-recovery-fota-device.zip from a recovery
(Option 2) Extract the img from ...-recovery-fota-device.zip,
then use 'fastboot flash recovery twrp.img' to install to FOTA partition
Reboot the phone
Migrate Stock ROM to internal or MicroSD
Reboot to the FOTA Recovery (on boot or with power keys)
Ensure you have already installed Sony Stock Patcher or a custom bootimage
Perform a ROM Backup (at least system, data, cache, boot)
Add a ROM, select the previously made backup
Wait for the ROM to be installed (can take a while)
Reboot the phone
Update Stock ROM on internal or MicroSD
Backup internal data / storage
Upgrade to last FTF official release you want
Reboot to the FOTA Recovery (on boot or with power keys)
Install the Recovery image you want to use
Install Sony Stock Patcher or a custom bootimage
Perform a ROM Backup (at least system, cache, boot)
Add a ROM, select the previously made backup
Wait for the ROM to be installed (can take a while)
Inside *Storage*/multirom-*/, move the data folder
from the old installation to the new one
Rename and delete the ROMs as you wish
Reboot the phone
Changelog
Code:
MultiROM v33x - TWRP 3.1.1 - 07/06/2017
=========================================
* 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
MultiROM v33x - TWRP 3.1.1 - 24/05/2017
======================================
* Fix touchscreen init race condition on a specific variant
MultiROM v33x - TWRP 3.1.1 - 22/05/2017
======================================
* Include all recent improvements from TWRP 3.1.1
* Touchscreen init improvement to match Stock .223
* Fix for SDCardFS full support of the internal storage
* Known common issue : encrypted boot for now
MultiROM v33x - TWRP 3.1.0 - 17/03/2017
======================================
* Include all recent improvements from TWRP 3.1.0
* Proper TWRP support of Stock Nougat encryption
* Known common issue : encrypted boot for now
* Fix USB handling for Sony Stock ROMs
MultiROM v33x - TWRP 3.0.3 - 05/03/2017
======================================
* Built in a clean new tree of Android 7.1.1 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Include all recent improvements from TWRP 3.0.3
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
MultiROM v33x - TWRP 3.0.2 - 22/12/2016
=========================================
* Kernel updated to Stock Nougat, with proper
> and minimal patching for custom changes
* Touchscreen handling of Stock Nougat
* Encryption handling of Stock Nougat
MultiROM v33x - TWRP 3.0.2 - 18/12/2016
=========================================
* Minor improvements of MultiROM
* Added support for Sony Stock ELF (64 bits) bootimages
* libbootimg changes from my recent updates
MultiROM v33x - TWRP 3.0.2 - 08/10/2016
=========================================
* Initial dora public release
Recent ROMs tested so far :
Code:
Stock SONY 7.1 : OK (Primary & Second)
Stock SONY 7.0 : OK (Primary & Second)
Stock SONY 6.0 : OK (Primary & Second)
AOSP 7.1.1 : OK (Primary & Second, Work in Progress)
CyanogenMod 14.1 : OK (Primary & Second, Work in Progress)
Other ROMs : To confirm & report here
Reserved
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
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./external SD card. 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.
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.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.
Current local manifest of the MultiROM build
Code:
<!-- https://github.com/AdrianDC/multirom_development_sony -->
Informations : My 2017 releases of MultiROM and of TWRP include full support for Nougat encryption inside TWRP.
For MultiROM boot UI, Nougat encryption is not yet fully working, it's a common issue and I'm looking into it.
MultiROM 20170317 update : Includes my fix for USB handling inside Sony Stock ROMs,
due to stock files permissions losses : https://github.com/AdrianDC/multirom_core/commit/f42b7c5c7c07471882193c2e1e6d53f17dc71236
Would this work on xperia x too?
Gesendet von meinem F5121 mit Tapatalk
Can I use it with Xperia XZ?
86chan said:
Can I use it with Xperia XZ?
Click to expand...
Click to collapse
I have MultiROM "almost" ready for XZ but I'll release it once I first check something.
However you'll find my TWRP for XZ in the Sony Stock Patcher thread.
AdrianDC said:
I have MultiROM "almost" ready for XZ but I'll release it once I first check something.
However you'll find my TWRP for XZ in the Sony Stock Patcher thread.
Click to expand...
Click to collapse
Thank you for answering my question.
MultiROM 20170522: Release based on TWRP 3.1.1, including changes to match 7.1.1 touchscreen init.
Regular TWRP 20170521: TWRP 3.1.1 release, including changes to match 7.1.1 touchscreen init.
Note about MultiROM and SDCardFS devices
Here's a general note about MultiROM that involves issues with SDCardFS usage:
More and more devices OEMs are starting to use SDCardFS enabled by default on their releases.
Depending on the device and installations, we started finding random behaviours of MultiROM secondary ROMs.
Basically the issue is that a booted secondary ROM using SDCardFS would prevent access to the "Internal Storage",
mostly visible by an "unmounted" internal storage and mostly all Google applications failing in sequence.
A more in-depth search shows that running an "ls -l" on the internal storage paths
fail directly with an "-EXDEV" > "cross-device linkage" error, which means the original and target devices don't match.
The SDCardFS kernel driver is actually returning this -EXDEV failure when it detects such an issue.
Going a step further means comparing which partitions are mounted where, through "mount".
We can confirm SDCardFS is being used by the ROM through the following outputs :
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser,allow_utime_grp)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser,allow_utime_grp)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser,allow_utime_grp)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser,allow_utime_grp)
However, it also means that /data/media is "mounted" as an sdcardfs file system in the regular internal storage paths.
And the interesting part concerning MultiROM is that we actually mount /data/media on our own to match our paths.
On a "working" secondary installation, we have this type of mount :
/dev/block/mmcblk0p54 on /data/media type ext4 (rw,seclabel,relatime,noauto_da_alloc,errors=panic,data=ordered)
However on a "failing with -EXDEV" secondary installation, we have this type of mount :
/dev/block/mmcblk0p54 on /data/media/0 type ext4 (rw,seclabel,relatime,noauto_da_alloc,errors=panic,data=ordered)
As we can see, the internal partition is being mounted on /data/media/0, which is not an issue by itself,
but the fact the /data/media is later mounted as internal storage means that we're creating a cross-device linkage:
/data/media is owned by the /data partition, running from our external storage with MultiROM, and its sub-path ./0 is on the Internal,
whereas the working situation is that /data/media is directly owned by its original partition hence no cross-device linkage.
Now the question would be : Why the mounted path differs ?
The "multirom_create_media_link" function handles the internal storage mounting (https://github.com/multirom-dev/multirom/commit/c9bd12186baa6911d46138c6c77379c6c3eaa767)
A proper output of this function in the kernel logs is "multirom: Making media dir: api 25, media_new 1, /realdata/media to /data/media"
and a faulty one for SDCardFS to work is "Making media dir: api 25, media_new 0, /realdata/media to /data/media/0"
This was never an issue since 4+ years because the paths and loop would be invisibly used,
and the missing path created through the recursive mkdir hence path resolution was never an issue.
On the other hand, SDCardFS prevents this linkage therefore introducing the issue.
An initial fix can be found here, tested on the Xperia X Performance with and without an internal storage matching the issue.
https://github.com/multirom-dev/multirom/pull/11/commits/81295cd6971317d955cb0c78b41d147b891a601b
The change is also valid for non-sdcardfs devices, tested on Sony 8960 for example, since the path is used the same way.
I wrote this in public here in case other MultiROM devs or new maintainers would face such an issue,
and would not (yet) use our "multirom-dev" sources for updated MultiROM projects.
New special release of MultiROM from 20170607.
Implements something I wished to fix for at least 10 months on MultiROM:
External storage (MicroSD or USB Drive) using Ext4 or F2FS file systems are
now finally accessible from the Android userspace once booted from them,
by means of a special new storage folder called 'external_multirom' that serves
as a bridge between the external storage and Android.
You can therefore once again use the external MicroSD with Ext4 and store music, data, ...,
without Android blocking access to it with "Corrupted storage" notifications.
Why use Ext4 / F2FS MicroSD in the first place ? With MultiROM, these allow us
to install secondary ROMs directly on the MicroSD without setting space sizes / limits,
therefore directly on the drive instead of independent disk images as done for vFAT / FAT32.
The storage space is unlimited / shared between all installs and are faster to create / run / use.
About SDCardFS : A similar issue as the one reported and fixed in the previous post happens here,
the 'external_storage' is also a cross-device linkage and SDCardFS will fail on purpose to give access to the path.
Disabling SDCardFS (through the build.prop property) allows to use the ROM as usual while also accessing the path.
All technical details about the issue and the implementation can be seen here : https://github.com/AdrianDC/multirom_core/commit/0acfa4c53429a7fcf7c2c573b857f2ae69ca5b5a
Is this likely to work for the Xperia XA (F3111)? What would need doing if not?
Could you try to port this for Xperia X/X Compact Variants?
Building guide isn't clear for me, as try to Port MultiROM to S650 Devices
...
Dezqo said:
MultiRom doesn't seem to show up on boot even if I "inject current boot sector".
It is working though as the recovery works fine and I already installed a secondary rom.
I can't boot into it though.
Click to expand...
Click to collapse
See the third post. You can't keep your device encrypted if you want the bootimage to access data. Therefore a factory reset to erase the data partition (including internal data, careful) is needed.
...
Dezqo said:
Thanks for answering, no idea how I didn't notice that
Since there is no way to "decrypt" without wiping, is this completely impossible or just not yet integrated?
It's my day to day phone and even though I make nandroid backups I can't to wipe right now.
Click to expand...
Click to collapse
An easy way would be backup, save internal files to a computer, factory reset, restore data.
Factory reset is important, not just a "Wipe" because the encryption sectors would be kept with a wipe.
...
Dezqo said:
Thanks. Just to be clear, if I make a backup from TWRP to my sdcard and then factory reset, will the device then be decrypted or are any more steps necessary?
Sorry for all the questions but it seems not many people have actually tried MultiRom on this device.
Click to expand...
Click to collapse
Be specific. The term sdcard mostly designates internal storage.
Therefore you should backup to the "MicroSD" + backup all your relevant data from internal to MicroSD or PC.
Once factory reset, data partition is formatted, hence you start clean.
TWRP recommends to reboot to recovery at this stage, which you should do as advised.
- T R E B L E Y -
Android Partition Treblerizer
A tool able to seamlessly create / remove the vendor partition from within TWRP
INTRODUCTION
The creation of a tool able to create and remove the supplier partition from TWRP, so a computer was not required. So I created this flaming TWRP ZIP which can create and remove the vendor partition from the userdata system or partitions without a computer and without deleting the files in the mother partition in the recommended configuration.
In this way, our device can also have a treble just like a phone that came out of the factory with the vendor partition without touching the cust partition.
The tool will try to resize the mother partition without deleting it, either during the creation and removal of the supplier partition. However, this can only be done when the mother partition is ext4, only when the supplier partition is at the end of the mother partition and when the mother partition is not encrypted. The recommended configuration is the one that is obtained by selecting the first option in each option: subdividing 512 MB from the end of the system partition. A reboot is required after applying the patch to the partition table because the kernel needs to reload it before doing anything else.
REQUIREMENTS
Due to the use of a key detection binary, it is compatible only with ARM and ARM64 devices running TWRP. So far I have tested it in the Xiaomi Mi Note 2 but It should work in any compatible device. I made it this way so other legacy devices could transition to Treble ROMs + GSI, and Android Pie. Please let me know about other devices using this tool!!!!!
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
Either for creating or removing a vendor partition,, follow these steps:
A. Download Trebley_APT, Trebley_treble, Trebley_twrp.
1. Put Trebley_APT, Trebley_treble, Trebley_twrp to your External SD card.
2. Go to Install and flash the Trebley_APT ZIP file as any other ROM or MOD file to execute the tool.
3. Reboot to recovery again to ensure the changes are applied properly.
4. In some cases you will need to format the mother partition after adding or removing the vendor partition next to it.
5. Go to Install and select "Flash Image".
6. Flash the Trebley_twrp IMG file to recovery partition and reboot to recovery.
7. Wipe cache, dalvik-cache, system, vendor and data
8. Flash a Generic System Image in system partition (arm64, A only).
9. Reboot, and done.
CREATE A VENDOR PARTITION:
So far these are the available options:
Mother partition selection: system / userdata
Split position: Splitting from the end / start of the mother partition.
Vendor partition size: 512 / 915 MB
REMOVE THE VENDOR PARTITION:
Should a Vendor module already exists, Trebley offers to remove it, returning to a Non-Treble partition table. It will return the space to the mother partition, system or userdata. So, older non Treble ROMs could be flashed after the mandatory reboot.
DOWNLOAD
Trebley_APT_v1.0_ARM_20190215-signed.zip
Trebley_treble_scorpio-20190215-0521-signed.zip
Trebley-twrp-3.2.3-0-scorpio-custom.img
SOURCES
All rights reserved to the project: Party and its creator @Oki).
CREDITS
@someone755 for the keycheck binary
@Zackptg5 for the V4A install script that inspired my version.
@Oki for the base script.
@Psy_Man for the kernel and for supporting.
Trebley updated V1.0, is now affordable for all users, and above all is stable.
DarioRetr said:
I would be grateful if developers like @Psy_Man will update their project, making it compatible with the project treble with the vendor partition.
Click to expand...
Click to collapse
Nice work! I recently hunted down the original source of the keycheck binary and built it for x86/64 (and rebuilt it for arm/64) here: https://github.com/Zackptg5/keycheck
Here's compiled ones to save you some time: https://github.com/Zackptg5/Unity-Addons/tree/master/Volume-Key-Selector
The screenshots will be added soon!
Zackptg5 said:
Nice work! I recently hunted down the original source of the keycheck binary and built it for x86/64 (and rebuilt it for arm/64) here: https://github.com/Zackptg5/keycheck
Here's compiled ones to save you some time: https://github.com/Zackptg5/Unity-Addons/tree/master/Volume-Key-Selector
Click to expand...
Click to collapse
Thanks for the advice, I will evaluate if I will put in the next Trebley update, however, have you tried Trebley?
DarioRetr said:
Thanks for the advice, I will evaluate if I will put in the next Trebley update, however, have you tried Trebley?
Click to expand...
Click to collapse
No, my current devices are already treble compatible
Please post and open the thread in the designated Project Treble section.
Thank you for helping us keeping the forums organized.
Thread Closed
Funk Wizard
Forum Moderator
As it seems impossible to hotboot TWRP recovery for Magisk installation and installing TWRP only for this sole purpose is a little overkill, many people are using rooting procedure with flashing patched boot.img directly. However this does not automatically create a backup of stock boot image, which is used later for OTA updates.
It is fairly easy to create the backup manually (and hopefully Magisk developers will add this feature into Magisk Manager..).
Option 1 (ADB shell on the PC or terminal emulator on the phone):
Code:
copy boot.img into the root of internal sdcard
adb shell
su
cd /data/adb/magisk
./magiskboot sha1 /mnt/sdcard/boot.img
(copy generated SHA1 checksum)
./magiskboot compress /mnt/sdcard/boot.img /mnt/sdcard/stock_boot_[I]putSHA1here[/I].img.gz
cp /mnt/sdcard/stock_boot_[I]putSHA1here[/I].img.gz /data/stock_boot_[I]putSHA1here[/I].img.gz
Example:
Code:
tissot_sprout:/data/adb/magisk # ./magiskboot sha1 /mnt/sdcard/boot.img
cb925c4fe36ace17b2ff94b34ddcde1e564acaaf
tissot_sprout:/data/adb/magisk # ./magiskboot compress /mnt/sdcard/boot.img /mnt/sdcard/stock_boot_cb925c4fe36ace17b2ff94b34ddcde1e564acaaf.img.gz
tissot_sprout:/data/adb/magisk # cp /mnt/sdcard/stock_boot_cb925c4fe36ace17b2ff94b34ddcde1e564acaaf.img.gz /data/stock_boot_cb925c4fe36ace17b2ff94b34ddcde1e564acaaf.img.gz
Option 2 (Windows PC with Total Commander):
Code:
1. get stock boot.img
2. calculate SHA1 of it (file, create CRC, SHA1)
3. copy calculated SHA1 to clipboard
4. rename boot.img to [B]stock_boot_[I]putSHA1here[/I].img[/B]
5. zip to file, GZ
6. copy resulting file [B]stock_boot_[I]putSHA1here[/I].img.gz [/B]to /data on the phone
Option 2 will generate file with slightly different size than option 1, but it works just as fine for Magisk restore function.
Option 3 (rooted phone):
Code:
1. boot phone with Magisk patched boot.img
2. get stock boot.img
3. flash stock boot.img from Franco Kernel manager app, do NOT reboot
4. Magisk Manager - install, direct install
I tested this on Mi A1, but there is probably no reason why it shouldn't work on other phones too.
Option 4 (any phone)
After patching a stock image you can find a backup image in (assuming non-hidden Manager) /data/user_de/0/com.topjohnwu.magisk/install
Source
Important note - it seems that Magisk 20.2 changed the backup structure. Backups of stock boot.img are located in /data/magisk_backup_SHA1/boot.img.gz now. Each backup has its own folder.
v20.1 and below -> /data/stock_boot_SHA1.img.gz
v20.2 -> /data/magisk_backup_SHA1/boot.img.gz
Just a heads up that if you want to change the backup image to a different one you have to run magisk --path to get the path, edit the magiskpath/.magisk/config file to the new SHA1, force stop Magisk, and then restart Magisk
Note: the sbin folder does not always exist on Android 11 and up (see here).
Instead, look a folder under /dev with a random short name. In my case it was /dev/XFmlBk/.magisk
Armand Bernard said:
Note: the sbin folder does not always exist on Android 11 and up (see here).
Instead, look a folder under /dev with a random short name. In my case it was /dev/XFmlBk/.magisk
Click to expand...
Click to collapse
Holy hell, do you have any idea how long I've been searching for this very specific explanation on why I can't locate my sbin folder? Thank you!
Hi! I need your help.
I currently have Miui 11 port from sakura.
I want to go to the stock rom. latest version on android 9.
Where can I download it?
How do I install it? Using twrp as a custom rom or through MiFlash or another program?
Thanks for reading, I use google translator
There is lot of ways but the easiest ( in my opinion) is downloading Fastboot rom and flashing it via MiFlash
[CLEAN] Install Xiaomi Mi A2 Lite STOCK ROM:
(Instructions based windows)
Requiremets:
* Bootloader must be Unlocked. ()
Steps ahead assumes know-how-to-use ADB-fastboot.
Can be done through ADB-fastboot: "fastboot oem unlock" , but ...
search & study about it before as it brings critical changes,
and additionally 'oem unlock' will normally wipe all data on your device.
although "platform-tools" in the next steps includes this ADB-fastboot and uses its function(s).
Device Drivers for Windows needed. (Qualcom is the xiaomi's recomended, but Google's general driver works too.)
* If PC already "sees" the Phone Device through ADB then you don't need to install latest driver.
( Source: https://gsmusbdriver.com/wp-content/uploads/Qualcomm_USB_Driver_v1.0.zip ~10MB
includes "Qualcomm_USB_Driver_V1.0.exe" installer,
so I don't need to guide how to point .inf file through Device manager to manual update driver.
At any cases you need to Restart Computer for take effect installed driver, If there were not already installed. )
Download the latest "platform-tools" .zip for Windows.
( Source: platform-tools-latest-windows.zip ) ~11MB
Download the latest official [STOCK] ROM for your device model. (V11.0.21.0.QDLMIXM)
( Source: https://xiaomifirmwareupdater.com/archive/miui/daisy/ ) ~1.39GB
1. Extract platform-tools_.zip into a folder:
i. Just double click on "platform-tools_.zip" and drag & drop the "platform-tools" folder into the C:\ .
ii. Open "platform-tools" folder C:\platform-tools in a window as you will need it next in step "3." .
2. Manage needed files from downloaded latest official [STOCK] ROM:
This is the latest: "daisy_global_images_V11.0.21.0.QDLMIXM_20210630.0000.00_10.0_5cab9352ea.tgz"
Exract it in a folder, and then drag & drop from within, these "14 items, included 'image folder'",
into -> "platform-tools" folder. C:\platform-tools
Point "flash_all.bat" for later...
3. Open admin CMD in "C:\platform-tools":
Open "platform-tools" folder directory C:\platform-tools in a window, (from step "1. ii.")
[Shift+]R-Click in empty space -> "Open command window here",
or just type cmd in addrress navigation bar and press [Enter].
This will bring cmd prompt in C:\platform-tools\ with adb-fastboot commands environment.
Remember: "platform-tools" includes "adb-fastboot" 's functions, (ie .dlls & .exes).
i. Use ADB cmd to boot in fastboot.
(boot to "FASTBOOT" bootloader environment to proceed fastboot flash cmds between devices)
a. At this point, connect Phone to PC through USB !
b. In the cmd window opened, type adb devices just to check if connected...
should show device #Num plus connection type. (eg. 234afd3f0405 recovery)
c. Type adb reboot bootloader (to boot device in bootloader [FASTBOOT])
wait a moment, device should show FASTBOOT logo...
ii. Use Flash-All .bat script from [STOCK] ROM to install all system files at once:
By running this, ALL data existed on device will be wiped as a "factory reset".
a. In the CMD type: fastboot devices just to check if connected...
should show device #Num plus connection type. (eg. 234afd3f0405 fastboot)
b. In the CMD type: flash_all to start flash procedure.
should be look like: C:\platform-tools>flash_all
Remember, "flash_all.bat" script from STOCK ROM... doing now automatically the job:
wait the "flash_all" script to finish erasing old, and installing all system files, one by one, in both a/b slots . . .
/!\ DO NOT INTERRUPT procedure ! . . .
The phone will boot automaticaly in brand new fresh factory settings system.
Was a xiaomi Mi A2 Lite (daisy) "CLEAN" install . android One/ 10/ Q, stock ROM
Don't forget to delete C:\platform-tools folder as it weights 3.14GB and don't needed any more.
* Maybe you check the "platform-tools" for regulary use. (ie pull/push files or flash, install img, apk, zip etc.)
* maybe yet, want to TWRP, Magisk, root + OpenGapps with SafetyPass and other magi(s)k modules...
I hope this guide(s) will some day became useless because of future exists of Stable custom ROM for miA2Lite as possibly as degoogled. amen!
Sorry for my English