Database Users

[Q] Black screen after CM RC2 install

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?

Phone crash after battery died!!

my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..

Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje

Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?

everything was stock on mine, no root.......maybe thats why i could recover it??!!

Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.

I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.

Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions

That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!

I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1

Screen not responding right

Any ideas?
the Vega is on Vegacomb (not the very latest version but the previous one). It's sat doing nothing for around a month, I charged it the other day and went to use it (I've also powered it off and restarted numerous times).
I cannot long press on anything, it acts like a single press and launches apps, it's hard to swipe from screen to screen, only works 10% of the time (I've cleaned the screen thoroughly!)
occasionally if I press something on the right of the screen it selects something in the middle
how can I solve this?
does it need a wipe (hope not!)
cheers

I had these screen issues with vegacomb.
For me only the left third of the screen would work after a while.
I looked through many threads but it seemed as though its just a Vegacomb bug that's affects some but not all users.
I reflashed the modded stock rom, then reflashed vegacomb and it worked again but only for a day or so.
I love Vegacomb, but as I'm out and about with the tab and don't always have a laptop with me to fix it, I needed more stability. I went over to Corvus and the screen problem has never happened again since.
Hope you find a solution.
Sent from my HTC Desire using xda premium

Same problem :/

Motorola Atrix Sleep of Death

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.

franco.kernel problems.

I really, really like franco.kernel, but there is one problem.
When I first flashed the kernel, it worked fine for a day. Then the problems started to happen. After the first day of it starting to work, I woke the tablet up and it froze right at the lock screen. I then did the hold the power button for 15 seconds to reboot and it rebooted fine. I booted in to Android (thankfully) and again it froze right at the lock screen. I do this process about 3-5 times and then it finally works normally. And the next day, the entire process is done again, etc. I have absolutely no clue what the hell is up with that.
Just tell me if there is any way I can keep the kernel, or if I have to go back to stock (If it goes down to having to go back to stock, can someone tell me how to do that?)

CaptainBromo said:
I really, really like franco.kernel, but there is one problem.
When I first flashed the kernel, it worked fine for a day. Then the problems started to happen. After the first day of it starting to work, I woke the tablet up and it froze right at the lock screen. I then did the hold the power button for 15 seconds to reboot and it rebooted fine. I booted in to Android (thankfully) and again it froze right at the lock screen. I do this process about 3-5 times and then it finally works normally. And the next day, the entire process is done again, etc. I have absolutely no clue what the hell is up with that.
Just tell me if there is any way I can keep the kernel, or if I have to go back to stock (If it goes down to having to go back to stock, can someone tell me how to do that?)
Click to expand...
Click to collapse
do you have it "set to boot" on a high cpu oc or a high gpu speed?

Whenever I download a torrent, my tablet always freezes on Franco. I have to revert to lean kernel temporarily. It happens on every f.kernel build

Are you on the latest kernel?
Sent from my Nexus 7 using Tapatalk 2

I didn't have any problems with using Franco #25 on the ROMs based on 4.1.2.
If you are on a ROM based on 4.2.1, I'd like to recommend to go back to Franco #31. I think it was the most stable version on Nexus7 for 4.2.x.