I337MVLUFNC1 Rogers unlocked bootloader wifi stuck turning on - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

okay, this is what i lerned.
1) stuck wifi issues (random stick wifi on) starts to happen after cf auto root is installed
2) once you have a knox bootloader, you can downgrade bootloader but only up to the least recent big release ie) NE1 can be downdraded to NC1 but you cannot downgrade to 4.2 or 4.2, odin throughs an auth fail error. so because i bought a gs4 with NC1 im stuck with NC1
3) NC1 is very picky with custom roms and kernel. I have been runnining GETW Danvdh for a day now and no more stuck wifi. yet after initial flash, i did have issues enabling wifi. Seems that on the NC1 the rom and kernel need a day to settle before the wifi issue goes away? odd? i think the knox bootloader is interfering with the wifi driver load at boot. when it does not work, pulling the battery, booting into bootloader then switching off, toggling airplane mode and installing a different recovery are all things you should try when it acts up. when it fails its not always the same solution to fix.
4) re-flashing to stock will fix the issue but once you re-root stock with chainfire, issue comes back.
5) when wifi fails to start, flashing another custom rom does not fix wifi, wifi stick persists among different custom roms but reverting to stock via oden fixes wifi.

I've been having a stuck with problem myself when rooted and stock. Currently on stock when the wifi gets "stuck", I find if I turn on the wifi and bluetooth at the same time the wifi will eventually connect. Weird I know.
I need to warranty my phone before the first year runs out.
Sent from my SGH-I337M using Tapatalk

saj222 said:
I've been having a stuck with problem myself when rooted and stock. Currently on stock when the wifi gets "stuck", I find if I turn on the wifi and bluetooth at the same time the wifi will eventually connect. Weird I know.
I need to warranty my phone before the first year runs out.
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Same bootloader as me? Do you really think it's hardware related?

cantenna said:
Same bootloader as me? Do you really think it's hardware related?
Click to expand...
Click to collapse
My bootloader is NE1. Now that I think about it the stuck wifi hasn't happened since I've been on NE1 which hasn't been that long.
The stuck wifi definitely was quite prevalent this past Fall. I think this was 3 bootloaders ago.
As for hardware, I don't know to be completely honest. I do have another motivation for submitting a warranty claim - my phone's CPU sucks with custom kernels. It really likes stock. My hope is that the tech might just replace the whole printed circuit board assembly and I'd get a new CPU b/c believe me it's almost always cheaper to replace the assembly then to go poking around and lifting legs / desolding things and spend time doing it.

..........

.........

.........

..........

............

cantenna said:
Okay, back on google experiance by Danvdh, added the line above to build.prop and for now it seems to be working. :fingers-crossed:
So I guess people who say knox no big deal, have random wifi stucks periodically? I don't have this problem on MDJ bootloader
Click to expand...
Click to collapse
I have been having the same problem - wifi takes almost forever to connect, lock screen doesnt work, some widgets dont load until a "certain" event happens on the phone and then everything works perfectly. I have a SGH-i337 and I see the problem when running i9505 roms.
What works for me is to open recent apps and remove everything and then wifi will connect immediately. I am not sure if it will work for you but you could try.

...........

........

......

Related

