Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Try this
https://www.getdroidtips.com/twrp-recovery-redmi-note-8-2021-root/
I guess you have used a wrong recovery file, maybe one for another device
The problem is that the command 'flash recovery' does not work, because it says th partition does not exist....
Norah1838 said:
I am using a Redmi Note 8 (2021)
Click to expand...
Click to collapse
wrong forum ! , see Biloba forum
on some devices, boot+recovery are on the same partition, but not for Biloba
boot partition (+dtbo on some cases) is the kernel
i think you should look for official install of miui rom since it has IMG of most partitions ...
Related
a friend sold me new pixel 3 xl. they someone messed up rooting and screwed up something. $50 i paid
twrp was installed it was latest version
phone off and hit power or hold power nothing that i can see on screen
power and volume down i can go into fastboot mode, device says unlocked adb can see it in fastboot device
if i select restart bootloader i get nothing
if i select recovery mode nothing
what do i need to do?
tried this
C:\abd\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.599s]
Writing 'boot_a' OKAY [ 0.508s]
Finished. Total time: 2.562s
C:\abd\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 1.529s]
Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
fastboot: error: Command failed\
Opps delete
kingrat said:
C:\abd\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 1.529s]
Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
fastboot: error: Command failed\
Click to expand...
Click to collapse
Your cut and paste was a fail. The command you entered was to boot twrp, but the "error" returned occurred after "SENDING BOOT.IMG". Quit screwing around and flash the full factory image first and try to get it to boot to System first. Report any errors.
Crap, I see what occurred. Sorry to bother you, someone else replied and told me what to do and that work and he wasn't Richard cranium about it. Thanks for your response.
Today i tried to install custom rom on my realme 3 pro and i was successful in doing it, later decided to revert back to stock Realme UI so i downloaded the Ozip from official site of realme, flashed it using twrp and rebooted......
Device is not booting to the system instead it is booting back to Fastboot mode and i even tried booting to recovery from fastboot and it is coming back to fastboot mode..
tried flashing recovery image from fastboot and it is throwing error
./fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.424s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
what ever command i try to pass, i am getting the same error...
HELP NEED ASAP please...
hi, long story, solution needed, help!
I was on evolutin x + orange fox recovery.. was working pretty fine for 2 months.. I was using chrome and all of a sudden the phone just froze and I had to force shut it down..
now it boot loops.. ofox stays on welcome screen and doesnt go past it..
tried "fastboot clear userdata".. then tried " fastboot flash recovery recovery.img" it gives out error
--
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (47472 KB)...
OKAY [ 1.008s]
writing 'recovery'...
FAILED (remote: Error flashing partition : Write Protected)
finished. total time: 1.099s
--
tried flashing stock fastboot rom via miflashtool it says "Flash xbl error"
bootloader is unlocked aswell
what to do now? any help much appreciated..
So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy