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
Related
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
revery0 said:
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
Click to expand...
Click to collapse
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
arthios said:
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
Click to expand...
Click to collapse
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
revery0 said:
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
Click to expand...
Click to collapse
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
87insane said:
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
Click to expand...
Click to collapse
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
revery0 said:
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
Click to expand...
Click to collapse
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
87insane said:
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
Click to expand...
Click to collapse
Thank you but I already did flash the official recovery image, both extracted from a factory update.app and your recovery.IMG also... None of them worked.... Iam still in the same bootloop.
I am starting to believe that the partitions have been ****ed up.
Any way to repartition?
Also is there a procedure to create a flashable zip with huawei software extractor? I edited the accompaning XML to add the p7 device on the list (copy data from p6 and changed the name) created the zip but fastboot doesn't flash the zip because its missing 2 XML files which I can't remember their name.
And at this point I would like to give my 2 cents of advice to everyone who might listen,
Before you flash anything from a microsd, first verify the card with h2testw, and always use high quality microsd and never ever stop a flashing procedure by any means. . i would like to make it more extreme and advise to use a software with copy verification (like richcopy) when you copy files that are going to be flashed.
I tend to believe that a faulty microsd is the cause of my problems... Even though I checked the microsd afterwards and didn't got any errors.
I would advise the ROM creators to append this on their posts!
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.
I'm getting stuck on fastboot mode everytime i flash derpfest rom , i've tried ''fastboot reboot'' i've tried to install ''twrp'' or boot to it , nothing works everything i try takes me back to the fastboot logo although the install of the rom was succesfull , i've tried with TWRP-3.3.1-8-siankatabg and also with regular TWRP and also with ORANGE FOX recovery , i'm on miui 11.0.7 EU version , can anyone help me
In TWRP, format data and then flash derpfest ROM. Take note that your data will be wiped though.
sangbuana said:
In TWRP, format data and then flash derpfest ROM. Take note that your data will be wiped though.
Click to expand...
Click to collapse
I did just that I placed the ROM in /tmp/ using TWRP file manager then I formated system and cash and data and then I did the data format by writing "Yes" then went back and erased everything a second time for good measure but still after flashing the ROM I get stuck on fastboot with no ability to boot to recovery or use commands like "fastboot reboot" the only solution for me that time is to reuse mi flash to flash stock rom which doesn't work but lets me boot into recovery which i use to flash miui 11.0.7 zip which apparently works just fine .
Also the basics are covered I made sure to allow usb debuging and update TWRP and all of that
1. flash using miflash
2.setup ur phone
3.enable dev optmake sure oem unlock too
4.going for twrp
5. wipe
6. flash ur rom
7.dont go reboot to system
8.format data then rebot to system
In case nothing else helps you can try to flash vbmeta first, following these instructions.
Cheers
Toscha
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Did you type on your pc fastboot reboot as a final step? Maybe you have to repair or reflash the stock rom using miflash and try again (you cant clear cache without twrp) as a way to get the system prepared to Flash a modified boot image
I have the exact same problem. I tried older versions of Magisk, then the Canary build, but nothing helped..
Bilihh said:
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Click to expand...
Click to collapse
Found a solution! It's right here:
How to flash twrp recovery and root redmi note 10s?
I can't install a twrp recovery if I tried A message appears (remote : this partition doesn't exist)
forum.xda-developers.com