I was using an unlocked xiaomi redmi note 5 pro {Pixel ecperience plus 12}. With OrangeFox custom recovery. Today i saw a new update of pixel experience so I downloaded it and then installed it from the OF recovery. But when i rebooted, I was unable to boot into system & booted into the recovery everytime. Then I installed TWRP recovery but it got stuck on its bootlogo. I waited an hour but nothing happened. Then i decided to Flash Orangefox recovery again from fastboot mode.
downloading 'boot.img'...
OKAY [ 0.781s]
booting...
FAILED (remote: Failed to load/authenticate boot image: 00000050)
finished. total time: 0.981s
Click to expand...
Click to collapse
& this error occurred.
So now I am stuck.
PS: I ****ed up, i thought fastboot -w command would fix everything but now the device only flashes into fastboot mode & this problem still persists.
I plugged in my USB cable into USB 2.0 port and it worked!!
Related
Hi,
i was trying to installer lineageOS and was having some issues trying to install.
I read online to update TWRP since I was on a older version. I downloaded
twrp-3.2.3-0-flo.img 8.8M 2018-07-29 15:35:06 EDT and installed it via TWRP (old version)
rebooted and it does not load in to TWRP now and only takes me in to fastbook mode when i try to go in to recovery it takes me back to fastbook.
I also wiped out the OS since i was going to install LineageOS right after.
Any suggestions or help?
Thanks
dieselhomey said:
Hi,
i was trying to installer lineageOS and was having some issues trying to install.
I read online to update TWRP since I was on a older version. I downloaded
twrp-3.2.3-0-flo.img 8.8M 2018-07-29 15:35:06 EDT and installed it via TWRP (old version)
rebooted and it does not load in to TWRP now and only takes me in to fastbook mode when i try to go in to recovery it takes me back to fastbook.
I also wiped out the OS since i was going to install LineageOS right after.
Any suggestions or help?
Thanks
Click to expand...
Click to collapse
Hi, I just updated to twrp-3.2.3-0-flo.img via my old TWRP and see no problem. Here is a quick solution, in fastboot mode run: fastboot flash recovery twrp-3.2.3-0-flo.img
The latest fastboot app: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
just tried that with the latest fastbook app and a new .img downloaded twrp 3.2.3.-0 I get:
C:\>cd adb
C:\adb>cd platform-tools
C:\adb\platform-tools>fastboot flash recovery twrp-3.2.3-0-flo.img
< waiting for any device >
Sending 'recovery' (6 KB) OKAY [ 0.008s]
Writing 'recovery' FAILED (remote: image is not a boot image)
Finished. Total time: 0.033s
C:\adb\platform-tools>
sweet just downloaded it from a different computer and looks like i was able to update! cheers man
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.
Hope you guys can give me a hand and get me out of this situation...
What I am using
Xiaomi Redmi Note 5 Pro with:
- Pixel Experience Rom
- TWRP 3.5.2_9
Windows 10 21H1 x64
What happend
- Updating Pixel Experience Rom failed
Downloaded update
Booted into Recovery (battery 85%)
Recovery stuck on Logo
After 30m I tried to reboot to system (thinking update failed or never started)
Reboot in to Recovery
Stuck on Logo
What I tried
- I tried XiaomiFastBootADBTools (latest version)
Device is recognized in Recovery mode
In recovery I can't do anything
Rebooting to System from here results in reboot into Recovery
Booting to fastboot works, but device is not recognized
Re-installed drivers, but no luck
Still recognized in Recovery mode
Still NOT recognized in Fastboot mode
Windows Device Manager > The drivers for this device are not installed. (Code 28)
And turning of phone is not possible, just goes back to Recovery
Don't know what else to do. I have installed all the drivers I could find. Even used Snappy Driver, but nothing seems to do the trick when the phone goes into Fastboot mode. PC just doesn't recognize it.
So can't do anything in Recovery mode; just watching the TWRP logo.
And device is not recognized in fastboot mode; forgot usb debugging?
And can't boot into system to change that, because of bootloop to Recovery.
So, am I **** out of luck and bricked my phone?
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
zaqm said:
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
Click to expand...
Click to collapse
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
FlashyDuck said:
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
Click to expand...
Click to collapse
What about trying to flash latest fastboot rom with MiFlash since fastboot now works?
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
FlashyDuck said:
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
Click to expand...
Click to collapse
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
--double, woops--
zaqm said:
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
Click to expand...
Click to collapse
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
FlashyDuck said:
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
Click to expand...
Click to collapse
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
zaqm said:
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
Click to expand...
Click to collapse
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
FlashyDuck said:
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
Click to expand...
Click to collapse
Maybe some glitch of OrangeFox recovery and yeah, let's hope that this issue won't appear anymore.
All the best, zaqm!
hello,
in Fastboot-mode I flash TWRP successfull, but when I want to boot recovery, it starts Redmi-Recovery 3.0.
No start of twrp-recovery.
Commands: (same commands I have tried with Windows 10, other TWRP-versions I tried too.)
$ fastboot devices
tkx4gm5575vod69p fastboot
$ fastboot flash recovery twrp-3.7.0_9-0-begonia.img
Sending 'recovery' (31380 KB) OKAY [ 0.876s]
Writing 'recovery' OKAY [ 0.248s]
Finished. Total time: 5.123s
Shutdown phone, Press Power On/off + Volume-Up, Press Volume-Up and it starts Redmi-Recovery 3.0.
Where is my mistake?
got done, used alternative twrp
"twrp-3.7.0_9-0-begonia.img"
I think this is official twrp, but this is for Android 9.0
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
edu.mc said:
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
Click to expand...
Click to collapse
which lineage did you flash?
There is no official as far as I can see. unofficial too.
lineage-20.0-20220822-UNOFFICIAL-begonia.zip
(I don't know from which address I download it. I searched unsuccessful)
https://sourceforge.net/projects/darkjoker360-developements/files/Xiaomi/Redmi%20Note%208%20Pro/ROM/20.x/lineage-20.0-20220822-UNOFFICIAL-begonia.zip/download?use_mirror=netcologne&use_mirror=netcologne&r=
So i unlocked the bootloader and then i tried to instal twrp on "fastbootd', the code: "C:\adb>fastboot boot twrp.imgSending 'boot.img' (26460 KB)OKAY [ 1.136s]Booting FAILED (remote: 'Unrecognized command boot')fastboot: error:Command failed"then i tried the "fastboot_bootloader" version and "C:\adb>fastboot boot twrp.imgSending 'boot.img' (26460 KB) OKAY [ 0.630s]Booting(bootloader)Command is not supportFAILED (remote: '')fastboot: error: Command failed"I said to try only flashing the gsi without TWRP and it flashed but it was stucked on a bootloop.I tried changing partitions and all things that recomended and not work.Please help
vvladf221 said:
I said to try only flashing the gsi without TWRP and it flashed but it was stucked on a bootloop.I tried changing partitions and all things that recomended and not work.Please help
Click to expand...
Click to collapse
I am pretty sure even flashed with TWRP it wouldn't work.
Some GSI just never boot or always bootloop.
Some I found only booted after factory resetting specifically from Recovery (for whatever reason?)
I would honestly just give up. When i first flashed my GSI i could only find 3 that would boot on the entire internet.