Database Info

[Q] Bricked Transformer

I had a working Transformer until earlier today when the OTA update came along. Having accepted installation, my device now gets to the Eee Pad / ASUS logo and hangs there (waited for about 45 minutes after the update). Trying to reboot into recovery gives:
Android WW_epad-user bootloader < e> released by "WW_epad-8.2.3.6-20110414".
Checking for android ota recovery
Booting recovery kernel image
It does not give me the Up to recovery, Down to wipe option.
Any thoughts on how I might recover the device?
Many thanks in advance for your help.

Ohh **** that dont sound good
Sorry i cant help with any advice on fixing it, apart from trying a factory reset ?
Did you apply the update with under 50% of the battery available ?

No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.

morak said:
No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.
Click to expand...
Click to collapse
There are some things you can try in this thread - http://forum.xda-developers.com/showthread.php?t=1032374
Here a few key combinations for anyone interested:
VOL_DOWN + POWER (continue holding VOL_DOWN when it starts booting until you get a prompt) = Bootloader which offers two prompted options: (1) Recovery if you press VOL_UP within 5 seconds or (2) Data wipe if you press VOL_UP later. None of these seem to offer any USB devices like fastboot etc.
VOL_UP + POWER or VOL_DOWN + VOL_UP + PLUG IN USB = NVFlash mode. It clearly is the NVFlash APX device that we see appearing, but it barfs as soon as we run any sort of nvflash on it (Many Windows and Linux versions have been tried). Please note that in this mode the screen stays completely blank and the only way to get out of it is the following option:
Hold POWER for ~10s = Forced power off. This always helps if you are stuck in some weird mode and nothing on the screen
Dont know if any of these key presses will work on yours, worth a try to get it to recover ?

Yeah I had seen that thread. Unfortunately no joy from either option. I dont get the prompt when I do VOL DOWN+POWER, just seems to go straight into recovery. And as the post says, NVflash doesn't help at the moment.
Can't even seem to get the ADB USB devices to show up, I can only get the APX device which seems to be fairly useless ATM. Looks like I may have to RMA the thing.

What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?

Or maybe microphone ? lol i personnaly don't think those tablets would actually have a reset button, would check the manual first before sticking a paper pin into every holes...

My Transformer just came in, I accepted the OTA update and while installing it saw this thread and had a dreadful feeling. Thankfully, it rebooted fine and is working... sounds like something's wrong with yours unfortunately OP .

If you haven't tried the 10 second power button method as mentioned in an earlier post it's definitely worth a try.

stuntdouble:
I thought the 10 sec power button thing just turned the device off. Is there something else I can do that I am missing?

I think it clears cache and/or ram too. I'm not saying it will definitely fix your problem, it may not, but if it was me I'd try everything. It won't damage anything so don't worry.

Have you tried getting into the Clockwork mod recovery? You need to place it on an external microsd and when you do the holding down when switching on thing, it goes into the recovery on the card instead of the stock one. It might allow you to flash a rom to get it running again.
You can find the Clockwork recovery with instructions here
http://android.modaco.com/content/a...od-recovery-for-the-asus-eee-pad-transformer/

Good idea, unfortunately it didnt work. It doesnt appear to be allowing me to get to the point where it will read EP101_SDUPDATE.zip from the SD.

You sure filename is EP101? Shouldnt it be TF?

All the instructions call for EP101, but I tried TF too just in case!

dotpro said:
What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?
Click to expand...
Click to collapse
It's a microphone. If you go poking a paperclip in there, good luck claiming under warranty.

Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.

hecatomb said:
Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.
Click to expand...
Click to collapse
sonofab*tch same here. You would think they would warn people that this could happen. This is ridiculous. Their worthless phone tech kept traying to get me to hold f9. I wanted to reach through the phone and punch him.

So you are getting bricked units with stock? No modications or rooted devices?

stuntdouble said:
So you are getting bricked units with stock? No modications or rooted devices?
Click to expand...
Click to collapse
Root doesnt work on the US devices, also, OP hadnt rooted.

[Q] Can't get into recovery - Rooted and CWM

Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?

Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.

ferparedes said:
Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?
Click to expand...
Click to collapse
For the cwm thing: first of all, with your tablet turned on, try if the VOL UP and VOL DOWN keys are working. Then turn it off.
Press VOL DOWN + POWER until you see a little write on the upper left corner, then release all and press VOL UP.
For adb: turn on your tablet and connect it to your pc. On the screen of the tablet click on the icon of asus sync in the lower right corner then click on the popup. It will search for asus sync on your computer (have you installed it, right?). From that moment on, adb should work normally.
Hope this has helped.

Thanks! adb worked. Still can't get into recovery. I think it's borked, because I used "adb reboot recovery" and the tablet just rebooted normally.
Any more ideas??

akameswaran said:
Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.
Click to expand...
Click to collapse
Maybe that's it. I'll try it...didn't want to, because I don't want to wipe anything. This nice device of ours is so much more complicated than my SGS

Try this app, if CWM is installed correctly it should work. Cheers.
http://forum.xda-developers.com/showthread.php?t=1173434&highlight=reboot+recovery

Thanks! CWM was definitely broken, probably because I attempted OTA update.
So I went and used the guide in the nvflash unbricking thread, and since that guide installs Prime 1.4, I went ahead and updated to 1.7. Now I'm rooted, cwm'ed and prime'd!!!!
Sent from my Transformer TF101 using Tapatalk

[Q] Stuck at ASUS splash screen after April update (RESOLVED)

Ok so i've looked, cant find anything to help me out here... Its always possible i used the wrong search terms but i think i did pretty good...
Anyway, i had flashed i believe a CWM version of ICS when it first came out because it was easy to do, and i was able to keep root. Well I ended up with the CWM Recovery version that had the problem of constantly booting into CWM, so i fixed that and the tablet was telling me there was a firmware update, so i did it..
Now im stuck at the splash screen... When i try to boot into Recovery, it says its loading the recovery image but never does anything else. When i tried to load the other screen where you can choose recovery or the OS, i think people call it the linux screen? I dont remember, but when i did that, the big battery meter displayed on the phone for a second then disappeared... Wont turn on now, so i just plugged it in.. Is there something im missing? Or something i can do that anyone is aware of?

Check if the Android Debug Bridge works, and is your device a B60 or lower, (sbkv1)? If so you can use NvFlash to restore the tab.

Thing O Doom said:
Check if the Android Debug Bridge works, and is your device a B60 or lower, (sbkv1)? If so you can use NvFlash to restore the tab.
Click to expand...
Click to collapse
Its B90, SBKv2...
Last time i tried to boot, i tried Power+Volume Up and i saw the large battery that android phones typically show when they are powered off and you plug it in.. If i remember right, TF101 typically boots up if you plug it in when turned on, but it turned on, flashed that battery image and shut off, havent been able to turn it on since... Plugging it into my computer though, it wont turn on, plugging it into the wall outlet it turns on and sticks at the splash screen, so i'm gonna leave it there for a bit and see if it charges, then i'll try plugging it into the comp to see if ADB works... I'll let you know, thanks!

To get to recovery its power +vol down. Power + vol up gets you to apex mode, blank screen.
Sent from my Transformer TF101 using xda premium

.....don't know if I read all your info correct but to enter recovery is volume down + power until you get a message at the top of the screen then you let go both and press volume up to enter recovery or if you don't hit volume up it takes you to the cold boot / wipe data screen.

Yes, i posted that... I tried booting to recovery and it freezes when it says its loading the recovery image.
I was trying other combinations trying to remember the linux screen or whatever it was called, but either way. ADB mode doesnt work, im stuck at the splash screen.

SOLUTION: Do not do the update after fixing your TF101 if you have this same problem, because you'll have it again! Either way, here's what you do.
1) Since you cant shut off the TF101, hold the power button until the screen goes blank, then immediately let go of the power button and hold volume down. 2) The splash screen will re-appear, dont let go of the Volume Down button until you see the text at the top left corner of the screen prompting you to press volume up to enter recovery.
2) Dont press Volume Up since it will freeze trying to get into recovery. Instead, just wait and make sure your not holding down or pressing any buttons.
3) After a few second, you will be presented with two icons, one to wipe data and one to boot android/linux, selecting android/linux WILL work and boot, but you'll have the same issue as before without fixing anything if you reboot again. Follow the instructions to wipe your data. YOU WILL LOSE EVERYTHING!
4) At this point, Recovery still wont work. Boot your TF101 and get it setup and use the Play Store to download a terminal emulator
5) Open the terminal emulator and type SU and press enter, confirm superuser access.
6) Type in the following and press enter when done: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
7) Restart your transformer, let it boot normally the first time, after that, recovery should work.
8) Problem solved, DONT install the update this time! Install a custom ROM the typical way using CWM, and your set!

So, one thing i've noticed is im being spammed out of my mind from the OS to do that system update, so i've found that the best thing to do once your bootable, is to flash a custom ROM.
I tried this but went back to the same ICS version I had before, and ran into the same problems. Ended up with a whole other ROM, and now all problems are solved!
Good luck to anyone that has this issue!

#3
so you lost all data, all apps, all settings, all the effort and work and time to config apps and settings... UGH
I am in the same boat on my TF201 after the JB update bricked my tablet... really pisses me off as Asus says RMA it (which you know they will just wipe your data) or wipe the data yourself and hop it works. So badly want to salvage my app settings and all the work I did to trick out my tablet. F***** Asus, their own update fried my tablet.

[Q] no fastboot no adb wrong drivers?

WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help

jerimynal wiley said:
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
Click to expand...
Click to collapse
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.

graphdarnell said:
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
Click to expand...
Click to collapse
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager

jerimynal wiley said:
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
Click to expand...
Click to collapse
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.

graphdarnell said:
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
Click to expand...
Click to collapse
im sure it was the wrong recovery i dont know why i did it. i had another ics tablet and for some reasone i put both recovery images in the same folder the link u provided is one that i had previously read. I cant even get fastboot to "see" the tablet.

[Q] no adb and fastboot access - no root possible?

Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked

You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.

Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.

1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.

I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?

fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.

No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.

jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk