Database Info

Q: Recently rooted and unit won't turn on

Ok, stop me if you've heard this one before (I've searched and searched to find a solution to this issue, so I appreciate any help I can get)
I recently rooted my TF101 and have been flashing different ROM's to see which one I like the best. I'm not a complete NOOB, but I've never done flashing on a tablet before. I flashed Megatron 1.6.1 and when I went to reboot I couldn't get out of recovery and it kept looping back to recovery despite my doing a complete re-wipe/flash. When I finally powered down I wasn't able to power back on.
Now the unit will not turn on, either regularly or in recovery. It's completely dead. I've been letting it sit plugged in for a while to see if that helped and still nothing. I've held the power button down in every conceivable way and for different lengths of time and still nothing.
I'm at my wits end... any help would be AMAZING!!! Thank you in advance.

Can you get into APX mode? You may want to nvflash back to stock and try again.

Sometimes the tf not really shutdown, it just freeze in black screen when we thought it already shutdown. Undock it and plug in charger to see if it charging as it might be given up totally battery drained.
Sent from my awesome rooted Defy: 2.3.6 XDA premium

I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!

Rogueharvest said:
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Click to expand...
Click to collapse
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do

redninja007 said:
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
Click to expand...
Click to collapse
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.

new damages
farsight73 said:
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
Click to expand...
Click to collapse
i already tried nvflashing back to stock it went back to stock but the screen still wont turn on...i charged it for 12 hours still nothing.but it plays music still ...after getting pissed off,,,my wife hits the tf101 screen and then it turns on finally but the screen was orange and red... then she hit it again then i think she damaged it once more hahhaha....im pissed off too but when thinkin bout her face while hitting the tf101 EPIC hahahha...any help wanted i wanna buy new screen... attatched is the picture she sent me hahaha

[Q] Screen won't turn on.

I've been running the latest CM10 M release for a couple weeks now. Today I upgraded to the latest modems. Everything was working great for a few hours when my phone randomly shut off and now won't turn back on.
I've tried pulling the battery and charging. Can't ever see anything on the screen although it does vibrate sometimes when I hold the power button. LED will turn on when charging.
Any ideas or suggestions?

See if you're able to boot straight into download or recovery, thus will show intact boot and recovery systems.
One other test, pull battery and with phone off plug into your PC if it shows a red light its likely hard bricked.
I had the unfortunate experience of flashing wrong kernel and bricked my phone was not going to recovery or download. However if you can get to these then it may be a soft brick and restore with odin
Sent from my VS920 4G using Tapatalk 2

One my phone got stuck
jerhurwitz said:
I've been running the latest CM10 M release for a couple weeks now. Today I upgraded to the latest modems. Everything was working great for a few hours when my phone randomly shut off and now won't turn back on.
I've tried pulling the battery and charging. Can't ever see anything on the screen although it does vibrate sometimes when I hold the power button. LED will turn on when charging.
Any ideas or suggestions?
Click to expand...
Click to collapse
Once my phone got stuck because I flashed a new recovery that wasn't compatible with my phone so each time I tried to boot into recovery or tried to turn on the phone nothing would happen. The only thing that got my phone working again was to go into download mode (Odin) by holding power, volume down and home buttona and than canceling it. from there the Rom started working again. I don't know if it will help in your case but you can always try.

That was a strange experience. Left it plugged in for a few hours. Came back, and was able to boot normally... although the battery was extremely low despite being plugged in for a few hours. No problems since then.

Congrats =)
Seems like disaster was avoided.

jerhurwitz said:
That was a strange experience. Left it plugged in for a few hours. Came back, and was able to boot normally... although the battery was extremely low despite being plugged in for a few hours. No problems since then.
Click to expand...
Click to collapse
Do you know what percent your phone turned off at? Around what percent? Was it 23-25%?

[Q] Rebooting phone causes pseudo-brick

