You need to update your ADB. Minimal ADB and Fastboot 1.4.3 works
[RECOVERY][grus] KudProject's Unofficial TWRP 3.4.0-0 [28-06-2020]
- Thread starter krasCGQ
- Start date
Is that a different TWRP from the one in the OP? If so, what is the difference or what is the advantage of yours? And what does the root version do differently?
It would be great if you don't share it on an existing thread to avoid every possible confusion.
Sent from my Mi 9 SE using XDA Labs
Silly question: why don't you start another XDA thread with your builds then?
Is this a Problem with your TWRP version? Cuz i cant install magisk... Goes with error 1 cant mount system. Installing the xiaomi eu version via your twrp worked.
EDIT: Strange...after 3 try it worked. You know whats going on? The mounting points should be correct or it woudnt work after 3 try now. hmm strange
So thx for your work and the builded TWRP for our phones
EDIT: Strange...after 3 try it worked. You know whats going on? The mounting points should be correct or it woudnt work after 3 try now. hmm strange
So thx for your work and the builded TWRP for our phones
Last edited:
Is this a Problem with your TWRP version? Cuz i cant install magisk... Goes with error 1 cant mount system. Installing the xiaomi eu version via your twrp worked.
EDIT: Strange...after 3 try it worked. You know whats going on? The mounting points should be correct or it woudnt work after 3 try now. hmm strange
So thx for your work and the builded TWRP for our phones
I had this issue too, my solution is to boot system and than go back to recovery and install Magisk. Maybe the system.img is not mounted after flashing.
---------- Post added at 07:10 PM ---------- Previous post was at 06:59 PM ----------
restoring a backup with twrp-3.3.1-2 does not work for me, after restore my phone only loads the fastboot mode. This always happen when I restore the system.img too. If I restore only data.img there is no problem, but this is not a full restore.
Mount point is correct following AOSP documentation; just Magisk can't handle installation if /system_root is mounted before flashing Magisk. ?Is this a Problem with your TWRP version? Cuz i cant install magisk... Goes with error 1 cant mount system. Installing the xiaomi eu version via your twrp worked.
EDIT: Strange...after 3 try it worked. You know whats going on? The mounting points should be correct or it woudnt work after 3 try now. hmm strange
So thx for your work and the builded TWRP for our phones
Open-GApps is unaffected and flashes correctly, however.
Is that system backup has older security patch than current system?
Sent from my Mi 9 SE using XDA Labs
security patch
No it is the same security patch. My phone came with miui 10.2.30. eea global, the backup was from this rom. And I have no done any system update.
No it is the same security patch. My phone came with miui 10.2.30. eea global, the backup was from this rom. And I have no done any system update.
Bear with me... I'm coming from Android 4.4 era devices, so couple of questions in order not to end with a broken new phone.
1. I'm on Global 10.2.1.0. Does it matter in case stock vbmeta attached here needs to be flashed? I expect it is not from my rom.
2. What happens after flashing recovery? Does it end waiting for my action or reboots automatically? I'm asking this since it is emphasized to immediately get back into recovery by pressing power+volumeup.
3. I have ARB set to 1. I suppose this means it is not enabled. And how can I get the info from recovery ROM what ARB settings it has?
4. What's the difference betwen Global and EEA Global roms?
1. You don't need it unless you try to flash GSI ROMs.
2. You don't have to reboot into the recovery immediately. But you have to reboot into recovery first before rebooting the system. If you boot into MIUI after flashing the recovery, MIUI will rewrite it with stock recovery.
3. Xiaomi's ARB can't be disabled. TWRP does not check the rollback indices before flashing, which is why nearly all bricks were the result of downgrading via TWRP.
4. EEA is for Europe and it has Widevine L1. Global is for everyone but China.
Last edited:
First unlocked the phone.
Then flashed and booted to twrp-3.3.1-2-grus-20190609.img
I believe here I swiped "allow modifications".
Rebooted and... Stuck on boot logo, then restarts back to recovery.
Is there a way to solve this without losing user data? I have a pattern/fingerprint set and some important data that could not be backed up (like google authenticator).
Any way to restore system perhaps?
Then flashed and booted to twrp-3.3.1-2-grus-20190609.img
I believe here I swiped "allow modifications".
Rebooted and... Stuck on boot logo, then restarts back to recovery.
Is there a way to solve this without losing user data? I have a pattern/fingerprint set and some important data that could not be backed up (like google authenticator).
Any way to restore system perhaps?
Flash disabled vbmeta image, but that will break stock ROM flashing.
Sent from my Mi 9 SE using XDA Labs
Guys but the correct procedure which one? On the first page it seems that before installing TWRP you need to issue the vbmetal command but fastboot by error. I tried to do as on other Xiaomi I installed TWRP after I made date format and installed Xiaomi eu and after DFE but the phone remains encrypted . Someone and kind enough to explain the correct steps?
Inviato dal mio Mi 9 SE utilizzando Tapatalk
Inviato dal mio Mi 9 SE utilizzando Tapatalk
I can't manage to keep TWRP installed after reboot... I can use it, flash MIUI updates and everything else, but it doesn't persist.
Not having problems with encryption, etc.
Followed every steps... :/
Anyone facing the same? Any solution?
Btw, thanks for TWRP!
Not having problems with encryption, etc.
Followed every steps... :/
Anyone facing the same? Any solution?
Btw, thanks for TWRP!
So... it went almost fine.
I extracted my stock rom's vbmeta and flashed it. Then I flashed twrp and using VolUp+Power rebooted into recovery. It asked me for a initial pattern for decryption and then offered me to swipe to allow modifications. I entered the pattern and allowed modifications. Everything looked good except that I can't boot into system - every time coming back to recovery. The only way is to go into fastboot and then boot the recovery image - using this it boots into the system. And this behavior persists.
It looks like the default booting option in the boot partition is set to boot into recovery. I encountered something similar once in the past with ASUS TF101... http://justanotherdave.ca/?p=351 & http://messingwithtech.blogspot.com/2013/11/asus-transformer-tf101-bootloader-fix.html show the solution for it.
Any hint how to solve it here?
Try flashing vbmeta again with disable verity to boot into stock ROM .
Doesn't help.
The only way to boot into the system is using fastboot to boot recovery image... then it goes into the rom.
First of all, no.
You need to flash vbmeta.img with fastboot with --disable-verity and --disable-verification in place.
The reason why you failed to boot system after allowing TWRP to do modifications because it trips AVB.
I think I have them explained the instructions in OP.
Sent from my Mi 9 SE using XDA Labs
Added some notes to 3rd post.
Hope this clears confusion of newcomers especially anyone who're coming from non AVB 2.0 as well as FDE devices.
Sent from my Mi 9 SE using XDA Labs
Hope this clears confusion of newcomers especially anyone who're coming from non AVB 2.0 as well as FDE devices.
Sent from my Mi 9 SE using XDA Labs
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone