Database Info

[Q] Cold Boot Leads to Dead Android Picture after 4.2

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.

[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!

TF700T stuck on the logo

I was trying to update the version 4.2 of android to a more current, first I root With fasboot superuser and using the wipe pass and not go along. The tablet in the left corner says "this device is unlocked" I can not do reboot with power and volume key, pc recognize not on, only recognized in apx off mode. I have it long time so when I take to the asus service told me I had to change the main board that cost more expensive than the tablet. Please if anyone can help me.

Sorry, only APX = dead. You need a new mainboard

Asus ME103k Crash Boot (Fastboot Mode)

Hello, it's been months that my tablet Asus Memo Pad 10 [Model K01E (ME103k)] is blocked in Fastboot Mode with "Secure Boot - Enable".
I can not access in the recovery menu (Power + Volume Up), I have already tried a dozen times, be sure (even with the other keys).
The tablet is recognized only as a bootable device but can't be seen outside of the (windows) device manager.
Please help me, :crying:
Cordially :fingers-crossed: