Database Info

[Q] HELP! I think i bricked my TF700 while installing Jelly bean.

Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??

Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.

_that said:
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
Click to expand...
Click to collapse
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
i think my problem is that the usb device drivers are not working hence win7 x64 cant recognize the tablet when it is turned off (APX mode i believe)

dazzyd said:
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
Click to expand...
Click to collapse
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).

_that said:
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
Click to expand...
Click to collapse
Hi again, no i cant see the usb icon,
i am only getting this Asus screen
the Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.

dazzyd said:
and it gets stuck there at the ASUS screen.
Click to expand...
Click to collapse
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.

_that said:
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
Click to expand...
Click to collapse
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.

dazzyd said:
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
Click to expand...
Click to collapse
Sorry, then I am out of ideas.

dazzyd said:
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Click to expand...
Click to collapse
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.

buhohitr said:
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
Click to expand...
Click to collapse
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.

dazzyd said:
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
Click to expand...
Click to collapse
The driver on your PC is not the problem. For using nvflash in APX mode you'd need the Secure Boot Key, which is unique for each device and which Asus does not give us, or the blob for the wheelie tool that can be created with the AndroidBoot hacked bootloader, which is also unique for each device. But for creating this blob, you need working fastboot access.

[Q] ROM manager clockworkmod update bricked tf700

Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.

shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.

Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.

No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!

shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.

MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T

MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.

I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?

shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.

OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards

ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.

[Q] TWRP problem

I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?

Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader

Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE

aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.

win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster

Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help

Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster

The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways

Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?

I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.

Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster

I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)

Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:

Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android

Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?

My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.

Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B

ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?

Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file

UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping

[Q] Killed Fastboot??

I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!

TerrorTodd said:
I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!
Click to expand...
Click to collapse
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...

LetMeKnow said:
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...
Click to expand...
Click to collapse
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...

TerrorTodd said:
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...
Click to expand...
Click to collapse
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?

LetMeKnow said:
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?
Click to expand...
Click to collapse
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.

TerrorTodd said:
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.
Click to expand...
Click to collapse
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..

and itightu
LetMeKnow said:
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..
Click to expand...
Click to collapse
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!

TerrorTodd said:
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!
Click to expand...
Click to collapse
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?

TerrorTodd said:
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?
Click to expand...
Click to collapse
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.

LetMeKnow said:
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.
Click to expand...
Click to collapse
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!

TerrorTodd said:
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!
Click to expand...
Click to collapse
Can you explain how you do it? You may miss a step or something..

LetMeKnow said:
Can you explain how you do it? You may miss a step or something..
Click to expand...
Click to collapse
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA

TerrorTodd said:
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Click to expand...
Click to collapse
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery

LetMeKnow said:
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery
Click to expand...
Click to collapse
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!

TerrorTodd said:
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!
Click to expand...
Click to collapse
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.

Pretoriano80 said:
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.
Click to expand...
Click to collapse
Dead Droid with the word "Error" underneath it is normal?
Yes the device is unlocked. I cannot get into recovery and cannot get Fastboot to work because the stupid USB drivers don't recognize the tablet. Works fine when not in Fastboot mode, but when goes into fastboot no USB. It's maddening!!!!

Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.

Pretoriano80 said:
Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.
Click to expand...
Click to collapse
Will do this tonight when I get home from work and will report back!

TerrorTodd said:
Will do this tonight when I get home from work and will report back!
Click to expand...
Click to collapse
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD

TerrorTodd said:
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD
Click to expand...
Click to collapse
What Windows version are you running? Win 8 doesn't seem to recognize the fastboot drivers, or maybe it was that you have to change the option of Windows only using Microsoft signed drivers?? Can't quite remember. But lots of people were unsuccessful getting fastboot to work in Win8.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

[SOLVED] Recovery and fastboot problems (soft bricked?)

I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
EDIT 2: I have finally solved the problem! I have quoted the important parts below in case anyone else has the same problem.
Basically I had some problems with the drivers the whole time on Windows 8. So what I did was disabled driver signature enforcement in Windows 8 (I think it re-enables after some time). I downloaded the drivers from this post and followed this other post , specifically this part:
jpasher said:
Making Windows recognize the TF300T
You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface
Open the file android_winusb.inf in the naked drivers directory.
Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
Code:
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83&REV_0232
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83
After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.
Click to expand...
Click to collapse
Then I booted up the tablet and connected to my computer. The drivers finally worked! I went into command prompt and typed "adb devices" and the device was there! Then I typed "adb reboot bootloader" and I got into the bootloader.
I had to look for the SKU too and since I couldn't find it cause I couldn't boot into Android it was in really small text in the bootloader at the top. Unfortunately after trying to flash the firmware in the bootloader it would not write over the system every time. So I followed this post instead: http://forum.xda-developers.com/showpost.php?p=49164067&postcount=167
After following the procedure it finally worked! Thanks cmendonc2 and everyone for your help, my friend is happy!

firtvid20 said:
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
Click to expand...
Click to collapse
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.

cmendonc2 said:
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
Click to expand...
Click to collapse
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP

firtvid20 said:
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
Click to expand...
Click to collapse
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.

cmendonc2 said:
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
Click to expand...
Click to collapse
Okay that's good to know. I am still unfortunately not able to get into fastboot. So I'll have to figure out what version the bootloader is before flash the firmware over.

Okay I got access to APX mode (useless from my understanding since my friends has no backups via nvflash), the bootloader while the recovery is loaded (although the driver isn't working for the bootloader), but I CANNOT GET INTO THE BOOTLOADER VIA VOLUME DOWN + POWER. Please help, somebody!

Here's a video explaining my problem.

firtvid20 said:
Here's a video explaining my problem.
Click to expand...
Click to collapse
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.

cmendonc2 said:
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
Click to expand...
Click to collapse
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?

firtvid20 said:
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
Click to expand...
Click to collapse
Its an option somewhere in TWRP called "ADB sideload".

cmendonc2 said:
Its an option somewhere in TWRP called "ADB sideload".
Click to expand...
Click to collapse
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.

firtvid20 said:
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
Click to expand...
Click to collapse
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.

cmendonc2 said:
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
Click to expand...
Click to collapse
Sorry, what is test mode? I am on Windows 8.

firtvid20 said:
Sorry, what is test mode? I am on Windows 8.
Click to expand...
Click to collapse
This should help: http://www.wugfresh.com/faq/8/

cmendonc2 said:
This should help: http://www.wugfresh.com/faq/8/
Click to expand...
Click to collapse
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.

firtvid20 said:
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
Click to expand...
Click to collapse
Hmm. Try using a different USB cable ( if u have it) or a different USB port.

cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?

firtvid20 said:
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
Click to expand...
Click to collapse
I vaguely remember someone posting that he succeeded to use adb/fastboot by installing a VirtualBox with Linux. You might have to search for the details.
Sent from my TF300T using Tapatalk

cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
Just an update. I got it working!! I did the following on this post to the universal drivers and then tried installing them on Windows 8. After booting my tablet to TWRP and plugging it in to my computer ADB works! I can reboot into fastboot now. Now I either have the option of flashing a JB compatible recovery or flashing the Asus firmware...

Since I'm not able to boot into Android would anyone be able to tell me what is the SKU on the picture below? So I can flash the correct firmware.
EDIT: Found it in the bootloader in small text. -.- It was the "WW" version.