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.
2 years ago I buy my galaxy s4 unlocked version from amazon.com. When I came back to Turkey I registered the Cellphones imei. After that I rooted my galaxy s4. I watch lots of tutorials and most of it did not work out. At the last try I was able to root my device. After a year my uncle bought me a gear 2 neo which needed a higher version of android. So i plug my galaxy s4 and updated trough kiosk. The result was my galaxy s4 was mys galaxy s4 lost its root acsess was gone and system was updated. Also most of the apps first run and then give a error. For example i downloaded can knockdown 3. First it worked fine then it stopped working. One of my friend suggested I need to downlad a rom and suggested cyanogenmod. I tried one button installer but it said the device is not supperted for this installer. But my phone is listed in the supported devices(GTI9500). Please help me. My cellphone is slowly dying. Also last thing. They say making a change on the phone sometimes deletes the imei registiration.
Just perform a factory reset and your issues will probably be resolved. If you want root again just flash cf auto-root.
I have done it and it hasn't changed. Still the same issues.
aebatirel said:
2 years ago I buy my galaxy s4 unlocked version from amazon.com. When I came back to Turkey I registered the Cellphones imei. After that I rooted my galaxy s4. I watch lots of tutorials and most of it did not work out. At the last try I was able to root my device. After a year my uncle bought me a gear 2 neo which needed a higher version of android. So i plug my galaxy s4 and updated trough kiosk. The result was my galaxy s4 was mys galaxy s4 lost its root acsess was gone and system was updated. Also most of the apps first run and then give a error. For example i downloaded can knockdown 3. First it worked fine then it stopped working. One of my friend suggested I need to downlad a rom and suggested cyanogenmod. I tried one button installer but it said the device is not supperted for this installer. But my phone is listed in the supported devices(GTI9500). Please help me. My cellphone is slowly dying. Also last thing. They say making a change on the phone sometimes deletes the imei registiration.
Click to expand...
Click to collapse
Sounds like your phone may have been corrupted when installing official firmware on top of the root. I would recommend re-flashing your phone with official stock firmware. You can use this website to obtain a stock firmware for your device model
http://galaxys4root.com/galaxy-s4-stock-firmware/
Your imei should not be affected if you re-flash your phone, however just to be on the safe side you can flash a recovery mod such as TWRP Recovery and back up everything such as your efs which contains your imei baseband in case a re-flash causes your phone to not work on cell networks in Turkey (which I'm guessing is not the country your phone was purchased in.) After you have backed up everything in TWRP to your sdcard you can safely reflash stock firmware.
Hi, i have an issue with a Galaxy S4 owned by a company.
I received the phone rooted and iI was asked to unroot it. I read on a few websites and forums, and i flashed the stock firmware, using Odin.
The device was flashed and now running android 4.2.2. I tried updating it to 5.0, but i cant because of the Wi-Fi. The Wi-Fi just doesn't wants to turn on. I tried factory reset, removing battery, Router power cycle. I tried finding the Path: /data/misc/wifi/wpa_supplicant.conf, aand i wasnt able to find it, because there is no good file explorer and since i cant connect to wifi, i cant downlaod any. I plugged it in a computer and i wasnt able either to find this path. What are your suggestions, knowing that its is a company phone, so i cant root, and i cant flash a custom recovery and then run a custom ROM. The phone needs to be updated and to stay stock.
Thank you for your help.
So, I recently ordered a new N910F on eBay to replace my dead N910T, which died catastophically last month after catching fire while charging. I recieved the F on the 11th, and all was working fine. Product was working exactly as seller described, new in factory-sealed and shrink-wrapped Samsung N4 box, complete with warranty paperwork. It even had the extras like stock charging cable/power supply and white earbuds. The sticky paper was on the screen as well. A visual inspection of the inside/outside of phone gave every appearance that it was in fact 100% new. Odin's download page read as Knox warranty 0x0, meaning it had never been rooted, TWRPed, etc. Completely virgin.
After powering it on I installed several OTAs until there were no more updates. At this point audio was fine, I had to test my SIM card to make sure calls worked, no issues.
Earlier yesterday I downloaded the following firmware from SamMobile, which is latest UK BTU:
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/BTU/download/N910FXXU1DRI2/249766/
It flashed in Odin fine, I factory reset afterwards, ROM boots up.....but audio isn't working anywhere. I cant hear calls, YouTube plays videos but without audio, touch sounds dont work even though audio is completely turned up. It is also crashing/freezing semi-frequently.
I live in the US, I am using this phone on T-Mobile's network. At this point I'm stumped, a stock firmware flash *SHOULD* resolve this, but nope. I'm going to try for awhile to fix it some other way, if I can't then I will contact seller to see if they will return me return the phone for an exchange.
If anyone can suggest how this might be diagnosed and fixed then I'd appreciate the help.
Thanks!
Edit: I'm also trying to do an emergency firmware repair with Kies. I've tried both Kies 2 and Kies 3, they say device not supported. And they say that Samsung Smart Switch supports my device. But after installing Smart Switch, it also says device not supported. I'm going to try a KitKat downgrade with Odin and see what happens. I'm at wit's end here.
I wasn't able to flash KK, 7-Zip gave an error when trying to extract the tar.md5 from the zip. Anyway, I'm convinced that the speakers on my new F must have been defective out of box, there's no other possible explanation.
As a test, I flashed TWRP with Odin, then Resurrection Remix Pie by @mobspyguy.....audio doesn't work in RR either. Which means it isn't a firmware problem, since a custom ROM had the issue. I just find it strange that audio stopped working immediately after flashing stock firmware, but was OK before that.
So I'm going to Odin it back to stock, I already left a detailed message with the seller about an exchange, hopefully they'll get back to me on that.
I wish to root my soft-bricked S5mini.
But have realised that I cannot use djibe89's tutorial without enabling USB debugging in settings (which are currently unavailable).
I've tried to install Kies to reinstall firmware, but get endless connection error, and troubleshooting connection error (i.e. reinstalling Samsung USB driver) doesn't fix it.
It seems like Odin is able to connect to the phone (at least I get ID:COM blue).
Question 1: Does this mean that I can flash fresh firmware/ROM to the phone with Odin?
Like described in this guide by jackeagle (and then enable USB debugging)?
Question 2: How and where do I find the right firmware/ROM?
I have a Danish language SM-G800F phone, but it doesn't seem like Samsung is providing firmware anymore. When I check sites like sammobile.com, there are 3 different version 6.0.1 in mutiple languages (including multiple UK versions) but not Danish one.
Can I use any firmware version (including ROM Unofficial Lineage OS 16 provided in djibe89's Galaxy S5 mini G800F pack)?
Or is there a specific UK/US version that would work with my phone?
I hope someone can help, because my backup phone stopped working a couple of days ago
[Created a new thread under Q&A, Help, and Troubleshooting, because it doesn't really belong here]