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.
Hi,
I used jaggyjags Tutorial http://forum.xda-developers.com/showthread.php?t=1415223 for unlocking and rooting my HTC Explorer.
I managed to unlock the bootloader.
When I set to adding a recovery and ran the recovery.bat, nothing happened and after waiting 30 minutes of waiting for "writing recovery" I unplugged the phone and rebooted it.
I tried again and failed again. So I panicked a bit and selected _Factory Reset_ in the Boot Menu and now the phone wont even boot any more.
How can I get out of this mess?
Let me note the following things:
-In Fastboot mode the phone says unlocked in the top line
-When I try to run the recovery.bat again I get a _<waiting for device>_ prompt.
I would greatly appreciate on how to fix this.
cheers, akilaki
Have u turned usb debugging to on before running the bat file? If not go in settings--->manage apps---->development and tick usb debugging!
Sent from my HTC Explorer A310e using xda premium
akilaki said:
Hi,
I tried again and failed again. So I panicked a bit and selected _Factory Reset_ in the Boot Menu and now the phone wont even boot any more.
Click to expand...
Click to collapse
You shouldnt have factory reset the phone after unlocking the bootloader.... this creates a bootloop. Anyways, are you still able to access the CWM recovery??
jaydenmonckton said:
Have u turned usb debugging to on before running the bat file? If not go in settings--->manage apps---->development and tick usb debugging!
Click to expand...
Click to collapse
No, I haven't.
And now I am stuck in a bootloop, unable to access the settings ...
Do you have access to recovery?
Gladiator00 said:
Do you have access to recovery?
Click to expand...
Click to collapse
Sorry, but I am a newbie to all this ...
How would test my access to recovery?
psycoder said:
You shouldnt have factory reset the phone after unlocking the bootloader.... this creates a bootloop. Anyways, are you still able to access the CWM recovery??
Click to expand...
Click to collapse
In the original tutorial, there was no mention of a CWM recovery.
Gathering from reading, are supposing that I should try to flash the CWM recovery.img onto the phone via fastboot command?
Tried to flash the CWM recovery.img and that is the result I got:
-fastboot flash recovery cwmrecovery.img
->sending 'recovery'
->OKAY (0.871s)
->writing 'recovery'
and then nothings happens. No OKAY, on indication of finishing, no indication of activity or completion even after waiting some minutes.
Then I chose Reboot from the phone menu
and got the following message:
->FAILED (status read failed (Unknown error))
->finished. total time 698.061s
Any pointers, what might go wrong?
Try TWRP.
shortyoko said:
Try TWRP.
Click to expand...
Click to collapse
I get the same result as with CWM Recovery.
Writing the recovery fails with Unknown errror.
USB cable problem
akilaki said:
I get the same result as with CWM Recovery.
Writing the recovery fails with Unknown errror.
Click to expand...
Click to collapse
This problem may happen due to your USB cable also. Try to check ur cable is working properly or gave a try with another USB cable... I face similar problem with my USB cable but i had some other USB cable compatible for my phone so it resolve that problem.
Also post ur phone screen snap when u flashing the Recovery here and also the cmd screen shot...
i hope u get the information...
Solved
vasanth3008 said:
This problem may happen due to your USB cable also. Try to check ur cable is working properly or gave a try with another USB cable... I face similar problem with my USB cable but i had some other USB cable compatible for my phone so it resolve that problem.
Also post ur phone screen snap when u flashing the Recovery here and also the cmd screen shot...
i hope u get the information...
Click to expand...
Click to collapse
The problem was my Windows Installation. I used my XP virtual machine (on an iMac) for the whole procedure. When everything else failed I hooked the phone up to a Windows7 machine and voila, the phone booted into recovery.
So actually the flashing of the recovery was successful after all ...
Thanks to everybody for all the pointers in the thread.
Flash again with same rom
after flashing do clear/wipe data
that is very important which prevents any boot loop
akilaki said:
The problem was my Windows Installation. I used my XP virtual machine (on an iMac) for the whole procedure. When everything else failed I hooked the phone up to a Windows7 machine and voila, the phone booted into recovery.
So actually the flashing of the recovery was successful after all ...
Thanks to everybody for all the pointers in the thread.
Click to expand...
Click to collapse
S its HTC diver's bug..
...
http://dl.xda-developers.com/attach...b4976/50e47574/9/1/3/0/9/4/A310E_Recovery.zip
extract this file...connect ur fone (bootloader )
and run recovery.bat from the extracted file.........
:cyclops:
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.
I cant install ClockworkMod Recovery on my Asus TF700T, i have followed the guide, and tried with both ver. 6.0.4.4 and 6.0.4.7, and both give error "cannot load recovery".
My tablet is rooted, and running android 4.2.1, version number is 10.6.1.14.8, usb debugging is on, and all drivers should be installed on my pc, so i dont know what the problem is ???
Plz help, so i can get another rom, because it is really slow and "laggy" with the stock ROM
I'm new in here, so sorry if there is another thread with this question, i have tried to look around in the forum.
Sir M said:
I cant install ClockworkMod Recovery on my Asus TF700T, i have followed the guide, and tried with both ver. 6.0.4.4 and 6.0.4.7, and both give error "cannot load recovery".
My tablet is rooted, and running android 4.2.1, version number is 10.6.1.14.8, usb debugging is on, and all drivers should be installed on my pc, so i dont know what the problem is ???
Plz help, so i can get another rom, because it is really slow and "laggy" with the stock ROM
I'm new in here, so sorry if there is another thread with this question, i have tried to look around in the forum.
Click to expand...
Click to collapse
You are unlocked?
What do you get with this command when connected in fastboot mode:
Code:
fastboot devices
berndblb said:
You are unlocked?
What do you get with this command when connected in fastboot mode:
Code:
fastboot devices
Click to expand...
Click to collapse
It is unlocked, with asus unlocktool.
When i start it in fastboot mode, and writes fastboot devices, nothing happens ??
It is unlocked, with asus unlocktool.
When i start it in fastboot mode, and writes fastboot devices, nothing happens ??
Sir M said:
It is unlocked, with asus unlocktool.
When i start it in fastboot mode, and writes fastboot devices, nothing happens ??
Click to expand...
Click to collapse
You need to install the correct drivers. Try my thread here:
http://forum.xda-developers.com/showthread.php?t=2646279
my vega has boot loop. i cannot boot into recovery because it stucks there whenever i try to get into recovery. the only thing i have is fastboot. adb is useless because no usb debug. i connect it with my computer its detected as fastboot but i cant do anything to format it. i try unlock bootloader and it worked. but after i use run_cwm_adb.bat to boot a temporary recovery it has locked back my oem bootloader. after i runs the file.bat i managed to get into recovery,but it said failed to read system. i try to mount everything it still failed. so how should i do? wish i could make a bootable sdcard to fix this. it thinks its iso faulty. please help me. this is my email [email protected]
XDA Visitor said:
my vega has boot loop. i cannot boot into recovery because it stucks there whenever i try to get into recovery. the only thing i have is fastboot. adb is useless because no usb debug. i connect it with my computer its detected as fastboot but i cant do anything to format it. i try unlock bootloader and it worked. but after i use run_cwm_adb.bat to boot a temporary recovery it has locked back my oem bootloader. after i runs the file.bat i managed to get into recovery,but it said failed to read system. i try to mount everything it still failed. so how should i do? wish i could make a bootable sdcard to fix this. it thinks its iso faulty. please help me. this is my email [email protected]
Click to expand...
Click to collapse
Hello, and welcome to XDA! Perhaps you could try to fastboot flash the recovery again. If that doesn't work, reflash stock firmware. Or if you register, you can post your question here for more help: http://forum.xda-developers.com/android/help
Good luck!