Database Info

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.

newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium

Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!

I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?

I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.

Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?

newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.

Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.

He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O

@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves

Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

[Q] Phone occasionally becomes completely unresponsive with non-stock ROMs

Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?

power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?

redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.

What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app

c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.

GPS on when this happens, by any chance?

redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.

Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app

Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me

I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.

No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.

nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.

I understand what you're saying but i have checked it,i'm sure..

nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).

No my main problem are the Sleeps of Death.There are no BSODs in android

nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.

Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.

I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often

random reboot vibating and camara flash flashing on and off

Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.

Probably a sticky power button. Although the camera flash is weird. It's a common problem. Search stuck power button
Sent from the short bus

Ya I figured that thought I'd ask thx I'll have to grab a #0 phillups tomarrow

I had this exact same issue on the UCLL3 leak for AT&T. I got out whenever I would flash gs2user's mods on top of the odexed stock version. It required me to reflash my ROM.
Sent from my SGH-I727 using xda app-developers app

Well I've reflashed stock rogers and wiped 3 times before and after flash so I hope that fixes it skyrockets not my daily driver but my friendwants to borrow it so I hope I fixed it up

xstokerx said:
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Click to expand...
Click to collapse
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure

phone reboots and vibrates
tobesedated said:
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
Click to expand...
Click to collapse
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)

as-ny said:
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
Click to expand...
Click to collapse
Seems odd to me that it would be a sticky power button for one ROM and not another, but then I can't figure for the life of me why mine worked fine and his didn't. Twilight phone zone lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Ya so I cleaned mine and still it does it I odined back to stock still dose it I'm at my wits end its pissing me off
OK so I odined back to stock factory reset stock then flashed twrp in odin then updated twrp and flashed the super light cm10 with gapps haven't had a reboot yet fingers crossed that it worked must be a software thing I got no clue.

OK update my phone started doing this again to day did it like 6 or 7 times FML its defently a hardware problem.

I'd have to agree that it's a hardware problem
I wiped my phone shortly after my post and did a clean install of seanscreamz newer ROM as well as TWRP. Problem continued to happen...actually worse than before. But at that point I had yet to put a single app on it, so an issue of incompatibility of my apps and ROM did not seem to be the case. I then wiped my phone AGAIN, and di a clean install of CWMR and CM10 (I went from ICS to JB), figuring maybe a TOTAL change would do the trick. Not the case.
The phone still randomly reboots, but now that I am certain it is a problem with the power button, I know how to deal with it, and can minimize te recurrence and my frustration levels. I read a post that said someone else had the same problem, and smacked his phone on his desk repeatedly on the power button, and the problem stopped. I didn't do that, but when the problem occurs, I will repeatedly hit the bower button, or if my otterbox case if off, I will stick my nail into the button to pull it out.
It's too bad, 'cause it's a great phone otherwise!

I got an app called tap tap tap and it uses the proxy sensor to unlock the phone and adds a widget in the notification bar to lock the phone works great then my power button does not get stuck Cuz I don't need to push it.

[Q] Having problems with 4.3 on a rooted sg3

I try to keep up with latest os, but 4.3 has me baffled. The first time I tried to install 4.3 was on Jellybam 10.2. I followed the instructions to the tee, but it didn't work. All 4.3 roms I've loaded I've never had a signal. I don't know what I'm doing wrong. Now that all of the 4.3 roms have the custom recovery already on the rom, it still doesn't work. I have no signal. I thought about unrooting my sg3 and starting over, but that is a pain. So I'm basically stuck with 4.2.2. If anyone has anything to say about my problem please do so. Thanks

wily5150 said:
I try to keep up with latest os, but 4.3 has me baffled. The first time I tried to install 4.3 was on Jellybam 10.2. I followed the instructions to the tee, but it didn't work. All 4.3 roms I've loaded I've never had a signal. I don't know what I'm doing wrong. Now that all of the 4.3 roms have the custom recovery already on the rom, it still doesn't work. I have no signal. I thought about unrooting my sg3 and starting over, but that is a pain. So I'm basically stuck with 4.2.2. If anyone has anything to say about my problem please do so. Thanks
Click to expand...
Click to collapse
I'll second that. Was running cleanrom 7.0, thought I'd fool around with 4.3 Flashed a couple of different ROMS, and none worked. Restored my backup of Cleanrom, and still no signal. It shows 4 bars, can receive an occasional text, but trying to text or make a call the signal drops away. Help!
Tim

wily5150 said:
I try to keep up with latest os, but 4.3 has me baffled. The first time I tried to install 4.3 was on Jellybam 10.2. I followed the instructions to the tee, but it didn't work. All 4.3 roms I've loaded I've never had a signal. I don't know what I'm doing wrong. Now that all of the 4.3 roms have the custom recovery already on the rom, it still doesn't work. I have no signal. I thought about unrooting my sg3 and starting over, but that is a pain. So I'm basically stuck with 4.2.2. If anyone has anything to say about my problem please do so. Thanks
Click to expand...
Click to collapse
moonfarm said:
I'll second that. Was running cleanrom 7.0, thought I'd fool around with 4.3 Flashed a couple of different ROMS, and none worked. Restored my backup of Cleanrom, and still no signal. It shows 4 bars, can receive an occasional text, but trying to text or make a call the signal drops away. Help!
Tim
Click to expand...
Click to collapse
when you flash, co you clean flash? and what recovery are you using? This info would help in getting your questions answered.
i've been running Mastamoon's unofficial 10.2 (Android 4.3) nightlies (http://forum.xda-developers.com/showthread.php?t=2385652), and regularly flash back and forth between TW Roms as well and have never had any real data problems. sure, drops data every once in a great while, but Mastamoon puts a lot of work into cleaning up issues.
one thing: IF you flash, and you don't have data, did you wait more than a couple of minutes? Sometimes it takes a while on first flashes. Also, did you check what your status said? (menu >system settings >about phone >status? Also, check to insure your mobile network is set up correctly (menu >system settings >more > mobile network settings) and check your CDMA subscription is set to RUIM/SIM and NOT NV, and network mode is set to LTE/CDMA/EvDo sometimes during a bad flash, these can get hosed up.
like i said, i run Masta's unofficial version, and go in and out of data areas (no data in the subway tunnels) and it always goes right back.
give that a try, and if still having problems, add more information befor just saying "i don't get any data with any 4.3 rom

goldsmitht said:
when you flash, co you clean flash? and what recovery are you using? This info would help in getting your questions answered.
i've been running Mastamoon's unofficial 10.2 (Android 4.3) nightlies (http://forum.xda-developers.com/showthread.php?t=2385652), and regularly flash back and forth between TW Roms as well and have never had any real data problems. sure, drops data every once in a great while, but Mastamoon puts a lot of work into cleaning up issues.
one thing: IF you flash, and you don't have data, did you wait more than a couple of minutes? Sometimes it takes a while on first flashes. Also, did you check what your status said? (menu >system settings >about phone >status? Also, check to insure your mobile network is set up correctly (menu >system settings >more > mobile network settings) and check your CDMA subscription is set to RUIM/SIM and NOT NV, and network mode is set to LTE/CDMA/EvDo sometimes during a bad flash, these can get hosed up.
like i said, i run Masta's unofficial version, and go in and out of data areas (no data in the subway tunnels) and it always goes right back.
give that a try, and if still having problems, add more information befor just saying "i don't get any data with any 4.3 rom
Click to expand...
Click to collapse
Good afternoon, and thanks for your help.
I wish I could give you more information, but I broke one of my cardinal rules about messing with my phone and didn't take notes. Suffice it to say I was trying a couple of different 4.3 ROMS in the forums, as well as the two available MIUI roms that were in there. I use TWRP.
I did wait quite a while before declaring no data, it has actually been a couple of days. It does show I have a signal, and I can get texts that are sent to me. When my wife tries to call my phone it goes right to voice mail, even when it does say I have a signal (4G, full bars). I also cannot send a text, it immediately goes to 'failed message'.
I tried setting my phone back to LTE/CDMA/EvDo, but I don't see an option for CDMA subscription. I wonder if I accidentally tried a Global ROM instead? All I am really looking for is some 4.2 love, I like what my daughters Nexus 4 has for lock screen widgets, and my Cleanrom installation is acting a little wonky now and again, so thought it was time to flash something new. Silly rabbit, trix are for kids.
Thanks again. Thinking of flashing a stock ROM and starting over. Any thoughts?

moonfarm said:
Good afternoon, and thanks for your help.
I wish I could give you more information, but I broke one of my cardinal rules about messing with my phone and didn't take notes. Suffice it to say I was trying a couple of different 4.3 ROMS in the forums, as well as the two available MIUI roms that were in there. I use TWRP.
I did wait quite a while before declaring no data, it has actually been a couple of days. It does show I have a signal, and I can get texts that are sent to me. When my wife tries to call my phone it goes right to voice mail, even when it does say I have a signal (4G, full bars). I also cannot send a text, it immediately goes to 'failed message'.
I tried setting my phone back to LTE/CDMA/EvDo, but I don't see an option for CDMA subscription. I wonder if I accidentally tried a Global ROM instead? All I am really looking for is some 4.2 love, I like what my daughters Nexus 4 has for lock screen widgets, and my Cleanrom installation is acting a little wonky now and again, so thought it was time to flash something new. Silly rabbit, trix are for kids.
Thanks again. Thinking of flashing a stock ROM and starting over. Any thoughts?
Click to expand...
Click to collapse
follow my last post; Mastamoon has his version of CM10.2 (4.3) running great, and is very quick at answers (during the week that is) as well a couple of other DEVs that follow that tread are always willing to offer help. AND he has a download app, that once you install will tell you when there is an update, give you a direct link to it, and after downloading, will check the MD5 to insure a good download.
providing you are on VZW that is.

I actually had this problem coming from hyper drive to dirty Unicorn. But i started out on the Droid X back in the day so I was used to it. While I don't know if this really works but it worked for me is do *22899 then *228# ( so the keyboard pops up ) i did it a few times also i turned it off the cell service and turned it back on using the toggle. While i dont know if that will do it it worked for me. I know LTE dont need do that because of the sim but it does for me in the hiccup.
A question i have that i cant post in the Dev Fourm because of lack of post. I been part of XDA for long time just never posted. But I'm running Dirty Unicorn and theres a option for fast charge but it does nothing. I've used this feature before and makes my car charger work better and home charging and my battery sucks now but does anyone know how to get it working? I've tried terminal did SU and FFC but nothing.

I'm running twrp recovery. I'm asuming the latetest version. And i do let it settle for a while. As for the settings you mentioned, everything is normal,and as it should be. The imei,meid, ect. Is normal. Thanks for the input.

I've fixed this by going full ODIN, putting a stock image back on, and following the instructions at http://forum.xda-developers.com/showthread.php?t=2066133 Seems to be working, it is no longer on roaming.
Tim

wily5150 said:
I try to keep up with latest os, but 4.3 has me baffled. The first time I tried to install 4.3 was on Jellybam 10.2. I followed the instructions to the tee, but it didn't work. All 4.3 roms I've loaded I've never had a signal. I don't know what I'm doing wrong. Now that all of the 4.3 roms have the custom recovery already on the rom, it still doesn't work. I have no signal. I thought about unrooting my sg3 and starting over, but that is a pain. So I'm basically stuck with 4.2.2. If anyone has anything to say about my problem please do so. Thanks
Click to expand...
Click to collapse
When I tried 4.2 and turned off data it completely killed my signal. None of my recoveries of 4.1.2 had signal. Flashing back to stock fixed the signal problem.
Hellfire and Dirty Unicorns have worked great for me since going to 4.3 and 4.3.1. I use cwm touch recovery but idk how much of an effect recovery has with flashing a rom successfully.
But this tool makes rooting, unlocking the bootloader, and recovery very simple and easy. (but I would flash the latest recovery after using the tool just in case)
http://forum.xda-developers.com/showthread.php?t=2332825
jailbreaktoroot said:
I actually had this problem coming from hyper drive to dirty Unicorn. But i started out on the Droid X back in the day so I was used to it. While I don't know if this really works but it worked for me is do *22899 then *228# ( so the keyboard pops up ) i did it a few times also i turned it off the cell service and turned it back on using the toggle. While i dont know if that will do it it worked for me. I know LTE dont need do that because of the sim but it does for me in the hiccup.
A question i have that i cant post in the Dev Fourm because of lack of post. I been part of XDA for long time just never posted. But I'm running Dirty Unicorn and theres a option for fast charge but it does nothing. I've used this feature before and makes my car charger work better and home charging and my battery sucks now but does anyone know how to get it working? I've tried terminal did SU and FFC but nothing.
Click to expand...
Click to collapse
I believe fast charge is kernel related and not because of a rom. I haven't ever used fast charge but all the kernel threads always list fast charge as a feature. But which DU build are you running?

[Q] Cyanogenmod 11-M9 crashy as hell on Hammerhead?

Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?

starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.

Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.

starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.

Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.

And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens

No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.

Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.

Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.

Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...

Im using M9 snapshot too and i have not had 1 problem its been excellent

No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.

simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5

last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?

trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any