Database Info

Soft Bricked

I just got my TF300 on Wednesday, and it decided to get stuck on the boot screen.I have rooted, but NOT unlocked this transformer. I do NOT have CWM, or any working access to ADB and fastboot.Using the Power + Vol Down for the RCK results in an Android on its back with a Red Exclamation. Continuing on past the RCK Screen, it gives two options (No USB Icon), one to wipe and one to cold boot Android. Neither have those has worked. I also let the TF300 completely drain itself, and fully recharged and still has not worked. Windows 7 reports that the TF300 as an "Asus Android MTP Device", but giving an error code of 10, which is "The device cannot start". I have not seen any ADB devices either.
I also have tried to put the latest firmware (.30) onto a microSD card, and booting into all the available options with nothing working.
Does anyone have any ideas on how to at least get ADB and/or fastboot running?

Condemned08 said:
I just got my TF300 on Wednesday, and it decided to get stuck on the boot screen.I have rooted, but NOT unlocked this transformer. I do NOT have CWM, or any working access to ADB and fastboot.Using the Power + Vol Down for the RCK results in an Android on its back with a Red Exclamation. Continuing on past the RCK Screen, it gives two options (No USB Icon), one to wipe and one to cold boot Android. Neither have those has worked. I also let the TF300 completely drain itself, and fully recharged and still has not worked. Windows 7 reports that the TF300 as an "Asus Android MTP Device", but giving an error code of 10, which is "The device cannot start". I have not seen any ADB devices either.
I also have tried to put the latest firmware (.30) onto a microSD card, and booting into all the available options with nothing working.
Does anyone have any ideas on how to at least get ADB and/or fastboot running?
Click to expand...
Click to collapse
Only option without FB and ADB is choose wipe with Vol- and the press Vol+ to do the wipe.
Then try reboot.
But you should have ADB at least. We will try out that later.

http://forum.xda-developers.com/showthread.php?t=1777203
This works TF700

zeus34 said:
http://forum.xda-developers.com/showthread.php?t=1777203
This works TF700
Click to expand...
Click to collapse
How do you have to name the update on a tf300?
SWame name then on a 700?

mikaole said:
Only option without FB and ADB is choose wipe with Vol- and the press Vol+ to do the wipe.
Then try reboot.
But you should have ADB at least. We will try out that later.
Click to expand...
Click to collapse
I have already tried that, but it just ends up being stuck on the boot.
Also, I would like to know if the filename should be the same as the TF700 for the FW update.
EDIT: The filename should be the same! It did actually work how it was specified. I'm on the boot screen waiting for the progress bar to finish, but it looks promising.
Appreciate the help guys!
Edit 2: Well she boots up perfectly now, I just need to do it again because its in Chinese, so I made a mistake somewhere.. anyways, Thanks for the help!

[Q] can't get in to RCK bricked?

So I had some trouble with my device bad third party app im guessing, it would crash all the time and i couldn't restart it. so I wiped it that worked fine, now a few days ago i decided I'd like to get kitkat on it. before doing anything i wanted to test if i can get in to RCK, so I start my device volume down and a message appears at the top corner:
Key driver not found,,booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.5-20130902" A03
Starting fastboot usb download protocol.
then when I press up volume on RCK I get the dead andriod error message after a few seconds of initializing
anything I have read about this tells me to re flash my device the problem is the device is not flashed.
So if I understand the process correctly i need to get in to RCK in order to get to the usb connection and then flash my device
so I'm kinda stuck.
appreciate any help you can give me.
btw I'm running the original asus 4.2 update never did anything to the device besides the bad app

nebunami said:
So I had some trouble with my device bad third party app im guessing, it would crash all the time and i couldn't restart it. so I wiped it that worked fine, now a few days ago i decided I'd like to get kitkat on it. before doing anything i wanted to test if i can get in to RCK, so I start my device volume down and a message appears at the top corner:
Key driver not found,,booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.5-20130902" A03
Starting fastboot usb download protocol.
then when I press up volume on RCK I get the dead andriod error message after a few seconds of initializing
anything I have read about this tells me to re flash my device the problem is the device is not flashed.
So if I understand the process correctly i need to get in to RCK in order to get to the usb connection and then flash my device
so I'm kinda stuck.
appreciate any help you can give me.
btw I'm running the original asus 4.2 update never did anything to the device besides the bad app
Click to expand...
Click to collapse
You are not bricked, that means that you have not yet flashed a recovery.
First you have to flash a compatible recovery. That means you have to install fastboot on your computer and use it with this guide:
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
If you tablet detects a computer plugged in, it will automatically go to fastboot, despite the dead android. Therefore, plug your tablet into your computer, and then turn it on while holding the vol down key.

[Q] Unknown History

I have a customer who bought a tf300t used...knowing it was broken.
I have experience unlocking, rooting and installing custom ROMS on previous tablets and phones...but, no experience with the transformer.
After hours of reading I can only guess someone flashed the wrong recovery version on this thing.
It boot loops the ASUS screen with "The device is UnLocked" in the upper left corner.
When holding VOL DWN key, I get a little more... it says:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
Booting recovery kernel image​Then it reboots after about 4 seconds.
On the SD card that is in the device is a recovery.img file and a META-INF directory. Digging through that it looks like its for some version of CWM.
ADB and Fastboot never see the device nor does device manager in Windows.
I tried various original firmwares and recovery IMG and ZIP files on the root of the SD card to no avail... nothing changes, nothing boots.
Thoughts? Is my customer S.O.L?

I can get Windows to recognize it in APX mode... thats it.

motorcyclegoat said:
I can get Windows to recognize it in APX mode... thats it.
Click to expand...
Click to collapse
After power+vol down try to press vol up when it shows "Device is UnLocked".

motorcyclegoat said:
I can get Windows to recognize it in APX mode... thats it.
Click to expand...
Click to collapse
If the PC will never show the device as adb or fastboot and it will not boot into recovery .....
There is nothing that can be done ....:crying:
Do you see the screen with a usb icon ??
APX mode is only if you have backed up the tablet nvflash files, which has to be done before the tablet is in this kind of state....
Sorry for the bad news....
Thx Josh

That's what I was figuring, too. Just wanted someone with specific knowledge of the tf300t and its recovery process to confirm.
I believe whoever sold this to her knew they were selling a bricked device. They sold it to her for $50... a year ago. And, at that price, they knew it was broken...but, told her it just needed an SD Card.
Thanks for your input!

TWRP Trashed my tab. ADB shows offline. Fastboot unresopnsive.

Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!

supwiddiss said:
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
Click to expand...
Click to collapse
nobody?

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.

Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse

Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.

I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?

'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!