Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced
dough30i said:
Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced
Click to expand...
Click to collapse
Your first mistake was to try to use Rom Manager with this tablet. There is info in various threads warning not to use it.
I'm not certain that you are bricked, but I'm also not exactly sure what you should do, other than keep trying to get to fastboot mode, so you can reflash the stock image.
Good luck!
okantomi said:
Your first mistake was to try to use Rom Manager with this tablet. There is info in various threads warning not to use it.
I'm not certain that you are bricked, but I'm also not exactly sure what you should do, other than keep trying to get to fastboot mode, so you can reflash the stock image.
Good luck!
Click to expand...
Click to collapse
yeh now i know, thought i read all the thread, but guess i was wrong on that part. mane thanks for the lil info
If you cannot get into any recovery your only hope is fastboot. I experimented a bit for the last few days with the new AOSP ROMs and got into some challenges myself. I managed to solve it by installing the stock .26 frmware with TWRP and subsequently reinstalling Zeus ROM, *but* fastboot was uncooperative when I tried pushing over a new recovery image.
Try to get into fastboot and push over the recovery.img that's posted by dasunsrule in the new thread on ClockworkMod Recovery -- dual benefits: you seem to prefer CWM anyway, and it might flash with fastboot. ; ) If you've gottn your feet wet with that for abit, report back in here. don;t think you're unreccoverably bricked, but fastboot is a minimum requirement until we get our mitts on an NvFlash that's working... Good luck!
EDIT: you might want to look here for the fastboot commands you need, and for other info as well: http://forum.xda-developers.com/showthread.php?t=1833212
MartyHulskemper said:
If you cannot get into any recovery your only hope is fastboot. I experimented a bit for the last few days with the new AOSP ROMs and got into some challenges myself. I managed to solve it by installing the stock .26 frmware with TWRP and subsequently reinstalling Zeus ROM, *but* fastboot was uncooperative when I tried pushing over a new recovery image.
Try to get into fastboot and push over the recovery.img that's posted by dasunsrule in the new thread on ClockworkMod Recovery -- dual benefits: you seem to prefer CWM anyway, and it might flash with fastboot. ; ) If you've gottn your feet wet with that for abit, report back in here. don;t think you're unreccoverably bricked, but fastboot is a minimum requirement until we get our mitts on an NvFlash that's working... Good luck!
EDIT: you might want to look here for the fastboot commands you need, and for other info as well: http://forum.xda-developers.com/showthread.php?t=1833212
Click to expand...
Click to collapse
YES there is hope for my 1 month old tablet, but i cant get into the recovery mode with the usb icon though like i said before when i did that power and volume down it went in to this:
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
so how am i goin to go fastboot mode with out the usb icon. mane it has to be an easy way to fix this softbrick or hardbrick what ever stage im at. is just so damn complicated for me to even comprehend this. *sigh*
What does it do when you power on while presing VOL-DOWN and let go? I mean, don't press VOL-UP to boot into the recovery module. Then you should be presented with the option to switch USB fastboot on...
MartyHulskemper said:
What does it do when you power on while presing VOL-DOWN and let go? I mean, don't press VOL-UP to boot into the recovery module. Then you should be presented with the option to switch USB fastboot on...
Click to expand...
Click to collapse
okay when i do that it goes to this state right below me, and it just stuck there with asus logo that's it
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
but the first time when it all started to happen i was able to go the state where i can reboot or go to USB mode and wipe data, but i remember reading the thread where if do the wipe data it will help but it didn't. so now im just stuck with this below me
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
dough30i said:
okay when i do that it goes to this state right below me, and it just stuck there with asus logo that's it
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
but the first time when it all started to happen i was able to go the state where i can reboot or go to USB mode and wipe data, but i remember reading the thread where if do the wipe data it will help but it didn't. so now im just stuck with this below me
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
Click to expand...
Click to collapse
Hey dough30i,
I had the same problem like you.
I m not really experienced and didnt know if it helps, but here http://forum.xda-developers.com/showthread.php?p=32787029#post32787029 I wrote a little story how I managed to bring my transformer back to life.
Good luck!
dough30i said:
okay when i do that it goes to this state right below me, and it just stuck there with asus logo that's it
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
but the first time when it all started to happen i was able to go the state where i can reboot or go to USB mode and wipe data, but i remember reading the thread where if do the wipe data it will help but it didn't. so now im just stuck with this below me
(Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image)
Click to expand...
Click to collapse
Don't let it attempt to boot into recovery. Once it brings up that list, hit VOL-UP within the 5 seconds to get the option to start fastboot.
Hello, I have noticed that there is no longer a fast-boot icon on the Bootloader.
I have found a workaround for this using Cyanogenmod 10.1.
1. Go to settings > Developer Options
2. Enable advanced reboot
3. when rebooting select "Fastboot" from the menu
Also, this very but you can still select options well in fast-boot. For instance I could highlight and select recovery when in fast-boot. It seems ASUS does not want us to be able to use fast-boot.
ostar2 said:
Hello, I have noticed that there is no longer a fast-boot icon on the Bootloader.
I have found a workaround for this using Cyanogenmod 10.1.
Click to expand...
Click to collapse
Read the text in the upper left corner in the bootloader menu - fastboot is always on.
_that said:
Read the text in the upper left corner in the bootloader menu - fastboot is always on.
Click to expand...
Click to collapse
Sorry, I did not realize that. I just had read in many other threads that the icon was missing.
And why it says Key driver not fond.. Booting OS? what is that
maxrdlf95 said:
And why it says Key driver not fond.. Booting OS? what is that
Click to expand...
Click to collapse
Same here
When i press and hold power and volume down until you get the option:
RCK - Andriod - wipe data
up left says:
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
This mean fastboot is working?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Yofinity said:
Same here
When i press and hold power and volume down until you get the option:
RCK - Andriod - wipe data
up left says:
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
This mean fastboot is working?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
yes, Fast boot is enabled...UNLESS you pick one of those three options by using the volume up button (enter).
Hi,
After I upgraded it to (ASUS) JellyBean and created a second user on it, my TF700 got slower and slower. Boot times were longer and longer, until it didn't boot at all. I'm trying to fix it, and need some help. My TF700 is not unlocked, and not rooted (plain stock, I just updated the firmware through OTA).
Here is the situation, all done not docked on the keyboard and unplugged from the charger (note that the tablet is correctly charging (yellowish light when plugged, turn green after some time)):
"Normal boot"
When I press the Power button, I feel a vibration, but either :
- (most of the time) nothing appears on the screen
- or on some occasion that the logo appeared, then changed the silver 3D and ... it reboots (sometime it doesn't even reach the silver logo, it just reboots from the white one) [note : I managed yesterday to reach the home screen, but it rebooted 30s after I entered the unlock pattern]
"reset" with pin in side hole
Didn't appear to do much... (when I was stuck after hard reset (see below), it just turned the screen black)
"Hard reset"
Pressing Volume Down & Power, I managed to get to the recovery menu. I get this
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
Then I have 3 choice : RCK, Android, Wipe data.
- if I proceed with "RCK", I get :
Booting Recovery kernel image
Signature match
Then I get the Android "droid robot" 3D logo with "installing system update" (or something like that, since my system langage is not in english), then I get the Droid lying, open with a "!", and under that "Error".
- If I proceed with "Android" : I get
Cold-booting Linux
Booting failed
Unrecoverable bootloader error (0x00000000).
- If I proceed with "wipe data" : it goes through, and back to the 3 choices (RCK, Android, Wipe dat).
Firmware on microSDCard
1) I put WW_epad_user_10_4_4_20_UpdateLauncher.zip on a microSD card, renamed it EP201_768_SDUPDATE.ZIP, put the microSD card on the TF700, rebooted with VolumeDown &Power, but get the same thing as above :
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
and the 3 choices : RCK, Android, Wipe data. I proceeded with "RCK", and got :
Booting Recovery kernel image
Signature mismatch
Booting failed
Unrecoverable bootloader error (0x00000000).
2) I put WW_epad_user_10_6_1_14_8_UpdateLauncher.zip on a microSD card, renamed it EP201_768_SDUPDATE.ZIP, put the microSD card on the TF700, rebooted with VolumeDown &Power, but get the same thing as above :
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
and the 3 choices : RCK, Android, Wipe data. (whichever I select, I get the same results as above in "Hard reset")
Can anyone tell me how I can fix this ?
eyaeya said:
Hi,
After I upgraded it to (ASUS) JellyBean and created a second user on it, my TF700 got slower and slower. Boot times were longer and longer, until it didn't boot at all. I'm trying to fix it, and need some help. My TF700 is not unlocked, and not rooted (plain stock, I just updated the firmware through OTA).
Here is the situation, all done not docked on the keyboard and unplugged from the charger (note that the tablet is correctly charging (yellowish light when plugged, turn green after some time)):
"Normal boot"
When I press the Power button, I feel a vibration, but either :
- (most of the time) nothing appears on the screen
- or on some occasion that the logo appeared, then changed the silver 3D and ... it reboots (sometime it doesn't even reach the silver logo, it just reboots from the white one) [note : I managed yesterday to reach the home screen, but it rebooted 30s after I entered the unlock pattern]
"reset" with pin in side hole
Didn't appear to do much... (when I was stuck after hard reset (see below), it just turned the screen black)
"Hard reset"
Pressing Volume Down & Power, I managed to get to the recovery menu. I get this
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
Then I have 3 choice : RCK, Android, Wipe data.
- if I proceed with "RCK", I get :
Booting Recovery kernel image
Signature match
Then I get the Android "droid robot" 3D logo with "installing system update" (or something like that, since my system langage is not in english), then I get the Droid lying, open with a "!", and under that "Error".
- If I proceed with "Android" : I get
Cold-booting Linux
Booting failed
Unrecoverable bootloader error (0x00000000).
- If I proceed with "wipe data" : it goes through, and back to the 3 choices (RCK, Android, Wipe dat).
Firmware on microSDCard
1) I put WW_epad_user_10_4_4_20_UpdateLauncher.zip on a microSD card, renamed it EP201_768_SDUPDATE.ZIP, put the microSD card on the TF700, rebooted with VolumeDown &Power, but get the same thing as above :
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
and the 3 choices : RCK, Android, Wipe data. I proceeded with "RCK", and got :
Booting Recovery kernel image
Signature mismatch
Booting failed
Unrecoverable bootloader error (0x00000000).
2) I put WW_epad_user_10_6_1_14_8_UpdateLauncher.zip on a microSD card, renamed it EP201_768_SDUPDATE.ZIP, put the microSD card on the TF700, rebooted with VolumeDown &Power, but get the same thing as above :
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
and the 3 choices : RCK, Android, Wipe data. (whichever I select, I get the same results as above in "Hard reset")
Can anyone tell me how I can fix this ?
Click to expand...
Click to collapse
You are pretty close - but you neglected to unzip the downloaded firmware file ONCE, the result should be a zip called "US_epad-user-10.6.1.14.8.zip".
That's the file you need to rename to EP201_768_SDUPDATE.zip, copy to a microSD, insert it and boot into recovery. This time the recovery will recognize it and flash it.
But use the 10.6.1.14.8 firmware. The bootloader will not allow you to flash ICS firmware (that's the signature mismatch you got earlier).
Now stuck in recovery loop...
berndblb said:
You are pretty close - but you neglected to unzip the downloaded firmware file ONCE, the result should be a zip called "US_epad-user-10.6.1.14.8.zip".
That's the file you need to rename to EP201_768_SDUPDATE.zip, copy to a microSD, insert it and boot into recovery. This time the recovery will recognize it and flash it.
But use the 10.6.1.14.8 firmware. The bootloader will not allow you to flash ICS firmware (that's the signature mismatch you got earlier).
Click to expand...
Click to collapse
Thanks, I missed the unzipping stage.
So did the unzipping, renaming, copying, inserting and booted into recovery. Looks like the recovery did recognize it : I had Android "droid robot" 3D logo with "installing system update" and a blue bar underneath ... but after approx 5mn it rebooted at once to the same screen/message, and has been doing so (reboot fater reboot) for an hour. I powered OFF and ON : the white ASUS logo appeared, with a grey bar underneath (and a bit of light blue at the beginning of the bar) ; the bar filled with ligth blue and I was locked here. I reseted with the pinhole ; I have bee trying to re-run recovery, but can't managed to do so (the tablet is virbating when I hold the key, but he screen stays black (that was previously the case 3 times out of 4, now it seems it's 4 out of 4)
Any clue ?
eyaeya said:
Thanks, I missed the unzipping stage.
So did the unzipping, renaming, copying, inserting and booted into recovery. Looks like the recovery did recognize it : I had Android "droid robot" 3D logo with "installing system update" and a blue bar underneath ... but after approx 5mn it rebooted at once to the same screen/message, and has been doing so (reboot fater reboot) for an hour. I powered OFF and ON : the white ASUS logo appeared, with a grey bar underneath (and a bit of light blue at the beginning of the bar) ; the bar filled with ligth blue and I was locked here. I reseted with the pinhole ; I have bee trying to re-run recovery, but can't managed to do so (the tablet is virbating when I hold the key, but he screen stays black (that was previously the case 3 times out of 4, now it seems it's 4 out of 4)
Any clue ?
Click to expand...
Click to collapse
That sounds really bad my friend. If you cannot get into the bootloader menu with Volume Down and Power, it's time to send it in to Asus. I hope you are still under warranty. This baby is a brick....
berndblb said:
That sounds really bad my friend. If you cannot get into the bootloader menu with Volume Down and Power, it's time to send it in to Asus. I hope you are still under warranty. This baby is a brick....
Click to expand...
Click to collapse
Am not anymore under warranty
I don't seem to be able to boot on recovery : I just get the white ASUS logo, with a grey bar underneath (and a bit of light blue at the beginning of the bar) ; then the bar fills with ligth blue and :
- most of the time stays locked here
- on the last occasion, the tablet rebooted, show the regular white Asus boot logo, then the silver Asus logo, then rebooted and so on (loop).
Too bad for I'm leaving a week for a 28 hours travel (3 fligths, with lots of waiting time), and I'd really whish I could have my tablet for watching series/movies. Not to mention the 19 hours travel back
----------------
update : I gave it one more try after it stopped looping in "normal" reboot. I did manage to boot in recovery, selected RCK (still with the 10.6.1.14.8 firmware) ; it does the same as previously => Android "droid robot" 3D logo with "installing system update" and a blue moving thin bar underneath ... but after approx 3 or 4mn, the bar stopped moving for 1 mn, and the tablet rebooted (well it looks like reboot : the screen turns black - backlighted, then not backlighted, then backlighted again) to the same screen/message, is looping in reboot after reboot)
eyaeya said:
Am not anymore under warranty
I don't seem to be able to boot on recovery : I just get the white ASUS logo, with a grey bar underneath (and a bit of light blue at the beginning of the bar) ; then the bar fills with ligth blue and :
- most of the time stays locked here
- on the last occasion, the tablet rebooted, show the regular white Asus boot logo, then the silver Asus logo, then rebooted and so on (loop).
Too bad for I'm leaving a week for a 28 hours travel (3 fligths, with lots of waiting time), and I'd really whish I could have my tablet for watching series/movies. Not to mention the 19 hours travel back
----------------
update : I gave it one more try after it stopped looping in "normal" reboot. I did manage to boot in recovery, selected RCK (still with the 10.6.1.14.8 firmware) ; it does the same as previously => Android "droid robot" 3D logo with "installing system update" and a blue moving thin bar underneath ... but after approx 3 or 4mn, the bar stopped moving for 1 mn, and the tablet rebooted (well it looks like reboot : the screen turns black - backlighted, then not backlighted, then backlighted again) to the same screen/message, is looping in reboot after reboot)
Click to expand...
Click to collapse
If your tablet were unlocked with a custom recovery, there would be quite a few options to try. It seems to me that the initial flash of the firmware goes ok and then it hits a roadblock somewhere - possibly a corrupted partition...?? But with only the stock recovery and without fastboot - very little you can do.
If you get into the bootloader menu again, try the other options: Push Volume Down twice to highlight 'Wipe Data' and then Volume Up to execute. Maybe that clears whatever is blocking the flash. Selecting the Android and pushing Volume Up would boot you into system.... if you had a working OS....
Just try any combination of the above - there's nothing you can do wrong at this point.
berndblb said:
If your tablet were unlocked with a custom recovery, there would be quite a few options to try. It seems to me that the initial flash of the firmware goes ok and then it hits a roadblock somewhere - possibly a corrupted partition...?? But with only the stock recovery and without fastboot - very little you can do.
If you get into the bootloader menu again, try the other options: Push Volume Down twice to highlight 'Wipe Data' and then Volume Up to execute. Maybe that clears whatever is blocking the flash. Selecting the Android and pushing Volume Up would boot you into system.... if you had a working OS....
Just try any combination of the above - there's nothing you can do wrong at this point.
Click to expand...
Click to collapse
Well, I have access to fastboot. lj50036 is helping me out. I'm applying the commands from this page http://forum.xda-developers.com/showthread.php?t=2538028 , starting from "sudo fastboot devices" (skipping the Nvflash part at the beginning of the post).
It did hang on the commands "sudo fastboot -w", "sudo fastboot erase misc", "sudo fastboot erase cache" -> I manually rebooted into flashboot/recovery each time.
But it also hangs during flash of the firmware, and this one I cannot skip... :
[email protected] ~ > sudo fastboot -i 0x0B05 flash system /media/mint/D/boot.blob
erasing 'system'...
OKAY [ 2.248s]
sending 'system' (800927 KB)...
OKAY [123.853s]
writing 'system'...
eyaeya said:
Well, I have access to fastboot. lj50036 is helping me out. I'm applying the commands from this page http://forum.xda-developers.com/showthread.php?t=2538028 , starting from "sudo fastboot devices" (skipping the Nvflash part at the beginning of the post).
It did hang on the commands "sudo fastboot -w", "sudo fastboot erase misc", "sudo fastboot erase cache" -> I manually rebooted into flashboot/recovery each time.
But it also hangs during flash of the firmware, and this one I cannot skip... :
[email protected] ~ > sudo fastboot -i 0x0B05 flash system /media/mint/D/boot.blob
erasing 'system'...
OKAY [ 2.248s]
sending 'system' (800927 KB)...
OKAY [123.853s]
writing 'system'...
Click to expand...
Click to collapse
So your bootloader is unlocked after all?
berndblb said:
So your bootloader is unlocked after all?
Click to expand...
Click to collapse
No, it's still stock. The file "boot.blob" is the stock Asus firmware ; I need an unlocked bootloader to flash it from my PC ?
eyaeya said:
No, it's still stock. The file "boot.blob" is the stock Asus firmware ; I need an unlocked bootloader to flash it from my PC ?
Click to expand...
Click to collapse
Is there any possibility to unlock the bootloader from a PC attached to the tablet through USB ?
(I guess I learned at leats something in the process : one should unlock its bootloader as soon as the warranty expires..)
eyaeya said:
Is there any possibility to unlock the bootloader from a PC attached to the tablet through USB ?
(I guess I learned at leats something in the process : one should unlock its bootloader as soon as the warranty expires..)
Click to expand...
Click to collapse
Sorry - the only way to unlock is with the Asus Unlock tool, which is an apk you have to install and run on the tablet.
hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)
nasiroddin said:
hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)
Click to expand...
Click to collapse
If you see three icons on your bootloader menu, you have a newer bootloader version than ICS. You can ckeck the bootloader version when you are in it and it is in the upper left corner with a small tiny prints. You are also already in the the fastboot mode if you are in the bootloader menu. You can check your fastboot by typing "fastboot devices" to see if your PC can communicate with your device. Good luck...:fingers-crossed:
on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?
nasiroddin said:
on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?
Click to expand...
Click to collapse
sbdags created a zip installer for twrp and you can check out the script here:
http://forum.xda-developers.com/showthread.php?t=2646279
This is a very nice tutorial for installing adb/fastboot and you can find out more information on this post:
http://forum.xda-developers.com/showthread.php?t=2688891
Please read through these two posts before proceeding with installing your new twrp, good luck...:fingers-crossed:
Hi all,
I am new in this forum, and also a newbe when it's about rooting and flashing android devices. My TF300T tablet is 3 years old and I wanted to give it a second live by upgrading from 4.2.1 to 5.1.1.
I understand form several threads that you have to make sure you follow a few steps before upgrading to 5.1.1:
1: Enable developer mode, activate USB debug and accept not verified apps. (Done!)
2: Unlock bootloader. (Done! unlock message appears when tab starts up)
3: Flash TWRP via fastboot. This fails over and over...message: "waiting for device"
I can perform the command ADB reboot bootloader via CMD, so it looks like the drivers work and the connection is there. What could I be doing wrong? Before I unlocked the bootloader, I used the "wipe data" option in the bootloader and suspect because of that I can't run recovery via the RCK in bootloader anymore. Are both issues linked to each other?
Beside the fact that I am stuck on this, I also don't know if I run a JB bootloader or not. Can somebody confirm if this is a JB version? This is my bootloader message in bootloader mode:
key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" a03
Starting Fastboot USB download protocol
*Update*
While I was still trying options and reading threads after placing this thread, I decided to also install adb/fastboot on my mac, and there I get a more specific error message when I try to flash TWRP. It's not saying "waiting for devices" but "error: cannot load 'twrp.img'"
Also when I run fastboot devices, I get the device serial back so the link is there.
Is it possible that there is a problem with the destination folder or partition?
Thanks for your help!
No need for further support, I was able to solve the issue. When I point to the specific directory where the twrp file is stored during fastboot flash recovery, it works just fine.
Strange this is not discribed in any instruction.