Unrecoverable bootloader error but not Bricked!

Search This thread

gianlu76

Member
Aug 30, 2013
19
1
If you mean the Android keeling over, no, that's normal. Follow the steps outlined in the thread I linked to for flashing the firmware from the microSD

Sent from my Nexus 5X using Tapatalk

---------- Post added at 07:43 AM ---------- Previous post was at 07:11 AM ----------


What recovery do you have now?
If you cannot get a fastboot connection your only option would be to flash either bootloader and recovery in your current recovery (assuming it even works...) or flash the Asus stock firmware and start from scratch.
Check the OP of the CROMi-X, Omni rom and ZOMBi-Pop threads. lj, sbdags & Co at some point posted recovery flashable bootloader /recover packages you can use.
Or download the Asus firmware, unzip it once and flash the resulting zip in recovery.
If your current recovery works, that should get you back on a total stock system.

Sent from my Nexus 5X using Tapatalk
I had TWRP but I don't remember which version. Thw problem is I can't access to old twrp recovery, I can access only in stock recovery (three icons) with the message error. I can't install any new recovery over this corrupt recovery because fastboot doesn't work on TF300T. First, I think I need to know the correct version of recovery to install, then, understand how to install.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
 

Sindee75

Senior Member
Dec 19, 2016
106
13
Nice? Nice does not begin to cover it!
FWUL is friggin awesome! Just prepped a USB drive myself and connected 4 Android devices one after the other without rebooting, without any fuss.
And for all of them I had adb in Android, adb in recovery and fastboot. This is the first time that I had adb in recovery for my TF701 - never got that to work in Windows.
@Sindee75 you still around? This is the answer to your troubles!!!

I surprised myself. I figured out how to do the FWUL and booted from a Usb! In lunix, problems are similar.. when I issue fastboot erase system, it just sits and does nothing instead of saying "waiting on any device".. adb devices does show recovery. In file manager you can see my Transformer tablet, but you can't access it as it won't mount then at some point I get an error "unable to open MTP device usb:001,17"..

does this help to figure out my problem??????
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
I had TWRP but I don't remember which version. Thw problem is I can't access to old twrp recovery, I can access only in stock recovery (three icons) with the message error. I can't install any new recovery over this corrupt recovery because fastboot doesn't work on TF300T. First, I think I need to know the correct version of recovery to install, then, understand how to install.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

