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

Battery issues, what is my best course of action?

Currently on dirkk's 1. 1 uv kernel(voodoo) and the superclean Rom
My phone thinks the. Usb is always connected and flashes between "fully charged" and real battery level. Also getting a lot of force closes for process. Android. Acore. It's quite frustrating. I have tried clearing battery stats in clockwork mod. This combination worked fine until about a week ago.
What else should I do? Start over? Try another Rom?
Thank you!
Sent from my SCH-I500 using XDA App

im no expert but i blame voodoo. try uninstalling it.

-removed voodoo
-installed a new kernel and ROM (superfast and blackhole)
The problem persists
The phone thinks it is connected to the USB when it is not, and also getting a force close for process.android.acore every few minutes. FML

Wipe the dalvik cache and batt.stats again and try another cable.
Sent from my SCH-I500 using XDA App

Tried and tried.
Have brought the phone back as close to stock as possible without using Odin. That's my next option. No force closes but the USB and battery issued persist. Geek squad warrenty might be worth it: x

mikey6p said:
Tried and tried.
Have brought the phone back as close to stock as possible without using Odin. That's my next option. No force closes but the USB and battery issued persist. Geek squad warrenty might be worth it: x
Click to expand...
Click to collapse
You have a one year warranty on the phone. If it's a genuine hardware problem, take the phone in and have it replaced.

Its looking like a hardware issue, I used odin to get it completely stock and the issue is still there. USB thinks it is always connected (which made it a huge PITA to get into the SD card to add files or use ADB) and the battery life is everywhere. Also wont boot without a USB cable plugged in. Very interesting hardware issue, my guess is the USB port got buggered up.

No usb available, other options?

I have a very strange issue going on with my fascinate right now. Before I go into too much description, here is my setup, to see the big picture. Rooted, stock vzw with geekniks stupidfast for DI01 (thought original kernel was original issue). I've tried to force the ota to DL09 and I get "IP_PREVIOUS_UPDATE_FAILED" as it fails to verify the dl signature.
Ok, on to my true issue. When I plug my SF into my pc, I get unrecognized usb device. I have the drivers installed properly and have previously been able to use odin via usb. My pc doesn't see the sd card mounted or anything. I'm debating unistalling the usb hub and restarting the pc so it will pick it back up as a new device. I have debug mode and unsigned checked, however, the little red triangle is no longer present like it used to be. I also every once in a while have issues with my battery level being accurate, as in it shows 100% when its really at 36% etc. It still charges, and recognizes being plugged in (haptic and audible confirmation).
Anyone have a clue or suggestion? I'm new to android, but well versed in the pc world. I just installed the android sdk in hopes of maybe doing a wireless adb push eventually. I'm A) trying to correct the issue and update my os/rom, or B) somehow get me back to stock and unrooted without being able to usb odin, so I can swap out for a new phone.
Thanks in advance for any help, whether it works or not.
Sent from my SCH-I500 using XDA App

Oh yeah, I'm running Win7 64bit.
Sent from my SCH-I500 using XDA App

so you are on stock vzw but you have used odin before. Did you use it to get clockworkmod on the phone?
did you return to stock from dj05 or dl09 OR have you always been on stock rom

I used odin to flash cwm. I'm on DI01 upadate-1. Had done the first update ota, then rooted and flashed cwm. I have been running that since until today. Thought kernel may have been issue, so flashed geekniks kernel for DI01 and have seen no change, except better performance as was expected. That is where I am now. Thinking about going back to previous kernel, but this seems better until I decide what I can do. Original nandroid and other in betweens to date still manifest the issues, which are only recent, like last few weeks.
Thanks again.
Sent from my SCH-I500 using XDA App

Does not see the Samsung SD Card
I have had similiar issues since DL09.
Try turning off your phone then reconnect USB after it reboots.
Seems to want to see it as a CD Rom.
norm883

I've rebooted my phone and pc, multiple times, no luck. Oh, one other thing, I tried popping the sd card into a card reader and I was able to see the files briefly, and upon trying to select anything, it totally disappears from view, as in pc doesn't see card anymore. Now I can't get the pc to see it at all. So I can't read/write it that way. My phone still sees it and can mount and unmount for removal on phone itself, but not with the pc.
Sent from my SCH-I500 using XDA App

I'm non-voodoo as well.
Sent from my SCH-I500 using XDA App

Try flashing a different kernel. My first fascinate was picky with which kernels wanted to work right with the.usb connection.
Sent from my SCH-I500 using XDA App

In my experience, you can still use ADB to push and pull things from your device even when your pc doesn't recognize your device. I know this doesn't help with flashing DL09, but it could help you push a different kernel to your device (or you could download one from xda forums via the xda app). A different kernel might clear up the issue for you. Good luck!

This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709

For your first issue it is because you are rooted you will not get ota updates. You should use odin and flash DJ05 imo it is much better and there are more ROMs and kernels
Sent from my SCH-I500 using XDA App

Thanks for all the help, I'm going to give it a whirl later and see if it works. I'll let you know.
Sent from my SCH-I500 using XDA App

Before I get too far deep in, could I just unroot via a terminalapp and then force the OTA to get me up to speed? Would at least like to see if I can deal with the minor malfunction while still being current.

nunyazz said:
This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709
Click to expand...
Click to collapse
This won't fix the problem because he is not on DL09. It will likely make his problem worse. You might want to read the entire post b4 you give suggestion.
To answer your question sir: if you can't get your pc to read your sd card with a card reader, the problem most likely has nothing to do with your phone. It probably is a corrupted|damaged card. It could also be a problem with your computer (this can be ruled out by successfully connecting another usb device to your computer).
Most likely, you will have to buy another micro usb card.
Sent from my Vanilla Froyo Fascinate

Ok, been trying a few things, and I'm starting to lean towards the sd card being corrupt (as one of the issues), sending my important pics and backups of my contacts, sms, etc to dropbox as we speak. I actually tried the SV kernel from adryn, and my phone has seen no ill effects (possibly no haptic, but didn't care at this point), everything seems to be working just like nothing changed. I actually briefly got the USB debug icon up for a second and it said usb connected, however I was not connected to anything, lol. It had done this on the stock kernel as well. I've booted my phone without the sd card in and it starts up normally, but the USB debug icon is still not present, even though the option is ticked on.
I can still force my phone into download mode, however my computer still doesn't recognize the COM port, so odin is out of the question right now. If I were to get my hands on the stock kernel again, could I factory reset the phone, remove root, and potentially force the OTA and then reroot? I've seen some options for terminal apps where I could ru superuser and busybox. Any thoughts on that route? I may give my roomie's pc a try, when he's out, as well to widen my test field.

Well, I got my pc reading the card via a card reader, but not while inserted in my phone. I'm going to try to uninstall the usb hub on my computer and restart my pc with no usb periphs connected. I read somewhere that someone was able to get the phone recognized again, but I have a feeling that it isn't going to work, since I never see the USB debug icon anymore.
On a side note, I get a com.android.settings force close message somewhat frequently, on stock, geeknik and adryn's kernel. I've started unloading apps left and right, but no avail. Thinking I need to get back to full stock somehow without odin. Suggestions?

I had similar issues. No usb, battery flashing to 100%. Tried everything as you have. Couldn't figure out how to get back to stock without odin. I'm running DJ05 superdark with geeknik 1.54 kernel.
This went on for a week and I was ready to give up and go buy another phone when one day the usb icon flashed momentarily when I plugged it in to charge.
In the end, it turned out to be a dirty usb connector on the phone. Cleaned it with a paper swab dampened with alcohol. I still have no idea why it was so sensitive to the small amount of dirt that came off it.
Hope this helps.

Well, I tried the alcohol swabbing, and it mildly worked. I get the usb debugging icon more often, but it also shows that the usb is connected, even though it isn't. My pc briefly recognized it once. Would I be able to disassemble it and clean or replace the usb port myself?
I've even blasted it with compressed air.
Sent from my SCH-I500 using Tapatalk

You've gone farther than I had to. I didn't need to resort to compressed air.
Do you have more than one usb cable available? I had bought an aftermarket one in addition to the one that came with the phone.
The original cable is still wonky on connection. It charges ok (no more battery jumping to 100%), but usb recognition is a fifty-fifty proposition. The aftermarket cable does charging and usb correctly.
I have had to reset my PC's usb drivers once by rebooting the phone while connected (the PC recognized it as a CD-ROM drive). This may be coincidental or an indication of a chronic connection problem.
I speculate in my case that the aftermarket cable distorted the phone connector somehow so that it doesn't like the original cable any more. Pure speculation.
Anyhow, glad to see that you're making progress. I know how frustrating it was for me. Keep us posted.

I had the same problem at one point. I found out that if your turn the phone off, plug in the usb cord from the computer, then turn the phone on while the phone is still plugged in. once the phone reboots, unplug the phone, then replug the phone in to the computer and then the computer should recognize it. This works for me every time that i have this problem

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

[HELP] The usb on my n4 won't communicate with anything, no matter what.

I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
I would go back to stock to try and fix it if I could, but I can't transfer anything to my phone.

studjuice said:
I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
Click to expand...
Click to collapse
Same here. I am still searching for a workaround. I think it is a USB brick.

Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.

asawoszc said:
Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.
Click to expand...
Click to collapse
I installed almost every ROM and kernel there is, there's no connection via USB and the battery life is just terrible (around 6 hours until it's completely empty).

Read through some of your posts Ultraschorsch and I'm definitely in the same boat. I have airdroid to transfer files, but it's slow. I'm gonna try to go to the deodexed stock rom and kernel (but still rooted), and hope I get lucky.
I've already gone into recovery and wiped and reflashed in every combination I could think of and that hasn't helped. It's very frustrating.
I seems like it heated up so much that it destroyed the usb chip on it or something, and it wiped the info of what kind of device it's supposed to be or something. It was seriously so hot that I couldn't hold it in my hand (and that's with a case on it).

This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
I use dropbox to transfer files on my N4, I think it's faster than airdroid.

Ultraschorsch said:
This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
Click to expand...
Click to collapse
Can too! read here: http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
This is what I'm going to do and try to get an RMA tomorrow.
Also, I feel like the only solution would be to open the device. It seems like something actually broke when it overheated when this happened, so it needs to be replaced. whatever IT is.

Dude! If this works I really owe you! I'm going to try this tomorrow! Thanks in advance! :good:

If it works post back here so I (and future people with this problem) know!

So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214

Hello,
Thanks for this tutorial, do i have to lock the bootloader first? I was thinking it was the last thing to do...
(I have to return the phone to google, so I need to restore everything)
studjuice said:
So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
Click to expand...
Click to collapse

Hello all,
This is my first post in here and the reason why I'm here, is that I got the exact problem as mentioned in the opening post.
I've got my N4 last thursday, so 1 week ago. It worked like a charm and since I was busy finding out all the stuff and apps, I hadn't connect it to my PC before the weekend started.
Saturday in the morning I left for a trip and I navigated to the destination, using my car charger. The phone became extremely hot but it was the first time I tried the navigation, so I tought it was 'normal'.
That day and the days after (until today) my battery drained like hell, 6 hours standby with max. 45 minutes of active usage and it is empty.
So I started looking out for a custom ROM to solve it. But I never could connect it properly to my PC. Tried different PC's and different cables. Never a proper connection, only 'usb not recognized' or no connection at all!
Luckily I couldn't connect...because now it's still in the unlocked state as when I got it.
Today I'm going to call the company where I've bought it and ask for an RMA. Only problem is...they imported it from another country since the device isn't for sale in my country (Netherlands).
I'll keep you up to date.