[Q] Baseband: what does it control and when is it updated? - Galaxy S 4 Q&A, Help & Troubleshooting

From my searches I have now learned that the baseband firmware is separate from the kernel in the sense that they control different pieces of the hardware; baseband being more involved with the signal/radio.
I have an i9505G with which I am having some Bluetooth and USB-connectivity (to a computer) issues. I rooted it from stock, which was the precursor to my aforementioned issues.
My question is simply this: what all does a baseband version/firmware control on the phone?
Is it possible that during my rooting I somehow updated the baseband and that's causing my issues with BT and USB-connectivity?
I was about to do the Rooted Restore to stock for i9505G in the hopes of fixing my current issues, but stopped in my tracks. I didn't want to go into this blind like the first time around and make matters worse for myself.

KrossX said:
From my searches I have now learned that the baseband firmware is separate from the kernel in the sense that they control different pieces of the hardware; baseband being more involved with the signal/radio.
I have an i9505G with which I am having some Bluetooth and USB-connectivity (to a computer) issues. I rooted it from stock, which was the precursor to my aforementioned issues.
My question is simply this: what all does a baseband version/firmware control on the phone?
Is it possible that during my rooting I somehow updated the baseband and that's causing my issues with BT and USB-connectivity?
I was about to do the Rooted Restore to stock for i9505G in the hopes of fixing my current issues, but stopped in my tracks. I didn't want to go into this blind like the first time around and make matters worse for myself.
Click to expand...
Click to collapse
What kind of issues are jou having?Please elaborate!

I was having Bluetooth issues. I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!
Sent from my GT-I9505G using Tapatalk 4

Related

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

[Q] Updated my S4 to 4.4.2 now it no longer functions correctly. Solution?

I recently decided to return my phone to stock, so I downloaded the most recent update of KITKAT 4.4.2 from sammobile. I uploaded the new firmware using ODIN and experienced no issues up until I started my phone for the first time. I performed a factory reset and also deleted the cache but it made no noticeable difference.
I now have absolutely no control over my phone, it now lags and I am unable to make phone calls, connect to WIFI or turn up the volume.
I'm not very familiar with these phones but im fairly certain that either something wasn't updated correctly or one of the files may be corrupt.
Could anyone point me in the right direction and provide me with the correct firmware or information to correct this issue?
Thank you.
PHONE:SGH-I337M TELUS
BASEBAND: I337MVLUAMDJ
BUILD NUMBER: KOT49H.1337MVLUFNI2
KERAL VERSION: 3.4.0-2767305
Your modem looks to be very outdated. See if updating it helps with reception. Did you flash the correct firmware with odin?
As far as I know I updated with the most recent software.
Is it possible that a modem update could fix all the issues I'm experiencing?
Would you be able to provide me with the most recent firmware and modem update?
I've been having nothing but issues trying to download from these mirror sites.
No, as I don't have your variant of the S4. I have an SGH-M919. Flashing is pretty standard across the board assuming you can install a custom recovery. I'm not sure if you have TWRP/CWM or are using SafeStrap. I can't stand touchwiz, so I usually run some form of AOSP. That may not be an option for your handset, especially if the bootloader is locked.
Watson30 said:
I recently decided to return my phone to stock, so I downloaded the most recent update of KITKAT 4.4.2 from sammobile. I uploaded the new firmware using ODIN and experienced no issues up until I started my phone for the first time. I performed a factory reset and also deleted the cache but it made no noticeable difference.
I now have absolutely no control over my phone, it now lags and I am unable to make phone calls, connect to WIFI or turn up the volume.
I'm not very familiar with these phones but im fairly certain that either something wasn't updated correctly or one of the files may be corrupt.
Could anyone point me in the right direction and provide me with the correct firmware or information to correct this issue?
Thank you.
PHONE:SGH-I337M TELUS
BASEBAND: I337MVLUAMDJ
BUILD NUMBER: KOT49H.1337MVLUFNI2
KERAL VERSION: 3.4.0-2767305
Click to expand...
Click to collapse
Latest update for your device is: HERE .You must follow this steps:
1. Download, unzip it and flash the .tar file through ODIN.
2. Wait the process finish and reboot your phone.
3. Reflash the same firmware if you still having problems with WIFI, lag, sound, etc.
4. Good luck

S4 i337M - No sound on calls (in/out) after flashing Stock 5.01 Loliipop ROM

Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.
Try flashing the latest stock from sammobile.com.
Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse
Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.
Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.
You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.
@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.
Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.
Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw
Okay, try flashing with a pit file and the latest stock rom from sammobile.
audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone
I attached a 16 GB pit file from my i337m.

Rom Access or advice for TAB S4

My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin

Categories

Resources