Database Develop

Lost TWRP and system after flash custom rom

Hi guys,
I flash Havoc-OS on Mi9T Pro Global PFKMIXM 10.3.1 by TWRP, after reboot do not start system and not enter on TWRP again.
I try this commands on fastboot below.
Code:
adb devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
fastboot reboot recovery
Can anyone give me a help?
Thanks.

fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.

S3miniFin said:
fastboot devices
fastboot flash recovery recovery.img
> now just push volume up + power to boot to twrp. (those boot and reboot not working some reason always)
... i tried use same custom rom, but fail also. Then i test LineageOS, that boot normally. I used EUxxx ROM before and after. I just got enought to test custom roms so far.
Click to expand...
Click to collapse
Hi friend, mainly thanks for helping.
I tried your suggestion, but it doesn't work.
I restored with Mi Flash Tolls, the only alternative. Now it works well.
You will now try the Flash I Rom and waiting for new updates and then flash any custom rom.
After I want share stuff tools and congratulations.
Have nice guys!

I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
E:\Downloads\Mobile Phone\ADB>fastboot flash recovery twrp-3.3.1-13-raphael-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.400s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.732s
E:\Downloads\Mobile Phone\ADB>
Click to expand...
Click to collapse

Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
Yes, that's what happened to me.
The only solution I found was to install the new rom via fastboot.
For this you will need to perform the following steps:
1 - Install Mi Flash + drivers (this is boring, if you have Windows 7, it will be easier). In this link you will find some downloads and more details.
2 - Download the Sotck Rom (for fastboot important) from your device, in my case it was PFKMIXM 10.3.1 for Mi9T Pro. You need to extract zip then before.
3 - Flash the new rom via fastboot (approximately 10 minutes).
After that, your device will start with the new rom, then you can flash TWRP again and everything will work. The Magisk installation may cause error 1, but only flash boot.img through TWRP.
Be quick, because if the battery drain, you won't be able to start it in fastboot again.
If you need any links, ask me. I didn't have time to share everything.
Have a nice and good luck!!

Madaz2 said:
I have the same stuck in fastboot No recovery img, no rom loaded so cant use XiaoMiTool
I booted into TWRP but it didnt ask me for my dycrpt password or somehow i wasnt paying attention and when in with cancel.
I was preparing to flash a new ROM so i wiped all but user data then went to flash my ROM and found i was in the wrong partition
so i rebooted TWRP back into recovery but it booted to fastboot
once i realised i had no recovery i tried flashing again it says it passes but doesnt boot to recovery?
any ideas please.
Click to expand...
Click to collapse
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)

rodolphe06 said:
To boot to recovery After fastboot flash recovery , you will need also a system...
As you wiped all, you dont have anymore. I made the same mistake when decrypting After unlocking.
Extract system.img from stock fastboot rom and fastboot flash system system.img.
Then again (why not lol) fastboot flash again reco and reboot to recovery with buttons.
If it dont work , miflashtool will recover it ( DONT SELECT CLEAN_LOCK)
Click to expand...
Click to collapse
Yes, very important.
In Mi Flash, check only "Clean All" dont clean and lock.
Thanks.

thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower

Madaz2 said:
thanks, hopefully i didnt break it further as i accidently flashed a global indian ROM when i should have flashed CN
now my only option might be EDL via testpoint, i have a mate who can help i will try and find the right version CN rom tonight and go slower
Click to expand...
Click to collapse
Thank you for sharing your experiences.
Too bad you couldn't recover. I hope you can do it again.
Today I had to flash twice, once because I flashed Kernel Quax and couldn't rollback and once for trying Rom Syberian. I hope that in the future we will have a firmware balanced with the customs kernel and roms.
Good luck.

Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.

Madaz2 said:
Thanks I dont think it will work
i bought a Deep flash cable to see if i can get it into EDL mode without opening.
Click to expand...
Click to collapse
With flash cable or have you open?

Hot-Proton said:
With flash cable or have you open?
Click to expand...
Click to collapse
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL

Madaz2 said:
with flash cable, have to wait for it to arrive now.
if that doesn't work i will have to open and do EDL
Click to expand...
Click to collapse
I think works, for me it was like this.
Have nice.

Mi A2 rooting issue! Help urgently

I just unlocked bootloader, flashed boot image and twrp image(temporary) from pc but when i come to my device mi a2 in twrp mode the twrp is unable to read the twrp image or magisk zip. I can see then when i go to file manager in twrp but when i am in flashing screen they just don't appear and other files names are also changed. Is there something missing. I used unlock bootloader and fastboot boot --.img . I am in November patch and my only reason to root was i am not getting further updates after November 2018. So pls help guys

Do this after unlocking critical unlock.. Your storage is encrypted just boot to twrp and do a factory reset under wipe->Format data then type yes!! now your storage will be ready to use as normal then copy your files to phone through pc Don't forget to unlock critical otherwise you cant able to flash stock rom if anything goes wrong

Sivakumar$ said:
Do this after unlocking critical unlock.. Your storage is encrypted just boot to twrp and do a factory reset under wipe->Format data then type yes!! now your storage will be ready to use as normal then copy your files to phone through pc Don't forget to unlock critical otherwise you cant able to flash stock rom if anything goes wrong
Click to expand...
Click to collapse
Thanks for the reply! I have already flashed boot img will there be no problem if i use unlock critical now? I have formatted data though

just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk

Sivakumar$ said:
just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk
Click to expand...
Click to collapse
Where can i get stock boot img. I have been searching and all post are about patched boot img

Sivakumar$ said:
just flash the stock boot img and do unlock critical and then do all the flashing stuffs if you dont want to be taking any risk
Click to expand...
Click to collapse
Hey bro please reply as soon you can i have been waiting for weeks stuck here . Is the process of flashing boot image same as patched boot image? I have to keep the boot image in patched boot image folder and flash using same code?

sourav56 said:
Hey bro please reply as soon you can i have been waiting for weeks stuck here . Is the process of flashing boot image same as patched boot image? I have to keep the boot image in patched boot image folder and flash using same code?
Click to expand...
Click to collapse
It's the same process. Flash stock boot.img then unlock critical. You flash stock boot and patched boot the same way. You can keep patched boot.img in same folder just change the code in flashing command flash boot.img to flash patched boot.img. If I recall correctly.

Files changed because you are encrypted flash DM-Verity to decrypt your file or do a wipe in internal.

Accidentally flashed TWRP in boot partition.

So..I was trying to unlock the bootloader using the fastboot commands. When it was all done and I was booted into TWRP, I flashed the TWRP image onto the boot partition instead of the recovery partition. Realizing my mistake seconds after, I flashed TWRP onto the recovery partition as well. Now everytime I try to boot my device, you guessed it, it opens up TWRP instead.
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?) or should I just flash Pixel experience rom and it will change the partition according to its needs?
I am kinda worried..Hopefully, the device is fixable. Thank You.

BungeeWatcher47 said:
So..I was trying to unlock the bootloader using the fastboot commands. When it was all done and I was booted into TWRP, I flashed the TWRP image onto the boot partition instead of the recovery partition. Realizing my mistake seconds after, I flashed TWRP onto the recovery partition as well. Now everytime I try to boot my device, you guessed it, it opens up TWRP instead.
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?) or should I just flash Pixel experience rom and it will change the partition according to its needs?
I am kinda worried..Hopefully, the device is fixable. Thank You.
Click to expand...
Click to collapse
"If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."
https://twrp.me/xiaomi/xiaomimia2.html

ahenaol said:
"If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."
Click to expand...
Click to collapse
I used
fastboot boot *path of twrp.img*
to boot twrp on my phone, i guess that is called side loading? after that, when TWRP opened up, I copied the twrp.img into my storage. After that, I was supposed to flash that image onto the recovery partition by using the sideloaded TWRP but instead I flashed it onto the boot partition. I hope that is a bit clearer..anyway, even in this case will I have to flash the stock rom before trying anything else?

BungeeWatcher47 said:
I used
fastboot boot *path of twrp.img*
to boot twrp on my phone, i guess that is called side loading? after that, when TWRP opened up, I copied the twrp.img into my storage. After that, I was supposed to flash that image onto the recovery partition by using the sideloaded TWRP but instead I flashed it onto the boot partition. I hope that is a bit clearer..anyway, even in this case will I have to flash the stock rom before trying anything else?
Click to expand...
Click to collapse
You could try flashing just the boot.img file from stock image.

BungeeWatcher47 said:
... flashed TWRP onto the recovery partition as well.....
Click to expand...
Click to collapse
What do you mean here? There is no "recovery partition" in A/B slots structure of MiA2. Or did you totally reformated partitions?
BungeeWatcher47 said:
Previously I was using the Stock android 10 ROM with March's security update. I was wondering if there's a way to fix this? Maybe flashing the boot.img will fix this(if yes, then can one of you take a backup of yours and upload it, please?)...
Click to expand...
Click to collapse
Yes, If you were on stock A 10 march (11.0.6.0), and never re-paritioned device, then you can restore OS fasboot-reflashing stock 10.0.6.0 boot image to the slot you were using previously with 11.0.6.0 (and, btw, try to remember what was and is now in the opposite slot). I've uploaded 11.0.6.0 bbot images to: https://forum.xda-developers.com/showpost.php?p=82166125&postcount=58
BungeeWatcher47 said:
... or should I just flash Pixel experience rom and it will change the partition according to its needs?
Click to expand...
Click to collapse
Sorry, I'm on stock and never went deep into nuances of custom ROMs partitioning.

