Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:
there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...
Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse
no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know
nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:
Related
I recently updated my Galaxy S4 (i9500) to Android 4.3 [MJ5] using Kies. The phone is completly stock and non-rooted. After the update, I'm unable to pull down notification bar. However, after I restart the device, it works well for some time and then again refuses to be pulled down.
Has anyone else experienced the same problem? I have lot of data on the device that will be difficult to restore and hence and donot want to format the phone. Any suggestions/solutions that might resolve the problem?
Also, after the 4.3 update, when I check for OTA, a popup shows saying "Your device has been modified. Software updates are not available." Pulling out and reinserting SD card didn't solve the issue.
Same problem. .. No solution yet.
arpit88 said:
I recently updated my Galaxy S4 (i9500) to Android 4.3 [MJ5] using Kies. The phone is completly stock and non-rooted. After the update, I'm unable to pull down notification bar. However, after I restart the device, it works well for some time and then again refuses to be pulled down.
Has anyone else experienced the same problem? I have lot of data on the device that will be difficult to restore and hence and donot want to format the phone. Any suggestions/solutions that might resolve the problem?
Also, after the 4.3 update, when I check for OTA, a popup shows saying "Your device has been modified. Software updates are not available." Pulling out and reinserting SD card didn't solve the issue.
Click to expand...
Click to collapse
I am going mentally insane trying to figure this out. I have refreshed and wiped my phone 5 times for the same issue, but to nothing good. The notification bar simply wouldn't want to respond.
What's getting to my nerves is that in one of my experiments with solving this issue, I kept my phone as stock with no third party apps, and still faced the issue. I kept knox uninstalled thinking that's what is causing the issue, but that's didn't help. I did lots of these kind of attempts, but to no avail. I'm concluding that is a serious Bug that Samsung is not going to address to soon. And we're simply screwed until.
Same problem.. DEAL BREAKER
I am facing the same problem after update to 4.3 Andrew this is a deal breaker if Samsung does not fix immediately. Thinking of rooting Andrew moving to cyanogen mod beta.. This is crazy. Nobody tested this for sure.
4.3 official update notification panel drop down problem
I have same problem with this update.can anybody solve this problem ?
kish0007 said:
I am going mentally insane trying to figure this out. I have refreshed and wiped my phone 5 times for the same issue, but to nothing good. The notification bar simply wouldn't want to respond.
What's getting to my nerves is that in one of my experiments with solving this issue, I kept my phone as stock with no third party apps, and still faced the issue. I kept knox uninstalled thinking that's what is causing the issue, but that's didn't help. I did lots of these kind of attempts, but to no avail. I'm concluding that is a serious Bug that Samsung is not going to address to soon. And we're simply screwed until.
Click to expand...
Click to collapse
Is your device status showing as "CUSTOM" or "ORIGINAL"?
figured out temporary solution
After a lot of playing around, I seem to know what's causing the problem. It's the Phone (Dialer) application that is creating an issue.
when the problem arises again, try making a call, and while the call is being placed, pull down the notification bar....It begins working.
obv I Ousby this is no permanent solution, but will help you from needing to restart.
If anyone with deeper knowledge can PLEASE look at what from the inside is causing it, and how can we make a permanent fix, much appreciated.
let me know if it works for you, the temp fix.
---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------
[/QUOTE=arpit88;46809031]Is your device status showing as "CUSTOM" or "ORIGINAL"?[/QUOTE]
Mine says official, for you, I'd suggesting finding the correct 4.3 version with the correct region for your i9500 / i9505, and redo the firmware. Download the firmware off Sammobile, and use Odin 1.85 whilst your phone is in download mode. If you don't know any of these terms used, Google it. It'll be helpful.
Basically, the notification bar problem and device modified problem are separate issues.
Did u install the indian firmware or the unknown one?
yes boys same issue here after 4.3 installed
also my notification bar when its stacked works when you try it on a call but its a temporary solution. mine is official also. anybody find a permanent solution? should we again root 4.3 on 4.3? I think it must be that the 4.3 was installed over 4.2.2 maybe if we make hard reset it will be fixed?
It's the Indian firmware, that I downloaded using Kies but still it started showing as "custom".
I took the phone to samsung care, they said Official 4.3 isn't released for s4 in India yet. Lolz. However, then one of there geeky employees reinstalled the 4.3 update and now my both issues have been fixed. Notification bar is now working perfectly fine and Device status is now Official.
official 4.3 also problem task bar
mine is official because in germany 4.3 is released on samsungs update and my phone is from germany. sould I take it to samsung service and they reinstalling again 4.3 is finally fixed?
xxuemj8
I got an ota update xxuemj8 just now that seemingly has solved the problem. My test so far hasn't given complaints, but.let's see what's the situation in long term.
Indian version i9500 currently updated from xxuemj5 to xxuemj8
Should solve all your problems too if you refresh your phone with Odin. Meaning reinstall from fresh by downloading from sammobile and.installing.through Odin
UPDATE XXUEMJ8 doesnt help
Update: XXUEMJ8 doesnt solve any problem. The bug still exists, notification bar stops working.
Also, another issue is that under Settings > Battery, even if Wi-Fi is switched off, the wifi blue bar shows full all the time as if it were ON.
This confuses me to if this is only a software bug in displaying the battery status of settings where wifi is truly off, and it thinks it is on.
OR
Wifi remains on throughout, and switching it off in the software doesnt actually switch it off, eventually taking more battery.
kish0007 said:
I got an ota update xxuemj8 just now that seemingly has solved the problem. My test so far hasn't given complaints, but.let's see what's the situation in long term.
Indian version i9500 currently updated from xxuemj5 to xxuemj8
Should solve all your problems too if you refresh your phone with Odin. Meaning reinstall from fresh by downloading from sammobile and.installing.through Odin
Click to expand...
Click to collapse
Android 4.3 Update
I DEFINITELY AGREE with the earlier post by Kish0007. The bug is related to the PHONE (Dialer) App. The problem always occurs after receiving a phone call.
I changed from German Android 4.3 to Unknown Android 4.3 as posted on Sammobile hoping for the problem to disappear. But it did not !
Mich
The possible solution is to format your phone after installing 4.3 upgrade.
Goto Hard reset by pressing your Volume Key+Power key+Home Key......
Then goto Wipe data/Factory reset.........Don't worry your android Upgrade will not be reset, it will be as it is (4.3)....just it will format your data
and cache.
Do not forget to take backup of apps and your other data......!!
It worked for me & hope it will work for you as well........!!
I try format several times but problem still exist
update the firmware before format.
After upgrading your OS , please update the firmware from PDA:MJ5 to PDA:MJ8 also,
then try formatting.
Same problem after updating on my Samsung S4
Same problem after updating on my Samsung S4.
I have the Middle east version UAE. MJ5 build number currently.
i noticed the dialor was started this issue.
i hope there is a solution for this soon.
still issue after hard reset
Sid0406 said:
The possible solution is to format your phone after installing 4.3 upgrade.
Goto Hard reset by pressing your Volume Key+Power key+Home Key......
Then goto Wipe data/Factory reset.........Don't worry your android Upgrade will not be reset, it will be as it is (4.3)....just it will format your data
and cache.
Do not forget to take backup of apps and your other data......!!
It worked for me & hope it will work for you as well........!!
Click to expand...
Click to collapse
I made hard reset on my phone and tha issue still exists. from samsung service they told me its possible the viber on 4.3 that makes the problem so I unistall it I made hard reset but I still have stacked tool bar sometimes after receiving or making calls but no so often.
notification bar problem
I updated my s4 i9500 to 4.3 indian ver. INU mj5 via kies and recently MJ8.. and same problem happening to me... notification bar would not pull down on call ends... calling again fixes the problem but thats kind of annoying every time for fix..... even transition animation scale resets on opening camera app.... then I thought to give a clean install via odin on same firmware from sammobile... ie. INU MJ8 21 oct build.... but this even did not solve the above problems. .. I also uninstalled viber thinking it might be the cause.... factory reset... cache wipe ... everything but to no avail.... any permanent fix would be appreciated. ...
Phone Settings
Guys,
Do you have the phone setting answer call using the power button selected ? Please, let me know. My notification bar never crashed today after I un-selected this option.
Thanks,
Mich
EDIT: Here's a verbose log that was being recorded before the device rebooted as explained below. It happened 2 seconds after I locked the screen with the lock key...
http://www.fast-files.com/getfile.aspx?file=74248
I know it's a big file, and it's long but it does open in regular Notepad, just wait 40 seconds. Hopefully you can find the cause at the bottom of the log. I can't make sense of it.
---------------------------------------------------------------------------------------------------------------
Hey guys, any idea how to find out why my S4 seems to be rebooting every few hours, mostly after being woken up?
Some tech info:
Baseband: I9505XXUGNE5
Stock Kernel
SE For Android: Enforcing
Build Number: KOT49H.I9505XXUGNE5
Phone is rooted & Xposed installed
Quick bit of info:
It seems to happen 90% of the time when the screen goes off. By this I mean, the screen can go off no problem and then I can turn it back on without an issue. However if the phone does reboot, it seems to be when the phone is woken up after being locked/asleep. However it does happen sometimes whilst I am using the phone. Though very rarely.
It's also important to note that the phone does a 'fast reboot', not a regular one. Like it skips the 'Samsung Galaxy S4' screen and just goes straight to the spinning logo. It does reboot very fast, but it is really annoying.
However I don't have to put my SIM PIn in again, it just asks for my phone PIN and then starts to load apps as normally.
Is there some sort of App I can install that will log all errors right up to the point where it crashes. Then I could view the log and work out what caused the crash? I have the Donate of aLogcat but it doesn't seem to allow me to do this...
Any ideas guys? Any info would be absolutely awesome.
I really don't mean to bump guys but I've flashed 3 times now and still get reboots...
Could I need to flash a new boatloader or something?
The download is to slow. Just post your log in pastebin and post the link here.
What I would do in your case is to fully wipe (also wipe your sd card) and return to a clean rom. Don't install any apps, dont restore backups and see if the problem persists.
If even with a fress install you have to issues, then it's a hardware issue.
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I updated the post HERE if somebody is interested. More KNOX remains to freeze or delete
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I would suggest performing a factory reset before freezing the Knox stuff. That way you have a clean start.
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
wild wadi said:
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
Click to expand...
Click to collapse
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Lennyz1988 said:
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Click to expand...
Click to collapse
Chainfire asked in another post people who are experiencing these reboots to list their installed root apps which I sent to him.
http://forum.xda-developers.com/showthread.php?t=1538053&highlight=random+reboot&page=551
Maybe it is SdFix. I will check that out but, I would like to know if others who are experiencing reboots here have SdFix installed or maybe to list their installed root apps (like Chainfire suggested) so we can compare notes as to who is and who is not experiencing random reboots.
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Hi Mate,
Not saying this is your problem but i seen some people having issues with the power button , symptoms are similar to your random reboots like in constant reset....check the power button see if is stock and easy way to check is try to go to recovery without pressing the power button.....if is really stuck or short out you should be able to go to recovery without ( for a short time) ....that will prove that the problem is coming from there...
Of course if is very sporadic wait until is happening for testing ..
I had the same problem before because I disabled knox using supersu. What I did was delete all knox related apps and everything is good.
Many users had this problems with Knox as well. Try to uninstall everything relating to Knox, maybe it will work
Gesendet von meinem GT-I9505 mit Tapatalk
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Delete all knox related apps via "titanum backup" and you are good to go! :good:
martikip said:
Delete all knox related apps via "titanum backup" and you are good to go! :good:
Click to expand...
Click to collapse
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
pimpl said:
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
Click to expand...
Click to collapse
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
Indeed, I have never had a problem again, since I deleted the Knox-stuff. Just do it and the problem will be solved!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
It's right uninstall Knox and be happy
Gesendet von meinem GT-I9505 mit Tapatalk
I have the same issue at the moment - Phone is completely standard (Not rooted). All has been good until the morning of the 30th August when there was a new firmware update applied. I had already had the Kit Kat update earlier in August and the phone had been working with no issue, since this 220Mb odd 'patch' the phone will just randomly reboot, I say random but it just seems after it has been idle (Screen off) for a while on unlocking I can start an app (pretty much anything) and about 5 seconds later the phone will reboot. As the OP mentioned it is a faster than normal reboot and it doesn't play the normal start up sound either.
I am not sure what the update did, it mentioned ironically that it was fixing stability issues!!! - Is there a way without rooting the phone to roll back the firmware to before the patch?
Cheers.
Factory reset worked too
I have been struggling with a similar problem on my GT-I9505 since receiving a system update on May 30, 2014 -- random reboots many times a day, plus fairly reliable reboots about 30-40 seconds into any received phone call. I tried cleaning caches, uninstalling recently installed apps and then other unneeded apps, installing new updates, and lots of other things. My last resort was rooting and removing Knox as suggested here. But first I tried a factory reset, and it worked! I've now gone several days without an unintentional reboot. It's a pain to have to restore backups and reinstall apps, but it was worth it. I hope this information is helpful to someone.
Issues on my CF auto-rooted GT i9505
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Idebutterpiep said:
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Click to expand...
Click to collapse
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
No do I have to?
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
I guess this will help. Knox often causes this issues. Just uninstall everything relating to Knox with Titanium Backup
Sent from my Galaxy S4 using Tapatalk
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
c0dewana said:
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
Click to expand...
Click to collapse
I think I solved my problem: I deleted all Knox related items and when I rebooted my phone again it stucks on the Samsung logo. I installed the stock I9505XXUGNG8-DBT again with Odin. Installed CF Auto-root.and Phill''s CWM again. Installed Supersu again.
Now everything is working again without the frozen screen, time synchronizes and no booting by incoming phone call anymore.
So this just started yesterday but whenever I plug in a usb to my phone weather it'd be for charging or PC it starts playing this stock sounding ringtone that I've never heard before and it doesn't stop! The only way to stop is to unplug and reboot (rebooting while plugged in doesn't do anything). Why is this happening? It just started yesterday out of the blue and I'm forced to keep my phone on mute. How do I solve this? I'm pretty sure I haven't downloaded anything or tinkered with it at all so there shouldn't be anything that changed since say 3 days ago. So what in the world is doing this!? Also I am on GOLDENEYE ROM and I feel like it's giving me lots of issues as of late so if anyone could recommend a better TW-based rom (cuz of stupid gear) for my Canadian S4 (I337m) that'd be greatly appreciated as well so I can just ditch this broken ROM and get a brand new set up going
I-TensE-I said:
So this just started yesterday but whenever I plug in a usb to my phone weather it'd be for charging or PC it starts playing this stock sounding ringtone that I've never heard before and it doesn't stop! The only way to stop is to unplug and reboot (rebooting while plugged in doesn't do anything). Why is this happening? It just started yesterday out of the blue and I'm forced to keep my phone on mute. How do I solve this? I'm pretty sure I haven't downloaded anything or tinkered with it at all so there shouldn't be anything that changed since say 3 days ago. So what in the world is doing this!? Also I am on GOLDENEYE ROM and I feel like it's giving me lots of issues as of late so if anyone could recommend a better TW-based rom (cuz of stupid gear) for my Canadian S4 (I337m) that'd be greatly appreciated as well so I can just ditch this broken ROM and get a brand new set up going
Click to expand...
Click to collapse
Soory but i think you have to perform a Full Wipe. Install new Rom and test it.
Same thing happened to me. I have s rooted S4 but no custom rom installed. I plugged my phone into my PC and the ring tone called Over the horizon started playing and a couldn't stop it unless I rebooted my phone. I then plugged it into just a wall charger and the same thing happened again. I'm running 4.4.2 build number is i337UCUFNB1. I rooted my phone with towelroot a few months back and had no problems until today.
Ghost44 said:
Soory but i think you have to perform a Full Wipe. Install new Rom and test it.
Click to expand...
Click to collapse
Yah that's why I'm leaning towards getting a new ROM however full wipe doesn't solve the issue of why it is happening and how to fix it (other than full wipe)
I-TensE-I said:
Yah that's why I'm leaning towards getting a new ROM however full wipe doesn't solve the issue of why it is happening and how to fix it (other than full wipe)
Click to expand...
Click to collapse
have you tried to install a stock ROM ?
Ghost44 said:
have you tried to install a stock ROM ?
Click to expand...
Click to collapse
What would that do? I haven't ran a stock rom since day 2 I had my s4. The problem is with the rom I currently have which is (GOLDENEYE) and it's playing Over the horizon every time I plug in a usb. I want to fix that. Not go to stock
I-TensE-I said:
What would that do? I haven't ran a stock rom since day 2 I had my s4. The problem is with the rom I currently have which is (GOLDENEYE) and it's playing Over the horizon every time I plug in a usb. I want to fix that. Not go to stock
Click to expand...
Click to collapse
Yes i know but your device have any errors. That means you must to perform a wipe data factory reset and install the newest Stock ROM XXUGNG8. After that i'm sure your Problem is solved.
If your Problem is solved after this steps you can reinstall any Custom ROM you want
I-TensE-I said:
So this just started yesterday but whenever I plug in a usb to my phone weather it'd be for charging or PC it starts playing this stock sounding ringtone that I've never heard before and it doesn't stop! The only way to stop is to unplug and reboot (rebooting while plugged in doesn't do anything). Why is this happening? It just started yesterday out of the blue and I'm forced to keep my phone on mute. How do I solve this? I'm pretty sure I haven't downloaded anything or tinkered with it at all so there shouldn't be anything that changed since say 3 days ago. So what in the world is doing this!? Also I am on GOLDENEYE ROM and I feel like it's giving me lots of issues as of late so if anyone could recommend a better TW-based rom (cuz of stupid gear) for my Canadian S4 (I337m) that'd be greatly appreciated as well so I can just ditch this broken ROM and get a brand new set up going
Click to expand...
Click to collapse
fallen33 said:
Same thing happened to me. I have s rooted S4 but no custom rom installed. I plugged my phone into my PC and the ring tone called Over the horizon started playing and a couldn't stop it unless I rebooted my phone. I then plugged it into just a wall charger and the same thing happened again. I'm running 4.4.2 build number is i337UCUFNB1. I rooted my phone with towelroot a few months back and had no problems until today.
Click to expand...
Click to collapse
Do you use Gravity Box?
The update to version 3.3.2 caused this kind of issue. In this case just do the update to 3.3.3 there the bug is fixed
Send from my Galaxy S4 using Tapatalk
DarkerTimes said:
Do you use Gravity Box?
The update to version 3.3.2 caused this kind of issue. In this case just do the update to 3.3.3 there the bug is fixed
Send from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
Yes I have Gravity Box and I did update to the newest. I did a couple of things including updating to 3.3.3 so that must of have been it because it worked. Thanks.
I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk
Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?
Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.
Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk
mine did it too. had to reinstall the whole thing.
drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.
There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.