Develop Bugs

[MOD] Disable Forced Encryption on Robin [Updated 2016-10-09]

I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
{
"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"
}
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.

Thanks, worked well!
Thank tested, will se if it gets any faster. Have been having some problem with lag that comes from time to time that I haven't seen on other devices.
Otherwise, great to see support for such a small phone!

The Robin devs are trying to be Community friendly as much as possible its good to see.

can it still be updated using this mod boot ?

kanded said:
can it still be updated using this mod boot ?
Click to expand...
Click to collapse
Unfortunately no, because the OTA includes an updated delta for the kernel as well (which means the /boot needs to be 100% stock).
If you want to install via the OTA, you need to restore the stock boot.img (and the system partition - if you're rooted or modified it in any way, and the recovery too, if you have TWRP installed).
Alternatively, you may simply flash the updated stock ROM zip on top of your existing install - just be sure to flash the new boot.img zip immediately after (as well as SuperSU and any other mods you may have, if you want to preserve your current setup).

Thank you for this [deXter] it works great.
However does anyone have a solution for how to get rid of the 5 sec nag screen popping up at reboot?
Thanks in advance/arc.

For June update 350 please.

I need help!
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?

Angeldgaf said:
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?
Click to expand...
Click to collapse
This mod only allows you to use your phone unencrypted - it shouldn't affect your battery or WiFi. Are you sure you flashed the correct version?
Goto Settings - About. If you're on the June 1 ROM (Build 00WW_1_350) then your kernel version should say 3.10.84 Wed Jun 1. If these numbers do not match then restore to the latest factory image/ROM and start over. Also, have you tried a factory reset yet?

For 450 Please

Updated for build 450.

Hi everybody! Just receveid the OTA notification
I'm currentyl on 6.0.1 1450 rooted with twrp, do you have the modified boot.img for the Nougat beta as well? Thanks

Many thanks for this work. Getting the Robin rooted and usable was a struggle compared to the Nexus4. This mod helped greatly.

Boot image for N88 please. Thanks in advance.

So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?

Steffen1st said:
So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?
Click to expand...
Click to collapse
Yes. Lineage does not have forced encryption.

[deXter] said:
I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.
Click to expand...
Click to collapse
Boot.img for N108?

Use the modified FED Patcher for the Robin from this thread:
https://forum.xda-developers.com/ne...d-patcher-robin-forceencrypt-disable-t3352006
It worked fine for me on 108. After flashing the latest 108 7.1.1 file from the Razer forums, I flashed TWRP 3.1.0-0, then the FED Patcher, and finally Super SU 2.82.

[MOD][08/03/2016] MultiROM v33x for Xperia ZL [ABANDONED]

{
"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-odin.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-odin.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support 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 :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is 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/XperiaMultiROM/multirom (branch master)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)​
MultiROM available for Odin also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC​
XDA:DevDB Information
MultiROM for Xperia ZL, Tool/Utility for the Sony Xperia ZL
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned

Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-odin.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-odin.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Odin due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage 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...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Odin release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)

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.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
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.​

Hi mate I'm interested to try this mod. I'm currently on Xperia ZL c6502 10.7.A.0.222 stock rooted with unlocked bootloader and xz dual recovery. Is it enough to try this or any thing more stuff I need before I can start?

@Chippa_a, about keeping stock ROM 5.1.1 as primary, AFAIK if the recovery is flashed to fota partition, the device doesn't boot into recovery. Then how can it be used in stock ROM?
EDIT: Oops, didnt see the changelog.

[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.2.1-0:
- minui fixes (cryptomilk)
- Better android-8.0 compatibility in ROM trees (Dees_Troy)
- Fix missing library in android-8.0 (nkk71)
- Fix inconsistent SDCard naming (DevUt)
- Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD LINKS:
Current and past versions of TWRP can be found at one of the mirrors below:
- Primary (Recommended)
- Primary (Backup)
INSTALL INSTRUCTIONS:
TWRP install (requires TWRP 2.8.4 or higher already installed):
1) Download the latest version of TWRP appropriate for your device/firmware
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find other alternative installation methods on our website (direct link to your device)!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2, Tool/Utility for the Xiaomi Mi Note 2
Contributors
joe2k01
Version Information
Status: Stable
Created 2018-04-06
Last Updated 2018-04-06

I really want twrp 3.2.1-1. Miui firmware not Packed in new.dat are not installed on Android 8.

Thank you very much! Very nice to see the official one!

Sorry about the noob question but I'm not sure. Is possible updating with this version without getting the official recovery? Any explanation helps, thank you!

Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Sent from my Nokia 7 plus using Tapatalk

Stransky said:
Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Click to expand...
Click to collapse
I had the same problem a few days ago trying to recover root after updating to MIUI 9.5.4 and sadly have no idea whats going on.
I fixed it downloading the MIUI firmware to my PC (fastboot option) and used Mi Flash Tool to flash it above the existing one (no wipe) and it booted again normally.
I recently updated to 9.5.5 but I haven't tested yet if now it works. So far I have no clue what I'm doing wrong.
Sorry if my english it's not perfect, hope it helps.

Good morning friends!
I installed Rom Beta MIUI 10 Global 8.7.5 in TWRP 3.2.2
However, the system does not boot even though I'm formatting with TWRP.
Would there be some other method for ROM to reboot?
Can anyone help me with this question?
I install MIUI 10, do the procedure by installing TWRP, restart Smatphone via TWRP, install SuperSU, format the System. But when I restart my Smartphone, it does not leave the startup screen

Thanks a lot man. I've got a minor issue. Mouse cursor in the center for all time.

hi is there any way install twrp in mi note 2 with support of ota update

kmanilpillai said:
hi is there any way install twrp in mi note 2 with support of ota update
Click to expand...
Click to collapse
Always need to flash the full rom instead of ota after installing twrp. Why?

kmanilpillai said:
Always need to flash the full rom instead of ota after installing twrp. Why?
Click to expand...
Click to collapse
If you are referring to MIUI OTAs, those are differently sorted inside(folder wise) the archive... So TWRP will not find the files he needs to read...
Full ROMs are normally arranged inside (folder wise) and that's why you can flash them...

New version available 3.3.0-0 as of 20190412.
No changelog for scorpio, but article on XDA here about changes.
https://www.xda-developers.com/twrp-3-3-0-release/
Maybe useful if you need encryption, or edl?
Been using previous version for Xiaomi.eu with no problems.
Scorpio is actually a really good phone, very dependable, as long as you don't overheat it.

latest version of miui (miui11)
did it the latest twrp 3.3.1.0 work/run/installed fine on latest miui (miui 11.0.2.0) please help me
thanks in advance

I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)