We gave to get terminology straight here: When you are on the screen with 3 icons you are in the bootloader and fastboot mode, not recovery. You access recovery from there by pushing Vol up on the flashing RCK icon.
When in fastboot what do you get from 'fastboot devices'?
There are only three ways to flash a recovery (well... 4 ways, but I don't count apps like Flashify...)
In fastboot
In your current recovery
With dd command if you have adb in recovery

So,
find out if you have one of the above. Either fastboot or adb when you boot to recovery. Doesn't matter if you get stuck on the TWRP screen. Try it anyway.

---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------

I surprised myself. I figured out how to do the FWUL and booted from a Usb! In lunix, problems are similar.. when I issue fastboot erase system, it just sits and does nothing instead of saying "waiting on any device".. adb devices does show recovery. In file manager you can see my Transformer tablet, but you can't access it as it won't mount then at some point I get an error "unable to open MTP device usb:001,17"..

does this help to figure out my problem??????

What return do you get from fastboot devices?
What return do you get using the ls /sdcard / command?
Go slow, go methodically



Sent from my Nexus 5X using Tapatalk
 
Last edited:

gianlu76

Member
Aug 30, 2013
19
1
We gave to get terminology straight here: When you are on the screen with 3 icons you are in the bootloader and fastboot mode, not recovery. You access recovery from there by pushing Vol up on the flashing RCK icon.
When in fastboot what do you get from 'fastboot devices'?
There are only three ways to flash a recovery (well... 4 ways, but I don't count apps like Flashify...)
In fastboot
In your current recovery
With dd command if you have adb in recovery

So,
find out if you have one of the above. Either fastboot or adb when you boot to recovery. Doesn't matter if you get stuck on the TWRP screen. Try it anyway.



You are right berndblb, I'm sorry. My current recovery is not available (could better say previous recovery), I can access only in bootloader mode but in this case fastboot doesn't available. If I use "fastboot devices" on my pc I give any response from tablet. The tablet turn on normaly with kitkass rom but not in recovery.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Yes, he can flash it to the staging partition, reboot and the bootloader should do the rest

Sent from my Nexus 5X using Tapatalk
 

Sindee75

Senior Member
Dec 19, 2016
106
13
We gave to get terminology straight here: When you are on the screen with 3 icons you are in the bootloader and fastboot mode, not recovery. You access recovery from there by pushing Vol up on the flashing RCK icon.
When in fastboot what do you get from 'fastboot devices'?
There are only three ways to flash a recovery (well... 4 ways, but I don't count apps like Flashify...)
In fastboot
In your current recovery
With dd command if you have adb in recovery

So,
find out if you have one of the above. Either fastboot or adb when you boot to recovery. Doesn't matter if you get stuck on the TWRP screen. Try it anyway.

---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------



What return do you get from fastboot devices?
What return do you get using the ls /sdcard / command?
Go slow, go methodically



Sent from my Nexus 5X using Tapatalk


Same problem in linux/fwul. I open the easy adb icon. Click adb tab, select adb devices on menu, then select activate. It show device number and recovery. I select fastboot tab, then fastboot devices and nothing happens. Just sits.. the ls /sdcard/ command says invalid path or something like that.
I only have usb 3.0 ports, could this be my issue? Thanks!
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA

Ok, sorry - it's been crazy around here.
I do not like one bit that you do not have fastboot access in the bootloader and somehow suspect something else is going on, but I cannot make sense of it...

So you have adb in Android.
Make sure you are flashing the correct recovery this time, ok?
Rename the downloaded recovery image to twrp.img and place it into the root of your internal memory on the tablet. That is the same level where your Pictures and Documents folder are too. Do not put it into any folders, just into the root level of /sdcard
Then issue these commands:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p4
Then reboot the tablet normally. Turn it off again and now boot into recovery and check if it is accessible.
Best is probably that you copy and paste the dd command. Please make sure you type it correctly, especially the last bit: That's mmcblk"zero"p4
 
  • Like
Reactions: ebonit

gianlu76

Member
Aug 30, 2013
19
1
Ok, sorry - it's been crazy around here.
I do not like one bit that you do not have fastboot access in the bootloader and somehow suspect something else is going on, but I cannot make sense of it...

So you have adb in Android.
Make sure you are flashing the correct recovery this time, ok?
Rename the downloaded recovery image to twrp.img and place it into the root of your internal memory on the tablet. That is the same level where your Pictures and Documents folder are too. Do not put it into any folders, just into the root level of /sdcard
Then issue these commands:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p4
Then reboot the tablet normally. Turn it off again and now boot into recovery and check if it is accessible.
Best is probably that you copy and paste the dd command. Please make sure you type it correctly, especially the last bit: That's mmcblk"zero"p4
After work I'll try. The problem maybe is understand the correct version of TWRP to install. On KitKass lollipop thread speack about TWRP 2.8, I'll try to install this version.
Your help is precious.
 

gianlu76

Member
Aug 30, 2013
19
1
After work I'll try. The problem maybe is understand the correct version of TWRP to install. On KitKass lollipop thread speack about TWRP 2.8, I'll try to install this version.
Your help is precious.

This is what I did:
[email protected]:/ # su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p4
14252+1 records in
14252+1 records out
7297128 bytes transferred in 9.526 secs (766022 bytes/sec)

Reboot system.
Turn off tablet.
Turn on tablet in fastboot mode.
Same message "unrecoverable..........". I can only reboot system and access to android.

P.S.
I downloaded kang TWRP https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
 

gianlu76

Member
Aug 30, 2013
19
1
@berndblb I've done :laugh::laugh:
How? please don't kill me....I just plugged the tablet to another usb port :angel:
Changing usb port I had access to fastboot command and following post #12.
Sorry if I did not waste time....if you come in Italy you are invited to my house in Tuscany ;)
 

Sindee75

Senior Member
Dec 19, 2016
106
13
@berndblb I've done :laugh::laugh:
How? please don't kill me....I just plugged the tablet to another usb port :angel:
Changing usb port I had access to fastboot command and following post #12.
Sorry if I did not waste time....if you come in Italy you are invited to my house in Tuscany ;)
I have read on this forum and others fastboot doesn't work on many usb 3.0 ports. That's all I have. Did you by any chance switch to a Usb 2.0 port? Cindy
 

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