Develop Bugs

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

Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.​
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).​
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Beta 1 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.​
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.​
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11beta1-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11beta1-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.​
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]​
Downloads
2013-01-08 / 2013-01-19
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)
multirom-cm11beta1-20140119-c1905-test.zip (202 MiB, 1.2 GiB extracted)​
Screenshots
See Screenshots​
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree (used to build MultiROM Xperia):
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Beta 1 thread​
XDA:DevDB Information
MultiROM Xperia M, Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-11-04

Changelog and technical information
Changelog
2014-01-08
Added option to update/rescan for ROMs
2014-01-07
First public test release
Technical information
It works by extracting the boot ramdisk to root and patching init.rc files after boot selection.
More to be added​
Changes from the original MultiROM
This port is based on the original MultiROM by @Tasssadar, which is available for multiple devices including the Nexus 4, 5 and 7. However, since his original port did not account for supporting external SD cards, and also didn't handle most Xperia devices without a recovery partition, I've rewritten some part of his original MultiROM to handle these things.
Differences include:
All binaries are placed in the ramdisk altogether instead of the internal storage.
MultiROM Xperia does not mount the partitions before starting the real Android init. Instead, it generates a script and patches some files (including init.rc) to trick the target system to mount filesystem images (loop mounting loop devices).
One ROM can contain multiple user profiles (i.e. data, cache and persist).
The code to boot generic (non-Android) Linux ROMs is removed due to heavy rewrite of parts from the original MultiROM.
It currently only support using partition filesystem images, neither symlink nor bind mount is supported.

Reserved

Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks

aweosomeabhijeet said:
Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks
Click to expand...
Click to collapse
how did u get it work?
which model c1904 or c1905?
which sdcard?

Till now I've discovered a few bugs in this test release:
Sometimes, microSD card is not detected because the initialization is too long.
This varies between cards. A theory is that SDHC might take a longer time to initialize, which happens after MultiROM has scanned for partitions.
You can try rebooting a few times and if, by any chance, the card initialized right in time, you will be able to boot the external ROM.
I have a few possible solutions for this, and I will update to you when I've implemented a working solution.
USB OTG storage devices may not be detected properly. Needs investigation...
Thanks to @ansebovi for testing and informing about these.

i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?

ansebovi said:
how did u get it work?
which model c1904 or c1905?
which sdcard?
Click to expand...
Click to collapse
Flashed boot.img using fastboot.
Extracted ROM in the root of sdcard.
Rebooted. Selected sdcard>cm11>boot. And it booted
Model C1904
SanDisk micro sd 8GiB class4
Sent from my C1904 using xda app-developers app

I've added an option in the "Misc" tab to rescan for ROMs as a temporary measure. Flash the new boot image to get it. Please refer to the first post for download.
Sent from my Sony Xperia M (C1905)

GedeWK said:
i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?
Click to expand...
Click to collapse
Well, how to install gapps to the ROM? I need the play store

to do the tutorial I have to have the bootloader unlock?
alvinhochun said:
Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.​
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).​
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Alpha 2 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.​
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.​
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11alpha2-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11alpha2-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.​
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]​
Downloads
2013-01-07
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)​
Screenshots
See Screenshots​
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree:
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Alpha 2 thread​
XDA:DevDB Information
MultiROM Xperia M, a Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-01-09
Click to expand...
Click to collapse
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.

daruto80 said:
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.
Click to expand...
Click to collapse
u should not quote op on any thread...edit ur post..remove quote
and yes u need an unlocked bootloader

since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?

elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
It's only for Xperia M at the moment since it is not completed yet.
If anyone feels like porting it to other devices I will surely appreciate, but for me I will wait till most of it is ready before porting to other devices.

Uploaded test package with unofficial CM11 Beta 1. Just extract it to SD card, just like the previous test release.
Although I don't expect daily usage on a pre-alpha test release, if you want to keep your data in CM11 Alpha 1, copy the `default` directory from cm11-alpha2 and replace the one in cm11-beta1.
Just a little update, I am coding as I type this, but you cannot expect the alpha release of MultiROM Xperia to be here in a short time 'cause there is a lot to do. You can still try the test packages at the moment.

Is the testing still in process? Because I can't wait to try this out. I hope it would be done sooner...

Booting all the 4 ROM(s)!
Thanks Alvin :highfive:

elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
XZ already have multi rom elias it has been done by mithun46

