My Droid 3 running steel droid 4.5 began bootlooping a couple of days ago. I don't think it's an actual bootloop though because sometime I manage to get to the lockscreen and am able to unlock my phone. However, I can't do anything after unlocking my phone because the screen is black and is unresponsive unless I get a text via handscent messenger.
I have feeling that one of my apps is making it crash because the screen is black. I am using GO launcher with wallpaper changer. Also for some strange reason I don't have the option to do a nandroid recovery even though I have a nandroid backup on my SD. Does anyone have any suggestions as to what I can do aside from a factory reset?
Related
Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
Hi,
Recently, my Desire HD has crapped out during the process of changing my back ground wall paper. It restarted and some how the screen got stuck on lock screen with the screen being totally unresponsive. I can tell the device is semi-working as the top bar does all its started processes and the top lock button works (although it is with a delay).
Is there a reason why this is happening?
Any solution to it? (Yes I have gone through google for 2 hours without solution found)
If I have to resort to hard reset, is there any way I can back up my messages + things in the phone aside from programs before resetting?
Any help would be great!
Thanks in advance!
K20rtune said:
Hi,
Recently, my Desire HD has crapped out during the process of changing my back ground wall paper. It restarted and some how the screen got stuck on lock screen with the screen being totally unresponsive. I can tell the device is semi-working as the top bar does all its started processes and the top lock button works (although it is with a delay).
Is there a reason why this is happening?
Any solution to it? (Yes I have gone through google for 2 hours without solution found)
If I have to resort to hard reset, is there any way I can back up my messages + things in the phone aside from programs before resetting?
Any help would be great!
Thanks in advance!
Click to expand...
Click to collapse
there is so many reason why it happening one is the phone may be low on "RAM" to accommodate the task
If you need to back up your file you can sync your your phone to Google acct or buy Titanium Backup Pro on Market
As the title says, I was using my N10 quite a bit yesterday but just before I went to bed I noticed a strange icon (?) in the notification bar that I couldn't get rid of... kind of a white spot/circle fading out towards the edge... Anyway I turned off the Nexus using the power key and choosing shutdown. It was then stuck on the Nexus "X" screen loading for ages >10 minutes! Occasionally it partially loaded my lock screen but not for long enough for me to unlock it or anything, and then reverted back to the loading "X" screen. Anyway the only way I could "fix" it was to go into boot recovery and choose "data wipe/factory reset".
Its working now but I am slightly frustrated that I have lost all the photo's and downloads I saved onto it (I know I should have had a backup but I wasn't modding it or anything).
My questions are, has this happened to anyone else with stock rom and unroot and any idea what the icon was in the notification bar? Also, should I return it for a replacement?
Much appreciado!
Rob
First off, using Velocity 1.2b18 on an old LG Ally. As the thread title says, it's based on (ancient by this point I guess) Android 2.2.2/Froyo.
Velocity comes with a modified lock screen font that has a square/robotic/futuristic/etc font chopped in for the numbers. Since it was about as far from matching my launcher clock font as it could possibly be, I figured I would simply switch Velocity's stock font for that of the launcher font. Others have apparently done this in the past, it seemed simple enough, so I figured...why not?
I used 7zip to grab the font from the apk it was in, dropped it into my SD card, and started the process. I did the following in Total Commander, while the phone was running; in hindsight I realize this was a terrible idea. Anyway, I copied the replacement font into the fonts folder, renamed it to Clocktopia.ttf, and renamed the old one Clocktopia.old. Then I exited and tried to lock the phone.
It tried to shut off and lock, came back up, then the screen shut off again. After that, whenever woken up, the key lights and backlight would come on, but it simply freezes on a black screen. Opening the physical keyboard (which would normally auto-unlock) does nothing, and it won't go back to sleep via the power button. Rebooting the phone, since it normally boots to the lock screen, has the same result.
"Ok," I thought, "so I'll simply remove the replacement font and re-rename the original and all will be well". And so, booting into recovery and accessing the phone from adb, I did just that. Rebooted the phone after this: same result as before. A bit of googling suggested clearing the cache when messing with fonts, so I cleared both caches and rebooted: same thing.
I've since made a nandroid of this apparently now borked android installation and restored a backup from the middle of the month (note to self: backup BEFORE screwing with things I don't fully understand next time), but my questions are...where did I go wrong? Was it that I performed the replacement while the phone was running? Why didn't restoring the original font reverse the effects, and is there any way to save the backup from its currently screwed-up state?
I'm at the end of my rope with this. Several days ago my s5 started refusing to drop down the notification panel and the quick settings menu. I'm running stock rooted kitkat 4.4.2. I did a factory reset, disabled xposed (in case some notification bar mod was causing this even though I hadn't changed my xposed settings for months), got a replacement SIM card, went back to an earlier version of google, and now sometimes it will work for a whole day and then stop responding again. I took out the external SD card and it still does it. I uninstalled anything new (not much) that had recently been installed. I have been using Nova as my launcher, so I tried going back to just Touchwiz, but no change.
It's not just the drop down screens, when I open Titanium Backup and try to use the "clear" or "menu" buttons at the top of the screen, they don't respond either. It's like something is freezing the top half inch of the screen (I measured it in frustration).
I went into the diagnostic menu and checked the screen and everything is responding as far as I can tell--the line goes up to about an eighth of an inch from the top of the screen but the pictures for this when I googled looked like that so maybe they aren't supposed to reach the actual top of the screen.
Googling shows that several models at least of Samsung, and even some Sony, are showing this problem and nobody seems to know how to fix it.
Has anyone got any clues they can give me about this? I can't seem to find what the problem is.
Update--I tried flashing Hispasian Kernel but it didn't solve the problem. I tried defrosting everything I had frozen with Titanium Backup and that didn't solve the problem.
Flash latest stock lollipop FOL1 and see if it's still there. If that doesn't work then you have a hardware defect and you'll need to get your phone repaired.
That's a good idea. Thanks!