Unrecoverable bootloader error but not Bricked!

Search This thread
No, he's trying to do a buster99 by wiping all partitions and then flashing the Asus firmware blob. If you get an 'unrecoverable bootloader error' that's pretty much your only option. The commands are ok but something is off with his fastboot setup - no idea what though. Unfortunately fastboot error reports are so general, they are useless.
I would try it in Linux, that would at least exclude all the issues Windows has with fastboot/adb. Maybe set up an old PC with Linux Mint or try a dual boot alongside Windows. Or even better, ditch Windows for good and run Linux :victory:

Sent from my Pixel 2 using Tapatalk

Wont flashing the Asus firmware take him back to the Asus recovery console also? - NP
 
Last edited:

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Yep it gets you back to the original Asus JB 4.2 state. A good place to start when you really messed up [emoji16]

Sent from my Pixel 2 using Tapatalk
 
  • Like
Reactions: Nektopoli

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
That is normal. ADB only works when the tablet is booted into Android or the recovery (if the recovery supports adb and TWRP does). You have access to neither at this point, so forget about adb at this point. Fastboot is your only option. What do you get when you run the fastboot flash system blob command now?

Sent from my Pixel 2 using Tapatalk
 

lalisek

Member
Jan 29, 2019
5
0
That is normal. ADB only works when the tablet is booted into Android or the recovery (if the recovery supports adb and TWRP does). You have access to neither at this point, so forget about adb at this point. Fastboot is your only option. What do you get when you run the fastboot flash system blob command now?

Sent from my Pixel 2 using Tapatalk

On ubuntu do it nothing. Only send command a then the same error message like in Windows or only sending and after 20 minut no change. After unplug usb again the same error mesage and error in SendBuffer
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
That is too bad! I assume the blob file is in your current directory when you run the command? Post the terminal window
Try adding the path to the file and sudo:

sudo fastboot flash system /your_directory_path/blob
You'll have to enter your password after the command which does not display in terminal.

Sent from my Pixel 2 using Tapatalk
 

lalisek

Member
Jan 29, 2019
5
0
That is too bad! I assume the blob file is in your current directory when you run the command? Post the terminal window
Try adding the path to the file and sudo:

sudo fastboot flash system /your_directory_path/blob
You'll have to enter your password after the command which does not display in terminal.

Sent from my Pixel 2 using Tapatalk

I have try it like you write with sudo and path of blob. I have extrackt blob to folder with fastboot. Password was good. I will post the window tomorrow, i dont have time today. Thank you for answers and again sorry for my english.
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Sorry to hear it. I'm all out of ideas at this point. Seems fastboot is working on the PC side, but something is broken on the tablet side. I think your only option left is to find a new or used motherboard if you think it is worth it..
Good luck.

Sent from my Pixel 2 using Tapatalk
 
  • Like
Reactions: ebonit

proza

Senior Member
Sep 18, 2012
169
3
I got the following errors when try to erase system:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
erasing 'system'...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
 

ebonit

Senior Member
Nov 28, 2015
701
431
Berlin
I got the following errors when try to erase system:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
erasing 'system'...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s


I'm sorry, but this looks very strange. What is shown in your fastboot window after putting in "fastboot device"? Does your device appear correctly?
What Windows version do you have? As far as I can remember @Buster99 gave in his post a signal that Windows 8 sometimes sucks for Fastboot stuff.
 

ebonit

Senior Member
Nov 28, 2015
701
431
Berlin
It shows xxxx Device
I am using OS X.


I think in your case only helps "Try & Error" as method. First of all check your USB driver. Maybe Windows 10 sucks sometimes as well. After that use another USB port of your PC. Finally try ADB instead of fastboot protocol.
It may also be helpfull to read all posts from berndblb and NP in this thread about driver and fastboot stuff. Start with post #480 upwards. Go ahead!
 

swpross

New member
Feb 12, 2012
2
1
Ocala, FL
My solution

I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back

i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.

Here how i restored my TF300T JB

download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file

install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)

Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot

(the folowing i did at least 10 times already but didn't erase misc)

fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot


* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s

im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )


hope i could help you out!

cheers
-Buster
This saved me as well! Even in 2021, LOL.
 
  • Like
Reactions: Buster99

Top Liked Posts

  • There are no posts matching your filters.
  • 165
    My solution

    I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back

    i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.

    Here how i restored my TF300T JB

    download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file

    install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)

    Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot

    (the folowing i did at least 10 times already but didn't erase misc)

    fastboot erase system
    fastboot erase recovery
    fastboot erase userdata
    fastboot erase boot
    fastboot erase misc
    fastboot erase cache
    fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
    fastboot -i 0x0B05 reboot


    * it also took a lot longer as it should:
    C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
    erasing 'system'...
    OKAY [ 1.695s]
    sending 'system' (800935 KB)...
    OKAY [133.121s]
    writing 'system'...
    OKAY [153.973s]
    finished. total time: 288.789s

    im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )


    hope i could help you out!

    cheers
    -Buster
    6
    1st this is not for the dev section. You should ask questions in the Q&A section.


    Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. put this blob in your fastboot folder.
    Open cmd and type:
    fastboot -i 0x0B05 flash staging blob

    let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till its finished.
    Now you should be back to full Stock with Stock recovery.
    3
    Thanks you Ebonit and berndblb, I got as far as typing in "fastboot devices" and it says "waiting for device". I assume USB drivers. Found a link to them on this site but page not found came up. I could not find in asus website. Tried another link which hijacked my browser.. messed with this all day. Uggg. Anyone know a good link for the USB drivers if that is my problem? Thanks, Cindy

    This can be an annoying problem and you may have to try several driver packages, uninstall them if they don't work and try other ones. The drivers from the Asus PC Suite were for Windows XP. They may and may not work anymore - depends on your Windows version.
    As you found out, you want to stay away from all these driver downloads sites - they are usually infested with malware.
    You could try the Universal Naked Drivers from here: https://forum.xda-developers.com/go...nt/adb-fb-apx-driver-universal-naked-t2513339
    I believe those are the ones I used when I moved to Win 8 and then Win 10. If you have the 64 bit version of Win 8 or 10 you have to disable Windows driver verification feature to install them: https://www.youtube.com/watch?v=71YAIw7_-kg

    I think I can't get into recovery from inadvertently hitting wipe data when I had those 3 icons. Now it loops from twrp splash page to 4 peguins says Old FW. Continuous reboot of this. Can't get into anything else holding power and volume down. Can't even power it off.. I think I'm bricked. See my attempts to fix this further down.. thank you!

    Oh my... You do need to get adb working, I know only of one way to get out of that loop and it involves a couple of steps in adb. Check out this guide: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
    Somebody recently used this method to get out of the loop and he had only a few seconds connection in adb to perform the steps described. He created a script to run the two commands in that tiny window. Let me try to find the posts, maybe I can hook you up with him.

    Edit: Here it is, last post: https://forum.xda-developers.com/tr...f700t-bootloop-twrp-install-official-t3584529
    Try to PM @[email protected], maybe he can send you the script he created
    3
    No one's figured this out? I tried flashing the blob file and my system won't boot at all
    2
    I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back

    i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.

    Here how i restored my TF300T JB

    download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file

    install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)

    Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot

    (the folowing i did at least 10 times already but didn't erase misc)

    fastboot erase system
    fastboot erase recovery
    fastboot erase userdata
    fastboot erase boot
    fastboot erase misc
    fastboot erase cache
    fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
    fastboot -i 0x0B05 reboot


    * it also took a lot longer as it should:
    C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
    erasing 'system'...
    OKAY [ 1.695s]
    sending 'system' (800935 KB)...
    OKAY [133.121s]
    writing 'system'...
    OKAY [153.973s]
    finished. total time: 288.789s

    im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )


    hope i could help you out!

    cheers
    -Buster

    Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.

    Sent from my HTC One using xda app-developers app