Database Info

[Q] TF101 BB0 full bricked...

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

Am I bricked?

So I made the mistake of installing Clockwork recovery mod when I installed Rom Manager on accident. Stupid mistake. I tried getting into recovery after that and it would hang right after pressing volume up at 5 secs. I did a normal restart of the tablet and decided to do a factory reset and see if i could restart with with and install TWRP. I ran the factory reset and restarted my tablet when prompted. This is when the issue started and now I'm stuck at the boot screen, the first screen you see when you start up. So i tried to start it up into recovery and it still wont budge. whats weird is it doesn't ask to press vol up it just says "Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03. Checking for android ota recovery. Booting recovery kernal image." Yet nothing happens. So am I bricked... is there any way out of this. My bootloader is unlocked and i am rooted... am i screwed? I read somewhere I might be able to fastboot, but is that possible if i cant get into recovery?

UPDATE: After doing some research I discovered that it might be possible using the NVflash method using site below but unfortunately NVflash is not compatible with the tf700 atm. Meanwhile I have submitting a ticket to asus but i do think NVflash would be my only hope if it actually worked for me.
androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/

NVFlash will *not* work on the TF700 - others have tried - it will probably make your situation even worse.
I don't know the answer to your question off-hand, but I'm sure someone will be able to provide a method to get you back up - just stay away from NVFlash on the TF700...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] Request for assistance with bricked tf300t

Reading through different forums I have read problems similar to mine but nothing exactly the same. I followed each fix anyway but I have not been successful.
The last thing I remember I did before the brick, I flashed CWM touch then CyanogenMod 9. I am unsure what occurred but I tried to flash back to my JB backup and the problem started.
Now my tablet comes on and just hangs on the Asus splash screen. If I turn the tablet off, it automatically comes back on.
I have tried to turn the tablet off and boot into recovery but it just boots back up to the splash screen and hangs; I have no option to go into recovery, android or fastboot.
I can get into what I think may be USB mode by pressing power and volume up through a couple of cycles; my computer detects a device but I cannot load drivers.
I have downloaded the Android USBPCdrivers but each time I try to navigate to the folder to install the device manager fails.
If anyone has any thoughts I would appreciate any assistance, thanks for your time!
UPDATE TO ORIGINAL POST
I as able to finally get my computer to recognize the tf300t in device manager by wiping all the usb drivers and installing "Universal Naked Driver 0.7" posted by 1wayjonny from XDA's website http://forum.xda-developers.com/show....php?t=1766220, not sure if it matters my computer "sees it" as a ASUS transformer prime rather than tf300t.
Now I am reviewing an ASUS unbrick called Wheelie http://forum.xda-developers.com/show....php?t=1687285, I believe this is geared towards the tf101. Anyone have any thoughts based on my status at this point? Thanks

If you are on JB stock, there is no way to flash a booting Cyanogen 9 ot 10 Rom.
Only Hydro JB is running!!!! And JB Stock.
1st of all you have to download a special Recovery. I highly recommend TWRP. You have to dl the JB version!!!!!
Flash it through fastboot. Then flash the Stock JB via TWRP recovery
Then flash TWRP again via fastboot.
Than flash The Hydro JB rom
Then reboot
Then go back to recovery
Then flash the latest Hydro update and reboot
You are like me stuck on the f...... new JB Bootloader and Kernel. All other roms are for the ICS Bootloader and Kernel, so no way of getting them running until the Cyanogen devs finding a solution.

Fastboot not an option
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?

mfsmith said:
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
Click to expand...
Click to collapse
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.

krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)

喔喔兒 said:
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
Click to expand...
Click to collapse
Waiting for nvflash won't do you any good since you needed to have it BEFORE bricking your tablet. If your tablet is already bricked, APX/nvflash will not help you.

krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
He could still try sending it for RMA. Mine got repaired for free for some reason.

An unusual Asus TF300T brick
Yeah, I'm having problems with my TF300T, too. I had CWM installed, but when I tried to flash a new ROM, I bricked it. No problem, I had figured it out before. But when I was in the bootloader, I inadvertantly erased instead of selecting the USB. Now, All I get when I try to boot up is the white ASUS screen with;
The Device is Unlocked
Android cardhu-user bootloader <2.0 e> released by "ww_epad-9.4.3.26-20120416" A03
Checking for android ota recovery
Booting recovery kernel image
My computer sees the tablet. The Device Manager shows: Asus Transformer Prime APX Interface
But it only shows up when I reset. As soon as I try to boot the tablet, it no longer sees it. I can't access the bootloader and Fastboot doesn't do anything except "waiting for device".
SO! If anyone can give me some help, I'd appreciate it. It's a puzzle for ya, anyway.
Thanx

As your last resort, this worked for me
Link to my thread---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to ask anything.

[Q] TF700t - Stuck on "Encryption unsuccessful" on stock system

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

[Q] Gifted Brick - Gift or not?

Ladies and Gents,
Received a tf700t from a friend who dabbles without reading. Not me, I swear! I've looked around and don't see an obvious lead so I will outline my situation and hope:
- Got a tf700t from a friend.
- He only gave it to me because he "attempted to flash a custom rom after unlocking the bootloader... and something else" without backing up blobs.
- Attempting to boot normally results in: "device is unlocked" screen... forever.
- Boot with Power+Volume_down results in:
"device is unlocked.
android cardhu-user bootloader <2.10 e > released by 'US_epad-9.4.5.26-20120720' A03
checking for android ota recovery
booting recovery kernel image"
- Can't seem to get device recognized by fastboot or adb.
Any guidance would be appreciated.
PS. XDA needs an additional 'post icon' wich looks like a brick with a ? on top of it
Thanks,
Sockky

You got a tablet with an ICS bootloader. If your friend tried to flash anything current - no wonder you're in a stuck boot....
Now the questions is: Did he flash a custom reocvery? And if yes - which one?
So boot to the bootloader menu (you should have 4 icons), use Volume Down to highlight RCK and Volume Up to enter recovery.
If you get an Android keeling over with an open belly you have the stock recovery. If not, the custom recovery should boot. Note name and version.
If you have a custom recovery you can use it to flash a current bootloader. If you have the stock recovery you have to manually flash the Asus firmware to get you current.
Post your answers and we take from it there.

berndblb said:
You got a tablet with an ICS bootloader. If your friend tried to flash anything current - no wonder you're in a stuck boot....
Now the questions is: Did he flash a custom reocvery? And if yes - which one?
So boot to the bootloader menu (you should have 4 icons), use Volume Down to highlight RCK and Volume Up to enter recovery.
If you get an Android keeling over with an open belly you have the stock recovery. If not, the custom recovery should boot. Note name and version.
If you have a custom recovery you can use it to flash a current bootloader. If you have the stock recovery you have to manually flash the Asus firmware to get you current.
Post your answers and we take from it there.
Click to expand...
Click to collapse
Very much appreciate the response.
- What recovery, I can't tell and I'm pretty sure he won't be able to either. I will assume cwm because of popularity.
- When I "power+volume_down", I am presented with the aforementioned "android cardhu-user(2.10 e) ... " message. I don't get any sick android (keeling over) or any other option.
Thanks again and anxiously awaiting your reply!
Sockky

sockky said:
Very much appreciate the response.
- What recovery, I can't tell and I'm pretty sure he won't be able to either. I will assume cwm because of popularity.
- When I "power+volume_down", I am presented with the aforementioned "android cardhu-user(2.10 e) ... " message. I don't get any sick android (keeling over) or any other option.
Thanks again and anxiously awaiting your reply!
Sockky
Click to expand...
Click to collapse
Ummm - on that screen with your bootlaoder version. You don't have 4 icons? RCK, Android, USB and Wipe Data?

berndblb said:
Ummm - on that screen with your bootlaoder version. You don't have 4 icons? RCK, Android, USB and Wipe Data?
Click to expand...
Click to collapse
I only get the message, as quoted in the top left of the screen, with the asus logo in the middle "ASUS, inspiring inovation...". nothing in terms of options.
Thanks,
Sockky

So I've led myself to 'https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/' and outlook looks positive except for the fact that I can't get to the point of "Checking for RCK image".
It would be beautiful if I could get some fastboot love on this thing. Drivers working on windows and same thing on linux.
"fastboot devices" returns nothing.

sockky said:
So I've led myself to 'https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/' and outlook looks positive except for the fact that I can't get to the point of "Checking for RCK image".
It would be beautiful if I could get some fastboot love on this thing. Drivers working on windows and same thing on linux.
"fastboot devices" returns nothing.
Click to expand...
Click to collapse
It is apparent to me that I'm going to need access to fastboot in order to move forward and that doesn't seem to be an option at this point. Given the notes I've posted on my bootloader, does anybody know of a way to recover/restore fastboot access? I'm beginning to think there is no hope for this device...

sockky said:
It is apparent to me that I'm going to need access to fastboot in order to move forward and that doesn't seem to be an option at this point. Given the notes I've posted on my bootloader, does anybody know of a way to recover/restore fastboot access? I'm beginning to think there is no hope for this device...
Click to expand...
Click to collapse
It can be very difficult to get fastboot to work with a borked tablet. What did you try?
Android SDK? The 15 second ADB tool? Minimal adb fastboot tool?
Are you using the original cable?
A USB 2.0 port, not 3.0?
The problem is on ICS you ahd to select the USB icon from the bootloader menu to get to fastboot mode - and you don't seem to get to that screen...
Sorry, wish I could be more helpful....

berndblb said:
It can be very difficult to get fastboot to work with a borked tablet. What did you try?
Android SDK? The 15 second ADB tool? Minimal adb fastboot tool?
Are you using the original cable?
A USB 2.0 port, not 3.0?
The problem is on ICS you ahd to select the USB icon from the bootloader menu to get to fastboot mode - and you don't seem to get to that screen...
Sorry, wish I could be more helpful....
Click to expand...
Click to collapse
I used Android SDK from a windows machine as well as a linux mint machine. I use both of these machines regularly for this type of thing so I don't think there is an issue with either environment.
Is there any way to do a factory-default type thing via aix mode? I can actually get the device in this mode -just not sure if there's anything I can do...
Yes to original cable and usb 2.0.
Thanks again... really appreciate it. This device is very new and shiny -I wonder if the cost of getting asus to fix it would be greater than grabbing one from ebay...

sockky said:
I used Android SDK from a windows machine as well as a linux mint machine. I use both of these machines regularly for this type of thing so I don't think there is an issue with either environment.
Is there any way to do a factory-default type thing via aix mode? I can actually get the device in this mode -just not sure if there's anything I can do...
Yes to original cable and usb 2.0.
Thanks again... really appreciate it. This device is very new and shiny -I wonder if the cost of getting asus to fix it would be greater than grabbing one from ebay...
Click to expand...
Click to collapse
You may be in luck since you're on a pre .30 bootloader. The nvflash thread you linked to earlier was for JB roms. You are still on ICS. Check this out: http://forum.xda-developers.com/showthread.php?t=1901479