Database Users

I337MVLUFNC1 Rogers unlocked bootloader wifi stuck turning on

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.

...........

........

......

[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] Thought I fixed a bad flash, still having trouble

Sorry if this belongs in the stupid question thread, I just have no idea what went wrong, or why I'm still having problems. I've had my S4 for a while now, and it's been rooted pretty much the entire time. I wasn't aware of the auto update when I first got the phone, so before I had a chance to root it, I was updated from MLD to MK2. This wasn't a problem because SafeRoot had recently been released. I was never really concerned with voiding my warranty, and up until recently, never had. I later upgraded to NB1/NC1 to test out some of the KitKat ROMs.
I've flashed dozens of different ROMs, and several different recovery apps. The worst thing to come from my tinkering was the "Custom" logo on boot. Never tripped Knox, never soft-bricked, etc... Until recently.
I was browsing around the
[INDEX]All things AT&T MK2, NB1, and NC1 (including ROMs) thread and found a few ROMs I hadn't tried before. I don't remember specifically which ROM it was, but it definitely had an Aroma installer. During the installation there was a warning that my warranty would be void. Having been warned about voiding my warranty in virtually every ROM thread, I didn't really think much of it. I did my usual flashing of the ROM, flashed the NC1 modules, then SuperSU 2.0 just in case. I've performed the same steps numerous times. Unfortunately this time when I rebooted, everything went haywire.
I got the unauthorized software message, Knox had been tripped, and I'm pretty sure I had the yellow triangle, along with everything else that comes with a semi-brick.
I don't remember all of the details because it's been a couple of weeks now, but I used Odin to get back to NB1 stock, and since then I've had trouble with sending/receiving texts, and sometimes calls. It's really strange because there is no indication that it's stopped sending or receiving. I have to reboot the phone several times per day in order to get the signal back. I know that when I originally restored to stock, I used the NB1 stock file for Odin, then flashed the NC1 update, rooted and installed ShoStock. I kept having data/mms connectivity problems, but wifi was never an issue, so I thought it may have been the NC1 modules or something. I've tried several different variations of ROMs, modules, APN settings, etc. but even with a full return to stock, I'm still losing the ability to send/receive texts at seemingly random times.
I guess my question is, could I have flashed a modem or something in Aroma that is still sticking around somehow, even after using Odin to get back to stock? One of the ROMs I flashed was for the i9505, and it seemed to run fine, the phone was identified as an i9505, but adjusting the APN settings allowed it to work properly on AT&T. IIRC, that was the ROM I was using prior to the issues (Echoe).
I'm currently on the stock NB1 ROM and haven't taken the OTA update yet because it didn't seem to help the last time. I have no idea if anyone here has any insight into why this is so sporadic, but it's driving me nuts so I'm asking for help before I toss it out the window My apologies if I've left out some info. I'll be happy to provide any details I can. I'm just at work and having to type this up in a bit of a hurry. Thanks for reading, and any suggestions you all may have.

Galaxy S4 Wifi Won't Turn On

Galaxy S4 - i337m - Android 4.3
Okay, so here's my problem.
Today in the morning after I woke up, I checked my phone and it said it had downloaded a software update. It was just a complimentary update for 4.3, it said bug fixing, etc. in details. I clicked accept and the installation started.
After this, all crap started to happen.
The Wi-Fi NEVER worked again, everytime I clicked the Wi-Fi widget in the notification bar, it turned green and immediately switched back to gray. It also didn't work when trying to turn Wi-FI on from the settings menu.
I tried everything, the battery pulling, the thing of disabling the Wi-Fi energy save, and nothing worked. It all pointed to a factory reset.
So I did all my backups (My S4 was rooted), and finally made the factory reset.
After this finished, I did all the starting configuration of the S4 (like when it was brand-new). Then, I tried to turn on Wi-Fi.
Surprise, surprise. DIDN'T WORK.
I'm so desperate right now, I don't know what to do.
I'm currently downloading 4.4.2 to flash it via Odin, and see if this works.
Any help, please?

Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.

Strephon Alkhalikoi said:
Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.
Click to expand...
Click to collapse
Fine. Right at this moment I'm installing 4.4.2
Hope this works.
I'll tell you what happens.

GS5 verizon 4.4.4 to rooted marshmallow

I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.

bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.

Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.

bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.

Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.

I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!

bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.

Ok. I'll read the guides on the head of this list and see if I can find the right information.

FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.

Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.

bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.

Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.

bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.

The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!

Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.

bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5

Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!

Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!

Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?