Database Users

[Q] SGS4 WiFi/Bluetooth Death, ZERO working solutions, willing to pay.

Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.

Wexberg said:
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Click to expand...
Click to collapse
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?

DeadlySin9 said:
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
Click to expand...
Click to collapse
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.

Wexberg said:
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Click to expand...
Click to collapse
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.

DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
DeadlySin9 said:
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
Click to expand...
Click to collapse

Wexberg said:
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
Click to expand...
Click to collapse
I don't know why that would work. At this point I'm not sure what else you could do. I know I used to have WiFi issues after some flashes with my Inspire but i never really had a fix even then.

i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom

Been there, done that.
It's not a hardware problem. It is, I believe, problems with the restrictive 4.3 update not playing nicely with some system settings. In short your system drivers or configuration settings are getting messed up to to bugs in how Knox and the bootloader are interacting with the modem.
I had your exact symptoms after installing certain custom ROMs, also noted that the problem could be temporarily "fixed" if the boot process was interrupted or by specific sequences of modem changes. The situation is not helped by Bell being more restrictive than other Canadian carriers e.g. Rogers, something that also caused me problems when I was enabling AWS on a Bell firmware.
The effective solution was to install a custom recovery to facilitate a complete wipe of files, then flash a Rogers stock image. Cured. And continuing to work properly if subsequently returned to a Bell stock image. Although, frankly you'd have a more stable and flexible platform if you you kept the Rogers image in the end. If the build properties edit doesn't solve your issue, then here is a path for you to pursue.
.

1/2 Lit Toggles - build.prop editing issue
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?

jrwebdev17 said:
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
Click to expand...
Click to collapse
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop

DeadlySin9 said:
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
Click to expand...
Click to collapse
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.

Editing build.prop is a plausible workaround if the OP has root access. If he doesn't wish to root his phone, then he can clean up his system configuration by reinstalling as I described earlier in the thread without requiring root. Two approaches to the same result.
And yes, you can add the entry if it doesn't already exist in your configuration.
.

jrwebdev17 said:
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Click to expand...
Click to collapse
UPDATE: I didn't have any luck using the build.prop fix, nor with the wpa_supplicant.conf fix that some of you may have seen mentioned. I ended up Recovering to stock MF3, (I was already on MF3). This gave up my root access, and I didn't take any additional steps to hide busy_box or anything like that, after my MF3 recovery it looked like I was safely unrooted and I contacted AT&T support via web-chat, and they asked some questions and sent me to a nearby AT&T device center. I took it there, they didn't ask a single question about how it happened, whether I had rooted it, etc(although I was paranoid that there would be traces left behind and they would turn me away). Long story short, they replaced the phone no questions asked!
In my opinion it would seem that while this problem could in some cases be caused by rooting and tinkering, it's enough of a known issue to AT&T that they would replace it under warranty. Hopefully Bell or other carriers would do the same. My advice is to try your carrier, particularly if you are with AT&T.

Just to help people who are searching for a solution. I had flashed a T-Mobile rom and my wifi stopped being togglable on my AT&T S4. That is, I couldn't turn on wifi. The button would get stuck on. After trying to flash what I thought was the right MK2 modem and still having the same issue, I thought I was out of luck. However, I found this one here: http://forum.xda-developers.com/devdb/project/dl/?id=3275 and hit paydirt. Flashing it using Safestrap and then wiping cache and delvik worked. The file is called jflteatt-MK2-modules.zip.

Only for WIFI, for me what worked was I had to open a litte bit the one side of the phone and close it again (removing a little the plastic, like if you were going to open the device) Wifi started working again, no need to flash any roms, it seemed to be something related with pressure, humidity or something inside the phone.
Regarding bluetooh I had no luck still not working, only keeps saying activating and never gets activated.
does anyone find a solution for this yet?

I have had the same issue for months. Started after warranty was up. I have AT&T on nc1. I tried everything mentioned here but nothing worked. Even left it with the phone repair guys for a week with no luck. It first started after I flashed Hyperdrive ROM. A reboot helped for a while. It actually came back for a week on Kevp's ROM, but then had an error that reboot the phone and lost it again. Phone is now on Craigslist and I am back to my S2. On a high note it's nice to not have a unlocked bootloader again.

you need to flash the exact same model/firmware's modem file atleast thrice before giving up.... i have a simalar issue the thing is my model number is 1377z and google doesnt have a working flashable modem file for it so basically i am screwed too wifi calling and video recording doesnt work....
update :: saw that you got it replaced !!
smoooth .....

Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
Just tried this on my sgh-i337m that was having the same wifi issues after rooting and flashing a kernel. Rebooted and wifi is up and running. So far so good. Thanks a lot!

!!!Stop SAMSUNG GALAXY S3 FREEZING Problems!!!

Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.

Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom

kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:

Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...

what?
i havent got this

Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.

jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?

Read the freezing thread sticky .
Delete this non working fix as well .

JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?

Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.

Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.

[Q] HELP: my GT-I9505 is randomly turning off and on again

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.

I9505 random reboots

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:

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa

TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.

kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.

kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others

Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.

This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps