Develop Bugs

[GUIDE] How To Flash TWRP And Root Xiaomi Mi Max

EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html

RESERVED

The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION

Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?

noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.

StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.

noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.

Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.

noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...

That's what I told you. Then please do.

noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !

Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?

noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry

noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing

Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!

So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.

Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?

So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.

Is there anyway to root the phone without connecting it to pc?

noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?

fail installing Magisk

I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me

IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:

marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!

marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)

bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:

marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??

Dirty flash Realme UI V 2.0

I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11.
Links available in telegram channel for Rm5p.
Anybody can do it...just dont forget to flash vbmeta with disable verity......

SShots

Do you have steps how to do it? I didnt actually get the steps in the telegram.

Kristopher28 said:
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Click to expand...
Click to collapse
Yes, I will post now

Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.

jijojamie said:
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
Click to expand...
Click to collapse
Is your phone rooted?

I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now

Kristopher28 said:
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Click to expand...
Click to collapse
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.

jijojamie said:
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
Click to expand...
Click to collapse
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.

Kristopher28 said:
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851
Click to expand...
Click to collapse
After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.

I dont know but the early access of 2.0 seems a little bit buggy for me

Kristopher28 said:
" but there's another bug where a specific files cant read by the phone."
Click to expand...
Click to collapse
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Or else did you mean you got into bootloop.
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.

Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.

jijojamie said:
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Click to expand...
Click to collapse
Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.

jijojamie said:
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Click to expand...
Click to collapse
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.

Kristopher28 said:
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Click to expand...
Click to collapse
Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.

Please be more specific which ROM did you dirty flash?

Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.

Point number 2. Stock firmware latest.

Cant find the files . Which telegram channel.
Link plz

Question Latest Twrp pros and cons

Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
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.

you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting

hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.

so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself

So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)

How To Guide [Recovery] [13] [12] TWRP & OrangeFox

Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka ADB) and USB drivers should be set beforehand. Latest versions are reliable enough. PixelExperience, PixelOS and MIUI (official and Xiaomi.eu) ROMs have been tested. Before proceeding to flash, make sure about your ROM type (standard or vendor_boot) to avoid not desired consequences. Blew are the most recent versions.
_________________________________________________________________________
TWRP (standard)
Android 12:
twrp-3.7.0_12-v7.7_A12-alioth-skkk.img
Android 13:
twrp-3.7.0_12-v7.8_A13-alioth-skkk.img
[Instructions]
1. Reboot to fastboot mode.
2. Execute command below in ADB on PC:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your downloaded recovery file address.
3. Choose "Flash current TWRP" from TWRP's "Advanced" option.
4. Reboot.
_________________________________________________________________________
OrangeFox (standard)
Android 12+:
[email protected]_3_A12.zip
[Instructions]
1. Reboot to TWRP.
2. Choose "ADB Sideload" from TWRP's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
_________________________________________________________________________
OrangeFox (vendor_boot)
Read this thread for a detailed explanation and list of vendor_boot ROMs.
This is beta release. Treat it as such.
Android 13:
[email protected]_1_vendor_boot_vBaR.zip
[Instructions]
1. Reboot to your ROM's recovery.
2. Choose "ADB Sideload" from recovery's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
fastboot flash vendor_boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your extracted recovery image address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Run "flash-whole-image.bat" file.
4. Reboot
_________________________________________________________________________
Ps: though there are some glitches, both recoveries can install Magisk to root the device.
_________________________________________________________________________
Sourceforge archive page
OrangeFox homepage
Platform Tools download page
Google USB Driver download page

Last time I tried installing lineageos using latest twrp it failed miserably

heybaybee said:
Last time I tried installing lineageos using latest twrp it failed miserably
Click to expand...
Click to collapse
Me too, better use its recovery.

New versions available. Links have been updated.

rashazad said:
New versions available. Links have been updated.
Click to expand...
Click to collapse
Thanks for the thread. Does the latest version support flashing MIUI Global ROMs? Im having a hard time flashing them via TWRP SKK 3.7.0_A12_V6.7_A13.

I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.

panjgoori said:
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
Click to expand...
Click to collapse
Which ROM are you using?

DarthJabba9 said:
Which ROM are you using?
Click to expand...
Click to collapse
MIUI EU 13.0.9

panjgoori said:
MIUI EU 13.0.9
Click to expand...
Click to collapse
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.

DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
I accidently bricked my phone and its in EDL Mode now. Can you help me please

panjgoori said:
I accidently bricked my phone and its in EDL Mode now. Can you help me please
Click to expand...
Click to collapse
Sorry, I know nothing about EDL mode for this device. But I'm sure there are lots of tutorials on XDA or in a general Google search.

Vendor_Boot recovery links and instructions added.
Small changes made in instructions.

New version (7.8) for TWRP A13 (standard).
New version (11.1_1) for OFox (vendor_boot).

New version (11.1_3) for OFox (standard).

DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help

néonaloj said:
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
Click to expand...
Click to collapse
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.

rashazad said:
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
"recovery.img" being your extracted recovery image address.
4. Reboot.
Click to expand...
Click to collapse
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')

nehalchoy said:
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
Click to expand...
Click to collapse
That error does not seem to be related to the process.
Something (probably free apace) is wrong about your pc or phone.
What ROM were you using?

rashazad said:
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
Click to expand...
Click to collapse
Well I didn't want to make a complete tutorial ...
To flash twrp trough twrp, 'install' > change with "image" > install the recovery.img.. It has always worked, for long years..
About flashing a A13 rom (++) coming from MIUI A12 (I each time restarted from scratch, re-installing global MIUI) : I've tried a lot of ways.
I began to install A12 twrp skkk in fastboot mode (1st 'boot' then flash), reboot to recovery, then upgrade to A13 twrp through twrp (reboot to recovery), then A13 FW > bootloop ;
I tried flash A12 twrp (fastboot)(reboot to recovery), then A13 twrp (fastboot too)(reboot to recovery), flash FW > bootloop ;
I also tried A12 twrp (reboot to recovery), then FW (reboot to recovery ok), A13 twrp (reboot to recovery) > bootloop...
I won't list all what i did ! but finally I flashed A13 twrp directly on A12 MIUI (reboot to recovery ok), flash FW (reboot to recovery ok) and that worked. I then flashed my A13 rom (without rebooting system first) > reboot to recovery +reboot system, and finally flashed Gapps, magisk and other stuff. I do know it's not a common way, but the one that worked.
EDIT : I do know it can work (maybe even easier) to flash the MIUI A13 fastboot rom, but had a other device hard bricked some time ago doing this. That's why i tried to only flash the FW
PS : if you can help, I've only one issue to solve yet : I've flashed magisk 26.1, i could have bank & pro apps to work correctly, the only app that I cannot is the FAI tv (error P531 'can't reach my account' (even if i'm well connected), probably root detected.. thanks ! (ofc it's on the deny list, with magisk modules such as Universal Safetynet Fix, zygisk ....)
And edit 2 : I forgot to thank you for this thread !

Common way to flash rom with upgrade (not update) is clean install.
Also, magisk handles safetynet with no problem. No need for that. And zygisk is not module.
For that specific application, check that it is fully selected in zygisk since sometimes all checkboxes for application is not selected.
You're welcome