Database Info

[Q] SOD I think..?

I'm running Prime 1.7 I never had any problems with my tablet. It has the creaking and light bleed. I was watching netflix the other day and watched all the way till the battery went completely dead 0%. I got home plugged it in and it charged up all the way but now the screen wont turn on. If i connect it to the mini hdmi i can see everything on the tv but screen still wont turn on.
I've tried:
Fixing Permissions
Clearing Cache
Undoing overclock
Removing SD
Turning it all the way off waiting then turning it back on.
Adjusted the Brightness
Changed Wifi.
I cant factory reset or anything in CWM because it doesn't show up on the tv through hdmi and i cant remember the each button pushes to do it blind.
Any Ideas?

Mine went blank once but that was the adw launcher. Rotating it fixed it and i was able to choose stock launcher. If nothing works you can try screencast to see the recovery on PC if you have Android sdk setup.

Did you try to hold down the Powerbutton till it switches off to make a correct Restart?
When the Tab is running hold the Powerbutton till it's off and wait till it starts again.
Normaly that helps with SOD.
Sent from my Transformer TF101 using Tapatalk

steini81 said:
Did you try to hold down the Powerbutton till it switches off to make a correct Restart?
When the Tab is running hold the Powerbutton till it's off and wait till it starts again.
Normaly that helps with SOD.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You should press the power button 10 to 15 seconds...

So far nothing worked. I'm on stock launcher also.
I've tried to resetting it over and over still nothing.
I attempted to letting the battery die completely again.
Placed it on the dock and nothing.
Thank you for the suggestions. I will update if i ever solve the issue. I'm going to try screencast, but i never used it before.

I got screencast to open up and running. however it wont work in recovery. ADB recognizes it. I keep getting a blank screen. Any ideas?
I'm thinking the best option would be to nvflash it to stock and RMA it if it doesn't work.

NV Flash
Hi
if nothing else seems to work then NV Flash might be the best idea.
Could you share the BXX(First 3 digits of serial number)?
Thanks

[Q] My TF101 stuck at EEE Pad Blue Bar screen!!!

Hi All,
I had ICS installed on my TF101. However yesterday it totally discharged when it was asleep and I had trouble turning it on. I never had this happen with HC. So I decided to go back to HC. I had my tablet rooted and su backed up. Had recovery installed.
I flashed official US HC fw and everything went fine until I tried to reboot the tablet. It's now stuck at the EEE Pad loading logo with the blue bar approximately half filled in. No amount of button combinations does anything. I can't enter Vol + & Pow button to enter ADB, and when I try to enter recovery mode, the white text shows up saying searching for OTA recovery and that's it, still gets stuck at the blue bar.
Any ideas or ways to get to my recovery before I return my 2nd tf101? Thanks!!
(Btw, I'm not a newbie, I would NEVER do this whole thing if ICS was stable and worked like it's supposed to, but I refuse to own a 390$ half working tablet that crashes, has battery drain issue and gfx glitches after the FORCED ICS update!)

Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?

Goatshocker said:
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Click to expand...
Click to collapse
Hi Goatshocker!
I have tried to cold boot it, but it does not allow me to get to the 2 icons you're talking about. When I hold down Vol - & Pow, it shows the regular white letters from bootloader, and gets stuck at the blue loading bar EEE Pad screen.
What I meant by force, is that after 4 delays of the update, ICS will install itself automatically! Even when the tablet is in sleep mode. That's what mine did.
In order to avoid this, the user would have to root his tablet and use Titanium Backup Pro, and disable certain system update processes. Which is NOT for the casual user or for anyone who wants to keep warranty intact.
The s/n I have starts with C2O.

my Asus transformer tf101 Eee Pad wont start.

just wont boot, it won't do anything when i power up my asus transformer tf101 it just get stuck on the first thing you see when you start you asus eeepad and it wont go any further when i power u p and press volume up it just wont go into apx mode so that i can do a easyflash so any suggestion guys plzz??? i really need this it's for my bro.

That's pretty vague. Do you know of it has a custom rom, a custom recovery?
Did you do anything before it reached that state?