Shok II said:
I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)
Click to expand...
Click to collapse
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.

cobben said:
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.
Click to expand...
Click to collapse
Ah so that's why.
Flashed Lineage 17, and now TWRP is persistent, thank you!
Oh right, I noticed that the display brightness is not working (default is too bright btw), as I slide to the right or left, there is no brightness change, TWRP 3.4.0. Haven't tried the older versions tho. Display brightness settings in Lineage works fine.

[ROM][Custom] - = EDGE PURE EDITION = -

{
"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"
}
- = EDGE PURE EDITION = -
Custom ROM based on Stock firmware RPDS31.Q4U-39-26-4-2
This custom ROM uses stock kernel without modification. The source for the stock kernel is not released by the OEM.​
Preliminary requirements:
- Unlocked bootloader.
- New and Clean Stock firmware is required!
- TWRP installed;
- Micro SDCard or USB flash drive should be formatted to exFAT.
What's done:
- Removed the restriction on writing to the system, which in Android 10 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified (in Magisk settings activate "Magisk Hide" function, in "Magisk Hide" tab give permission for Google Play Services, perform Google Play reset);
- Cleaned and lightened the system;
- Built in additional system color accents;
- Built in and updated to the latest versions at the time of firmware and Apps release . YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Command Center 2;
- Ringtones, notifications, alarms sounds have been replaced.
🛠 Installation:
1. Extract the system image from the archive (see tab "Download") and copy it to the SD Card.
Also copy the "Magisk Installer" archive Magisk-disable-dm-verity-v21.4.zip in to the SD Card.
2. Reboot the device into bootloader mode and then into TWRP.
3. Installing the ROM image. In the "Install" tab in the lower right corner, click the "Install img" button and select the firmware image. A window will open, where you will need to select the "Super" partition. "Swipe to confirm".
4. Go to the "Reboot" section and reboot the device back to Recovery.
5. Go to "Wipe" and do a "Swipe to Factory Reset ".
6. Install "Magisk-disable-dm-verity-v21.4.zip". Reboot in to the System.
7. When the boot is complete make the initial settings.
8. Launch the "Magisk Manager" app and update it. You will be asked to configure the work environment. Agree. Phone will automatically reboot itself when setup is done.
Download
Edge_R_Pure_Edition_02-1
Edge_Q_Pure_Edition_nowrz_04-2
Advanced
YouTube Vanced v.14.21.54 Black Magisk
Proven, absolutely trouble-free version of YouTube Vanced.
To prevent in Play Market from updating in to the stock YouTube app, you need to add empty file with the name "enable_detach" (without extension) into the folder "/cache" (at the root of file system) using RootExplorer and rebooting your phone. One minute after the reboot, the application will unbind from the Market.
Enjoy!