Aerobatic said:
What do you mean here? There is no "recovery partition" in A/B slots structure of MiA2. Or did you totally reformated partitions?Yes, If you were on stock A 10 march (11.0.6.0), and never re-paritioned device, then you can restore OS fasboot-reflashing stock 10.0.6.0 boot image to the slot you were using previously with 11.0.6.0 (and, btw, try to remember what was and is now in the opposite slot). I've uploaded 11.0.6.0 bbot images to: https://forum.xda-developers.com/showpost.php?p=82166125&postcount=58
Sorry, I'm on stock and never went deep into nuances of custom ROMs partitioning.
Click to expand...
Click to collapse
When you try to flash a image in TWRP, it gives you multiple options on the next screen. Namely, boot, vendor, system, data, recovery. I had flashed that TWRP.img into my boot slot lmao. It messed everything up. Your stock boot images have been saving me in multiple pinches.

Hello, thats my first entry in XDA forum. I did the same mistake with my mi9 and i have no idea how to fix it. Could someone help me, i hope i didn't killed it.
... i installed the mi 9 rom --> solved the problem

Accidentally flashed TWRP in the boot partition

Hello,
So I did a mistake by flashing TWRP into the boot partition... Now whenever I reboot my phone it enters TWRP. How can I fix that or is it bricked? I can't find anywhere on the Internet stock boot images, only some modded kernels or something like that. Can anyone tell me how can I get stock boot.img and flash it so that I can use my phone again?

Aspect13 said:
Hello,
So I did a mistake by flashing TWRP into the boot partition... Now whenever I reboot my phone it enters TWRP. How can I fix that or is it bricked? I can't find anywhere on the Internet stock boot images, only some modded kernels or something like that. Can anyone tell me how can I get stock boot.img and flash it so that I can use my phone again?
Click to expand...
Click to collapse
Downllad zip or tgz file for your extract firmware, ectract boot img and then flash by fastboot to boot

Question How to fastboot into reboot recovery?

I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
fastboot flash recovery recovery.img
fastboot reboot bootloader
and then select Recovery using Vol-Up/Down buttons + Power button to start the recovery ROM
Click to expand...
Click to collapse
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot
Click to expand...
Click to collapse
fastboot flash recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
fastboot boot twrp.img
Click to expand...
Click to collapse
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance

escalhavardo said:
I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance
Click to expand...
Click to collapse
hi
I think the arraki's TWRP on xda cannot be started.
Better to use orangeFox.
There is no Recovery partition on this phone, so we use "fastboot flash boot recovery.img".

I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot

escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Click to expand...
Click to collapse
Use Xiaomi Flash Tool.
If you can get into fastboot mode, you can restore.
Then do the following. or give up.
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot

escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot
Click to expand...
Click to collapse
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.

kousuke5555 said:
6.Select "Slot A is active"
Click to expand...
Click to collapse
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
Thank you so much, you're a lifesaver.

escalhavardo said:
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
thank you so much, your a life saver.
Click to expand...
Click to collapse
Go back to fastboot
"fastboot set_active a"
1.fastboot getvar current-slot
2.if the result is slot a.(slot a in which the system boots)
3.fastboot set_active b
4.fastboot flash boot_b New_fox.img
5.fastboot reboot recovery
6.Select "Flash current OrangeFOX" in menu (automatically flash to both slot a/b )
7.Select "back"
8.Select "reboot" in menu
9.Select "Slot A is active"
10.reboot

You solved my problem. Thank you so much for all your help. You're a life saver.

kousuke5555 said:
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.
Click to expand...
Click to collapse
Can you send me unlocked bootloader backup of poco m4 pro 5g i just locked it and i can't unlock it now because my phone is bricked and it's showing nv data is corrupted if you have solution on this plz share it.

delete

kousuke5555 said:
hi
We can't solve boot loops with the bootloader locked.
Please go to the service center.
Had you backed up seccfg.img, you could have unlocked it again.
However, it is specific to each device.
I can't send.
Click to expand...
Click to collapse
Do you have any other solution to this error "nv data is corrupted"

delete

It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.

V0latyle said:
It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.
Click to expand...
Click to collapse
hi
Unfortunately, some models of xiaomi cannot use the fastboot "boot" command.
The method mentioned in the thread here is a last resort.
I've talked to some developers but they don't accept this method.
sad.
However, there is no thread in xda, but the developer made twrp, so I think we should use it.

shanawgray said:
Do you have any other solution to this error "nv data is corrupted"
Click to expand...
Click to collapse
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.

kousuke5555 said:
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.
Click to expand...
Click to collapse
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?

shanawgray said:
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?
Click to expand...
Click to collapse
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.

kousuke5555 said:
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.
Click to expand...
Click to collapse
thanks.....!
but I think I got the solution

For those looking at this thread.
Just in case, I'll mention it below.
This article is about "arraki's" TWRP and orangefox.
Information is old.
there's a new TWRP, so any troubles or questions should be resolved in that TWRP thread.
Thank you