Wifi issue on Galaxy S4 I9505

Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
AndroidLEK said:
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
Click to expand...
Click to collapse
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
PSPNikos said:
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
Click to expand...
Click to collapse
When I first downgraded back down to the MEA firmware that I was linked to from another forum, I discovered straight after flashing that it was a pre-rooted ROM and the wifi still would not turn on then.
The phone has been sent back to Samsung again today for another repair but last night as a last ditched attempt, I downloaded & flashed the stock XXUAMDM firmware from April and the wifi still refused to turn on.
I'm still convinced that the problem itself is hardware related rather than software based going by that the problem is still present regardless of what ROM I'm on, it's just a case of trying to get Samsung to see that. I can understand now why that Samsung the first time round probably only did a fresh re-flash of the MGA firmware instead of going ahead and taking the phone apart/replacing parts as I imagine it's very labour intensive/standard procedure and not only that - the S4's mainboard (from what I've seen the wifi module is part of the mainboard) retails at over £200 which is a hefty repair cost on their part.
Liam
It is some sort of permissions issue.
If you do chmod 777 on /dev/*, /system/etc/wifi/* it should be working.
The only thing I haven't figured out is why
And it has to be done again after rebooting the phone, wich makes me sad.....
How I fixed my WiFi and sound problems after updating to latest firmware over
Hi there. (Sorry for any mistake about my English). By the way, I'm newbie on Android.
After freaking out about my WiFi problem, i didn't even care about the others problems like the sound, and I don't know if there were or if there is still some, but WiFi and sound got fixed.
After a lot of research on Google and XDA I came to the conclusion that if I could just re-install the firmware, I had
1- I Download the same firmware you are on (i guess it safer this way) I got the same (I9505VJUEMKE) that had caused the problem when was update trough Kies.
GT-I9505_PDA_I9505VJUEMKE_4.3
Changelist: 2210919
Build date: Wed, 27 Nov 2013
CSC: I9505ZTOEMKE_ZTO_Brazil
MODEM: I9505VJUEMKE
Gdrive: (créditos ao +Alexandre Affonso - Vlw)
Two links for download this firmware. (really fast download since its on gdrive)
goo.gl / UrZWAE .
goo.gl / omJC9e  "
2- Unpack the Zip File
3- Putt the phone in "Download Mode"
4- Open Odin 3.07 and Connected the cable. (check if Odin linked a port to your phone, i didnt get any color change, just the COM Port number and the "added" mentioned on Odin)
5- Load the firmware on "PDA", wait a few seconds till Odin load it.
6- Click Start and wait the whole process. Don't disconnect the cable until Odin says that it was Successfully.
Finished!
After all I did the root with Odin + CF Auto Root + Supersu and So far everything is fine and better than before.
Hope I can help few of you guys.
Thanks.

[Q] 3g/4g connectivity issues

Hello guys,
For the last month i have been fighting with connectivity issues on my SG4 i9505.
It starts out with just losing the connection and then getting it back, gradually over time it gets alot worse, so that it then requires using airplane mode and back to normal. along with *#*#4643#*#* disabling radio and enabling it again.
The next step is rebooting, but this does not always help, i often need to suppliment this with a cache format, which in new android versions is a real pain, exp with kitkat due to ART with it compiling. Anyway this is fare from the correct solution to do this multiple times a day.
I have also tried factory wipe, etc without luck, its the same as wiping cache with the side effect of losing my settings.
I tried getting a new simcard from a completely different carrier, this has not helped a bit, i also tried disabling 4g so that it only uses 3g (my carrier does not have 2g connectivity and on my previous carrier using 2g only did not help anything.
i started out with the XXUAME2 baseband, and i am now at XXUEMK9 and it has not helped to upgrade it.
I have been unreliable for over a month, phone calls drop, i can't reply to sms's without rebooting/wiping cache etc, asking around in diff irc channels without luck.
Does anyone have suggestions/solutions to this problem ? I really like to get my phone back up and working.
djgalning said:
Hello guys,
For the last month i have been fighting with connectivity issues on my SG4 i9505.
It starts out with just losing the connection and then getting it back, gradually over time it gets alot worse, so that it then requires using airplane mode and back to normal. along with *#*#4643#*#* disabling radio and enabling it again.
The next step is rebooting, but this does not always help, i often need to suppliment this with a cache format, which in new android versions is a real pain, exp with kitkat due to ART with it compiling. Anyway this is fare from the correct solution to do this multiple times a day.
I have also tried factory wipe, etc without luck, its the same as wiping cache with the side effect of losing my settings.
I tried getting a new simcard from a completely different carrier, this has not helped a bit, i also tried disabling 4g so that it only uses 3g (my carrier does not have 2g connectivity and on my previous carrier using 2g only did not help anything.
i started out with the XXUAME2 baseband, and i am now at XXUEMK9 and it has not helped to upgrade it.
I have been unreliable for over a month, phone calls drop, i can't reply to sms's without rebooting/wiping cache etc, asking around in diff irc channels without luck.
Does anyone have suggestions/solutions to this problem ? I really like to get my phone back up and working.
Click to expand...
Click to collapse
This sound u haven't correct Firmware installed. Where are u from? Ur phone is branded or unlocked? Go to Apps - Setting - More - About device and make us a beaty screenshot
Joku1981 said:
This sound u haven't correct Firmware installed. Where are u from? Ur phone is branded or unlocked? Go to Apps - Setting - More - About device and make us a beaty screenshot
Click to expand...
Click to collapse
CM11 apparently does not have screenshot support yet, so i'll just manually write it in.(i am running latest nightly)
model number: GT-I9505
baseband version: I9505XXUEMK9
I am from Denmark, so the phone is unlocked.
I started out with Telenor, then Bibob and now Oister as carrier all 3 have had the same issues.
My phone came stocked with XXUAME2 so i am using the correct firmware according to varrious threads around.
djgalning said:
CM11 apparently does not have screenshot support yet, so i'll just manually write it in.(i am running latest nightly)
model number: GT-I9505
baseband version: I9505XXUEMK9
I am from Denmark, so the phone is unlocked.
I started out with Telenor, then Bibob and now Oister as carrier all 3 have had the same issues.
My phone came stocked with XXUAME2 so i am using the correct firmware according to varrious threads around.
Click to expand...
Click to collapse
1. Use Odin v3.09
2. Untick Autoreboot
3. Flash modem: HERE
4. Reboot manually into Download Mode using (Vol Down plus Home button combi)
5. Flash Modem once more
6. Once done,unplug then reboot device manually.
7. If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
* If u have problems with wifi -> Try WIFI FIX too:HERE
Use it with care!!!
Open in Odin as PHONE or CP!!
djgalning said:
Hello guys,
For the last month i have been fighting with connectivity issues on my SG4 i9505.
It starts out with just losing the connection and then getting it back, gradually over time it gets alot worse, so that it then requires using airplane mode and back to normal. along with *#*#4643#*#* disabling radio and enabling it again.
The next step is rebooting, but this does not always help, i often need to suppliment this with a cache format, which in new android versions is a real pain, exp with kitkat due to ART with it compiling. Anyway this is fare from the correct solution to do this multiple times a day.
I have also tried factory wipe, etc without luck, its the same as wiping cache with the side effect of losing my settings.
I tried getting a new simcard from a completely different carrier, this has not helped a bit, i also tried disabling 4g so that it only uses 3g (my carrier does not have 2g connectivity and on my previous carrier using 2g only did not help anything.
i started out with the XXUAME2 baseband, and i am now at XXUEMK9 and it has not helped to upgrade it.
I have been unreliable for over a month, phone calls drop, i can't reply to sms's without rebooting/wiping cache etc, asking around in diff irc channels without luck.
Does anyone have suggestions/solutions to this problem ? I really like to get my phone back up and working.
Click to expand...
Click to collapse
Hi,
I believe you have flashed a wrong baseband, try to downgrade it. I had a similar problem with mine some time ago, I was with bad signal due to an outdated baseband, then when I flashed a new one, it wasn't compatible with my bootloader... So, try checking this thread to get one better for you: http://forum.xda-developers.com/showthread.php?t=2192025.
I got my luck with the MJ5 baseband, I'm with the old bootloader too (UB).
Hope this helps,
~Lord
Hi guys, sorry for the slow reply, i had to be sure before saying if it was working or not working.
I downloaded the original rom/baseband from sammobile and tried it out, this turned out to be alot worse, due to i am unable to clear dalvik cache with the recovery clear cache.
also due to the lack of *#'*#4636#*#* it made the experiance alot worse.
the baseband i am now using is XXUEMKF with KNOX (so i am now knox 0x1)
I'm currently trying out the google edition, but looks like the issue remains.
funny thing is i do remember it working in the past with some old AOSP/AOKP version.
i'm completely lost, expecially due to its so random.
It gets to the point where i am unable to search for networks, and other times there is no issues.
Update:
Ok i've noticed something very strange, its some how tied into the wifi, when i disable wifi i lose my 3g/4g connection and when i enable it again the connection returnes quite fast. though the connection at points, can get lost again.
djgalning said:
Update:
Ok i've noticed something very strange, its some how tied into the wifi, when i disable wifi i lose my 3g/4g connection and when i enable it again the connection returnes quite fast. though the connection at points, can get lost again.
Click to expand...
Click to collapse
What Odin version are you using? Do you have installed kies 3 in your PC? If don't, install it to update the drivers and flash that 4.3 Rom you downloaded from sammobile again with Odin 3.09.
Fyi, once you had installed a4.3 knox rom, you are not able to return to a 4.2.2 stock Rom.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
What Odin version are you using? Do you have installed kies 3 in your PC? If don't, install it to update the drivers and flash that 4.3 Rom you downloaded from sammobile again with Odin 3.09.
Fyi, once you had installed a4.3 knox rom, you are not able to return to a 4.2.2 stock Rom.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I am using odin 3.09 and kies 3 is installed, its been flashed many times
I've tried multiple reflashings, in fact every day last week was 2-5 flashes a day. I install my apps again and set them up each time, takes quite a long time, just to remove it again later on, got any suggestions to saving my apps and settings along with wifi ? (google restore does not work with all roms and is not always effective).
Googling my issue returns quite a few results with people that have simular issues but no solutions.
djgalning said:
I am using odin 3.09 and kies 3 is installed, its been flashed many times
I've tried multiple reflashings, in fact every day last week was 2-5 flashes a day. I install my apps again and set them up each time, takes quite a long time, just to remove it again later on, got any suggestions to saving my apps and settings along with wifi ? (google restore does not work with all roms and is not always effective).
Googling my issue returns quite a few results with people that have simular issues but no solutions.
Click to expand...
Click to collapse
Sorry, but I only left to think you have a hardware problem...
You can make easy backups for selected user apps with System Tuner, and if you are root also system apps.
Good luck.
Enviado desde mi GT-I9500 usando Tapatalk 2

[Q] Phone rebooting randomly - help needed

Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:

[Q] I seem to have killed my WiFi - any suggestions would be appreciated

Hi there. Very sorry to post about this - I've tried my best to solve the issue on my own and doing various searches, here and elsewhere, but to no avail. Long and short of it is that WiFi and Bluetooth both seem to have died on me.
I have a Canadian Bell Samsung Galaxy S4 (SGH-I337M). I have been installing Danvdh's Google Edition ROM for some time now, and so far, it's been great. After installing 4.4.4 (clean, after a full wipe), it seemed to work, but my phone froze up - completely unresponsive, including the power switch. Pulled the battery but then afterwards could not turn on WiFi or BT - just says "Turning Wifi On" but nothing ever happens - the message just stays there perpetually. Bluetooth same thing, except the message goes away after a few seconds.
I've tried all of the following to try to restore WiFi, none of which has worked:
- Odin reflash of modem.bin and NON-HLOS.bin, multiple times (from the most recent stock ROM for my device - I337MVLUFNE1, 4.4.2)
- Complete reversion to stock (I337MVLUFNE1, 4.4.2) using Odin - neither WiFi nor BT worked under stock either
- Factory reset while in stock
- After rooting stock, using an SQL editor to check the value of wifi_display_on - it was 0 but just to make sure I set it to 0 again
- After rooting stock, deleting wpa_supplicant.conf in both /data/misc/wifi/ and /etc/wifi/
- Reinstalling Danvdh 4.4.4 (clean), but this time with the Googy kernel rather than the KT kernel (in both cases it was the customized version, not the pure Nexus one)
- Also tried, just for the heck of it, switching to ART to see if that might make a difference - it didn't
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Please note - I originally posted this in the thread for Danvdh's ROM. I didn't get any feedback there, so suspect I perhaps might be posting the question in the wrong place, so am trying here, in addition to the thread for Canadian S4s. I trust such cross-posting is OK (but if not please let me know).
not_su said:
Hi there. .....
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
To be honest, I have no idea if that could be related... on one of my I9300, directly after OTA, I lost the WiFi and BT. Problem was WiFi or/and BT, when I pressed to switch it on, was turning on, for maybe 0.5 sec, and then was turning itself off.
now the funny story: because I unrooted it and cleaned prior to OTA, it was immaculate, so I took it to Sammys hiTech local specialists.
They two times were returning phone to me, stating that they are unable to repeat the problem. So, I asked them to not send it back, and that I'll pick it from Service Centre. I used that opportunity, and asked another local master to show me how to use the WiFi on my 100% working phone. He itself packed it into same envelope and disappeard for half a time, after that itme I was informed that my phone will be sent to me after motherboard replacement.
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.
spamtrash said:
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.
Click to expand...
Click to collapse
Thanks very much - appreciate the suggestion, but the warranty on my phone ended last month, so I'd get hit for a bill for the repair.
You raise a good point - it may well be a simple hardware failure that happened, coincidentally, when I updated. Alas, I wouldn't know where to begin to try to figure out whether or not it is a hardware failure...
I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)
Tsuushin said:
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Click to expand...
Click to collapse
here....
Tsuushin said:
I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)
Click to expand...
Click to collapse
I don't remember where I got mine but it was extracted from the latest stock rom. Googling the build led me to this page, which seems to have links to download the most recent stock for the S4.
Not sure about your other question. I know when I update a new custom rom, the baseband version doesn't change - that only changes when I update the modem or flash an updated stock rom using Odin. You might also want to try flashing the NON-HLOS.bin file - I read elsewhere that that has helped others. Of course, feel free to also try all the other options I've noted above.
In case it helps other people with the same problem, here's what I did that fixed the WiFi issue:
I flashed the latest modem.bin (twice) and NON-HLOS.bin, but it didn't fix the WiFi.
I flashed the latest stock ROM, and now WiFi works.
Cheers.

[Q] NAE started loosing mobile connection & GPS?

RELEVANT DATA: Sprint Samsung Galaxy S4, Software version: NAE, Android version: 4.4.2, Baseband version: NAE, Kernel: KT-SGS4 4.4, Recovery: PhilZ Touch 6.48.4, SuperSU. Stock Rooted. Upgraded to NAE from MF9 with the method in this link: [HOW TO]Update to 4.4.2 NAE w/Root while Keeping MF9 Bootloader w/ Lock Screen Fix, so no Knox.
Upgrade went great, it was actually the most stable phone I have ever had. Then, all of a sudden, I started loosing my mobile connection and GPS a while after booting the phone.If I reboot the phone, they start working fine again, but after an unknown amount of time, they both stop working again. WIFI never stops working. I have no idea what caused this to start happening and it REALLY SUCKS!
I did edit my APN, trying to fix an issue I was having with sending MMS's, but I'm pretty sure I restored the NAE stock version, which didn't help.
I have attach a logcat filtered at warn and higher and I tried to make a call during this logcat and was told I had no mobile connection. I really can't read these things, so I don't know if there is anything useful in there.
If anyone has any idea what might be causing my problem, I would be eternally grateful for some assistance!
I'm becoming convincinced that I must hold some sort of record on XDA for having the greatest number of issues that nobody else has ever experienced...
rsngfrce said:
I'm becoming convincinced that I must hold some sort of record on XDA for having the greatest number of issues that nobody else has ever experienced...
Click to expand...
Click to collapse
Sound odd. Sorry I can't help you directly.
I would suggest using Odin to flash NAE firmware only tar again.
I'm assuming you've updated PRL and Profile?
I think you need to go full NAE tar file to fix your problems. When you do partial upgrades like you did they result in nothing but problems. If you want your phone to work everytime you use it. Flash the full NAE tar to bring your phone up to date, root it with cf autoroot, install your mods and enjoy a trouble free phone. There is nothing to worry about knox. It doesn't hamper your phone at all. Your warranty is already expired if you have a phone that has MF9 on it so update your phone and you won't have any of these problems.
I appreciate both your suggestions and will consider them. What I don't understand though would be why it would be working perfectly for a month or two and then suddenly develop the issues out of the blue? Also, I haven't seen anyone else who upgraded with this method mentioning this problem. This tends to make me think the problem lies elsewhere... possibly related, but elsewhere.
(By the way, I raised the question of why I would care about Knox if I was out of warranty and it was pointed out that once you have Knox, you can never go back to MF9... and who knows if I might decide I need to do that for some reason... I prefer to have the option at least.)
I'll tell you what is really STRANGE... right now my phone has been 17 hours since boot and both the mobile data and GPS are working... I can't remember the last time it has gone that long! Maybe my random twiddling finally fixed it...
WELL... of course, I spoke too soon, the issue has now returned. I'm at 22 hours after boot, but I don't know when it started and I did reboot since I said it was working after 17 hours...:banghead:

Categories

Resources