This is going to be a long question/story thanks for your patience!
Whenever i try to reboot my phone, regardless of method, it takes an elaborate set of actions (elaborate as in it requires a power cord, a complex series of button presses, chanting, chicken blood, etc...) for the phone to turn back on.
I'm going to include a lot of details, relevant or not, i cannot decide.
I was using SlimBean Build 7 for weeks. I was able to reboot normally. I had heard about an app, WifiKill, installed it, caused short lived havoc at work, no issues so far. A few hours later, I attempted to tether my laptop using the hotspot function (something I've done many times before with no problem). The wifi turned off immediately and would not come back on. My exact thought was "Huh, that's weird" and attempted to reboot the phone, it seemed to shut off normally but did not come back on. At this point i believe the battery was at 60% or close to it.
No matter how I tried the phone would not power back on.
I charged the phone over night, and it actually came back on. Of course the first thing I tried to do was reboot the phone. Same result.
Now the phone is still not starting when turn off or rebooted with the power button command, it will not reboot when done with adb, it will not reboot when I try within the recovery. Any of these things cause the phone to act as if "hard bricked" with no response from any of the buttons or screen.
My first thought was to flash a stock rom with odin, when i plugged it into my PC (windows 7 ultimate 64bit) it asked for QHSUSB_DLOAD drivers. I tracked those down and installed them of course they did not work for odin.
I ordered but have not received a download mode jig.
I thought maybe it had to do with the act of charging the phone that sparked the brief show of life so i drained my battery using another phone and then charged it in the skyrocket for two days. Battery at 100% at this point.
At this point, I've discovered that if I hold the power button long enough while plugged in the phone will vibrate over and over until the button is released and by accident I learned that if i unplug the phone wile doing it's little vibro-trance it will start normally.
If I try to reboot the phone with any of the methods I listed above, I have to pull the battery, wait 10 minutes, plug in a power cord (not connected to a computer) hold the vol+ and vol- and power buttons, wait till it starts buzzing and insert the battery, if the charging icon appears the phone will power on, if not, I have to start again.
Once I learned that trick I was able to boot the phone into download mode and flashed back to stock JB and twrp.
I have since flashed slimbean build 8 and twrp 2.6.0.0. The phone is working fine but I don't have the guts to attempt WifiKill, tethering or reboot.
If you're still with me, good on you. I think the universe is mad at me for messing with people's wifi connection.
Anybody got any ideas?
THANK YOU!!!

ilike3point14 said:
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, I'm guessing that wifi kill app had something to do with it. I've tethered on slim bean 7 & 8, so I doubt it has anything to do with that or the ROM. Is say it's like you said, karma rearing its ugly head for playing wifi gatekeeper on unsuspecting individuals
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

[Q] Photon Q won't boot up

Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?

amateurhack said:
Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?
Click to expand...
Click to collapse
Have you tried to force reboot (Vol down + Power button for about 7-10 secs)?

Yes. Thanks for the reply. That's what I meant by soft reset. What the issue, I figured out, was that my battery had decided to self-destruct. It didn't have enough charge to even boot the phone successfully, so it was not possible to put it into recovery mode or anything else. I took it to Sprint and they replaced it under warranty.
Sent from my XT897 using XDA Premium 4 mobile app

Is my Nexus5 dead or only its battery?

Howdy!
My phone doesn't work anymore, and I try to assess what's going on. I searched before posting, and I decided to post here because I found mixed answers.
Context:
I bought my phone in January 2014. I took extra care of it, it has never fallen on the ground from high, no scratch, nothing. Regarding the battery, I tried as much as possible to charge when it was close to 0%, I wasn't a heavy user of my phone, and I was turning off a lot of things so that the battery would not deplete quickly (Wifi, localisation, Bluetooth, auto-typing, et cetera...).
However, recently (the last month), I was feeling the battery was weak, depleting more quickly than before. I also felt the phone was warmer than usual. Sometimes the phone would turn off suddenly when I was short on battery (under 15%) and using a "heavy" feature (photography with flash, video game).
A week ago, the phone suddenly turned off, never to turn on again. The phone died. I was just typing a message, the phone was charging and the battery was around 60%. I was surprised.
As of today, the phone doesn't turn on. Plugged on a wall outlet or on the USB port of my computer is the same.
I tried many combination of buttons to fastboot, reboot, reset, or whatever, nothing sparked any life in my phone. (I tried holding power key for 30s+, 15s+ ; I tried holding power key + volume up for 15s+ ; power key + volume down ; power key both volume ; in fact whatever combination I could read here on XDA forums, on Reddit, on Google Forums...).
My first insight was: it's just the battery. I can buy one off the internet, and voilà!
However, when I plug the Nexus 5 on my computer via USB, the computer reacts with the sounds when you connect something. Is it just the battery then?
At first, it was saying: "QHS_USB BULK", and the computer was trying to install whatever to make that peripheral work.
When it was done, it read "Qualcomm HS-USB QDLoader 9008 (COM4) has been correctly installed.
Hum, okay.
Still, nothing shows in the peripheral.
I continue to hear the plug in plug out sound when I... plug in and out my phone in the computer, but that's the only thing.
With all that, I can't really tell if all the phone is dead, something grilled inside or I don't know what; or if it's just the battery that is dead and the phone is unreachable and unrecognizable when "there is no battery" in it.
I'm not sure if I shall invest money into buying a new battery.
Do you guys can light my lantern on that matter?
I would greatly appreciate it.
Thanks,
Cheerio!

If I may just address a little bump on this very subject of particular interest to myself :3
Cheerio!

Any insights on this? mine´s doing the same. Doesn´t turn on or go into bootloader, when i connect to charge it red light blinks for like 10 sec and then goes off. Nothing happens after hours of charge.
Did you try replacing the battery as you mention on the post?

Sorry, but have to say this with caps: BLINKING RED NOTIFICATION LED MEANS ITS DEAD BATTERY. Can't be 100% sure, but usually it means that the phone doesn't have enough power to boot up. Mine did this when it drained to the absolute 0%
edit: There can be other problems with power going to phone, but if you are lucky its just the battery.

So i changed the battery. When i plugged it to charge no red lights came on, just the typical white battery with the light bolt appeared for a few seconds, after that it went on with screen off (or at least i thought it did). After 3 h of uninterrupted power charge i went to turn it on. Nothing happened. Can´t turn it on or go into bootloader.
Nothing happens on my pc when i plug it. No sound and nothing on Device manager (no drivers for nexus 5 installed, don´t know if that matters for windows to recognize it as any device even if its not as android device).
Edit: yeah, i got enlightened and literally unplugged the battery and plugged it back in and it worked like charm. I get stuck on the intro animation but i can get into bootloader and recovery just fine. Just gonna install those drivers and flash something. right? Thanks to everyone that read and even more to those who replied!

qaleq14 said:
So i changed the battery. When i plugged it to charge no red lights came on, just the typical white battery with the light bolt appeared for a few seconds, after that it went on with screen off (or at least i thought it did). After 3 h of uninterrupted power charge i went to turn it on. Nothing happened. Can´t turn it on or go into bootloader.
Nothing happens on my pc when i plug it. No sound and nothing on Device manager (no drivers for nexus 5 installed, don´t know if that matters for windows to recognize it as any device even if its not as android device).
Edit: yeah, i got enlightened and literally unplugged the battery and plugged it back in and it worked like charm. I get stuck on the intro animation but i can get into bootloader and recovery just fine. Just gonna install those drivers and flash something. right? Thanks to everyone that read and even more to those who replied!
Click to expand...
Click to collapse
Yeah, search from youtube how to flash factory image nexus 5. It should make it work. And try to find video with using adb instead of toolkit, adb is way more stable/trustable. (ADB is the android debug bridge, it may look like very hard and confusing but in the end its just typing 1 command and it flashes everything needed) If you need help in flashing the image, just ask!
Try this, it installs only tools needed for adb (also drivers) http://forum.xda-developers.com/android/software/tool-platform-tools-adb-fasbootdrivers-t3061441
Edit: This should work https://www.youtube.com/watch?v=5ka5dnPghzI