Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
luisgarino said:
Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
Click to expand...
Click to collapse
I am getting the same thing after a recent update to Cromi 4.4
bender_123 said:
I am getting the same thing after a recent update to Cromi 4.4
Click to expand...
Click to collapse
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
berndblb said:
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
http://imgur.com/AABbF14
bender_123 said:
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
yEAP... That's the screen... I have a stock tablet,stock firmware, not unlocked, not rooted.
The buttons do respond... but nothing seems to work...
thanks.
Click to expand...
Click to collapse
Try to boot into fastboot: Hold Power and Volume Down buttons until you see three icons.
If you can get into the bootloader (see above) you have a fighting chance to get this solved. Although I have not tried the fastboot/adb commands I have in mind on a locked device. No idea if they would work but no harm in trying.
You can also try to get adb access while in recovery, but you need to set up fastboot/adb on your computer first.
Let me know if you need help with either.
Sent from my K00C using Tapatalk
Sound like you need to reinstall the os. You can find info here
http://forum.xda-developers.com/showthread.php?t=1946456
Related
Hi,
I have a BB0 eeepad. So, I've tryied to change kernel, After doing that, my eeepad continue rebooting, stucking on the Eeepad first screen (before the asus logo). CWM is not accessible, if I try to power on in apx mode, the tablet does that correctly. I have installed the correct driver using your tutorial (video) but i get the following error:
rcm version 0X4
Command send failed (usb write failed)
If I try to get into CWM, i get the double icon screen, wipe data or android. If i choose wipe, it works, but the tf101 won't boot. If i choose android, the screen show me "cold booting android" and it get freezed...
Could you help me ?
Thank you
Boot into recovery, you have to press Volume UP before the option to 'wipe' or 'cold boot' comes up to get into recovery. I have a feeling you aren't doing that.
Nope, i did it, but in this case, it continues to reboot in loop... (Same as wipe data)
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
baseballfanz said:
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
Click to expand...
Click to collapse
Yep, Immediately Reboot over and over again...
can you or not acces to cwm? if you can your device is not fully bricked
wich version of cwm recovery do you have?
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
If you have no recovery, and you cannot get into your ROM, and you are SBK2..hang it up, you FUBARed your tab..sell it to someone who needs some hardware maybe? Try to RMA it to Asus, who knows- and then go sign the petition to release the SBK2 and this problem would not inconvenience you or Asus any longer when this happens..
Sorry guys
magnumrt562 said:
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
Click to expand...
Click to collapse
You need to put working adb. try with a linux livecd or whatever you can, with that version of cwm recovery you will need some commands to be able to acces a microsd card and reflash the device
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Antjac said:
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Click to expand...
Click to collapse
You more than likely voided your warranty by flashing or rooting your device BTW..so good luck getting Asus to cooperate (fooling them)
Unfortunatlly, i've not other choice... (except if NvFlash's team find a solution for B70+)...
Wait and see...
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
magnumrt562 said:
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
Click to expand...
Click to collapse
That is supposed to happen, you need to execute adb shell to get a shell or adb push file /sdcard/ to push a file to the sdcard
I have the exact same thing, upgraded to ics, all worked ok, rooted, all ok for 2 day then nothing after a reboot, cant nvflash vol+ & power doesnt find any options bar stock if i recover goes to dead android with ! then asus logo and nothing. So it seems the issue is with the upgrade but as most of us rooted we may have a problem, mind you i did the wipe and recovery so it may have erased evidence.
If anyone is selling a TF101 I would love to buy one...
I forgot my TF101 on top of the car and ran it over, still works but the housing and lcd digitizer are dead >.<
Please email or pm me if interested
Well, good news...
As I said, I've sent my TF101 to Asus (to Czech Republic). I said my Tablet was bricked by updating to the ICS rom (That's not wrong in fact...).
So no problem, they flashed my tablet and sent it back. I've received it yesterday, everything is OK
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
V4lk0 said:
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
Click to expand...
Click to collapse
Just let the battery run dry. Then let it boot up normally without pressing any buttons when the battery runs out by connecting it to your charger. Hope it works!
Thanks for the reply. I tried that, but nothing happens, just the indicator LED on the power button turns on orange. The tablet does not boot on itself, if I connect the charger. I have to press the power button, but this results again in "Boot image verified failed"
Edit: Update. I figured out how to get into fastboot. I read something on google, with switching the screenlock switch on and off. That doesnt worked for me: The thing was, to hold the power button AND the volume button with the two knobs, then the tablet starts, to release the power button and THEN, while still HOLDING the volume button pressed, to switch on and off the screenlock button. Then the bootloader starts into fastboot mode, going into androidsdk and typed in cmd "fastboot oem unlock" solved the problem. The ROM starts and everything is fine
Why you don't write into the mentioned thread? There seems to come the issues from then ask there, sorry can't understand why opening new thread instead asking there.
Also the first time heard sucha thing, I also change the rooms from cm10 to Jacobus, back to stock, on cool one and to cm and back, to test everything and try something out.
Never had issues buy this ways
Gesendet von meinem GT-N7000 mit Tapatalk 2
I don't have the right to post in the proper thread, so I opened up a new one.
In order to install a JB based ROM, you need the JB compatible CWM. The version of CWM you used is apparently for ICS, so I am a little surprised it worked to install CM10. Where did this 6.0.2.3 come from? Use 6.0.1.5 from pawitp. I've used it and swapped/flashed ROMs at least ten times. Never encountered that issue (or any issue). As a matter of fact, I would just run Vorbeth's EasyRoot as it does all the grunt work for you. I've used it twice and it worked flawlessly.
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
V4lk0 said:
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
Click to expand...
Click to collapse
Hi I had the same issue after flashing from CM10.1 to CoolOne. However I fixed it by unlocking the bootloader => reinstalling recovery => flashing CM 10.1 back.
Did you have any luck recovering from APX?
Gullinbursti said:
Did you have any luck recovering from APX?
Click to expand...
Click to collapse
No, unfortunately not. I gave my tablet 2 weeks ago to the acer repair service and got it back today. The support said, that they have changed the mainboard and flashed the latest android on the tablet, but they did that on guarantee, so I didn't had to pay something ^^ Now it is running Android 4.1.1 Stock ROM from Acer.
Exact same problem
I am having the exact same problem. I am able to boot into recovery mode but then I get the android laying down with with the red triangle, question mark. My bootloader is unlocked but aftrer the update my screen is stucked on the ICONIA TAB startup screen.
Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
PaulCopel61 said:
Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?
TF700T first ever problem
berndblb said:
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?
Click to expand...
Click to collapse
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Trust that helps ...I am newbie at this worked perfectly up to now
PaulCopel61 said:
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
That's ok and healthy. You are in the bootloader menu and seeing exactly what you're supposed to see here.
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Click to expand...
Click to collapse
Mhh, this doesn't quite make sense...
If you say: Moving along to Android symbol - you are pushing Volume Up?
You toggle between the icons with Volume Down and execute them with Volume Up.
"Booting recovery kernel" would indicate that you pushed Volume Up on the flashing RCK icon which would fire up your recovery, and since it doesn't find a valid update file you get the Android on his back and the error message.
Since you are on stock your options are very limited. My guess is somehow your system partition got corrupted and your tablet can't boot into Android anymore.
You can give it a shot by using Volume Down to get the Android icon to flash and then pushing Volume Up, but I doubt that it would help since the tablet refuses to boot your system in the first place.
So if the above fails, go the Asus support website, the download section, enter "Transformer" in the search box, select the TF700t, choose "Android" as OS and from the resulting page choose the firmware for your SKU. If you are in Europe it would be WW, US for North America, JP for Japan - you get my drift...
Download the file and then unzip it ONCE, the result being another zip file. Rename that zip to EP201_768_SDUPDATE.zip and copy it to a microSD.
Turn the tablet off and insert the microSD.
Boot into the bootloader with Volume Down and Power.
Push Volume Up on the flashing RCK icon to boot into recovery and it should recognize the firmware zip and start to flash it.
You will probably loose everything you have on the tablet if it is not backed up. But I don't see any option for you to save your data if you want to get the tablet working again. I just hope you knew and lived by my mantra: Data not backed up is data not yet lost....
Good luck.
Tried advice
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul
PaulCopel61 said:
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul
Click to expand...
Click to collapse
I think you are going to have to wipe the device mate.
wipe
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul
PaulCopel61 said:
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul
Click to expand...
Click to collapse
When you are in the bootloader menu, choose the third icon 'Wipe Data'. You navigate there by pressing Volume Down twice, then it should be flashing. Press Volume Up to wipe your device.
You will have to re-install the firmware (same procedure I described already)
Thanks...
Everything working !!
Finally...
So I don't have similar problem again should I unlock?
What program should I use ?
Could you point to thread to show me how too ?
Paul
Glad you got it going!
Check this out: http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Daughter loves her xoom but a few days ago her password quit working- same password she has used since she got it in 2012, plus it doesn't show my wifi network on the unlock screen anymore. Xoom is bone stock with all current updates.
I figure it was stuck in a loop and attempted soft reboot-no luck...on to hard reset, pwr+down vol., goes to android recovery but no selection available just a picture of android on it's back with access hatch open and a large red triangle containing an exclamation point...froze up at that point but would soft reset and reboot to unlock screen but still no-go on the password and no-go on identifying the network.
I have gone through this 5-6 time since with no luck but now it will not go to android recovery, but instead "starting fastboot protocol support" comes up every time in LH corner of the screen.
I have exhausted my limited knowledge...any ideas??? Motorola support online was a waste of time and they want $100 if I send it in.
Thank you in advance.
Leatherneck2111 said:
Daughter loves her xoom but a few days ago her password quit working- same password she has used since she got it in 2012, plus it doesn't show my wifi network on the unlock screen anymore. Xoom is bone stock with all current updates.
I figure it was stuck in a loop and attempted soft reboot-no luck...on to hard reset, pwr+down vol., goes to android recovery but no selection available just a picture of android on it's back with access hatch open and a large red triangle containing an exclamation point...froze up at that point but would soft reset and reboot to unlock screen but still no-go on the password and no-go on identifying the network.
I have gone through this 5-6 time since with no luck but now it will not go to android recovery, but instead "starting fastboot protocol support" comes up every time in LH corner of the screen.
I have exhausted my limited knowledge...any ideas??? Motorola support online was a waste of time and they want $100 if I send it in.
Thank you in advance.
Click to expand...
Click to collapse
When you are in the android robot screen, press both volume up and power button and the recovery option will appear. You can do factory reset from there and delete user data to reset the password as well
superbay said:
When you are in the android robot, press both volume up and down and the recovery option will appear
Click to expand...
Click to collapse
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Leatherneck2111 said:
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Click to expand...
Click to collapse
Ah just edited my post just now. Try it when you can go to recovery
superbay said:
Ah just edited my post just now. Try it when you can go to recovery
Click to expand...
Click to collapse
Thanks, but it won't even go to recovery anymore- just to fastboot protocol support. No matter what I do. Should I try a complete battery drain and then recharge and see if something resets and allows access to recovery again? I'm out of ideas.
Thank you again for the suggestions.
Leatherneck2111 said:
Thanks, but it won't even go to recovery anymore- just to fastboot protocol support. No matter what I do. Should I try a complete battery drain and then recharge and see if something resets and allows access to recovery again? I'm out of ideas.
Thank you again for the suggestions.
Click to expand...
Click to collapse
Hmmm that's odd. If i may suggest, maybe you can try sbf too since it requires you to go to fastboot as well. But that's the very last resort everyone could ever do to their device. Never knew about battery drain method but you can try your way if you want to
Leatherneck2111 said:
Tried it when the robot appeared...nothing. It was frozen and I had to soft boot to get out. Now it won't even go to recovery, it goes dtraight to "starting fastboot protocol support" and then freezes.
Click to expand...
Click to collapse
Since you still can get to "starting fastboot protocol support", you can still use fastboot from command line.
Go google this "Motorola Xoom final rescue". It will teach you how to flash it back to
Stock Rom (Honeycomb).
Once your Xoom back in action, you can always upgrade it back to Jellybean.
You can boot into recovery using below command if USB debugging is enabled.
> adb reboot recovery
I have messed around with all my electronics in the passed, rooted them, put custom roms etc. with no trouble. So after getting frusterated with my Asus TF700T, I decided it was time to put Cyanogenmod on it. I read up on the forums and it recommended TWRP, I have always used clockwork mod but because TWRP was recommended I used that. I followed the directions and rebooted to the startup and it is stuck on the Cyanogenmod startup screen. So thinking that maybe it was just taking a long time because it was the first time, I waited and waited and waited. 24 hours later still stuck on the startup screen. I decided to try again, I pressed the power button and the volume down button and this is what I see:
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
Than I have 3 choices to choose from: RCK, Android, and wipe data
When I press volume up once to select RCK I get a message stating:
Booting Recovery Kernel image
Booting Failed
Unrecoverable bootloader error <0x00000000>. (This part is in red)
After reading I decided to try tranformer tool kit. So I put the tablet into APX mode. Seems to work, tablet restarts with a blank screen, the computer makes the appropriate noises expected when it detects the tablet, but when I check ADB I get a message ADB is not working or communicating with your pad. Evidently I screwed things up somewhere but I don't know where to go from here... Please, If anyone can help, It would be so appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
I sounds like the recovery flash failed. If you haven't already, I would try to re-flash TWRP through ADB and fastboot.
If you aren't sure how to do that through ADB use this post:
http://forum.xda-developers.com/showthread.php?t=2688891
Its the beginners guide in the general section.
I may be wrong here, but I've taken my TF700 from the brink of death and back again a few times.
What TWRP version did you flash and how???
The unrecoverable bootloader error is not good news. Usually you need a buster99 to get your tablet back - if you still can get into the bootloader and fastboot.
If you can, follow the instructions below to the letter (naturally you have to flash the TF700 system blob, not the TF300!), then flash a compatible recovery and a rom compatible with your recovery and bootloader. And if you're not sure ask first, then flash....
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
xellysiax said:
I have messed around with all my electronics in the passed, rooted them, put custom roms etc. with no trouble. So after getting frusterated with my Asus TF700T, I decided it was time to put Cyanogenmod on it. I read up on the forums and it recommended TWRP, I have always used clockwork mod but because TWRP was recommended I used that. I followed the directions and rebooted to the startup and it is stuck on the Cyanogenmod startup screen. So thinking that maybe it was just taking a long time because it was the first time, I waited and waited and waited. 24 hours later still stuck on the startup screen. I decided to try again, I pressed the power button and the volume down button and this is what I see:
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
Than I have 3 choices to choose from: RCK, Android, and wipe data
When I press volume up once to select RCK I get a message stating:
Booting Recovery Kernel image
Booting Failed
Unrecoverable bootloader error <0x00000000>. (This part is in red)
After reading I decided to try tranformer tool kit. So I put the tablet into APX mode. Seems to work, tablet restarts with a blank screen, the computer makes the appropriate noises expected when it detects the tablet, but when I check ADB I get a message ADB is not working or communicating with your pad. Evidently I screwed things up somewhere but I don't know where to go from here... Please, If anyone can help, It would be so appreciated.
Click to expand...
Click to collapse
xellysiax - We are sorry to hear about your tablet and is this still an ongoing issue? Send us an email at [email protected] with this post and your serial number and we will be more than happy to assist you.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Ummmm let me take a wild guess what customer support will advise:
Sorry you unlocked so no warranty but send it in and for $300 we may repair it. If we can't we only charge you for shipping both ways.
Nice to see you, Asus! Where've you been the last 2 years?
berndblb said:
Ummmm let me take a wild guess what customer support will advise:
Sorry you unlocked so no warranty but send it in and for $300 we may repair it. If we can't we only charge you for shipping both ways.
Nice to see, Asus! Where've you been the last 2 years?
Click to expand...
Click to collapse
Hush! @Asus_USA wanted to anounce the roll-out of Android Lollipoop for ASUS Transformers. Or was it the source code of bootloader?
das chaos said:
Hush! @Asus_USA wanted to anounce the roll-out of Android Lollipoop for ASUS Transformers. Or was it the source code of bootloader?
Click to expand...
Click to collapse
Yeah - I had that dream too one time or another....
Hi all, I just encountered this same error message for the TF700T when going into fastboot mode
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
All I have done is unlock the tablet. I was on the "Practice/Background" step in berndblb's (awesome) custom ROM guide before starting to load up fastboot and adb, when I saw the message in the upper left corner. When I go into RCK, "booting recovery kernel image" then appears under the error message. After 3-4 seconds I get the dead android with "error!" screen. When I power off, the tablet goes into normal bootup and the stock ROM still works perfectly fine.
Since it does, is there something I should do to resolve this issue BEFORE trying to push TWRP to the tablet? Just trying to be prudent...
Many thanks,
MM
Every Asus tablet I have seen has the "key driver not found" on boot - ignore it.
The dead Droid also is perfectly normal. It's the stock recovery not finding a firmware file to flash. Just keep going
berndblb said:
Every Asus tablet I have seen has the "key driver not found" on boot - ignore it.
The dead Droid also is perfectly normal. It's the stock recovery not finding a firmware file to flash. Just keep going
Click to expand...
Click to collapse
Brilliant, thanks. Now, let's see how this goes...
Cheers