Wifi issue on Galaxy S4 I9505 - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[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.

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.

[Q] Phone wouldn't connect to WiFi with Stock Rom & won't play any SOUND OR MEDIA

I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
masterof1010 said:
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
Click to expand...
Click to collapse
try with this firmware
lets me see
k thanks i'll try it (once it's slow download is done) and update this post. Looks the same except I guess it's android v5.0.1 (well and it's a different CSC/PDA).
K well i've tried that firmware and it's given me some abnormal problems.
Odin typically just writes in like two minutes and boom done, but when I tried to flash with the firmware you suggested like every 15 seconds it would say ...
"Receive Response from boot -loader"
"Transmission Complete.."
"Now Writing .. Please wait about 2 minutes"
It kept cycling through those 3 messages until it FINALLY finished and it say's PASS but it took 9 min 53 seconds which is like 5 times longer then it's ever taken.
Wheather this is relevant or not i'm not sure just trying to give as much details as I can.
Anyways, after booting the phone the samsung logo came up as usual and usually it takes like 5-10 min sitting at this logo before the phone completes loading, presumably setting up the firmware I imagine.
It's been now sitting at that logo for over 20 minutes and i'm about to try wiping with TWRP the davlic cache/cache/data/internal and either trying again with odin (v3.07) OR
If that contines to not work I might put the tar.md5 on the external SD card and recover a saved backup I have on the SD card (with the stock firmware I had before that doesn't allow Wi-Fi to be enabled nor audio/media to play) and use Mobile Odin Pro .apk (I paid for the pro version) from within that restored recovery to flash the firmware you suggested to my phone again.
This is probably redundant but I just figure I might as well try absolutely everything I can possibly think of with your firmware.
If you have any idea why I might be experiencing these abnormal Odin flashing and/or initial loading conditions of the firmware you (or anybody ) suggested i'd appreciate any advice you can give.
I'm going to try and reflash with Odin on my PC again right now (i'm certain thing's like the USB cable are fine and my PC and phone can transfer data without issue .. but that's why i'm going to try mobile odin if after this next attempt doesn't work either).
I'll keep the thread updated, any and all advice is welcomed and highly appreciated
EDIT: OMG it made a like startup theme sound ... that's the first time it's outputted sound in 3 day's !!! It's at the Samsung screen loading the newly flashed firmware so hopefully that completes because wow my phone made noise finally !! Now to wait, and wait....
It won't go past the Samsung logo. So I guess i'll try Mobile Odin. I don't have much faith but it's worth trying.
Uh the backup of the stock firmware I made won't load ... but the hyperdrive rom did. Sound and the dialer work perfectly fine in this rom now, so I guess thing's are more or less fixed. Even though i've wiped the cache/davlic/internal/data in order to prepare to flash the other firmware or this hyperdrive rom (I wipe it every time) in this rom it's reporting my phone's baseband to be I337MVLUGOC4 which is that of the firmware you suggested ...
I'd still rather not use this rom, I thought it was ok at first but meh i'm going to try to go back to CM (after all this *rolls eyes*), trying to use Mobile Odin to install the firmware that you recommended and that appears to have ... somehow fixed the sound can't detect the model of my phone and is dumping, this is not something that has happened with the app before so I don't think i'll be flashing the firmware you suggested.
If it did something to globally fix the crashing when an app was instructed to play audio as it appears to have I guess i'm going to just go download the full CM now, put it on the SD card and install it with TWRP.
So uh, not 100% there yet but it does appear what you've suggested has solved my problem (because worst case scenario i'll just be stuck with the Hyperdrive rom ... but i'll have a working phone) so thanks so much bud I was quite upset and worried about what I was going to do still paying off a useless phone on a contract i'm stuck with for another year still.
I suppose there's no real need in continuing to update this thread as it appears my problems are solved and all that's left are things i'm doing not to fix anything but just because of personal preference over what rom to use but if you want to know anything more just ask, otherwise thank you so much you saved my ass and i'm very grateful.

Galaxy A500FU - the phone doesnt turn on

Hello, im new to this forum
Ive bought a Samsung Galaxy A5 back in September 2015 to my girlfriend.
At the time i opened the case to see if it was everything ok with it before giving it to her. unfortunately i installed oficial updates in the phone after connecting the device to the internet.
Wanting to give the phone just like ive bought it, i started to making all things wrong. i tried to reset the phone back to the factory reset (using the volume up + home + power buttons) but after that the version that was still installed was the updated one and not the factory one.
Then i tried to download the factory version from here htt p://updato.com/firmware-archive-select-model?r=&v=&q=Galaxy+A5+205 using odin and this guide htt p://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
it was installed but when the phone restarted it never turned back on again. despite being the correct version for my region i believe i installed a variant version and not the factory reset version.
I tried turning the phone on, using recovery mode and download mode keys but the phone never gave any signal again. plugin in the usb in the pc didnt work either.
I ended up buying the same phone since i wasnt able to solve the problem and her anniversary was close and ended up with an extra but damaged phone.
i never tried to get the phone to the warranty because i knew that i was losing the it the moment i tried to use odin.
is there anything else i can try to solve the phones problem? or is this problem unrecoverable?
thanks in advance
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
akil777 said:
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from ="htt p://www .sammobile.com/"]sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
Click to expand...
Click to collapse
It must have been other variant rom.
http s://gyazo. com/7ac9dfe107976eeb802cae50a23b23a1 - here is a screenshot
Samsung Galaxy-A500FU - to get there you need to go to "updato" site (first link), place on the search "Galaxy A5" and select Portugal as "region"
There are 7 options, 6 are for locked phones to the main Portuguese operators and one for unlocked phones (i assume), because it says "Porgugal TPH" - TPH means the phone house witch is a store that sells phones and other electronic equipment.
Despite the phone not being bought at the phone house i assumed it was this rom since there was no other one and the phone is not locked to a particular operator.
Ive checked the site you provided and it as almost the same rom´s as updato and the only one that is not locked to a particular operator is TPH one.
So my only option is to use a usb jig to force the phone into download mode? will that work with or without a motherboad change?
please have in mind that the phone does not respond to any other button or combination of buttons comand and trying to charge the phones battery only produces heat at the phone and charger, nothing else happens.

Categories

Resources