Develop Bugs

stuck on HTC logo

Suddenly my phone stopped working. On this morning i wanted to turn it on and found, that it is stuck on htc logo.
Phone is locked and s-on. Hboot is 0.98
I still can enter bootloader and fastboot.
fastboot.exe getvar mainver
mainver: 6.04.605.07
I've tried factory reset, but nothing.
When i've tried commands:
fastboot erase cache
fastboot oem rebootRUU
- On every command my phone just hangs. I can't navigate thought menu by vol+up/down buttons. It stays on last option, which i chose. Only pulling out battery helps.
What can i try else? Or maybe it is hardware problem?

Shugard seenLial
I've unlocked bootloader with htcdev.
And now, for example when trying to flash recovery
fastboot.exe flash recovery recovery-clockwork-5.0.2.0-vivow.img
sending 'recovery' (3722 KB)... OKAY [ 1.144s]
writing 'recovery'...
And phone hangs in this time.

Keen16 said:
I've unlocked bootloader with htcdev.
And now, for example when trying to flash recovery
fastboot.exe flash recovery recovery-clockwork-5.0.2.0-vivow.img
sending 'recovery' (3722 KB)... OKAY [ 1.144s]
writing 'recovery'...
And phone hangs in this time.
Click to expand...
Click to collapse
To flash recovery you need to flash the recovery .img file not an .exe
Sent from my ADR6350 using xda app-developers app

FordNate said:
To flash recovery you need to flash the recovery .img file not an .exe
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Is recovery-clockwork-5.0.2.0-vivow.img an .exe file ?

Keen16 said:
Is recovery-clockwork-5.0.2.0-vivow.img an .exe file ?
Click to expand...
Click to collapse
no. the recovery-clockwork-5.0.2.0-vivow.img is what you want to flash through ADB while the phone is in fastboot connected to the PC with a cable

[Q] Won't boot - won't recover[HALF-SOLVED] just won't boot now

HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:

freedom74 said:
HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:
Click to expand...
Click to collapse
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img

Thant said:
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img
Click to expand...
Click to collapse
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?

freedom74 said:
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?
Click to expand...
Click to collapse
Yes. depend what you want to install I prefer Philz 5.15.9 there mount sd card work perfect.

Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?

freedom74 said:
Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?
Click to expand...
Click to collapse
change usb cable or usb port on the computer. Maybe faulty cable
@freedom74 what is your batter-voltage now?

Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...

freedom74 said:
Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...
Click to expand...
Click to collapse
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery

Thant said:
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery
Click to expand...
Click to collapse
The one you suggest... Philz 5.15.9
Code:
C:\adb>fastboot getvar battery-voltage
battery-voltage: 3976mV
finished. total time: 0.172s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\adb>
Stuck again, but now on "htc quietly brilliant" screen

freedom74 said:
The one you suggest... Philz 5.15.9
Click to expand...
Click to collapse
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
@freedom74 you must to put recovery.img and boot.img in your fastboot folder and then flash it

Thant said:
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
Click to expand...
Click to collapse
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Thant said:
you must to put recovery.img and boot.img in your fastboot folder and then flash it
Click to expand...
Click to collapse
@Thant As you can see from terminal output, that is the case.

freedom74 said:
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Click to expand...
Click to collapse
maybe bad download on the recovery try download again or flash TWRP2.8.0

Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...

freedom74 said:
Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...
Click to expand...
Click to collapse
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery

Thant said:
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery
Click to expand...
Click to collapse
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays

freedom74 said:
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays
Click to expand...
Click to collapse
no I am sure you don't do something right try again redownload CWM or TWRP check the MD5SUM then flash it don.t flash boot.img.
1. Delete all img files from your fastboot folder
2. Paste only your ecovery.img file there and rename it to recovery.img
3. run fastboot flash recovery recovery.img
4. run fastboot erase cache
5. Powerdown the power from bootloader manu and disconnect the phone from computer
6. Press and hold volume down and then press and hold power button until you go in bootloader, choice recovery and press power button
7. Report
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive

Thant said:
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive
Click to expand...
Click to collapse
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...

freedom74 said:
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...
Click to expand...
Click to collapse
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone

Thant said:
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
Click to expand...
Click to collapse
As I wrote eariler, I've done exactly as you said.
I know the combo for entering bootloader and I know it suppose to be first VolDn and then Power.
My Power+VolUp in previous post does not show the order I pressed the key. Sorry for me not being clear enough.
Thant said:
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone
Click to expand...
Click to collapse
I am disconnecting, but since you wrote
5. Powerdown the power from bootloader manu AND disconnect the phone from computer
Click to expand...
Click to collapse
I was follow that order, first powerdown from menu and then disconnect.
In that case red LED turn on before I was able to disconnect the USB cable.
I will try to first disconnect USB cable so that phone goes back from FASTBOOT USB into just FASTBOOT and then power down from menu.
And then VolDn+Power to enter bootloader and recovery.
My battery drop to 3.700mV so I need to recharge it a while.
p.s.
Thanks for your help and time.

No progress. Always ending at "htc quietly brilliant" screen.
I will try different recoveries with same steps but I don't see why would other work
when twrp 2.8.0.0 with good md5sum does not.
Code:
C:\Android>fastboot.exe getvar battery-voltage
battery-voltage: 3698mV
finished. total time: 0.109s
C:\Android>fastboot.exe flash recovery recovery.img
sending 'recovery' (6536 KB)...
OKAY [ 0.842s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.577s]
finished. total time: 1.420s
C:\Android>fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\Android>

Question OP9P stuck in fastboot mode, no OS or recovery Help!

I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.

Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.

oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery

eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then

Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.

RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back

Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.

eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps

IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.

Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.

IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz

Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.

Xiaomi Mi 10 Lite - Recovery mode

Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10

stephane_p said:
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
Click to expand...
Click to collapse
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup

Spuffyffet said:
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Click to expand...
Click to collapse
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.

stephane_p said:
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
Click to expand...
Click to collapse
However, it's still not working. I have the same issue.

stephane_p said:
However, it's still not working. I have the same issue.
Click to expand...
Click to collapse
well use "fastboot reboot recovery"

Spuffyffet said:
well use "fastboot reboot recovery"
Click to expand...
Click to collapse
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here

stephane_p said:
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
Click to expand...
Click to collapse
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)

Spuffyffet said:
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Click to expand...
Click to collapse
I downloaded platform-tools zip file (r33.0.0 for windows) and extract it in C:\Android\platform-tools
Then, I retry
C:\Android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 5.415s]
Writing 'recovery' OKAY [ 0.586s]
Finished. Total time: 6.017s
C:\Android\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But, I still get the fastboot screen instead of recovery mode.
Thank you for your help.

Have you tried with another recovery image, like TWRP ?

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
well i have and it worked for me

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

stephane_p said:
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using the wrong command bro, don't use boot. Use "fastboot flash recovery twrp_recovery.img". Why are you flashing recovery.img as boot bro?

OK guys I've found my mistake. I thought the model of my phone was Monet. But it's not. It's Toco... A stupid error showing that I have to be more rigorous.
I thank you again for your help. All the best for xda.
See you

[Redmi Note 8] Unable to boot to recovery or fastboot (System has been destroyed)

Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?

Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL

loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .

Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?

No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.

Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.

Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...

loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)

bro how did you booted into fastboot i also in same situation

how did you fixed i also in same situation

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;

Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.