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.
Related
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.
The situation : I am unlocked with Clean Rom installed. I cannot get in recovery or fastboot but the tablet will boot to CleanRom
What I am thinking about doing is installing the ASUS Transformer Pad Infinity TF700T Firmware: V10.4.4.25 (for US SKU version only). It is my impression that the Firmware will reinstall the bootloader etc. Then reloading CleanRom.
Will this work?
RLGL said:
The situation : I am unlocked with Clean Rom installed. I cannot get in recovery or fastboot but the tablet will boot to CleanRom
What I am thinking about doing is installing the ASUS Transformer Pad Infinity TF700T Firmware: V10.4.4.25 (for US SKU version only). It is my impression that the Firmware will reinstall the bootloader etc. Then reloading CleanRom.
Will this work?
Click to expand...
Click to collapse
How would you install the firmware without recovery?
What happens when you try to get to the bootloader menu? (turn off, hold volume-down while switching on)
_that said:
How would you install the firmware without recovery?
What happens when you try to get to the bootloader menu? (turn off, hold volume-down while switching on)
Click to expand...
Click to collapse
Does that not install from the PC?
I can get to the menu, make a selection then is just hangs and doesn't load anything else.
RLGL said:
Does that not install from the PC?
I can get to the menu, make a selection then is just hangs and doesn't load anything else.
Click to expand...
Click to collapse
What do you select? RCK, Android, or USB? Caution: Don't select "wipe data" under any circumstances until your recovery is known to be good or you will hard brick your tablet.
_that said:
What do you select? RCK, Android, or USB? Caution: Don't select "wipe data" under any circumstances until your recovery is known to be good or you will hard brick your tablet.
Click to expand...
Click to collapse
Finally I am back where I was yesterday. I can now boot to recovery fastboot works BUT sideload does not work with either TWRP or CWM (device not seen) . I have Super SU installed Should I switch to Super user?
Any other ideas?
RLGL said:
Finally I am back where I was yesterday. I can now boot to recovery fastboot works BUT sideload does not work with either TWRP or CWM (device not seen) . I have Super SU installed Should I switch to Super user?
Any other ideas?
Click to expand...
Click to collapse
Looks like a problem with your PC/driver setup. SuperSU/Superuser has no effect in the recovery.
_that said:
Looks like a problem with your PC/driver setup. SuperSU/Superuser has no effect in the recovery.
Click to expand...
Click to collapse
so what is the missing link? The device when booted is seen by the PC ADB devices returns the S/N. My SDK is updated.
Sideload works with my DNA but with the tablet The return is "error device not found"
RLGL said:
so what is the missing link? The device when booted is seen by the PC ADB devices returns the S/N. My SDK is updated.
Sideload works with my DNA but with the tablet The return is "error device not found"
Click to expand...
Click to collapse
Which version of TWRP is installed?
Does "adb devices" work while the tablet is in recovery?
What does "lsusb" say (if you are using Linux) or Windows Device Manager? It may be that the recovery is using a different USB device ID than Android.
Which version of TWRP is installed?
2.4.3.0
Does "adb devices" work while the tablet is in recovery?
No
What does "lsusb" say (if you are using Linux) or Windows Device Manager? It may be that the recovery is using a different USB device ID than Android.
Asus Android Composite ADB Interface
RLGL said:
Asus Android Composite ADB Interface
Click to expand...
Click to collapse
I don't know much about the Windows USB drivers and how they decide which devices to drive - other than that it doesn't work for everyone. Is this the same device displayed as when you are running real Android? Also compare the detailed properties of the device when running recovery and Android.
Alternatively, try booting a live linux environment, obtain the adb binary from somewhere, and try it under Linux.
_that said:
I don't know much about the Windows USB drivers and how they decide which devices to drive - other than that it doesn't work for everyone. Is this the same device displayed as when you are running real Android? Also compare the detailed properties of the device when running recovery and Android.
Alternatively, try booting a live linux environment, obtain the adb binary from somewhere, and try it under Linux.
Click to expand...
Click to collapse
I don't do linux. I will try a different recovery version from TWRP. When the device is connected while in recovery the computer makes a different sound for connecting, as if there is something wrong with the recovery usb identifier
RLGL said:
I don't do linux. I will try a different recovery version from TWRP. When the device is connected while in recovery the computer makes a different sound for connecting, as if there is something wrong with the recovery usb identifier
Click to expand...
Click to collapse
I am down to a driver issue. Other than the driver that comes in the Asus sync software what else is there. My SDK is up to date.
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
Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...
What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.
huy_lonewolf said:
What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.
Click to expand...
Click to collapse
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers
tf700tTRANSF said:
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers
Click to expand...
Click to collapse
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.
huy_lonewolf said:
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.
Click to expand...
Click to collapse
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?
tf700tTRANSF said:
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?
Click to expand...
Click to collapse
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.
huy_lonewolf said:
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.
Click to expand...
Click to collapse
I really dont get it....It just wont work. Fastboot still wont recognize my tablet.
If i get my hands on another Windows PC I will make a second attempt.
If someone knows a different solution, please tell me. Fastboot on the pc is properly installed for whats it worth....
Try Goo manager Open Recovery Script
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
tf700tTRANSF said:
Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...
Click to expand...
Click to collapse
mustafa_droid said:
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
Click to expand...
Click to collapse
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?
TWRP
berndblb said:
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?
Click to expand...
Click to collapse
I had to flash it with openrecovery-twrp-2.6.3.2-tf700t.blob. using the platform-tools because I could not use the one with Open Recovery script by that time I wiped the entire device! It could have been my fat fingers but I just installed CM 11-20131221 (Kit Kat 4.4.2) on my tablet today without any issues. I have not done much with it yet but I will let you know later.
hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
is it possible to root using adb sideload or install twrp using adb sideload?
articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence