I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?
No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.
For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.
I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.
I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.
The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?
i have already done it, even the SD card, still same problem.
Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!
Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!
I get restarts because the modem crashes... its a known issue apparently
gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back
Related
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).
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.
Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)
I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!
I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!
Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.
You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck
Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.
Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.
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