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.
Related
Hi. I've recently bought my TF700 and upgraded to JRO03C.US_epad-10.4.4.25-20121228 (JB 4.1.1). Now I want to root my device, so I first unlocked the bootloader using the ASUS unlocker. That went fine, since it says "the device is unlocked" in the boot sequence. The device boots and works properly.
Now I wanted to get to the stock recovery mode for a backup, but it fails miserably. I get to the four icon menu (RCK, Android, USB, Wipe) and select RCK. Then an android icon with a blue rotating icosahedron in its chest apears for a couple of seconds and then a "dead" android with it's cover opened and a "!" enclosed in a red triangle. After a couple of minutes, the device reboots normally (I can force that by pressing down the power button for 10 seconds).
I tried to get to fastboot by choosing the USB icon, but it does nothing (just freezes in the four icon screen and stops responding to any other buttons); the PC doesn't see an USB device of any kind. I tried connecting the USB cable both before and after selecting the USB icon with no difference. I'm sure I have at least some good drivers because I can use adb with my device when the OS is running.
I'm new to this device, so I may be doing something wrong. Any suggestions? Thanks in advance.
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
_that said:
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
Click to expand...
Click to collapse
Thank you, _that. Whatever drivers it might need, I cannot install them because no USB device of any kind appears in my computer besides my keyboard. I think I should be getting "Starting Fastboot USB download protocol" or something. How can I get fastboot to work?
Sorry, it seems it was a USB port problem! I changed the port and the fastboot device is now available in my PC. Fastboot is now able to send commands like 'reboot' to my device.
Thanks for your clarification about the stock recovery mode, _that.
Hello all,
I've been waiting for this 4.2 update for the tf700 hoping that it would fix the sluggish performance of my tablet, but sadly, it has not. Now I am trying to root it. I read on the forums that if I unlock my device (which i did), i can root it from JB by downloading a root.zip file and installing it through recovery mode. But i am having difficulty getting into recovery to root it. When i hold the power and volume down button, it brings me to the screen with 3 choices (RCK, an android figure, and wipe data). and when i select RCK, it bring me to a screen with an android on the center saying 'Installing system update' and then always results in a dead android saying error. Luckily i can just reboot it from here but i really wanna root my device and from what i know, the only way is to get into recovery.
Also, at the part where theres the 3 choices, it says:
'Key drivers not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol'
if that helps solve this problem...
Thank you for any input you can give, and if i lacked any details, I will do my best to get back to you asap.
bznazz said:
Hello all,
I've been waiting for this 4.2 update for the tf700 hoping that it would fix the sluggish performance of my tablet, but sadly, it has not. Now I am trying to root it. I read on the forums that if I unlock my device (which i did), i can root it from JB by downloading a root.zip file and installing it through recovery mode. But i am having difficulty getting into recovery to root it. When i hold the power and volume down button, it brings me to the screen with 3 choices (RCK, an android figure, and wipe data). and when i select RCK, it bring me to a screen with an android on the center saying 'Installing system update' and then always results in a dead android saying error. Luckily i can just reboot it from here but i really wanna root my device and from what i know, the only way is to get into recovery.
Also, at the part where theres the 3 choices, it says:
'Key drivers not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol'
if that helps solve this problem...
Thank you for any input you can give, and if i lacked any details, I will do my best to get back to you asap.
Click to expand...
Click to collapse
Try using Motochopper to root.
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 imageThen 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!
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?
Hey everyone. So some time ago I unlocked the Bootloader, rooted and flashed with custom ROM my Nvidia Shield K1 and flashed TWRP. All was going well untill I decided to flash another ROM with an app (which was stupid indeed) Long story short it seems now as if I have no ROM and no recovery and all I got is the "Bootloader info screen" or whatever its called.
So the only thing I can make it display is:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Unlocked
Serial Number xxxxxxxxxxxxxxxxxxxxxxx
Press <Power> to select [...]
Continue
Fastboot Protocol
Recovery mode
Reboot
Poweroff
1. Using Continue does nothing, just says booting failed for like 100ms and goes back to where it was.
2. Fastboot Protocol just reboots the devices to the same thing after like 2 sec
3. Recovery mode same as Fastboot Protocol
4.Reboot and Poweroff does what it says
I've tried everything I could find online with it. No physical key combination can make it boot the ROM or TWRP.
I tried adb fastbooting with minimal adb and fastboot like Ive done times before with this Shield K1 and I cant make it see this device. ( "adb devices" wont list it)
I have tried using different USB ports, usb drivers, usb cables, PCs, fastboots and reinstalled everything multiple times and nothing changes.
I tried using any and every USB driver, ADB fastbooting Nvidia offers for this device.
The PC itself seems to detect the tablet just fine. Pluggin and unpluggin results in a notification and the android device is detected in Device Manager properly.
Powering off and on the tablet also results in a notification on the PC.
I have no idea what to do at this point and my last hope is this thread.
I had the same issue. Finally decided to reflash to stock and all is well