xvls said:
just wont boot, it won't do anything when i power up my asus transformer tf101 it just get stuck on the first thing you see when you start you asus eeepad and it wont go any further when i power u p and press volume up it just wont go into apx mode so that i can do a easyflash so any suggestion guys plzz??? i really need this it's for my bro.
Click to expand...
Click to collapse
yea i did everything i could it just wont load up anything i try anything possible but it wouldnt let me in plus i think is not brick it have something to do with the software.

I am having the same symptoms
Model:
TF101 B70 rooted with CWM, custom kernel, and custom ROM.
Symptoms:
Stuck at Eee Pad ASUS logo screen with no progress indicators
Cannot turn tablet off. I can reboot by holding down the power button or let its battery run down.
Cannot boot into APX mode. I have tried holding down Vol+, Vol-, and both buttons before, during, and after power button depressed for reboot. I have tried holding them down for 6, 15, 30, and many seconds.
Cannot boot into recovery
Possible causes:
First had trouble with a bad pre-flash wipe script which took me to where I am now
Troubleshooting steps tried:
Attempts at APX mode and recovery using methods above.
Removed bezel to rule out Vol or power button external switch problems
Stock charger died, so I spliced a 12V 1.5A line into the stock USB cable just in case the TF101 needed something higher voltage to function properly
Bought a new cable
Installed Universal Naked Drivers 0.72 into my Windows 8.1 box
Searched XDA, Transformer forums, and with Google across many other domains with very few hits on this symptom.
I have several computers running and any OS one could want for the USB side of the 40pin cable.
search tags: bricked, can't boot into APX, eeepad logo, eee pad logo, asus logo, tf101, transformer tf101, b70

Just making sure, you guys are aware that the screen stays off in apx right? Have you tried to put it into apx while plugged in to the computer? Plug it in, and then hold volume up and power until the computer recognizes a new device.
jortony, what did you right when this started?

samdudelinxman said:
Just making sure, you guys are aware that the screen stays off in apx right? Have you tried to put it into apx while plugged in to the computer? Plug it in, and then hold volume up and power until the computer recognizes a new device.
jortony, what did you right when this started?
Click to expand...
Click to collapse
I was installing a new ROM which necessitated a wipe. I don't remember the name of the script I used, but I remember selecting the wrong option and rebooting mid wipe to try and prevent the wipe from starting. I wasn't able to recover it then and so I put it on my project shelf until I could get back to it. It's been there for a couple years and I am making one last attempt before I try something drastic like transplanting the flash from a broken TF101 or breaking it down for components... It would be such a waste..
I would love to be able to boot to APX mode, but I just can't get there. If you're near Chicago I'll buy you lunch and you can try your luck. =)

jortony said:
I was installing a new ROM which necessitated a wipe. I don't remember the name of the script I used, but I remember selecting the wrong option and rebooting mid wipe to try and prevent the wipe from starting. I wasn't able to recover it then and so I put it on my project shelf until I could get back to it. It's been there for a couple years and I am making one last attempt before I try something drastic like transplanting the flash from a broken TF101 or breaking it down for components... It would be such a waste..
I would love to be able to boot to APX mode, but I just can't get there. If you're near Chicago I'll buy you lunch and you can try your luck. =)
Click to expand...
Click to collapse
I'd love to take you up on that, but I'm in Alabama at the moment. What was the script supposed to wipe? Just a general prepare-for-new-rom wipe?

samdudelinxman said:
I'd love to take you up on that, but I'm in Alabama at the moment. What was the script supposed to wipe? Just a general prepare-for-new-rom wipe?
Click to expand...
Click to collapse
I'll be in Spanish Fort around Christmas. =)
The script had multiple options, I chose the wrong one in haste..

jortony said:
I'll be in Spanish Fort around Christmas. =)
The script had multiple options, I chose the wrong one in haste..
Click to expand...
Click to collapse
That's odd that it won't go into apx as the result of a wipe script. I was under the impression that apx was so deep in the system that it was pretty much untouchable. I would especially think some wipe script wouldn't be messing with apx. Are you absolutely sure you remember trying just plugging it into a computer and holding down power and vol + continuously? When you do this your computer didn't sense a device?

