I would like to know if there is anyone who knows how to fix the bootloader error on a TF700T with the Unrecoverable bootloader error. I have access to fastboot and the entire device is wiped due to following another tutorial for fastboot to recover from the bootloop error.. there is no more way to enter recovery or cold start android... the device has two options, fastboot mode, or being stuck at the asus logo untill the battery runs out. I don't think i can flash anything with fastboot as the bootloader is locked.
i'm open to any and all critiques and pieces of advice..
DrScrad said:
I would like to know if there is anyone who knows how to fix the bootloader error on a TF700T with the Unrecoverable bootloader error. I have access to fastboot and the entire device is wiped due to following another tutorial for fastboot to recover from the bootloop error.. there is no more way to enter recovery or cold start android... the device has two options, fastboot mode, or being stuck at the asus logo untill the battery runs out. I don't think i can flash anything with fastboot as the bootloader is locked.
i'm open to any and all critiques and pieces of advice..
Click to expand...
Click to collapse
Tried the pin hole reset?
Is that not doing the same thing as a hard reset?
DrScrad said:
Is that not doing the same thing as a hard reset?
Click to expand...
Click to collapse
I dont believe so, think it reverts to the Nvflash, kind of like a backup. https://www.justanswer.com/computer/8zhza-tf-700t-stuck-boot-up-will-not-shut-down.html
Related
Hi all
I have tried to make my device brick proof using NVFlash metod. I have flashed the AndroidRoot bootloader:
fastboot -i 0x0b05 flash staging ebtblob.bin
I have AndroidRoot 9.4.5.30r01 on the screen after rebooting.
cant generate nvflash blob files with the
fastboot -i 0x0b05 boot nvfblobgen.img it gets stuck. (waited forever)
It would not boot up anymore. It would not get pass the first asus logo.
Fast boot and APX works. Cant get into recovery it gets stuck.
Anything i send to it over fastboot device gets stuck.
is there any way to get back to previous bootloader?
or is there any way to get it fixed?
thank you.
Have you tried downloading ASUS original firmware and put it on your microSD and recover from there.
Refer to this: http://forum.xda-developers.com/showthread.php?t=1755576
Best of luck!
Malkaridae said:
Have you tried downloading ASUS original firmware and put it on your microSD and recover from there.
Refer to this: http://forum.xda-developers.com/showthread.php?t=1755576
Best of luck!
Click to expand...
Click to collapse
That didn't work. It just goes to "booting recovery kernel image" and gets stuck.
is there any other way?
Which ROM are you running? The latest unofficial CM10 (by hiemanshu) requires the JB bootloader -- it wouldn't boot on my 700 with the AndroidRoot bootloader. There is a link to a simple how-to here:
http://forum.xda-developers.com/showpost.php?p=32647108&postcount=659
After you've tried that, please report back in.
Oh, and errrr, on my computer, the connection server is wonky. Try and give the commands to kill and restart the (adb) server -- that always starts functionality on my x64 Windows 7 machine):
adb kill-server
adb start-server
Are you still able to boot in fastboot mode?
Pretoriano80 said:
Are you still able to boot in fastboot mode?
Click to expand...
Click to collapse
Yes I am still able to boot i fast boot mode.
kluikis said:
Yes I am still able to boot i fast boot mode.
Click to expand...
Click to collapse
Ok,so far so good,but what kind of error you get when you try to flash something via fastboot?Have you tried to flash the AndroidBootloader again?
Pretoriano80 said:
Ok,so far so good,but what kind of error you get when you try to flash something via fastboot?Have you tried to flash the AndroidBootloader again?
Click to expand...
Click to collapse
kluikis said:
[...]
fastboot -i 0x0b05 boot nvfblobgen.img it gets stuck. (waited forever)
[...]
Click to expand...
Click to collapse
I got this error too, but when I (re)started the adb server, I could connect with no further issues -- hence my earlier advice. Have you tried that, kluikis?
MartyHulskemper said:
I got this error too, but when I (re)started the adb server, I could connect with no further issues -- hence my earlier advice. Have you tried that, kluikis?
Click to expand...
Click to collapse
Now I am in even more trouble. I have tried to do this:
ASUS original firmware and put it on your microSD and recover from there.
Refer to this: http://forum.xda-developers.com/show....php?t=1755576
and it just got stuck on "booting recovery kernel image"
and any time I turn it on now with power button + volume down button it just goes automatically to "booting recovery kernel image" and hangs there forever. Cant even get options anymore to get to fast boot .
kluikis said:
Now I am in even more trouble. I have tried to do this:
ASUS original firmware and put it on your microSD and recover from there.
Refer to this: http://forum.xda-developers.com/show....php?t=1755576
and it just got stuck on "booting recovery kernel image"
and any time I turn it on now with power button + volume down button it just goes automatically to "booting recovery kernel image" and hangs there forever. Cant even get options anymore to get to fast boot .
Click to expand...
Click to collapse
Sorry mate,but at this point you can't recover your device anymore,only Asus can fix that.
kluikis said:
Now I am in even more trouble. I have tried to do this:
ASUS original firmware and put it on your microSD and recover from there.
Refer to this: http://forum.xda-developers.com/show....php?t=1755576
and it just got stuck on "booting recovery kernel image"
and any time I turn it on now with power button + volume down button it just goes automatically to "booting recovery kernel image" and hangs there forever. Cant even get options anymore to get to fast boot .
Click to expand...
Click to collapse
Shame you didn't try the kill/restart trick -- that might have given you the blobs you'd need to recover from this. I do not think there is an option to recover with adb/fastboot access, although you might try scrounging the forum and get a lucky hit. Otherwise, it's ASUS tech support for your device.
MartyHulskemper said:
Shame you didn't try the kill/restart trick -- that might have given you the blobs you'd need to recover from this. I do not think there is an option to recover with adb/fastboot access, although you might try scrounging the forum and get a lucky hit. Otherwise, it's ASUS tech support for your device.
Click to expand...
Click to collapse
As long as your device is recognized in fastboot mode you have a high chance to recover but he can't get in fastboot anymore, so sending back to Asus it's all he can do.
Pretoriano80 said:
As long as your device is recognized in fastboot mode you have a high chance to recover but he can't get in fastboot anymore, so sending back to Asus it's all he can do.
Click to expand...
Click to collapse
I fully agree, and already said so -- but still it's a shame he didn't try to restart the adb server.
tf300t
I was using energy rom, I am 90% sure it was the 4.1 version. (the rom folder was labed Energy.TF300.JB.11.30.2012.zip)
Today i tried to revert it back to complete stock. tried to flash the latest blob from asus' website using fastboot, and when it rebooted, i got the dead android logo, and then nothing. I then followed some other guides from here and such to try to recover it, and now I am stuck with it going straight into TWRP v2.3.1.0 recovery. It then asks me for a password. I can use the adb reboot bootlader command to get back to the fastboot screen, but anytime i try to flash anything, it never takes. the command window says it went, but the tablet just freezes up, until I hold down power until it reboots. Is there any fix for this? Or am I completely and utterly screwed? I will reply asap to any posts, so feel free to ask me for more info if neeed, ill answer the best i can.
Basically you have flashed a 4.2 bootloader onto a 4.1 recovery (TWRP 2.3.1.0)
Sorry but that is a brick.
If you had updated TWRP to a compatible version at the same time you may have been able to save this first ......
As far as I'm aware the only fix is to send it back to Asus for repair.
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
rboutin2 said:
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
Click to expand...
Click to collapse
Well any chance you had has now gone as you wiped from the bootloader which has now sent a message to the incompatible recovery to wipe and it doesn't understand the partitions so who knows what state it is in now. Sorry.
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
rboutin2 said:
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
Click to expand...
Click to collapse
Unlucky mate. You never know Asus might fix it for free? It has happened.
Hi,
I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.
I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.
I have somehow managed to "temporarily" unlock the bootloader by entering the following command.
Code:
fastboot oem unlock
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img
Code:
fastboot erase flash
fastboot flash recovery recovery.img
But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.
I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.
I have come here seeking for help as I believe XDA is the most active Android community online.
If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.
Thanks in advance.
At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
NexusUser5 said:
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
Click to expand...
Click to collapse
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Primokorn said:
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
Click to expand...
Click to collapse
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.
JonesL said:
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Click to expand...
Click to collapse
I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."
UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
audit13 said:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
Click to expand...
Click to collapse
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
audit13 said:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
Click to expand...
Click to collapse
Thanks a lot for your help, very much appreciated.
So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.
C4SCA said:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.
Click to expand...
Click to collapse
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop
migidid said:
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop
Click to expand...
Click to collapse
After these steps can u enter recovery? Tried to factory reset via recovery?
No i still cannot get to recovery no matter what i try. i never could. i can get to cm fastboot and coloros fastboot but no recovery at all. its like its missing. ive been tinkering with this phone for almost a week so ive been trying many times and many combinations but nope.
migidid said:
So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...
Click to expand...
Click to collapse
I also have the same problem what to do? if your problem is solved tell me how to do?
please help if you fixed this..Same thing is happing to me...
phillipmckinnish said:
please help if you fixed this..Same thing is happing to me...
Click to expand...
Click to collapse
You're not being able to boot into fastboot mode and device is bricked?
Same here but I can't boot into recovery or fastboot or anything...
If you have Linux PC try ubports might fix things then reinstall whatever os you feel like
https://ubuntu-touch.io/get-ut
Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
The problem is, that I'm stuck at the Asus boot (static white) logo and can't go further in booting.
I've tried ADB, but there's no response on the "adb devices" command.
I've also tried fastboot, but only two commands are woriking:
"fastboot devices" comes back with an alphanumeric number and
"fastboot continue" turns off the tablet.
The other fastboot commands are returning with the message "fastboot failed <remote failure>"
So finally I've found some hints that maybe with xFSTK I would able to fix fastboot, then with the Asus Flast Tool I supposed to be able to flash the stock raw rom (which I've already done before).
But unfortunately xFSTK is ether not working (no communication) or I'm using it wrong. As far as I know TF303CL has Intel SoC with Baytrail platform, so I used the Baytrail B0 tab in xFSTK and I've loaded the *ifwi*.bin file which I found in the stock raw rom.
Is this the right way to fix fastboot or I have to do something else? Or the tablet may has hardware defect?
mucden1 said:
Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
Click to expand...
Click to collapse
I think it was a good idea to open this thread. To my mind your device is really very close related to TF300T and TF700T. The OS is Android 4.4. So it might be worth to attempt to flash a CR like "KatKiss - Nougatella"
But before you may start is to clarify following:
1. Is the bootloader on your device unlocked?
2. Is there already any custom recovery like TWRP on your device?
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!
1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
2. Is there already any custom recovery like TWRP on your device?
As far as I know it has stock recovery.
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
I think Power on & Vol down is the key combination for recovery mode. Power on & Vol up is the combination for fastboot. I can't access to recovery, but fastboot may partially work.
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!
Whit adb
Code:
adb devices
command has no response. With fastboot I have a response on the
Code:
fastboot devices
command, it returns some kind of an id. Beside this
Code:
fastboot continue
makes the device to turn off. Other fastboot commands (as I wrote) are returning with the "fastboot failed <remote failure>" response.
These are what I have tried so far:
reboot, reboot bootloader, update, flash (several images), erase cache, erase data
mucden1 said:
1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
Click to expand...
Click to collapse
People usually unlock their bootloader to root their device or install Custom ROM on it. I think your bootloader is still locked. On the other side in the left above corner of the dark screen should appear the hint "the device is unlocked" during the boot process.
For the TF300xx family there is an Asus unlock tool V8 available. I don't know if it is useable for your device. Please call Asus support and ask them about that. On the other hand there is a tutorial here: https://qitapso.com/how-to-unlock-asus-transformer-pad-tf303cl-bootloader/
Should I try to unlock the bootloader?
mucden1 said:
Should I try to unlock the bootloader?
Click to expand...
Click to collapse
Of course!
But it's on your own risk. You have to make the decision yourself.
ebonit said:
Of course!
But it's on your own risk. You have to make the decision yourself.
Click to expand...
Click to collapse
The link above goes to "AutorootTools" which is not a real sw, only promising download after an unwanted and long survey. I consider it as a dangerous site.