I flashed realme x2 pro stock rom C. 38, I forgot to format data and clicked on reboot to recovery. It showed.. Your (Boot/recovery) destroyed ..then I went to fastboot mode... Tried to flash twrp. And vbmeta from PC... It showed successful... But still I'm not able go to recovery.... And I'm stuck in fastboot mode... Can anybody help??
I am having the exact same issue, can anyone help with this.
Related
Hey there, I need help. I tried to flash latest twrp for Mi A2 but after flashing everything seems fine on command window but phone isn't booting in recovery mode. Either it get normal boot or get switched off completely , even if I try to boot into recovery by using volume up and power button , it shows 'no command' . I tried to flash magisk and it worked, but after every boot it root is getting lost automatically.. please help.. thanks
Amnvlad said:
Hey there, I need help. I tried to flash latest twrp for Mi A2 but after flashing everything seems fine on command window but phone isn't booting in recovery mode. Either it get normal boot or get switched off completely , even if I try to boot into recovery by using volume up and power button , it shows 'no command' . I tried to flash magisk and it worked, but after every boot it root is getting lost automatically.. please help.. thanks
Click to expand...
Click to collapse
Yes it's not easy to flash twrp on mi a2 , don't know why. What you do is go to this link (https://twrp.me/xiaomi/xiaomimia2.html) and download both .img and .zip file from there. Then get into fastboot mode and do the command -
fastboot boot twrp.img
Then it will boot into TWRP. And then flash TWRP.zip file and it will flash it permanently to your device. This step is mandatory so the stock recovery doesn't come back.
Hope this works !! Let me know if it helps !!
I had the bootloader unlocked with TWRP as recovery, the device was bricked in the Realme logo (loop), I decided to lock the bootloader and now it does not boot into the fastboot mode.
Now I have a loop "the current image (boot / recovery) have been destroyed and can not boot. Please flash the correct image or contact costumer service to fix it"
Please help me!!! i can't boot into the fastboot mode to unlock the bootloader and install TWRP again!!!
Hi
At the moment there is no solution, since it really has not released the flashable firmware through qpst tools
Have you tried flashing a stock rom image? Global versuon?
eden8707 said:
I had the bootloader unlocked with TWRP as recovery, the device was bricked in the Realme logo (loop), I decided to lock the bootloader and now it does not boot into the fastboot mode.
Now I have a loop "the current image (boot / recovery) have been destroyed and can not boot. Please flash the correct image or contact costumer service to fix it"
Please help me!!! i can't boot into the fastboot mode to unlock the bootloader and install TWRP again!!!
Click to expand...
Click to collapse
If you have the bootloader unlocked I can help you, if there is no solution I think
Enviado desde mi RMX1931 mediante Tapatalk
eden8707 said:
I had the bootloader unlocked with TWRP as recovery, the device was bricked in the Realme logo (loop), I decided to lock the bootloader and now it does not boot into the fastboot mode.
Now I have a loop "the current image (boot / recovery) have been destroyed and can not boot. Please flash the correct image or contact costumer service to fix it"
Please help me!!! i can't boot into the fastboot mode to unlock the bootloader and install TWRP again!!!
Click to expand...
Click to collapse
Thats Why in the other Thread they told us not to Lock THE BOOTLOADER or it would give a HARD BRICK
im using realme x2 pro. and i have same problem
Sergiocubano1 said:
If you have the bootloader unlocked I can help you, if there is no solution I think
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
and i flash orange fox recovery by using adb
fastboot flash recovery ******.img
and
fastboot flash vbmeta vbmeta.img
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
and you must work to boot to recovery mode
download the rom for RMX1931 and put it in your phone
flash it with orange fox recovery
and clear data after flashing rom is very important step
and the phone work
Miroyas said:
im using realme x2 pro. and i have same problem
and i flash orange fox recovery by using adb
fastboot flash recovery ******.img
and
fastboot flash vbmeta vbmeta.img
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
and you must work to boot to recovery mode
download the rom for RMX1931 and put it in your phone
flash it with orange fox recovery
and clear data after flashing rom is very important step
and the phone work
Click to expand...
Click to collapse
You don't get it do you.
He locked the bootloader after he got this message "the current image (boot / recovery) have been destroyed and can not boot. Please flash the correct image or contact costumer service to fix it".
He cannot boot into bootloader to do what you say he needs to do.
I had that error message, the only solution is to take it to Realme service center.
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!
Hello,
As long as you have access to fastboot mode, am sure you can recover your device.
You need to download the official ROM that corresponds to your specific devices. If it is global version, download the global version.
Also, before flashing, make sure you unlock the bootloader.
jaybirdxyz said:
Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
this temporarily boots you into TWRP so you can reflash TWRP again. with this method the TWRP will be deleted once you reboot si you need to reflash TWRP in TWRP. then dont reboot, flash a Good working rom.
Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
ai5g said:
Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
try other TWRP images? or your boot partition fried?
fastboot flash boot twrp.img and see What happens
ok heres where i am in slot a i have twrp recovery and fastboot im not able to boot into system slot b i have fastboot and stock poco recovery and stuck in a poco screen bootloop if im not booted into one of the previously mentioned slots my phone is recognized by my computer i go on every flash tool i could find none work with every one it throws an error i need the files and the commands to fastboot these images can you help me please im not to fluent in fastboot
POCO M4 PRO 5G
this is the error i get on the flash tool
It's fixed thanks @NOSS8