samdudelinxman said:
That's odd that it won't go into apx as the result of a wipe script. I was under the impression that apx was so deep in the system that it was pretty much untouchable. I would especially think some wipe script wouldn't be messing with apx. Are you absolutely sure you remember trying just plugging it into a computer and holding down power and vol + continuously? When you do this your computer didn't sense a device?
Click to expand...
Click to collapse
That, and also, do you have the APX drivers installed? I don't think UND covers that.

Duchman said:
That, and also, do you have the APX drivers installed? I don't think UND covers that.
Click to expand...
Click to collapse
UND is supposed to cover apx. It did for me, but hey, what do I know. My TF101's essentially bricked right now!

samdudelinxman said:
UND is supposed to cover apx. It did for me, but hey, what do I know. My TF101's essentially bricked right now!
Click to expand...
Click to collapse
Hey, I just want to thank everyone for troubleshooting this with me.
Just to start, isn't it possible to boot into APX mode without any computer attached? If this is the case, then I should be able to reach APX mode with or without the drivers correctly installed and configured. If it does require the computer to be set up properly, I am going to test this on a couple other machines in two days (hosting family Thanksgiving) with all the drivers I can find.
As for the wipe script, I would be surprised if that would be possible too, but if it didn't directly cause the problem it was coincidental and exceedingly likely to be a cause.
Though there are a couple other vectors for my woes: Incorrect power supply (i'm trickle charging on USB) to allow the tf101 to overcome some very low-level programmed switch enabling normal/debug functions; or, incorrect wiring for the my DIY power supply along my troubleshooting escapades which fried something, though I don't see evidence of internal power transformer death within the tf101 which would probably be characterized by periodic reboots, or just plain inky black death.

APX mode works without a PC, it's all on the TF101 (Vol up & power from a powered off state) nothing appears on the TF screen, only sign is the USB connect sound if you have it connected to the PC
UND are specifically for APX mode, but are not signed, so if you are running an OS later than Win 7, or a 64bit OS, you will need to disable driver signing from the F8 safemode boot options (Advanced boot, Win 8.x)
Or use Win 7 32bit

My bad, for some reason I remembered UND not working for me.
I'm guessing you are having trouble with APX mode because you are not able to turn off the tablet completely. Try this: when your tablet is stuck on the logo, press and hold down Volume Up and Power buttons until you see a black screen (release the buttons in 2-3 seconds after that), then connect it to your PC. You should see Asus Transformer APX Interface registered
If the tablet stays on the black screen but nothing is happening on the PC, follow *Detection*'s advice about driver signing.

I successfully disabled driver signing on my Windows 8.1 machine to install UND, but the APX mode is still my sticking point. I tried rebooting with Vol+ before, during, and after the screen turns off and the same with the power button, but that's not getting me into a black screen. I even tried discharging the battery completely to fully shut it down which did something new and interesting: The tablet booted to logo as usual, then the logo quickly disappeared leaving a blank screen but then rebooted again. This might have been the elusive APX mode coupled with an accidental reboot, but I only get to try it once every complete discharge, recharge, and first boot cycle. I am discharging again now to test this again.

[Q] Unresponsive TF300, stuck on 0%

Come across a strange problem on my TF300. The battery completely drained one night and thereafter it's become unresponsive. It charges, boots to the lock screen, but the battery is shown at 0% and I'm unable to interact with anything other than using the hardware keys. It freezes when attempting a cold boot or attempting to go to recovery. Had TWRP 2.8 on Katkiss 4.4, anyone got any ideas?

Just to update this, the dock just doesn't work with the tablet currently.. Despite being on charge for a number of hours there's been no progress. Both charging lights do go green eventually though, but still on 0%. It connects to my PC, and I can even view the files on it, but the tablet itself is unusable. Device manager shows it but I couldn't get it to appear in Adb for fastboot commands
Anyone know how to get it to show in Adb?

Bump on this since I'm out of ideas and would appreciate any help

Fixed this now, thanks to those who had a look. Somewhat simple solution, connected a mouse via USB, which allowed me to navigate the tablet. After that it was just a simple selection of rebooting to recovery from the power menu, which got me into TWRP and let me do a wipe and flash a new ROM.
Sent from my TF300T using XDA Free mobile app

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.