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.
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! I was trying to flash BAM Rom for TF300T. Unfortunately, i forgot to update my recovery (TWRP) in order to flash the KitKat version of the rom, and basicly now i can't launch the device normally since the flashing failed, but in the other hand i can still open my recovery and do stuff.
PROBLEMS: 1. I can't flash the newest recovery because my drivers simply aren't working ( <waiting for device> etc. )! I have tried installing ASUS Suite and other drivers i found online, both on 2 different PCs, nothing worked.
2. I can't flash a new rom with the recovery since there's no way to access the tablets storage. TWRP won't recognize my MicroSD
(Error mounting MicroSD).
So, here's what I need: Some way to access the device's storage or mount my MicroSd, or some way to fix the drivers so fastboot recognises my Tab!
pansysk75 said:
Hello! I was trying to flash BAM Rom for TF300T. Unfortunately, i forgot to update my recovery (TWRP) in order to flash the KitKat version of the rom, and basicly now i can't launch the device normally since the flashing failed, but in the other hand i can still open my recovery and do stuff.
PROBLEMS: 1. I can't flash the newest recovery because my drivers simply aren't working ( <waiting for device> etc. )! I have tried installing ASUS Suite and other drivers i found online, both on 2 different PCs, nothing worked.
2. I can't flash a new rom with the recovery since there's no way to access the tablets storage. TWRP won't recognize my MicroSD
(Error mounting MicroSD).
So, here's what I need: Some way to access the device's storage or mount my MicroSd, or some way to fix the drivers so fastboot recognises my Tab!
Click to expand...
Click to collapse
Have you tried reinstalling the Universal Naked USB Drivers? That fixes the fastboot issue for may people.
cmendonc2 said:
Have you tried reinstalling the Universal Naked USB Drivers? That fixes the fastboot issue for may people.
Click to expand...
Click to collapse
I have tried multiple times but I'm not sure if I'm doing it right.
pansysk75 said:
I have tried multiple times but I'm not sure if I'm doing it right.
Click to expand...
Click to collapse
Are you using Windows 8? There is a different way to do it with that. If it still doesn't work, you can try installing linux mint or ubuntu and work from there.
cmendonc2 said:
Are you using Windows 8? There is a different way to do it with that. If it still doesn't work, you can try installing linux mint or ubuntu and work from there.
Click to expand...
Click to collapse
No, I'm using Windows 7 (64 bit). I'm downloading ubuntu now...
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com