Can i Flash from Lineage or need stay in stock?

VitilinVk said:
Can i Flash from Lineage or need stay in stock?
Click to expand...
Click to collapse
"New and Clean Stock firmware is required"

Upgraded Edge Pure Edition!
- created an image in a different format which reduced its size by 6 GB;
- full mount of system in r/w and r/o, allowing the system to boot up fully if you forget to put the system in r/o after making edits to the system partitions;
- updated GApps to the base of 27/02/21.

I'm not sure if you actually know the rules but wrz are not allowed

Upgraded Edge Pure Edition!
- updated ROM to the latest versions of stock firmware QPD30.114-80-4 (09 March 2021) ;
- updated GApps to the base of 12/03/21.

Upgraded Edge Pure Edition!
- Chrome bug fixed

Updated the ROM to a version based on Android 11(R).

Anyone using this daily?

I use. Why can't this ROM be used as the main firmware?

Hi, I tried installing the android 11 version of this from after clean restoring to stock. I installed the .img to the super partition and the phone wont boot. I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address. Any help? Thanks

Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11

Nicktsaab said:
I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address.
Click to expand...
Click to collapse
This message appears because TWRP is not adapted to Android 11. Ignore it.

ilia3367 said:
Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11
Click to expand...
Click to collapse
Ahh thank you, I was trying to install on the Android 10 base. Thanks!

what is the difference between r and q? android 10 and 11 i assume?
also ive been out of the rom loop for quite a while (lg g8, just got unlock like a month ago), what is wrz and why is it not allowed? just curious.

im having a weird issue. i bought 2 edges recently, and wanted to install this rom. both are on final android 10 firmware, and im flashing the q img. obviously both are bootloader unlocked and using twrp 3.5.2.
i followed instructions on one, and it went perfectly fine no issues. on the second whenever i flash the image it wont boot and the twrp log has a few errors about partitions. also there are 2 super partitions listed. even restoring my bone stock twrp image or flashing the factory fimware i have the same issue and the twin super partitions persist. the phone will boot on the stock rom fine however.
edit: weirdness continues, now all of the sudden the rom image flashed perfectly fine, when i rebooted back to twrp for magisk.zip i had no errors. however there STILL is 2 supers listed. but i flashed magisk and booted to system... and it boots. idk.
in the select partition to flash to menu the partitions listed (in order) are: boot, dtbo, boot logo, recovery, super, vbmeta, vbmeta system, super. ive tried both instances of super and both had problems except for this time where it succeeded (i did the first instance this time).
i should also note that this was like this when i made my initial twrp backup, there were 2 super partitions in the backup menu. but, the other phone that had no issues, did NOT have 2 super partitions at any point. again... idk.

Unfortunately, I didn't understand a lot of it, because I don't know English very well.
The fact that in TWRP in Backup you see two Super partitions, it's not a big deal. Choose both, but in fact your backup will have one Super partition.

its just strange but i guess if it works.
but im also having issues with applications. for one, the asus gallery and file browser that are bundled always ask for storaage permissions, even if i grant them they wont launch and keep asking for permissions. wipe data, force stop, grant permissions again, nope they still ask for permissions. i dont know whats going on with them. also i cant set a picture wallpaper. not with gallery, google photos, google gallery, nothing. i get a notification that says "error, could not load media" every time i do it no matter what app i try to use. live wallpapers are fine.

There should be no such problems. This behavior can only be when you try to make these applications (Asus Gallery, Asus File Manager) system applications using, for example, RootExplorer.
I don't have this problem even after restoring a backup.
Install ROM on a clean, re-installed stock firmware.

Development [RECOVERY] [UNOFFICIAL] TWRP-3.5.1 [20210702]

{
"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:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.​
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)​
Supports Hentai OS encrypted devices​
Supports flashing MIUI zips​
Supports Vibration​
Supports wiping data without wrecking encryption. ​
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates

Reserved

Reserved

ayy pro <3

Yay Yahoo

Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."

I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...

vasishath said:
Great work.
Click to expand...
Click to collapse

blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.

@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app

vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.

deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?

Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse

vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..

NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?

Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.