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.

Stuck in safe mode help

I need help getting the wife's phone out of safe mode. I rooted the phone and its on a stock rooted 2.2.1 rom and if you do a restart it loads the the boot loader screen and I can pick recovery and then restart but it still boots in to safe mode says it in the bottom left corner. She has apps and stuff on there so trying to get everything back but not really sure how to get this fixed. Also have pulled the battery out and still no luck going to safe mode. I guess if I can't get it fixed can I install a factory stock rom back on it to fix this? I know if I do she will lose everything. Just need the best option to get this fixed.
Thanks

"Safe mode"???? I've never heard of that.

Yeah it the bottom left corner of the phone it says safe mode it says it down near the home icon and over top off the circle with the up arrow. It looks like it may only load mainly core apps and some others but not all kind of like a windows pc in safe mode. And like I said I've pulled the battery out and rebooted and still says it and also from the boot loader screen picked recovery and then restart and once booted it still says it in the bottom left corner.

I gotta ask... Are you sure this is an Inspire?

Yes this is a inspire. I'm at work and once I get home I will use my inspire and take a pic of the screen with it saying it and upload it here. Mine I just got and haven't rooted it yet still a little unsure on the new way so you may see some questions from me on it a little later.

I have seen people stuck in safe mode . The guy was stuck in hboot and would not boot up. somehow he managed to boot it up but he said it was in safe mode. he was going to flash the gingerbread ruu, but havent gotten an update.
you posted in the thread gene it was titled bricked.
as to the question isse here. you might have to flash a new rom, though not ideal. But google does a good job of backing up apps/settings

I'll be damned:
http://www.technipages.com/htc-hero-start-in-safe-mode.html
This seems more applicable to the Inspire:
http://www.myvusers.com/forums/htc-thunderbolt/7426-safe-mode-htc-thunderbolt-adr6400.html

I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks

sreadesjr said:
I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks
Click to expand...
Click to collapse
Apparently the hero has a "hard" menu key. The Inspire does not so you have to ue a different "hard" key. I tried it and the thunderbolt method works for the Inspire (using VOL "hard" key).
It was mentioned over on #liberatedAria that you may have a stuck VOL-UP key so it goes into safe mode every time you boot.

Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.

sreadesjr said:
Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.
Click to expand...
Click to collapse
No, I just rebooted. That's why we thought the key might be stuck.

yeah I think it is the vol key stuck as soon as you try to turn phone on it just goes to hboot screen. Sense I do believe the volume key is stuck does anyone know how hard it would be to fix this problem? I'm sure I can order a new volume button on ebay but not sure that will fix the problem. I need to get it fixed so I can get it back to factory rom so I then can take it back to AT&T cause I do have insurance on the phone but don't believe they will take it back cause of it loading to the hboot screen menu.

Can anyone give me any suggestions on what to do to get this fixed? And would it be possible to use the stock rom or stock exe file to put it back to stock form to take it back to AT&T to get it repaired or can I repair this problem myself by ordering a new volume key off ebay.

You should try gene pooles s-on tool in the Dev section. Since you have insurance I would just have it replaced

Need help with my Transformer and don't know where else to look.

So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!

Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?

Cronoadvan said:
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Click to expand...
Click to collapse
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.

nlheiz said:
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Click to expand...
Click to collapse
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
tingtan said:
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
Click to expand...
Click to collapse
The screen does not light up at all, and USB is accessible after around 4 secs of long pressing power and hearing the click noise(camera?) which is not normal since no device boots so fast. This tablet never did anyway, taking from 20 to 30 secs.
After USB is available I can adb shell from windows but that's pretty much it, I don't know what to do afterwards.

Cronoadvan said:
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
Click to expand...
Click to collapse
Check your serial number. If its below B70 you got SBK1.

Goatshocker said:
Check your serial number. If its below B70 you got SBK1.
Click to expand...
Click to collapse
Yes it is, it's B50. Is that a bad thing?

Cronoadvan said:
Yes it is, it's B50. Is that a bad thing?
Click to expand...
Click to collapse
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....

nlheiz said:
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
Click to expand...
Click to collapse
Thank you so much! That was my last resort and sadly was clueless on how to do that too!
Hopefully it's just some kind of weird software coma, but now even if it's a hardware problem there is still hope!
Thank you very much good Sir, may life repay you thrice as much

Your welcome......please read the apx and nvflash option really well. It is rather straightforward but you have to install the apx drivers correct and use power and volume + (together) to enter apx mode. Voor drivers maybe you can use this forum below:
http://forum.xda-developers.com/showthread.php?t=1185104
it had an option for installing apx drivers for win 7 64 bit.
Hope your screen will work again, and if not you can send it back without warrant loss...
good luck!!!!!

Can't access stock recovery on 4.4.2?

Not sure if anyone else has tried but today's ioroot 25 update includes root for those on 4.4.2. I tried using the manual method indicated only to realize that I can't reboot into the stock recovery. Apparently two other people with the D801 have the same problem, where after doing "adb reboot recovery" the phone boots into recovery for an instant and immediately reboots. Can anyone else running stock 4.4.2 confirm whether they experience the same behavior?

ChaoticKinesis said:
Not sure if anyone else has tried but today's ioroot 25 update includes root for those on 4.4.2. I tried using the manual method indicated only to realize that I can't reboot into the stock recovery. Apparently two other people with the D801 have the same problem, where after doing "adb reboot recovery" the phone boots into recovery for an instant and immediately reboots. Can anyone else running stock 4.4.2 confirm whether they experience the same behavior?
Click to expand...
Click to collapse
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?

18.4009 said:
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?
Click to expand...
Click to collapse
Same problem, just posted about this actually haha. Where's our solution?!?!

18.4009 said:
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?
Click to expand...
Click to collapse
That sucks. By any chance did you happen to have a copy of the stock ROM on your phone? I'm wondering if it just automatically flashes whatever file is made available to it. I did notice some of my widgets were reset but otherwise I can't see that anything about my phone was changed.

ChaoticKinesis said:
That sucks. By any chance did you happen to have a copy of the stock ROM on your phone? I'm wondering if it just automatically flashes whatever file is made available to it. I did notice some of my widgets were reset but otherwise I can't see that anything about my phone was changed.
Click to expand...
Click to collapse
No, sure didn't. I have it all setup again.. Going to hold off now until we see a for sure fix.
I really miss having root so I decided to follow this guide: http://forum.xda-developers.com/showthread.php?t=2432476
But now for what ever reason attempting to back to 4.2.2 will not work. Fails every time... I didn't have that issue before so I am not sure what the deal is.

autoprime said:
TMO D801 users on KK... there is SOME hope still. I am on ZVA on my Sprint G2(4.2.2) which has no "adb reboot recovery" option... it does tne same thing thats happening to you guys.. quick "system update" msg (or something along those lines) and then reboots phone.
now.. on sprint g2.. vol up + power brings you to the hard reset menu. BUT.. vol down + power brings me to the full STOCK recovery menu.
Now I know your method to get into the hard reboot screen is different.. i believe its vol down + power.. let go at lg screen the press again? well has anyone tried any alternate combos? there may be another button combo to bring you into the full stock recovery menu instead of the hard reset menu. once at the full recovery menu you can use adb sideload to flash to kk_root.zip in ioroot25.
good luck
Click to expand...
Click to collapse
It seems that ours is not the only model G2 with this issue. Looks like if we can figure out the button combo to bring us into stock recovery we should be able to get this to work. Having spent the greater part of the last hour trying to come up with something, I still haven't found anything. What I do know is pressing vol down + power until the LG logo and either vol down + power OR vol up + power will take me to the hard reset menu.
I also managed to get to a menu that asked if I want to answer phone calls with physical buttons by holding down all three, releasing and holding them again. But for some reason I wasn't able to replicate this. Now when I continue holding down all three buttons at the LG logo, after getting there using any button combo, the phone just shuts off.
Has anyone successfully entered the D801 stock recovery using button combos? I have yet to find any method other G2 users discussed that works for me.

Question I completely screwed up my phone, no recovery access

So, here it is in the title. People here are my last hope.
I wanted to do the TRWP bootloader change, but apparently i am way too stupid to do that, because my phone is rebooting incessently and the only things it show is:
Set Warranty Bit : vbmeta
Set Warranty Bit : Recovery
And i can't turn it off. Pressing volume up + volume down while pressing the power button does nothing. I searched on google relentlessly before coming here. Connecting my phone to my pc does nothing, nothing is recognized. I'm completely desperate. Is there any way to completely reset the phone without the recovery menu? I'm fairly sure there isn't but it doesn't hurt asking...
Thank you in advance for any suggestions.

Press both volume buttons only when connected to a PC and it should boot you to download mode. After the prompt, press VOL + to continue and then flash your stock ROM using Odin (download Odin from XDA, you can find it)

Thanks a whole lot, i finally have access to the download mode. Now i just have to find the original firmware

There are a few sites to download like sammobile and samfrew

I wanted to say: Thank you. Your instructions just saved my phone, and even tho i had a spare (my old phone) i'm glad i got it back.

icetoseeyoufr said:
I wanted to say: Thank you. Your instructions just saved my phone, and even tho i had a spare (my old phone) i'm glad i got it back.
Click to expand...
Click to collapse
Glad I could help.