rebelos said:
XZ already have multi rom elias it has been done by mithun46
Click to expand...
Click to collapse
it is out dated , and it needs an app , says always unsupported rom , mithun stopped the developing for it ( he never replies on his thread nor on any question about the multirom )

aweosomeabhijeet said:
Thanks Alvin :highfive:
Click to expand...
Click to collapse
How were you able to get it to read ROMs? I'm currently having trouble and have tried almost everything. I compared the test zip and the FXP311 zip and found out that they are completely different.

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

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

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

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

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

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

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

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

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

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

jip, thx

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

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

Thanks will try this

Running it now (H932). Thank you.

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

Is the vendor partition mountable ?
Are trebleized ROMs flashable ?

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

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

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

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

[Guide]Lenovo S5 K520: TWRP, Root and Decrypt data

Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.

Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide

does anyone enable lte bands, 4 and 28?

just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI

Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????

Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.

Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!

Does this work for s5 pro l58041?
Thanks

B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!

Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...

so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os

I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img

Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube

hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?

has anyone achieved unlocking bands in this phone?

Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/

After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ

jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try

Could you plz make tutorial about getting back to stock unroot...thx

Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back

[GUIDE][ROM] Realme 5 Pro global ROM for Realme Q

Realme 5 Pro global ROM for Realme Q
Code:
* We are 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.
{Mod edit}
If you know exactly what you're doing then jump go step 5)
1) Introduction:
Oh sheet. Here we go again. Hope you guys will make use of this little guide for at least 20 RMQ users PMed me here on xda, on Messenger and on Telegram to help them install RM5P ROM on their RMQ device and had to dump them for I had no idea. Now that I have tried it myself I'll try to do. I've an RMQ device 4+64GB variant which I ordered from AliExpress for 161$/148€ ( in September of 2019 ) and tried loads of tweakings on stock ROM to make it more fitting to a person like me for daily usage but I don't think I have to say... without much success. In this guide I'll try to show/tell you how to make with COS without weeks of testing and debugging I've been through on stock RMQ ROM since October of 2019.
2) Personal reasoning:
I heard there are people who like Color OS as it is existed but still I wouldn't want to believe you even after I talked with some of you. Since the very first day I held my device in my hands I started seriously despising Color OS for I've been a purist, minimalist and stock Android fan for 10 years now and always tried to stick to "clean" ROMs such as LOS, PE, Aosp Extended, AOSIP because of reasons. This is mainly because (Chinese) Android skins modify system/vendor so heavily that they prohibit or interfere (with) basic Android functions that work well on stock-like ROMs. {Mod edit}
3) Features:
Mostly same as on RMQ ROM but...
More languages are supported by the system.
Most of Oppo's restrictions are removed {Mod edit}
3.5) Known bugs:
None. You tell me!
4) Basic terms:
RMQ: Realme Q
RM5P: Realme 5 Pro
RMX1971CN: Realme Q device codename.
RMX1971EX: Realme 5 Pro device codename. Both are used to distinguish China and Global/India ROMs.
COS: Color OS
ROM: Read Only Memory (means for us the OS we use to flash with TWRP/Fastboot)
OS: Operating System
TWRP: TeamWin Recovery Project (the one recovery we use widespread to flash custom ROMs and fixes on our mobile device)
FASTBOOT: A mode of your device and a script on PC that you can use to flash stuff via USB cable onto your device. This is necessary if you are on stock recovery.
FLASHING: The process of writing onto our mobile device's ROM that wouldn't necessarily be possible without using external tools if TWRP wasn't there for us. Mobile device companies don't really support or encourage users to do this.
BOOTLOADER: Default state is locked on our and on most devices. Without unlocking it, it would be extremely hard if not impossible for us to flash custom ROMs on our mobile phones. You can unlock your bootloader by following this guide if you haven't already done that because without unlocking it, flashing global ROM on your device which comes with Chinese one preinstalled will likely be impossible at least not known to the RM5P/RMQ community so far.
MAGISK: Systemless solution which grants root access (admin-like) to the user without really tampering the ROM system, this way granting higher stability than it's predecessors.
5) Precautions:
If you aren't an advanced user and don't really know what you're doing follow the steps closely and it's highly advised to read the basic expressions to understand better what's happening just in case something goes wrong so you can fix it.
External SD card is highly recommended to use because to make this work formatting data is quite likely needed.
If you want to bring your data with you from your current ROM make sure to do either Titanium or Migrate backup and save it to your external SD card.
TWRP for RMQ (this one I highly recommend to use for it has a wide range of features and options that come in handy, unlike normal TWRP)
Magisk if you want root or/and want to pass Google's Safetynet completely.
Magisk COS beta FIX from here (step 6)
Modified vbmeta.img from here. (step 6)
Magisk modules: Busybox and MagiskHide Safety Props Config. (from inside Magisk Manager after successfully rooting with Magisk flashable zip file)
6) Prerequisites:
{Mod edit}
Probably formatting your data.
This means all your stuff, apps, data will be gone after you do this so be prepared and save your stuff to your external SD card.
7) Installing:
A) If you're coming from custom ROM then:
1) Wipe everything (except internal and external storage) including /data/system/dalvik/cache/ but not vendor and vendor shouldn't even appear in the list when wiping anyway.
2) Flash the ROM.zip
3) Flash TWRP.IMG as recovery and again flash it as boot.
4) Flash vbmeta.img as vbmeta.
5) Reboot even if you get notification "no OS is installed".
6) If you're stuck on boot logo for 15+ minutes or bootloop then turn off your device volume up+power then right after shutdown vibration and black screen enter fastboot mode by holding volume down+power, from there select recovery and you should be back to TWRP recovery
7) Select wipe and format data by typing "yes". This will delete all data on internal storage so take care.
8) Reboot to system
9) The device should boot up to COS. Do the initial setup and after that reboot to TWRP recovery again.
10) Flash Magisk.zip
11) Reboot to system
12) Enter Magisk Manager and disable core only mode
13) Reboot to TWRP recovery... again.
14) Flash Magisk COS Fix beta.zip
15) Reboot to system.
16) Check Magisk Manager. Core only mode should be turned off. Check SafetyNet Status. BasicIntegrity should be true now.
17) Download and install MagiskHide SafetyProps and Busybox from Magisk downloads.
18) Reboot to system (normal reboot)
19) Enter Magisk Manager and see if the two installed modules are active. (If yes you probably done everything well. If not, something is fishy.)
20) Download any terminal emulator app, I recommend Termux. Open it and by typing "su" without quotation marks and pressing enter you should grant root access to the terminal app you use. Now type: "props" and press enter.
Type 1) and press enter as edit device fingerprint.
Type f) and press enter as pick from certified fingerprint.
Type 6) and press enter as Google (you can use others too but I used this one so it should be tested).
Type 21) and press enter as Google Pixel 3a XL.
Type 1) and press enter as Android version 9.
Type y) and press enter as yes.
21) Reboot to system and open Magisk Manager. Check SafetyNet Status. Now both cts profile and basicintegrity should be true.
22) Enjoy your better Color OS.
B) If you're coming from stock rom:
If you haven't unlocked your device's bootloader it's time to do it.
After unlocking install TWRP for Realme Q. Then follow the steps above for they're the same.
Don't report issues. I can't help for I'm no developer and I've dyscalculia which means I should be bad at every Informatics stuff that requires math/logic thus I can't compile/rebuild/update ROMs. As for the developer he lost his phone so it's not his interest anymore to make fixes and updates for the ROM/device. Probably pointless to bug him.
Click to expand...
Click to collapse
ROM modified/made by: Birman34
ROM data/turorial written by: greenys'
ROM brought to you by: Realme 5 Pro/Realme Q global Telegram group
{Mod edit}
ROM information:
Security patch date: 2020.01.05.
Kernel version: 4.9.112
Build number: RMX1971EX_11.A.16
Android version: 9.0

It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!

bahuy2003 said:
It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!
Click to expand...
Click to collapse
Well, yes. I wish I had found a simpler method but I didn't and I wanted to make sure everything is going to work fine without letting issues happen during or after installation. Perhaps it seems complicated because of that and that I didn't want to take chances. Better be safe than sorry, I presume. For me, who has been flashing ROMs since 2010 it didn't take more than 5 minutes to complete all the steps. Evidently there are lots of users who just gotten into bootloader unlocking and don't know much about the details of flashing. That's why I tried to make this guide quite well detailed. Anyway, if I find a simpler way or I get know of an easier method or Realme itself will approve the change between regional ROMs I'll add those steps to my post of course. Don't thank me yet. Thank me if it worked btw!

Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ??

nagar.xda said:
Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ?
Click to expand...
Click to collapse
According to my knowledge official ROM change from global to China or vice versa is not possible. I don't know about OTA updates. I presume you can't update that way if you flash this ROM for as you said different partition sizes. This ROM while it's still made from global, several stuff from system were removed so it'd still fit onto an RMQ device's smaller partition. The ota updates are not modified this way so I think you couldn't update that way because the ota would be too big to fit onto the RMQ device's partition. I believe you shouldn't worry about root and bootloader unlock. Without rooting and using safetyprops Google notices your unlocked bootloader thus both cts and basicintegrity will fail. In my tutorial I go through that bothersome Magisk method to trick Google's security system. After doing that both SafetyNet checks pass, meaning Google shouldn't see your device as rooted. Root is dangerous for some apps because it can trick them. Unlocked bootloader is dangerous for the device and its owner. At least according to Google. Meaning with Magisk SafetyProps applied only DRM Widevine stuff shouldn't work completely like Netflix full HD and above. Every other app that requires certified device fingerprint should work. Banking apps and online purchases work just fine for me. I think you shouldn't worry, only if you're the type of guy who wants ota updates badly and watches DRM protected content all the time. Else this is completely safe ROM.

greenys' said:
...
Click to expand...
Click to collapse
THREAD CLOSED due to the distribution of warez.
XDA Forum Rules (excerpt).
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...
Click to expand...
Click to collapse

[CLOSED][RECOVERY] ORANGEFOX R11.0 for OnePlus 5 & 5T (Unofficial, Official soon)

OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
:good: Treble & Non-Treble Support
:good: No compatibility.zip error while flashing OxygenOS
:good: A lot of customisations
:good: Extremely beautiful UI ready to please your eyes.
:good: Dev team is always ready to fix your problems
:good: F2FS support
There were previously 10.1 builds for these devices for these devices and this is how current build is different from them:
New, more modern UI.
Fixed F2FS support
Upstreamed to R11
and many more...
Note: Official soon I've applied for it.
Screenshots
Screenshots at https://imgur.com/a/Ai8KWX9 and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://github.com/Maitreya29/OrangeFox-OnePlus-5-T/releases
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!

Thank you, I just installed it, I have everything set and customized! Not yet tested all the options but it's beautiful! Congratulations...

@Maitreya29 Since this supports both the 5 & 5T, would you like this thread to be moved to the 5 & 5T Cross Device Development forum? We can then close the same thread you created in the 5T forum since there won't be a need for it.

shadowstep said:
@Maitreya29 Since this supports both the 5 & 5T, would you like this thread to be moved to the 5 & 5T Cross Device Development forum? We can then close the same thread you created in the 5T forum since there won't be a need for it.
Click to expand...
Click to collapse
Hi there, thanks. Actually the download links for both the posts is different and I feel like I'd be able to give better support since I'd know which device is getting the error as both the 5 & 5T builds are different.

Maitreya29 said:
Hi there, thanks. Actually the download links for both the posts is different and I feel like I'd be able to give better support since I'd know which device is getting the error as both the 5 & 5T builds are different.
Click to expand...
Click to collapse
Alright, thanks.
Added to the OnePlus 5 Index Thread here.

shadowstep said:
Alright, thanks.
Added to the OnePlus 5 Index Thread here.
Click to expand...
Click to collapse
Thankn you, appreciate it

''IT DOESN'T DOWNLOAD IT JUST REFRESHES AFTER 5 SECONDS/DIRECT DOWNLOAD''. can you please look in to it thank you.

Sparda333 said:
''IT DOESN'T DOWNLOAD IT JUST REFRESHES AFTER 5 SECONDS/DIRECT DOWNLOAD''. can you please look in to it thank you.
Click to expand...
Click to collapse
It works fine for me, you must be having problems downloading. I don't host the download. Sourceforge does. However join the support group I'll share links.

Download links updated

I didn't have any issues downloading or installing... Are is fine now with my op5.

Awesome! Thank you

Finally ?

It seems working very nicely. Many thanks!

This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.

Thracks said:
This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.
Click to expand...
Click to collapse
Any recovery on android 11 can not decypt data with pin enabled. You need to set pattern for that.

Thracks said:
This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.
Click to expand...
Click to collapse
That's android 11 problem, A11 doesn't let recoveries decrypt with pin. Only patterns work.

This Recovery can decrypt the Data with Pattern in Android 11 ?

Thread closed on request of OP @Maitreya29 as the OP doesn't anylonger owns the device and is unable to support. However, thanks very much for your highly appreciated contributions.
Regards
Oswald Boelcke