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!
Related
I am hoping someone here will have mercy on me with my newb dilemma and give it the time for an answer.
I am a recent Galaxy S4 user- only 3 days ago (after 6+ years of jailbreaking every iPhone they've made.) So I am admittedly a bit new to all of this...
My S4 is a on a Sprint carrier, L720...MDC
Day 1: I rooted it, successfully (using Odin and CF-Auto-Root-jfltespr-jfltespr-sphl720.tar)
Later that day I flashed it with TWRP with a Wifi-tether workaround I got from downloadandroidrom.com. Everything I used was quite specifically for my model phone, carrier, modexed, etc... Still, after flashing I ended up in a start-up loop. (would hang at the startup Samsung logo)
Day 2: Things became difficult at this point since I had no more internet access. I needed to go research this at a friends and downloaded the STOCK rom in order to recover. After flashing the Rom I was back in biz! Yay!
...Or so I thought- Seems NOW I have no option in my settings panel for Wifi tether "Hotspot" AT ALL. It is no longer there! How can this be? I have tried flashing to stock and re-rooting, etc a bunch of different things but I cannot get it back. It WAS there because I tried it day one, before rooting, just to see what it would do. It clearly had "Hotspot" with a toggle between the WiFi and Bluetooth toggles.
I tried every app I could find (FoxFi, Easy Tether, etc...) but the phone warns me that "Hotspot not supported"
Day 3: I asked around and browsed all the developer sites for info but could find no answers.
At the end of the day I tried CWM's "Tether" app. THIS WORKED!
So my questions:
ARE there any ROMs I can flash this particular phone with? I can't seem to find ANY that specifically mention my firmware etc... (except the stock)
IS that even important? Can I flash it with Wicked, for instance?
What would YOU try in order to gain a hotspot? (untethered)
Thanks for ANY help or advice you can offer!
Yes you can tether.
Yes you can tether with MDC.
Yes you can tether with just a rooted stock ROM.
Yes there are ROMs that have tethering built in.
First thing you might want to do is spend some time going through the stickies and how-tos. They are very helpful.
Then maybe getting your phone to the latest firmware - MF9 (there are a few stickies and posts about that).
I use crawrj's hotspot mod on my phone (MF9) without issue.
Maybe just try a rooted stock MF9 and then add the hotspot and then go from there.
On the stock ROM, the wifi tether hotspot option will show up only after you allow sprint customization to run. If you installed the stock ROM, and skipped the sprint customization, the wifi tether option won't show up.
Once you get the wifi tether option, you can go to http://forum.xda-developers.com/showthread.php?t=2256950 to download the appropriate version (MDC/MDL/MF9 - odexed/deodexed) to flash in custom recovery - that will give you the hotspot mod.
If you want to go to stock MF9 (latest version for the Sprint S4), go to http://forum.xda-developers.com/showthread.php?t=2277480
Thanks!
jj14 said:
On the stock ROM, the wifi tether hotspot option will show up only after you allow sprint customization to run. If you installed the stock ROM, and skipped the sprint customization, the wifi tether option won't show up.]
Click to expand...
Click to collapse
I may be asking this prematurely since I am going to read up more on this per your advice, but I am curious about how I was supposed to "allow the customization to run."
I used the Odin installer and it just went through a loading process, more-or-less on it's own. I have reloaded the stock ROM a few times now and I saw no prompts for anything, though I had the Auto-restart option checked so it just restarted and I went from there. Should I not have had the auto restart on? At what point do I allow this customization?
TIA
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
I'm having the same issue as OP, and like him, I don't exactly understand what everyone is saying by the "Sprint customization".. I've flashed multiple times but I never get any prompt from Sprint or anything, just the standard setup for my Google account.
I've tried searching all over about this, but there doesn't seem to be that much on this unfortunately...
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
Click to expand...
Click to collapse
Correct a mundo on that. DONT stop that.
I have no idea what the 'sprint custmization' thingy he's talking about. May just the 'updating applications' but I don't know.
If you clear the dalvik cache, which the updater script for the hotspot mod does, or do it manually, you will always see that 'updating applications...' that is the system building the dalvik.
leaderbuilder said:
Correct a mundo on that. DONT stop that.
I have no idea what the 'sprint custmization' thingy he's talking about. May just the 'updating applications' but I don't know.
If you clear the dalvik cache, which the updater script for the hotspot mod does, or do it manually, you will always see that 'updating applications...' that is the system building the dalvik.
Click to expand...
Click to collapse
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
From the few people who've had this same issue, it's what jj14 said about needing to let Sprint run their "customization", but I'm never being prompted by Sprint to let anything install on my phone after various resets, so I'm quite lost...
Such a frustrating roadblock, got the mod and everything, just literally can't "turn it on". Because, well... The button. Isn't there. :/
None of the standard apps i used on the GN2 work either.
chosenhobo said:
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
From the few people who've had this same issue, it's what jj14 said about needing to let Sprint run their "customization", but I'm never being prompted by Sprint to let anything install on my phone after various resets, so I'm quite lost...
Such a frustrating roadblock, got the mod and everything, just literally can't "turn it on". Because, well... The button. Isn't there. :/
None of the standard apps i used on the GN2 work either.
Click to expand...
Click to collapse
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
Click to expand...
Click to collapse
Much of that issue discussed in crawj's thread and in a few others.
Though I don't have hotspot in my dropdown/menu/status bar I DO have it in the System Settings>Connections>Hotspot.
All I have to do is turn it on and it works (and of course I can then adjust any settings.).
I did try some of the things suggested (like adjusting stuff in the dbase(s) tables) in the follow-up posts to get it to show in the drop down, but never got that. Again just a VERY minor thing for me. As long as I can actually USE the tether/hotspot I'm good.
pic
All right sport, don't know what else to tell. Have fun with that.
Sent from my SPH-L720 using XDA Premium 4 mobile app
octojofo said:
I may be asking this prematurely since I am going to read up more on this per your advice, but I am curious about how I was supposed to "allow the customization to run."
I used the Odin installer and it just went through a loading process, more-or-less on it's own. I have reloaded the stock ROM a few times now and I saw no prompts for anything, though I had the Auto-restart option checked so it just restarted and I went from there. Should I not have had the auto restart on? At what point do I allow this customization?
TIA
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
Click to expand...
Click to collapse
Sorry about the delay in responding - was out of town.
When you flash the stock ROM, after the reboot, the phone does one update from Sprint. I'm told that this is the one that loads Sprint's bloat (sprint zone, sprint ID etc), along with the activation, and it is during this update, that the hotspot feature is made available on the phone.
(and I'm not referring to the Updating applications" message - that is just the android OS rebuilding the cache.
On a related note, I found this link - http://forum.xda-developers.com/showthread.php?p=44779759 - you can try this out to see if this helps.
chosenhobo said:
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
Click to expand...
Click to collapse
I'm pretty sure that Sprint's customization process doesn't run on most custom ROMs - the hotspot feature should be built into the custom ROM directly - if it is missing, you may want to reach out the developer and ask for suggestions/workarounds.
Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?
Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it
I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?
Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:
I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.
Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards
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.
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Update!
I got the wifi to work, temporarily. Deleting or renaming the data/misc/wifi directory and rebooting allows me to connect to a wifi network. The problem is that it only lets me connect to that network. If I try to switch ssids or leave the area it will revert to wifi not turning on until I delete or rename the data/misc/wifi directory and reboot again. Not sure what else to try here.
Any help would be appreciated.
Now with logcats
Checked out adb logcat, errors:
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)Client SS library: connect: Connection refused
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)SS_ConnectToDmnSndCmnData error
Anyone with a fix? Got the same problem today. It's fixed after a restore but if I change the network, wifi turns greyed out.
rstoops said:
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Click to expand...
Click to collapse
Found the fix.
Use Root Explorer.
Delete the files below that are inside /data/misc/wifi/
wpa_supplicant (folder)
wpa_supplicant.bak.conf
wpa_supplicant.conf
Go to build.prop press menu and select Text Editor than find this line:
ro.securestorage.support=true
change it to:
ro.securestorage.support=false
Save. Reboot, wifi should be fine.
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