Database Users

Problem: Screen Blackout - Buttons/Keyboard Unresponsive

The only thing I have done to this phone is root.
My phone several times today has had it's screen blacked out and cannot be awoken or used because all buttons on the phone become unresponsive. However, I know the phone is still working because it still receives notifications and I can hear it.
I have to take out the battery to fix this. Has happened about 5 times today.
Anyone else with this issue?

That certainly isn't normal. I would return it.

Also noticed that when using adb that it kicks my phone out after a certain time... something like 1 minute. Does this happen to anyone else?
I often have to do adb kill-server in order to see my device again.

I too have the same problem (though less frequently).
I have a rooted Epic using Joey Krim's method (raidagainstthecage-arm5.bin). I attributed it to the Overclock Widget which I have uninstalled to see if it gets any better. I like that widget for throttling down the CPU while the screen is off.
I guess it is best to start collecting data on this.
Phone was purchased at BestBuy.
Hardware version: D700.0.5
Anyone else seeing similar behavior? How about on a non-rooted Epic?

I was running SetCPU but uninstall the application and it was still happening to me. I have a feeling it has to do with the root method. My girlfriend's phone doesn't have root and it hasn't happened to her at all.
@jspielberg did you root via the one click method or manually with adb?

I rooted via adb.
Other root required apps installed:
Titanium Backup
Wireless-Tether Experimental (adhoc mode only working currently on the Epic it looks like)
Overclock Widget (now removed)
I think that is it for SU needed apps.

jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.

This happened to me not 30 minutes ago. And I'm 100% sure its root.
Sent from my SPH-D700 using XDA App

volcomjerk said:
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
Click to expand...
Click to collapse
I did indeed use my mac also for root via ADB...
I can't see how that would matter, but it is good data nonetheless.

Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.

antidelldude said:
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
Click to expand...
Click to collapse
Yeah everything is working fine. But I went to pick up the phone to make a call and it was dead. Complete blackout screen, not lights. Nothing.

@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.

I rooted Tuesday morning using Windows 7 32 bit mode, ran cmd as Administrator and followed Joeykrim's manual instructions.
I have had no problems with the screen being able to be turned back on and I have been on my phone performing various tasks for hours at a time.

volcomjerk said:
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
Click to expand...
Click to collapse
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App

ImSoHungry said:
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I rooted with One Click Root. Windows 7 32bit.

I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery

Is there a way to undo the "one click root" I did from the instructions here on XDA yesterday?

I rooted last night via OSX 64bit and have not experienced this issue. But now i am very afraid...

killahkosha said:
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Click to expand...
Click to collapse
Wow, after doing a full reset without root I am not seeing problems yet but this post makes me worried that it's not just related to root or unrelated to root at all.

I did a full reset through the menu on the phone, I haven't tried doing one through the holding volume down while booting method but I will after work

[Q] Phone won't turn on.

So I updated some apps on my phone, handcent and flash and my phone was having a lot of FC issues. Handcent was FCing for a lot of things and I couldn't open almost any app. So I figured lets do a quick reboot....chose the reboot option and the phone turned off but never came back on.....pulled the battery and I've left it out but still no go. Even pulled the memory card and SIM card but the phone won't do anything. Won't show charging when I plug it in but my computer does make a noise when it plugs in but the device doesn't show up on the computer anywhere.
Am I toast and do I need to get a new phone or is there something that I can do?

Wow never heard of that happening.. hmm try going to the bootloader... get a new battery maybe... this beats me
mytouch 4g
S-off
gfree method
running: royal ginger 1.6

How do I get to the boot loader from hardware keys? I can't for the life of me find that.

Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.

Spectral8x said:
Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.
Click to expand...
Click to collapse
If you are certain your battery is good and your phone does not respond to anything AKA brick then I think somehow you have ended up with a corrupted bootloader if that is the case you'd need a RIFF box or call HTC. I'm in the same boat as you i won't be buying the JTAG cable for that phone only so i'll be sending mine in.

I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.

Spectral8x said:
I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.
Click to expand...
Click to collapse
is adb recognizing your device? you did mention you heard a noise on your pc. The usb drivers should be kicking then (pray its not the qualcomm modem drivers kicking in lol)
you still have hope if you can get adb up and running.
Also were you on the stock bootloader or eng bootloader?

1. What was the state of your phone before those app updates? (Rooted? Custom ROM / kernel? Engineering bootloader?)
2. Do you remember specifically which apps you updated? Anyone else who updated the same apps recently, have you noticed anything?
3. Do you have ADB set up on your computer? Have you tried using 'adb devices' to see if your device is recognized?

Happen to me once due a battery pull then reinsert the battery should be able to boot back up. When you do a battery pull wait a few minutes like 5.
Sent from my HTC Glacier using XDA Premium App

That happened to me everything got messed up except bootloader and even that was freezing so I loaded pd151img.zip and pulled battery when updating bootloader to hide s-off
Sent from my HTC Glacier using XDA Premium App

So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there.
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.

Spectral8x said:
So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.
Click to expand...
Click to collapse
Well if it wont boot it won't be recognized I don't think.. and I just corrupted the bootloader by pulling the battery so they wouldn't see I had rooted and I wouldn't have to pay the fee (bad karma and all I know) so if you don't have insurance your sol. But on some other thread a Guy had this issue and held both volume keys and power while plugging it in and his comp recognized it as qualcomm cdma device or something like that. That maybe recognizable via adb not sure though..
Sent from my HTC Glacier using XDA Premium App

Well I should be fine under warranty tho since the device won't do anything. I'm going to try to see if I can get the device to show up in adb and if not i guess i'm getting a replacement phone and starting from scratch UGH! Lol.

why not to rename system app .bak (how I bricked my phone) - Resolved

Resolved: see post below.
Hi there, I'm really writing this hoping that maybe someone knows a fix for my problem and as a warning for why renaming system/apps with .bak is a silly idea when you can just do it via titanium or something similar.
About the device
Phone is a bell model, rooted but running the stock rom. I froze a bunch of apps with titantium (the smart way) but also added the .bak extension to some apps in the system/app folder.. I can't remember which ones but evidently important ones.
Everything was fine until today when an app I sideloaded caused my phone to go into a boot loop. I've been fighting with wakelock issues lately so I figured it wasn't a big deal to pop into the android recovery and do a factory restart. Problem is, some of the apps I added the .bak extension to are needed via the setup.
Problem I'm having
I can boot the phone fine and get to the blur setup screen which I can bypass as well. Problem is, once I skip the screen I immediately get a force close, and instead of taking me to the home screen, it goes back to the blur setup screen. I tried the keyboard shortcut bypass method which also works fine, but renders the phone useless since I can't access any menus, etc. It's just a black screen with the notification bar at the top. Horrah!
Long story short:
I can't enable usb debugging unless there is a way to sneak into the settings menu from the emergency call screen
Bell doesn't have a stock rom available
I can't re-root and fix my problem via adb because I can't turn on debug mode.
GAH!
Anyways, I'm pretty screwed. What are my choices?
I can return it to bell and hope they don't notice my giant gaff, flash an aftermarket rom and lose any warrenty I might have (I'm pretty toast now anyways) or buy a replacement phone.
Any thoughts would be greatly appreciated
- Kate

OMG
my heart had literally stopped beating for the past hour until I remember reading somewhere that you could text message a link to a replacement launcher hosted on dropbox.
OMG
Problem solved, phone is working.. I think.
Lesson for today kids: Do not mess with things you're not totally 100% sure about. Also, don't screw around with work phones. You need them to stay employed. Bricks don't keep you employed.

Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
And I have sent 2 of my atrixs back to at&t both were unlocked and rooted
No questions asked not on extra doller spent I love insurance its worth 5 dollers a month to me + my phones were both bricked by apps in the android market
that's my story and I'm sticking to it!!!
Sent from my MB860 using xda premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Does that work even if usb debugging is off? If so, that's fantastic! I'll keep that in mind next time I'm in a horrible jam.
It wasn't market apps though that was my concern though... rather it was messing with system/apps and build.prop that had me concerned. Any wise tech would know that my problems weren't caused by some error on Motorola's part, but rather a silly girl who's breaking things from within.
Thanks though

I once told the **tech repairs specialist** that I bricked my phone installing a custom rom and got asked " what kind of customer was on the phone?"
Try and find NFHimselfs atrix mods apk it will help a lot
sent from my Atrix via XDA premium

Nexus 4 USB-Debugging doesn't work

Hi Guys,
I used the new Nexus 4 Toolkit to unlock the bootloader.
As I unfortunately dont have 10 Posts, I cant ask in this thread, so I hope it's ok to ask here.
I installed the drivers with USB-Debugging (as before for my galaxy nexus) and unlocked the bootloader.
So far everything went normal and good!
Then I wanted to root the system. It was said that I've to enable USB-Debugging again and the system will reboot.
But then :
I tap on "Enable USB-Debugging" and I'm asked If im sure. After this, nothing happens. Usually I see a information-icon, that usb-debugging is enabled in the taskbar.
This icon is now missing. And im completly not able to connect to phone via PC and use ADB.
Im slightly desperated, as anything I could do requires ADB/USB-Debugging.
Can you guys help me?
Thanks in advance.

Does your phone show up as MTP storage OK?
I remember my One X decided to cease all USB activity except charging once, a reboot sorted it.
The USB debugging icon is a little jelly bean as per the attached screenshot.

thanks for your reply.
I dont remember If it was shown as MPT-Storage - will check this immediately after work
THe Jelly-Bean-Icon showed up before, when used the toolkit to unlock the bootloader.
I also rebooted the phone several times

Ok, now everything seems to be identified correctly, again. Very strange.
Maybe the PC needed to be restarted.
Sorry for this post. It can be closed.
Thank you!

Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.

ev!denz said:
Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.
Click to expand...
Click to collapse
I've got the same problem, except my device is not loading until 100%. It gets really hot while not doing anything and it's empty in about 3 hours.

I figured out that the Nexus is only charged via "USB" although it's plugged in the charger.

Now my device is charging up until 100% but it still gets hot, is empty in about 5 hours and if I connect it in fastboot mode my laptop says that the drivers are not installed properly even though I installed the naked drivers. Re-installing the drivers does not work either, it says that my laptop already had the right drivers installed. And when I connect my device when it's booted it is not recognized at all and does not show up in the device manager. I tried three other cables... Sounds like an USB brick, right?

Ultraschorsch said:
Sounds like an USB brick, right?
Click to expand...
Click to collapse
That's what I think, too.

ev!denz said:
That's what I think, too.
Click to expand...
Click to collapse
Having the same trouble guys. Anyone found any insight into this or possibly a fix?

loopyoyo said:
Having the same trouble guys. Anyone found any insight into this or possibly a fix?
Click to expand...
Click to collapse
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...

Ultraschorsch said:
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...
Click to expand...
Click to collapse
Tap Build Number in about phone 10 times.

zephiK said:
Tap Build Number in about phone 10 times.
Click to expand...
Click to collapse
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.

Ultraschorsch said:
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.
Click to expand...
Click to collapse
Yea...computer doesn't even recognize nexus under recovery or fastboot menus..I think it's really fooked up. Just submitted a rma request to lg so will see how this plays out.

I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...

studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
I have teh same problem.
1) the battery drains like crazy, even with franco kernel lastest nightly
2) USB debugging does not work now... when plugging into the pc the phone is just not found...
3) I can reboot to recovery but that doesnt do me any good since I cant do jack from it.
anyone has any insight ? what can be going on that the phone is not showing up in windows

studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4

spaceman860 said:
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
Click to expand...
Click to collapse
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?

al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes. If your on stock with a locked bootloader your warranty is still good
Sent from my Nexus 4

al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes, I called Google but they don't have any N4's in stock. so I keep rooted until I get a new device from them.

Phone Offline

I finally upgraded adb to show my device, but when i try using android commander it tells me the phone is offline. I think this "offline" mod is keeping me from install the hotspot mod. Just curious if anyone knew how to fix this "offline" issue.

You need to be using the latest adb to fix the "offline" issue. Type adb version to see what version you are using. I think the latest version is 1.0.31
Sent from my SPH-L720 using xda app-developers app

I did use the latest and adb now shows the latest. But Android commander says it's still offline. I'm also having an issue install a simple mod and am wondering if this offline thing is causing issues.
Sent from my SPH-L720 using Tapatalk 2

gadget069 said:
I did use the latest and adb now shows the latest. But Android commander says it's still offline. I'm also having an issue install a simple mod and am wondering if this offline thing is causing issues.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I had that same issue when I first got adb going on this phone. I forget what I did to fix it though, I was drinking at the time. Be sure you have debugging turned on, and also be sure to watch your screen on the phone when you connect. There is a pop up asking something about rsa keys that you need to tap ok, and also check a box allowing it each time. Good luck.
Sent from my SPH-L720 using Tapatalk 2

k2buckley said:
I had that same issue when I first got adb going on this phone. I forget what I did to fix it though, I was drinking at the time. Be sure you have debugging turned on, and also be sure to watch your screen on the phone when you connect. There is a pop up asking something about rsa keys that you need to tap ok, and also check a box allowing it each time. Good luck.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I've done all that. I'm using this phone on page+ not sprint, so I'm wondering their isn't something not activated on the phone causing this.
Sent from my SPH-L720 using Tapatalk 2

gadget069 said:
Yeah I've done all that. I'm using this phone on page+ not sprint, so I'm wondering their isn't something not activated on the phone causing this.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
No I think it's just the 4.2.2 locked up tight....I got the RSA key to come up once but I never got connected, going to setup ADB on another computer see if I can get that one right. I used it with my EVO before but the GS4 is killing me!!!!!

This has happened to me twice.
Once when I somehow didn't say it was ok to use the RSA key (I think i was drinking at the time), and once when I used some cheap USB cable that came with a cradle I had bought. I had heard people mention cables in the past, but never believed them until it happened to me.
Same cable works fine with my HTC... Samsungs USB can be funny at times...

I did install on my laptop and got the RSA key to come up but didn't help my problem. I can't get this hot spot mod to stick. I've used 4 different cables.
Sent from my SPH-L720 using Tapatalk 2