Hi All,
I have a stock TF300T with latest ASUS firmware (4.2.1) and it started throwing this error code the other day. I found it in an off state and when I try to start it, it says
Failed to initialize aboot
Unrecoverable boot loader error (0x37042000).
I did some searching for info on this error code to see what the deal might be but I couldn't really find anything. I also tried doing the Power On + Volume down to recover but all it will do is show this error code. I currently have an open RMA to send it back to ASUS, but I would really rather not waste the money/time shipping it back to them if I can somehow fix it myself. Does anyone have any insight into this error and how I can fix the problem?
Thanks in advance.
What have you done with your tablet? Did you try install recovery, system etc. that your tablet says "unrecoverable boot loader error"?
Hazard17 said:
What have you done with your tablet? Did you try install recovery, system etc. that your tablet says "unrecoverable boot loader error"?
Click to expand...
Click to collapse
Nothing at all. It is 100% stock. The only thing related to firmware I can think of that might have caused this in the last week is that it said it had a camera update available but it seemed to fail on reboot. I didn't really pay attention to it because I haven't used the camera much and it didn't affect what I do with the tablet.
Well...off to ASUS warranty service to see what the problem is. I'll post back any useful info I get for this bootloader error.
Related
Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc
To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks
Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.
I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
what boot loader> also you did wipe from recovery not the first menu right?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
bricked tf300
MaMMiTs said:
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
Click to expand...
Click to collapse
Yes it is unlocked Jellybean nothing happens if i keep holding the volume down and power except the screen goes off for a second the right back to the asus screen Fastboot won't work, it just says waiting for device My pc won't see it at all, not in device manager or anyuthing No apx either. If i could get fastboot to work i think i could fix it
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Also same problem. Fastboot 'sees' the TF300 device but does not flash.
I have the same problem. Fastboot 'sees' the TF300 device but does not flash. If somone has come up with a solution for this, could you please share, it would be greatly appreciated. Did Asus finally release NVflash for JB 4.2? It seems it is the only possible way of solving this, or isn't it?
Thanks for your help
aarsyl said:
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Click to expand...
Click to collapse
---------- Post added at 08:44 PM ---------- Previous post was at 08:31 PM ----------
It seems there is no solution yet. See this post:
http://forum.xda-developers.com/showthread.php?t=2179874&page=17
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
What happened in the end? Did you go to ASUS and get it repaired? How much did it cost?
Hi guys,
I solved the problem with the bootloader error (0x0000000) assistance in sending the TF300T. I told him that during the upgrade something must have gone wrong and the OS did not boot anymore. They repaired free of charge. My dealer to whom I entrusted the tablet is Mediaworld (a chain of electronic products Italian). I hope you can serve
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Try to flash stock from fastboot, maybe something on your system has been corrupted... Are you rooted or bootloader unlocked?
thegunrun said:
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Click to expand...
Click to collapse
You can try to recover to the recovery image.
https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image.txt
You can find the boot, system and recovery .img's here
http://forum.xda-developers.com/showthread.php?t=2388870
The blob and tegra114-roth here
https://drive.google.com/?authuser=0#folders/0B7j6Imwr_sirRnl5MFRRR2sxRWM
I would upload the userdata.img, but it's too big for me to upload, and I don't think it is needed...
Guys, the OP mentioned that he has not unlocked/rooted his device, so he cannot flash the recovery image.
That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):
1) On the boot splash animation, connect SHIELD to your PC and try to run "adb logcat" to see if you can see what is crashing. Attach the log here if you can get it.
2) If you cannot use adb, reboot your SHIELD while holding the back and home buttons. This will bring you to the bootloader menu. Then connect to your PC and try to "fastboot erase userdata" and "fastboot erase cache" before doing "fastboot reboot". This will remove all your user data, so your SHIELD should boot again correctly provided the OTA went without any issue. You might not like the idea of losing your user data though.
3) Contact NVIDIA. You have not unlocked your SHIELD, just did a regular OTA. This is covered by the warranty so they should be able to help you.
Gnurou said:
....That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):....
Click to expand...
Click to collapse
Fixed that line for you.
If the device is locked getting Nvidia to fix the software should not be a problem.
I had the same problem. NVidia swapped out my Shield with a retail refurbished unit.
Happened to me but I shut it down using the nvidia button and let it sit for a few minutes and it booted.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
i have got the same problem
its impossible to boot in 4.3. the only few times i got it, it tooks 10 ton 15 minutes
i go back to 4.2 and i had the same problem. the only way to get the shield back to normal is to format all (system, data, etc..) through cwmr
when i trie to update to 4.3 trought ota, i got the same problem and i have to repeat the proccess again to come back to 4.2
in 4.2 boots ok, and everything works, but i cant update
any ideas?
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
jdsemler said:
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
Click to expand...
Click to collapse
hi, i tried to boot without the sd and i get the same result
stock in boot logo
i thing the problem its something related with the ota update an my boot.img
someone has access to boot, system and recovery img from update 63?
maybe if i install from bootloader i get something
thanks in advance
If you power on holding back and home, you will boot into a menu. If you go into Recovery, do you get any options? On mine, it would say "No Command" and be stuck there. If yours also says "No Command", you can't really load anything using recovery.
You should consider going here. You'll have to either login or create a login, but after that, you can submit your problem to NVidia. That's what I did, and they shipped me a new unit overnight with a prepaid label to send my unit back.
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
cg_gm said:
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
Click to expand...
Click to collapse
good news!!! last update (64) solve the problem. now im in 4.3 and all is working ok
thanks for your help, hope thath nvidia dont mess up with the updates again
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
When updating the phone, I got a message saying that it was not possible to boot and try the yellow line again. Pressed and got a hard brick.
I found a service where they can fix it, and even the programmer managed to get to the bootloader, but it does not accept the factory image file from the Google site.
One recovery option is to try to write a firmware dump from another phone. If anyone has such an opportunity to record a dump, I will be very grateful.
RomanBykiv said:
When updating the phone, I got a message saying that it was not possible to boot and try the yellow line again. Pressed and got a hard brick.
I found a service where they can fix it, and even the programmer managed to get to the bootloader, but it does not accept the factory image file from the Google site.
One recovery option is to try to write a firmware dump from another phone. If anyone has such an opportunity to record a dump, I will be very grateful.
Click to expand...
Click to collapse
You should return the phone for a refund. Where did you get it from?