The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?
Related
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
I have never been able to get a tiamat kernel to work on my xoom. I followed a set of directions to completely start from scratch (again, plus formatted whole xoom 3-4 times before doing that) and flashed Tiamat ROM and it worked! I was even able to OC to 1.4, 1.5, then tried 1.7 which caused it to freeze and crash. Then it started acting funky so I did a restore and everything is fine until I turn the screen off or let it turn itself off with a timeout.
The system reboots into M screen and/or a black screen. A reset or two gets it rebooted. I increased the min freq and reset max to 1ghz. What can I do to fix this?? Thanks!
--- Update --- The browser causes a reboot as well. Random reboots into black screen. Def could use some help
ALWAYS stays on black screen when screen times out. Also does it after clearing data via honeycomb. Looking for a little help, can't post on the ROM thread yet
Well I would start from new wipe everything and reflash. Can't hurt. Sounds like something is broke. You can also try to fix promissions as well.
I've completely formatted the xoom including the sdcard and then started w/ 3.0.1 then did the 3.1 flash via CWR then the ROM install. The booting is better after complete wipe but screen still doesn't come back on after a time-out or i shut screen off manually. Browser also causes are boot which takes me to a 2-3 'M' reboot which then times out into black screen. 2 or 3 resets later and it boots up but then reboots within a couple minutes.
The official 3.1 update had my browser crashing which is why i said screw it, i'll flash new stuff. Could def use a hand
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Me as well I've tried everythingeverything. Currently on tiamat 1.1. With rc4 3.3.0
go into wifi settings and make sure your wifi disconnect policy is set to never
2JZ GZE said:
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Click to expand...
Click to collapse
+1
also occassionally find the xoom stuck on motorola boot screen without me trying to turn off or back on..
Ill try but I don't think the wiring has anything to do with the black screen. This will lock even if wifif is off
Mine didnt like 1.7 either, I ended up leaving it sat next to a desk fan for a while to cool it down whioe switched off, then very quickly when it booted managed to get into antutu widget to drop the speed down and hit apply before it locked up again, rebooted all fine now, set it to 1.2ghz to be safe..
Kippui said:
go into wifi settings and make sure your wifi disconnect policy is set to never
Click to expand...
Click to collapse
Dude. I think this worked. I switched my wifi disconnect setting to, never while charging..it was set as, never(uses more battery power). I am currently on Tiamat 1.4.5 with CWM (rc4)3.2.0. Just let it chill over night and charge after a factory reset and viola. Have booted the screen in rotation and a few power offs. Even running at 1.2 g with set CPU. Been running smooth for 2 hours and I can't force it to even freeze. Could it really be that simple. Hahahah. Well see.
I've been having the sleep of Death since I got my atrix I never use wifi so it can't be that it many happens whilst browsing the Internet once finished I lock phone leave come back to it say 5 minutes later and I can't wake the fone so I have to pull the battery out to get it started
Dose anyone else have the happen to them iv tried reset full flash but it's still there
And could I ask what FakeBlurXmppApp.apk is because since I renamed it I ant had a sod?
I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.
AndroidON said:
I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.
Click to expand...
Click to collapse
Na once I renamed it stopped going into sod
I had the same issue with my Motorola Photon 4G, people are having this issue, I don't understand why it keep doing this, how stupid?
The first time this happened to me I just plugged it in around 60% and went to bed and when I woke up in the morning there was nothing. Even taking the battery out and putting it back in, only the LED cokes on briefly but Jo other signs of booting and the only way I fixed it was by plugging it into a computer, or as I found out the second time an XBOX 360 so I'm thinking just something with a data connection, and pulling it out as soon as the LED flashes green then plugging it into the wall charger. Then the phone came up with the battery charging screen at 0%. After it charged I booted up like normal and it was fine for awhile until one time it died and I had to repeat the process to get it to come back up.
Send it in for a replacement, i had two do this to me and both ended up going out. They were unlocked but once they went out AT&T could not tell.
are you on a stock rom or custom rom? before calling for a new one try flashing 1.2.6 sbf and reroot and unlock the bootloader again.it wont say unlocked when you first flash the sbf reboot and reroot but it still is, itll say the boot loader is already unlocked when you go to unlock it thats fine just reboot and itll be back at the top. im saying this cause i had a similar problem and i couldnt turn the phone on or charge it at all i ended up using a different atrix to charge my battery when i turned it on it was stuck at the dual core boot logo. flashing this sbf fixed my brick and the no charging problem but youll be on the earliest firmware for the phone and have to redo all the rooting process. its worth a try and if it doesnt work then send it back.hope this helps.
I no don't think FakeBlurXmppApp.apk is making my phone sod as I've had it twice today its driving me nuts I don't no what's making it happen in another got no apps installed
Root/unlock causes this
I can tell you the issue is caused by either the unlocking of the bootloader or rooting. I unlocked, rooted, and installed a custom rom my 1st stock atrix and had this issue. I also had a hardware defect with the front camera lens so i returned it to stock via sbf prior to returning it. The problem disappeared. My new atrix worked perfect and after a couple days I unlocked and rooted but left the stock rom. Guess what, sleep of death returned, sbf to stock everything is fine. BTW I was using romracers recovery. So Im not sure if its rooting or unlocking or romracers recovery but it is one of the three. Hope that helps.
-Robert
i also have similar issues. it has some thing to do with deep sleep mode..as long as phone does not go in to deep sleep as son as screen is off the problem never happens.
so i tried wifi wizard and advanced wifi lock apps from market.wifi wizard switches on wifi when ever the screen is on. advanced wifi lock prevents phone from going into deep sleep.you can set a timeout.this works like a charm.i rarely get sod.
Sent from my MB860 using XDA App
Rooting isn't the cause. My first Atrix was rooted & I never had that problem. My second Atrix started right awaywith the SOD, shortly after the OTA update.
And I'm my opinion, unlocking is absolutely necessary. If I hadn't unlocked my previous Atrix so that my backup applications and data syncing would work properly, I would have really been screwed. But every other day my phone backs up my data and once I'm home, uploads out to my home pc.
Sent from my MB860 using xda premium
May be a little premature, but my current Atrix was have SOD & random reboot issues. I had given up & ordered a replacement. However, I changed the screen time out to never & I haven't had a freeze or reboot yet. I'm on day two & I've made a point to turn my wifi on and off. Hope this solves the problem. Guess I'll know if I make it through next week with no freezes.
Sent from my MB860 using xda premium
i bought my atrix within one month of the launch I have always had the sod it has nothing to do with the rom although some roms will make it not happen as much my wife got her atrix like in September and she has never had sod. i just put up with it i plan to leave att once my contract is up
EDIT... reminds me to see if it is up don't remember if its one or 2 yrears
SOD Fix
I was SOD free being rooted, BL unlocked, running rom racers recovery, CM7 then Neutrino 2.6 then my phone decided format its internal partition on me. My phone is back up running now and I was getting the SOD a couple times a day. I fixed it by following 1chris89's fix here. I've been SOD free so far on day two running an OC kernel. 1chris89's fix a bit involved, editing the build.prop file, and based on cm7 flavored ROMS, changing the performance settings. Be careful when messing with the build.prop file and make a backup before attempting! Check out Xploited's guide here for a less involved method to fix your SOD. Hope these help!
OK! But... where can I find this "cm7 performance menu"?
marcosvafg said:
OK! But... where can I find this "cm7 performance menu"?
Click to expand...
Click to collapse
I'm on Neutrino 2.6, to get to it I have to put a short cut on one of my home screens. First long press on your home screen and choose shortcut then choose cyanogenmod settings then choose performance settings.
would if i cannot even get into my phone to change the settings. Can someone with skillz put it into something that i can flash [1chris89's fix]?
it my just be a hardware issue for me also, but i did just get my know back from Motorola with a new screen installed.
When my phone does the SoD I can place a call to it, let it ring a few times, and then hang up. My display turns on and I can get get to the launcher to reboot the phone.
The SoD seems to get worse when I'm using the Bluetooth connection to my Sync system in my truck.
I've had my Nexus 7 since July and I've been completely satisfied with it. Once I got the 4.1.2 update some strange things have been happening and I'm trying to pin down the reasons since it seems to be a software issue and not a hardware one. The first event happened when I was trying a Live Wall Paper, Oceans HD. After setting the LWP and using it for a few minutes the next time I picked the tablet up and tried turning it on I noticed it had reset. No problem, except after the splash screen everything would go dark again and the power button didn't seem to work at all unless I waited for a while, and tried long pressing it and rebooting the device. After a few reboots of this the screen began to behave weirdly, sort of looking as it there was a problem with the video driver since it looked like a an old TV screen with static. I thought the video hardware was toast and was relived the next day when I tried to reboot again that the tablet rebooted to the default WP. No problems after that. I contacted the maker of the LWP thinking that was the problem. However, after trying out another LWP from another maker, the same thing happened after a few days of use. Jumped through the same hoops and got the WP changed to a static one. I went online and read through a few forums to see if anyone had the same problems but was not bale to find the same issue. I read something about the auto brightness and turned my auto brightness off to see if that works. What do you guys think about this? I use the tablet a lot and for professional purposes often. I cannot afford to have it go bonkers during a presentation.
Are you stock or rooted? I'd re-download a stock 4.1.2 ROM and re-flash if your rooted. Regardless I'd try to redo the 4.1.2 update. Or go back to 4.1.1 see if the problem persists, if not try the update again.
gokart2 said:
Are you stock or rooted? I'd re-download a stock 4.1.2 ROM and re-flash if your rooted. Regardless I'd try to redo the 4.1.2 update. Or go back to 4.1.1 see if the problem persists, if not try the update again.
Click to expand...
Click to collapse
It's the stock ROM. I think I know what the problem is. It appears the contacts of the battery may be loose, or that the battery's charge may be draining very quickly, since, after the tablet goes out, after waiting some time, I plug it back in and it reveals the charge to be 0. I know for a fact that it isn't 0, but this reveals the battery either was discharged or the contacts are loose. It is also charging up quite slowly. I'm beginning to think it is an electrical problem.
have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.
probably battery issue
Gibson295 said:
have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.
Click to expand...
Click to collapse
It's probably battery. Does the phone shut down on charge?
I have same issue and I don't think that it's something wrong with the battery, because I already changed the battery and nexus 4 still freezes sometimes. And it's looks like freeze, not regular shuted down phone, because it's hard to wake up after that happens.
I read somewhere that this may be issue with internal memory, but I'm not sure about it.
Gibson295 said:
have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.
Click to expand...
Click to collapse
Had same issue running on stock 5.1.1 or something like this. Shut downs, reboot, frozen screen, don´t wake up, start problems, networking complete breakdowns.......installed Lineage 15.1 official and no such issues so far.
So it might be Android related.
So best thing, unlock bootloader by Nexustoolkit, flash latest custom recovery TWRP (you have to flash an older version first, if not having TWRP allready) and then install Lineage 15.1 official. Use instructions provided by XDA. It might be dropped, but it runs great.