Database Users

6.0.1 - How to flash?

I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.

i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I

nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.

how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img

ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.

nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?

ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.

nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.

I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.

nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:

kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol

nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message

kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!

I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61

kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?

Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol

I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?

MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery

Losing root after rebooting (6.0.1 with SuperSU 2.61 & 2.62)

I've been trying to get help on this matter. I've followed every step to get this resolved other than a factory restore at this point.

GloriousGlory said:
I've been trying to get help on this matter. I've followed every step to get this resolved other than a factory restore at this point.
Click to expand...
Click to collapse
Tell us more. What ROM are you running? Are you on 6.0 or 6.0.1? If on 6.0.1 tells us how you got there. It's the little things that help.

Mr Patchy Patch said:
Tell us more. What ROM are you running? Are you on 6.0 or 6.0.1? If on 6.0.1 tells us how you got there. It's the little things that help.
Click to expand...
Click to collapse
I'm on Stock 6.01. I flashed everything from fastboot (boot.img, bootloader, cache.img, radio, recovery.img, system.img, twrp.img, and vendor.img) and afterwards I went directly into recovery (twrp) and flashed supersu 2.62.
Process:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Then did fastboot flash recovery twrp.img
Boot directly into recovery, flash supersu 2.62, reboot system (DO NOT INSTALL).
Everything works GREAT, then you reboot (power off) and lose root. have to boot into recovery and reflash supersu every single time.

GloriousGlory said:
I'm on Stock 6.01. I flashed everything from fastboot (boot.img, bootloader, cache.img, radio, recovery.img, system.img, twrp.img, and vendor.img) and afterwards I went directly into recovery (twrp) and flashed supersu 2.62.
Process:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Then did fastboot flash recovery twrp.img
Boot directly into recovery, flash supersu 2.62, reboot system (DO NOT INSTALL).
Everything works GREAT, then you reboot (power off) and lose root. have to boot into recovery and reflash supersu every single time.
Click to expand...
Click to collapse
If I'm seeing this correctly, it looks like you didn't flash userdata? So you won't lose data correct?
Maybe you should try flashing this first, http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
then flash 2.61. See what happens.

Mr Patchy Patch said:
If I'm seeing this correctly, it looks like you didn't flash userdata? So you won't lose data correct?
Maybe you should try flashing this first, http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
then flash 2.61. See what happens.
Click to expand...
Click to collapse
I'll give it a try.
Edit: Didn't work

Ok it's strange, on some reboots its fine on some it unroots.

GloriousGlory said:
Ok it's strange, on some reboots its fine on some it unroots.
Click to expand...
Click to collapse
What's telling you it's not rooted?

Mr Patchy Patch said:
What's telling you it's not rooted?
Click to expand...
Click to collapse
Supersu app "There is no SU binary installed"
Okay so first reboot lost root. second boot good, third boot good, fourth boot lost root, fifth boot good.

I'm seeing the same. After flashing 2.62-3, root is fine on 1st and 2nd boot. After that, "...no SU binary installed". Tried reflashing 2.62-3, same results.

snovvman said:
I'm seeing the same. After flashing 2.62-3, root is fine on 1st and 2nd boot. After that, "...no SU binary installed". Tried reflashing 2.62-3, same results.
Click to expand...
Click to collapse
Same here. On 6.0.1
Sent from my Nexus 6P using Tapatalk

For those who are seeing this issue, what was the disposition of your phone prior to this?
For me, I was on 6.0.0 using traditional root (2.52). I fastbooted to 6.0.1 and used 2.62, then 2.62-3 right on top.
I'm in the process of re-fastbooting boot.img, system.img and flashing 2.62-3 to see if it makes a difference.

You need to run the unroot zip before you use the systemless.

Gytole said:
You need to run the unroot zip before you use the systemless.
Click to expand...
Click to collapse
I thought unroot.zip was used for those that were using traditional (2.52 and pre) root? AFAIK, the zip simply removes the pieces left by system root. If there was nothing written to /system in the first place, what benefit would unroot.zip provide? The OP did flash unroot.zip and it didn't help him.
In this post, the instructions explain that if you're coming from 2.60, you can simply flash newer versions right on top (since nothing was written to /system in the first place). If you're coming from system root, reflashing the image will wipe out all the root modifications and allowing one to go systemless.
I did reflash boot and system, then 2.62-3. Same problem--on the 3rd boot, root goes away.

snovvman said:
I thought unroot.zip was used for those that were using traditional (2.52 and pre) root? AFAIK, the zip simply removes the pieces left by system root. If there was nothing written to /system in the first place, what benefit would unroot.zip provide? The OP did flash unroot.zip and it didn't help him.
In this post, the instructions explain that if you're coming from 2.60, you can simply flash newer versions right on top (since nothing was written to /system in the first place). If you're coming from system root, reflashing the image will wipe out all the root modifications and allowing one to go systemless.
I did reflash boot and system, then 2.62-3. Same problem--on the 3rd boot, root goes away.
Click to expand...
Click to collapse
Didja flash the modified 29M boot img or the stock from factory img...

Gytole said:
Didja flash the modified 29M boot img or the stock from factory img...
Click to expand...
Click to collapse
The purpose of systemless root SuperSU is to patch the factory boot image. A modified boot image is used to allow for system root. This thread is discussing systemless root using SuperSU to patch the factory image. As the OP described, we are flashing the factory image. Don't know what you're asking.

snovvman said:
The purpose of systemless root SuperSU is to patch the factory boot image. A modified boot image is used to allow for system root. This thread is discussing systemless root using SuperSU to patch the factory image. As the OP described, we are flashing the factory image. Don't know what you're asking.
Click to expand...
Click to collapse
I had a problem before flashing the modified for some reason. But never mind.

See my post here. I found the modified kernel to allow for system root. Until the lost of root issue is resolved, system root is a good alternative.
Just fastboot the modified boot, reboot into TWRP (using the phone keys, NOT fastboot reboot), flash SuperSU 2.52, and you should be good to go. Be sure to backup beforehand and wipe cache/dalvik for good measure.

[HELP] Uninstalling Magisk

every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?

die.henrique said:
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
Click to expand...
Click to collapse
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image

emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
but will not this reset the device? can I flash the stock boot.img without erasing the data?

die.henrique said:
but will not this reset the device? can I flash the stock boot.img without erasing the data?
Click to expand...
Click to collapse
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"

emiljano539 said:
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?

die.henrique said:
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
Click to expand...
Click to collapse
You should download the boot.img for mi a1 which corresponds with your update. For ex. boot.img of january rom.

device not found in adb fasboot after uninstall magisk
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.

caan90 said:
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
Click to expand...
Click to collapse
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly

emiljano539 said:
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
Click to expand...
Click to collapse
Thank you so much... it work.. my mi a2 just come back to life..

caan90 said:
Thank you so much... it work.. my mi a2 just come back to life..
Click to expand...
Click to collapse
I'm glad it worked. Make sure you leave a like in my comment if it was useful . Peace

my mi a2 is not detect in adb and in fastboot too what can i do

I need help with twrp ASAP please

I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.

willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)

willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..

SomethingWentWrong said:
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
Click to expand...
Click to collapse
Fastboot mode

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
I'll give that a shot, thanks!

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
Oh man you're a life saver! Worked perfectly! Thanks so much!

willineedhelp said:
Oh man you're a life saver! Worked perfectly! Thanks so much!
Click to expand...
Click to collapse
Glad to know I was able to help, it happens with me and this is how I fixed ?

Hello! Had the same problem and the procedure let me access recovery, yet everytime I reboot to system, the phone opens recovery instead.
I tried restoring a backup but rom is unstable and stuff keeps crashing. Any ideas?
EDIT: did a fastboot flash of .9 ROM and at got it back to work.

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!

willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Nvm, I just had a junk TWRP version.

willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
What MIUI version you have tried to go back?

👁️TWRP(SHARED)LIST OF TWRP A11/A12

Developed By :Skkk
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/lmi/

New version A12
https://androidfilehost.com/?w=files&flid=318240

Update
twrp-3.6.2_12-v3.8.2_A12-lmi-skkk​https://androidfilehost.com/?w=files&flid=318240

updated today

updated today

update Aug 02

Updated today
https://androidfilehost.com/?w=files&flid=318240

Updated Aug 11
https://androidfilehost.com/?w=files&flid=318240
,

Updated today
https://androidfilehost.com/?w=files&flid=318240

NOSS8 said:
Updated today
https://androidfilehost.com/?w=files&flid=318240
Click to expand...
Click to collapse
I?m doing a first flash and trying to figure out which to choose, what's the difference between the two versions?

oroboros74 said:
I?m doing a first flash and trying to figure out which to choose, what's the difference between the two versions?
Click to expand...
Click to collapse
One for Android 11 and one for Android 12.
V3.1.A11
V5.6.A12

Update:
https://androidfilehost.com/?w=files&flid=318240

@NOSS8
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com

jason88fr said:
@NOSS8
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
Click to expand...
Click to collapse
I put androidfilehost links to avoid any download errors.

Hello, I'm newbie
How to instal it for the first time? my boot loader already unlock

hiGoldsss said:
Hello, I'm newbie
How to instal it for the first time? my boot loader already unlock
Click to expand...
Click to collapse
Install TWRP via Fastboot mode
Download TWRP
rename it to twrp.img
open a command CMD
fastboot flash recovery twrp.img
fastboot boot twrp.img
or power shell
./fastboot flash recovery twrp.img
./fastboot boot twrp.img

that TWRP can flash into all devices?

NOSS8 said:
Install TWRP via Fastboot mode
Download TWRP
rename it to twrp.img
open a command CMD
fastboot flash recovery twrp.img
fastboot boot twrp.img
or power shell
./fastboot flash recovery twrp.img
./fastboot boot twrp.img
Click to expand...
Click to collapse
the new TWRP can be flashed on all devices?

hiGoldsss said:
that TWRP can flash into all devices?
Click to expand...
Click to collapse
You post on the Poco f2/k30 pro thread, I assume you have this device, don't you?

Update V6.3 A12
https://dl.akr-developers.com/?file...0Pro-POCOF2Pro_v6.3_A12-lmi-skkk_69ee5455.zip