[Q] Cyanogenmod Glitches - Sprint Samsung Galaxy S III

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.

Related

[Q] Phone deactivated?

I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules

[Solved] Urgent, LTE issue.

Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.
Solved. ODIN'd back to stock =) Thanks hednik!
RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

[Q] Maguro, Wifi is not working at all, suddenly. Help please, ideas?

I was connected to my wifi, left my phone alone for a few hours, and when I came back (yesterday), i saw the wifi not connected. I go to try and reconnect it, and it says wifi turning on, and nothing else happens, it is stuck there. I can not get it to connect to my wifi. Any idea what could cause this? what can I do?
Gsm galaxy nexus, paranoid android 3.99 android 4.3.
mobile data, calls, text, etc all work great, only problem is wifi seems to be stuck. I tried rebooting, but still nothing.
Any ideas, and thanks for your help.
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
malystxy said:
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Factory reset, nothing, restore previous nandroid from 6 months ago, noothing. Still stuck at turning on wifi, but nothing more than that happens. Would screen shots help I can post them. Last resort going to go back to pure stock see if that fixes it.
If not I am guessing hardware problem? anyone have somthing similiar happen, and what did you get to work if anything to fix it? or is my wifi module fried? Thanks any who have input.
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
iLeopard said:
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
Click to expand...
Click to collapse
Awesome, thanks for responding, was beginning to wonder if anyone was reading it
What I tried so far (each time wiping dalvic cache, cache, and doing full factory reset from both within android and cwm):
Factory reset on paranoid android 3.99 android 4.3 = nothing
Install cyanogemod 4.3 = nothing
Restore my nandroid backup of bixie deodexed stock rom (which i used before going to paranoid) = nothing
try other version of android from 4.1, 4.2, etc. on varion roms = nothing
restore to google stock (as far stock as possible minus locking bootloader, means yes, stock recovery and everything), 4.1, 4.2, 4.3 = nothing.
ran out of ideas, learned alot though, and got more flashing experience than I care. Did learn how to adb backup, more about android backups, etc though. Some good has come out of it, but my original problem of wifi was and is still not resolved.
Unless there are other ideas, I am pretty convinced the wifi antenna/module died (and a google search confirms others have had something similiar happen, they had to replace the pcb to fix it, which is costly where i live, Argentina). So may just use it sans wifi until I get a new phone, thing has a couple years anyway and nexus 5 is about to be announced.
But I am open to any and all suggestions least I still have hpsda+ speeds 70% of the time.
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
initialize, discoverPeers, connect : working
file trasnfer : not working
i guess, wlan driver of kernel space is missing. ex) nl80211.c & wl_cfg80211.c
my phone is android 4.1, 4.2 in AOSP.
i nothing solves it, too :crying:
somebody Help~~
This thread is over a year old, but I'm having the same problems lately. The device was reluctant to auto-connect to known wifi networks, which I attributed to the current and latest CM11 snapshot. Then, a few weeks ago, the phone became unstable, with random reboots 3 or 4 times a day. Clearing cache and Dalvik cache didn't help. I didn't want to do a full-wipe, with CM 12 on the horizon. About 2 days ago all wifi reception stopped. I could activate wifi in the software, but the device wouldn't receive any signal at all (checked with Wifi Analyzer). So I was afraid that the wifi died out permanently. This morning, in a last attempt I switched off the phone and took out the battery for a couple of minutes. On restart I was surprised to see that wifi found a known network and received an ip-address. However, an internet connection never established and the menu reported a bad reception. I then de-activated and re-activated wifi, but that didn't bring me any further. I guess I'll wait for the first CM12 nigthlies to find out if miracles still exist.

[Q] S3 Turning Off on its Own

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.

Categories

Resources