I've been regularly running cyanogenmod 11 on my Bell S3 without many issues. Last going off, I believe I was running either M11 or M12 of CM11, and all was well. Then, curiosity got the best of me, and I slapped on CyanideL Lollipop beta, and while that ran pretty damn well for me for about a month, I reverted back to CM11 a few days ago due to some minor bugs and annoyances (mostly camera). Anyways, since reverting back to CM11 M12, my phone has been randomly shutting off, not rebooting, just off. It has happened while it's in my pocket not really in use, or it can happen while I'm going to check my text messages.
Thinking this was an issue maybe with M12, I updated to the latest nightly, but nope, its still the same. Some of the times that its happened in my hands, I've seen the Power Button menu pop up, and then disappear. A few seconds later, boom, off she goes. It always powers up again when I power it back on, but I would like to try to get to the bottom of what is causing this, as it is being very annoying for me.
The question is, what can I do to try and nail down this issue? When flashing back to CM11, I did the full wipe, then dalvik/cache after the flash. Is there something that happens when you go from 5.0 back to 4.4 that may cause this?
This is possibly related. I tried out an unofficial cyanogemmod 12 rom on my AT&T S3 for a while, but decided to revert due to camera not working. So I installed S3Rx ROM on the phone and had some issues. The phone would get stuck on the loading screen and never get past that. I did the standard data/factory reset, cache wipe and dalvik wipe before installing S3Rx back, but no luck. The only way I could get it to install correctly was by formatting /system, /cache, /data and /data/media in ClockworkMod recovery. But be aware that you will lose all personal data when you do that so be sure to backup.
Alright, I'll backup what I need to, and do a full wipe as you suggested. I'm pretty sure I did that when I downgraded to begin with, but no hurt in trying it again.
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
audit13 said:
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
Click to expand...
Click to collapse
If I do go back to Stock 4.4.2, would I be able to re-root again? Its been a couple of years since I had to mess with stock, so I don't know what has changed.
I've tried a few different things here, completely wiping everything, installing a 4.4.4 kernel, installing CM11 from scratch, restoring from TWRP, etc etc. Still having the issue.
Last thing I'll try before going to stock is to try going back to lollipop.
Update: I'm starting to think that this is just a coincidental hardware issue. It seems to have something to do with my power button, perhaps there's something stuck in it that's cause the button to be pressed. Right before it shuts off, the power menu pops up for a split second once or twice, then the phone becomes unresponsive for a second, then its off. Certainly sounds hardware related. Just attempted lollipop again, and same result.
I think you are correct in your assessment. Open up the phone and see if you can find anything that looks odd.
Related
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
ernbrdn said:
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
Click to expand...
Click to collapse
I've never seen that before. Interesting. What rom are you currently using? Do you have an unusually large amount of apps installed? The first thing I would do, is make a nandroid backup of your current setup, and then do a full wipe and flash a format all.zip, then reflash a different rom. Or just simply restore a nandroid of a known good setup, and see if the problem persists. If it stops, I'd say it was something specific to the rom/kernel/setup that you were running before. If it continues happening on a clean install of a different rom, then I'd probably unroot, restore to stock, and then see if the problem continues. If it does, take it to Sprint. If it stops, and everything is fine, re root it and start over. That's just what I would do, but I've never been presented with an issue such as that.
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
ernbrdn said:
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
Click to expand...
Click to collapse
If it started happening right after you swapped out the kernel, that could be the culprit. If you want to try the gingersense rom, I'll all for it, and will tell ya that they ran super incredibly smooth for a factory rom. However, if you don't feel like changing roms just yet, maybe try a different kernel. I'd be suspect of that, if the problem started shortly after changing to a different kernel. I say try out a gingersense rom, you shouldn't be disappointed (unless your phone still hangs at the splash screen upon reboot, lol).
Has anyone has a similar problem to this or any ideas how to troubleshoot?
I've had my lovely 1X since launch. Soon after I rooted her and then had her run CM nightlies until the past week when I decided I wanted to revert to stock for a while
This went swimmingly; I locked, installed the RUU then a slew of updates and last night the phone was happy, stable, making and receiving calls. I plugged her in as normal before I went to bed.
Got up today, unplugged her and almost immediately she crashes and reboots. Continually getting to the first screen, able to unlock sometimes and then goes black and reboots or just freezes and needs resetting.
So I figure, it's software, right?
I unlock her bootloader again, flash CWR 5.8.4.0 again, flash the boot.img from this JB rom and then the rom itself, then 4.2 gapps.
Everything fine. While plugged in.
Unplug; reboot cycle again
Not entirely sure what to do with her now other than try a bunch of other roms. A problem that's consistent across roms/recoveries/boot images, locked and unlocked though...
Anyone have any ideas, please?
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
[email protected]|-|oR said:
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
Click to expand...
Click to collapse
I did wipe of course.
And if it happens across roms, lock/unlock etc. I probably IS hardware. Just want to be as sure as possible.
Ok, I'm at a total loss. For some reason my gnex running liquidsmooth started rebooting randomly today. I tried wiping cache/dalvik and that didn't work, so I did a factory reset. That also didn't help, as soon I was asked to choose a wifi network the phone froze and rebooted. So I tried restoring to a previous working version of liquid. I still had the same problem. It rebooted every 5 minutes! Then, I tried wiping everything and installing a fresh copy of liquid,but I still couldn't get past choosing my wifi network w/o a reboot. So I finally tried restoring to a really old aokp backup and it STILL is rebooting. what the heck is going on? Can anybody give me any help? Is this a hardware issue? I've also tried two different batteries by the way.
Some more info. It seems to be tied to notifications. I got it running on the AOKP rom on airplane mod, but when i received a text from my wife it rebooted 3 times. I only got it to stop by putting it back into airplane mod. Could it be a radio issue? I'll try flashing some.
why dont you flash back to stock and see if that works fine. that will tell you everything.
Zepius said:
why dont you flash back to stock and see if that works fine. that will tell you everything.
Click to expand...
Click to collapse
Good point. I'll probably try flashing muzzy's rom really quick, since it's supposed to be so stable to see if that does the trick. If not I'll try going back to stock. I've never had to go back to stock with this phone, so I wouldn't mind avoiding it if I can, but anything is worth a shot at this point.
I really just need to nurse it along until the VZW one or Moto X come out. I'm holding out for those at this point.
I wouldn't recommend flashing another custom ROM. You should flash the factory images.
I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
hotelmariofan said:
I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
Click to expand...
Click to collapse
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Robbie Doo said:
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Click to expand...
Click to collapse
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
hotelmariofan said:
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
Click to expand...
Click to collapse
You're right, there's no need for completely formatting the phone between nightlies. However, your modem seems to be an older version. I believe the CM 10 based on MD4 and the CM 11 is based on MK3. You can verify this in their respective forums though.
My suggestion would be to download the latest modem and the CM 11 onto an external card. Format your phone completely. Install the modem then install the CM 11 + KK Gapps.
Let us know how it went if you go through it.
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?
ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!
And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas