i seem to be having problems maintaining service in areas i know i should have it. i was on insane kit kat previously, i used to have to put in airplane mode or hot reboot just to get service again. everytime i would turn screen off it would drop service again. i even flashed the nb4 modem...so i switched to gpe 4.4.4 had great service..now again...in areas i had 4g i have nothing...not sure what to do at this point..tried both touchwiz and aosp roms...tried nb4...frustrated...anyone have any clue as to what else i am doing wrong? i alwasys enable roaming...always change network if needed to the most options...at a loss....
What bootloader are you on?
i am not sure...
serio22 said:
What bootloader are you on?
Click to expand...
Click to collapse
not sure what boot loader..how do i tell? is there a place to look?
not sure
Heffler said:
not sure what boot loader..how do i tell? is there a place to look?
Click to expand...
Click to collapse
i didnt start on 4.4.4...never had the official update to kit kat. only jelly bean. rooted then...been on custom roms since...never flashed anything except the nb4 modem while was on insane kk because i thought that might solve problem...
So you did the update to 4.3? Get phone info from playstore and under firmware info it will tell you what bootloader you are currently on.
bootloader
serio22 said:
So you did the update to 4.3? Get phone info from playstore and under firmware info it will tell you what bootloader you are currently on.
Click to expand...
Click to collapse
m919uvuamdl is my bootloader...ummm its also identical to the baseband version...not sure if that means anything...
Check your baseband version in settings, more, about device see if it matches up. To my understanding, you had flashed the NB4 modem correct? It might have failed
serio22 said:
Check your baseband version in settings, more, about device see if it matches up. To my understanding, you had flashed the NB4 modem correct? It might have failed
Click to expand...
Click to collapse
it matches up...m919....so this means i have to re odin flash the nb4? does the basband change on every rom you flash?
Yes Odin the NB4 modem, and no it does not change when you flash ROMs.. It probably just failed to flash, make sure you flash it twice
no go...
serio22 said:
Yes Odin the NB4 modem, and no it does not change when you flash ROMs.. It probably just failed to flash, make sure you flash it twice
Click to expand...
Click to collapse
flashed it twice with odin...i was told to open modem.bin file with the phone button in odin...although if its updating the bootloader...wouldnt i use the boot loader button? but no way was gonna test without checking...so only did with phone button..
Its not updating the bootloader, its updating the modem
Having the same exact issue - cell signal was working to make calls when I got the phone and for a while on an older SOKP rom.
Flashed a newer version and now signal is weaker, data/text works, but making a call fails saying "out of service area" and cell signal completely drops out for 10-15sec before returning for data/text.
I've flashed FROM MDL modem to MK2 and NB4 both and no improvement.
Flashed back to the older SOKP version, no fix.
Flashed other AOSP/GPE roms, no fix.
Flashed Wicked v10, no fix.
Flashed back to stock, no fix.
Flashed back MDL modem, no fix.
Checked IMEI, not stolen or blacklisted.
This is an SGH-M919 S4, but is unlocked (otherwise would not be getting ANY data/text signal either).
My next step is to make sure AT&T has the correct IMEI in their system and see if that helps at all.
But I'm really at my wits' end as to why it all of a sudden flaked out for phone calls.
[UPDATE] Went to AT&T and updated my IMEI number in their system. Signal strength has improved enough and I'm not able to make calls.
Related
so even if im on a MDB baseband and ive flashed MDL roms but my baseband still says MDB afterwards.. it updated me to MDL? Because ive noticed that after flashing serval MDL roms my baseband does not change. That sounds kinda fishy to me that it wouldnt say MDL. i was thinking that i needed to flash to MDL to insure it will work properly with MDL roms. i was about to odin a MDL root injected rom once i found one to fix this issue but now im skeptical since i think im aready on MDL. Your modem is your baseband? Can i just flash a MDL modem and it will show MDL afterwards not MDB in the about phone. How come it doesn't change when i flash a MDL rom. i rooted and flashed on the a stock MDB baseband and its read the same a dozen roms later. i also rolled back in odin my friends OTA updated MDL to MDB so i could use moto chopper to get root. it rolled back fine. I was able to get root with moto chopper but it still read MDL even afterwards. I was pretty sure it was on MBD even though it didnt say so.
djphillyphil101 said:
so even if im on a MDB baseband and ive flashed MDL roms but my baseband still says MDB afterwards.. it updated me to MDL? Because ive noticed that after flashing serval MDL roms my baseband does not change. That sounds kinda fishy to me that it wouldnt say MDL. i was thinking that i needed to flash to MDL to insure it will work properly with MDL roms. i was about to odin a MDL root injected rom once i found one to fix this issue but now im skeptical since i think im aready on MDL. Your modem is your baseband? Can i just flash a MDL modem and it will show MDL afterwards not MDB in the about phone. How come it doesn't change when i flash a MDL rom. i rooted and flashed on the a stock MDB baseband and its read the same a dozen roms later. i also rolled back in odin my friends OTA updated MDL to MDB so i could use moto chopper to get root. it rolled back fine. I was able to get root with moto chopper but it still read MDL even afterwards. I was pretty sure it was on MBD even though it didnt say so.
Click to expand...
Click to collapse
Answered your question in Q&A. No need to post in two different sections.
lordcheeto03 said:
Answered your question in Q&A. No need to post in two different sections.
Click to expand...
Click to collapse
Thanks for the link, but even after flashing the MDL modem in odin it still shows that im on UVUAMDB. is that right? shouldnt it show that im on UVUAMDL now? is it only a s4 problem? i heard on a youtube video that the baseband reads the same but DID update. i've flashed dozens of modems on my s1, s2 and s3 and i knew the modem changed because it say what modem im on. i just want to make sure im using the best modem for my area. i am having an issue with death star 4.0. i use to get a strong lte signal at my home now i barley get 4g and it goes on and off mostly off. lte does work if i drive down the street but most of the time i dont have internet connection at all then it pops up for a couple of minutes at like 4 bars then back to no connection figured it might have been a problem with the modem. other roms i used i havent had any issues with data yet. just test driving this rom because a buddy of mine wants it. i personally prefer aosp roms.
djphillyphil101 said:
Thanks for the link, but even after flashing the MDL modem in odin it still shows that im on UVUAMDB. is that right? shouldnt it show that im on UVUAMDL now? is it only a s4 problem? i heard on a youtube video that the baseband reads the same but DID update. i've flashed dozens of modems on my s1, s2 and s3 and i knew the modem changed because it say what modem im on. i just want to make sure im using the best modem for my area. i am having an issue with death star 4.0. i use to get a strong lte signal at my home now i barley get 4g and it goes on and off mostly off. lte does work if i drive down the street but most of the time i dont have internet connection at all then it pops up for a couple of minutes at like 4 bars then back to no connection figured it might have been a problem with the modem. other roms i used i havent had any issues with data yet. just test driving this rom because a buddy of mine wants it. i personally prefer aosp roms.
Click to expand...
Click to collapse
I did the same as you; got the phone with MDB and wasn't on the stock ROM for more than a day or so. It took a few flashes for my baseband to report as MDL once that was out.
I never had any issues with my old M919, which is still sitting in a drawer awaiting a new display assembly I cannot afford. It was running CM 10 perfectly and no issues with HSPA or LTE. I was suffering for a while with an HTC Espresso which I could not S-OFF due to HBOOT being incompatible with AlphaRev. Anyway, I ended up with my old roomate's M919 about a week ago and have had nothing but issues getting mobile data to work properly.
It already had the MK2 Baseband installed-though I did not bother to check if it worked on the stock 4.3 ROM he had already installed. Nor did he ever say anything about issues. Anyway, I tried almost all of the Infamous ROM's(and all the kernels available with AROMA) as well as Cyanogenmod 10.2. All ROM's have major issues maintaining mobile data connection regardless of network mode or which cell I am on. Wi-Fi works flawlessly however. Also, to note, my fiance is running MK2 on her stock M919 so I have had a reference of which type of cell we are on and its signal strength.
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.
fallofredmond said:
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.
Click to expand...
Click to collapse
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.
xdapowerapps said:
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.
Click to expand...
Click to collapse
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel
POQbum said:
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel
Click to expand...
Click to collapse
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
EDIT: I am also using a 4.3 MK2 modem on 4.2.2 and have no issues.
xdapowerapps said:
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
Click to expand...
Click to collapse
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warranty anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar (with knox and the MK2 LTE included) out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers
POQbum said:
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warrantly anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers
Click to expand...
Click to collapse
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!
xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!
Click to expand...
Click to collapse
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it
POQbum said:
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it
Click to expand...
Click to collapse
Open up odin, select PDA, choose the tar file you just downloaded.
Then put your phone in download mode (vol down + home + power), then connect it to your computer.
Once odin detects your phone, press start. It will take 15 to 20 mins and it will restart by itself.
After it reboots and for some reason you get stuck on the tmobile screen for more than 10 mins, go into recovery and wipe/data factory reset and wipe cache. Then your phone will boot up fine. Enjoy ^_^
Sent from my SGH-M919 using XDA Premium 4 mobile app
xdapowerapps said:
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:
Click to expand...
Click to collapse
Both M919's are set to fast.t-mobile.com, although I haven't checked to see if the settings all match. I will definitely check that later.
As for threads here and elsewhere to solve the problem, I have tried pretty much everything I have seen. Most of what I have been reading on both CM and custom TW ROM threads is "me too" or "I don't have that problem".
POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
Ok, now I just got thrown for a loop. Please use Heimdall to print your PIT and post it. On my PIT there appears to be only one partition with a radio... not 2.
xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
Cheers mate!
Click to expand...
Click to collapse
I'm not waiting 4-8 hours to download a ROM. Yes, I understand those estimates are ads to try to get you to buy "premium membership" but still, do you have a legit mirror?
okay so I understand that wifi is the kernel problem
and a lot of people are having problem with the wifi after FNE4 update
but so far I've looked around and couldn't find any fix, or one that does not guarantee on an AOSP rom so please help =)
this is what i did
I was on MJB and flashed this 4.4.2 from http://forum.xda-developers.com/showthread.php?t=2788357
however, it did not update my bootloader to NE4, it stayed MJB, and I noticed Wifi wouldn't turn on on stock rom, so I flashed KT Kernel, but it did not fix the wifi problem.
So i thought it was just the stock rom problem, then i flashed PA 4.4.2 rom, which fixed half of the problem... can turn wifi on and off and there are wifi networks, but can't connect (though some time i got lucky and wifi connect, which is rarely)
so any way to fix?
Bumpz
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
DocHoliday77 said:
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
Click to expand...
Click to collapse
the current bootloader is FNE4, i just updated it yesterday and no hope either
currently on dpk kernel, Rom is AOSPA 7/9
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
DocHoliday77 said:
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
Click to expand...
Click to collapse
I already flashed that yesterday, and other than the bootloader/modem changed from MJB to NE4, nothing else changed
and of course still can't connect to any wifi network
i guess i'll pull the last trick.. back to stock and see
since the last time i flashed, even though the rom is tw4.4.2, but the bootloader remained MJB, so this time i'll go back to stock with NE4 and see how it'll go
Probably the best option at this point. Good luck and let me know if that finally solves it!
DocHoliday77 said:
Probably the best option at this point. Good luck and let me know if that finally solves it!
Click to expand...
Click to collapse
well my last ditch fixed the problem.. so it's all about the bootloader/modem with the incorrect rom
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
DocHoliday77 said:
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
Click to expand...
Click to collapse
indeed it's really odd.. now i'm back on aosp and for some reason, wifi works but sometimes it wouldn't at all.. so im thinking it's the wifi chip or the driver that is damaged..
so I recently updated to pac man rc1 for 4.4.4 and just noticed my baseband is m919uvuamdl. before this update i have been receiving fluctuating full bars to no signal and thought maybe a rom update was needed. lo and behold even after updating my rom i still have these issues and think maybe the baseband is the issue?
i noticed that baseband M919UVUFNH7 is the most current one and found these instructions to update it http://androidromupdate.com/2014/09/17/m919uvufnh7-tmobile-galaxy-s4-m919-444-stock-firmware/ knowing that i will lose root and void warranty.
because i have already done my settings and downloaded my apps i wonder if these steps could work:
backup current image through recovery
follow the steps outlined in the link to update the baseband
root phone again
and restore rom image through recovery so that i have my current settings + updated baseband.
does this logic work? and also would updating the baseband fix my signal issues? (I am in southern california and only recently have had these strange signal issues)
dys4ea said:
so I recently updated to pac man rc1 for 4.4.4 and just noticed my baseband is m919uvuamdl. before this update i have been receiving fluctuating full bars to no signal and thought maybe a rom update was needed. lo and behold even after updating my rom i still have these issues and think maybe the baseband is the issue?
i noticed that baseband M919UVUFNH7 is the most current one and found these instructions to update it http://androidromupdate.com/2014/09/17/m919uvufnh7-tmobile-galaxy-s4-m919-444-stock-firmware/ knowing that i will lose root and void warranty.
because i have already done my settings and downloaded my apps i wonder if these steps could work:
backup current image through recovery
follow the steps outlined in the link to update the baseband
root phone again
and restore rom image through recovery so that i have my current settings + updated baseband.
does this logic work? and also would updating the baseband fix my signal issues? (I am in southern california and only recently have had these strange signal issues)
Click to expand...
Click to collapse
Disregard all that you just posted about how to update your baseband. You don't need to do all that.
The 2nd post of this thread has a link to the 4.4.4 modem.bin, and the OP of that thread links you to this thread which gives you instructions on how to do it and has links to Odin and everything. Just follow the instructions in shiamatsu's thread using the modem.bin you got from android_monsters thread.
That method I linked to updates just the modem. It doesn't update your phone firmware, bootloader, etc. There's no need to update your firmware and get KNOX unless you just WANT to.... By updating just the modem, you wont' get KNOX, you won't lose your user data, you won't lose root, and you can flash any version of TouchWiz, AOSP, CM, or GPE ROM for the S4 from 4.2.2 to 4.4.4 . And to answer your question: yes, your baseband is the exact reason your signal keeps dropping. It's been a known issue for those of us who are still on the MDL bootloader since 4.3 was released nearly a year ago.
thanks for the response. is the modem link this one https://www.androidfilehost.com/?fid=23622183712469704 1.5 gig?
or this one? http://forum.xda-developers.com/showpost.php?p=55373341&postcount=22
Not the 1.5 gig one. You just need the nh7 modem.bin file.
similar question
hey I just updated to 4.4.4 with baseband fn13. I was wondering if I can install a new ROM that is 4.4.2 or lower? I am running stock but I am interested in insane. thank you
BrockliRob said:
hey I just updated to 4.4.4 with baseband fn13. I was wondering if I can install a new ROM that is 4.4.2 or lower? I am running stock but I am interested in insane. thank you
Click to expand...
Click to collapse
Why flash my 4.4.2 Insane.......when you can flash my 4.4.4?
The Sickness said:
Why flash my 4.4.2 Insane.......when you can flash my 4.4.4?
Click to expand...
Click to collapse
Downloading now, sir
so this one?
https://www.androidfilehost.com/?fid=23622183712469693
(just being cautious)
found here under modems
http://forum.xda-developers.com/gal...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
dys4ea said:
so this one?
https://www.androidfilehost.com/?fid=23622183712469693
(just being cautious)
found here under modems
http://forum.xda-developers.com/gal...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
Click to expand...
Click to collapse
Yes, its fine.
The Sickness said:
Why flash my 4.4.2 Insane.......when you can flash my 4.4.4?
Click to expand...
Click to collapse
Im having a lot of fun with the rom. Seems stable, very tidy. I will be keeping it and updating it. Thanks, brother.
One question, though. When i power on, why do i get the seandroid message and root warranty bit? Anything to be conserned with?
BrockliRob said:
Im having a lot of fun with the rom. Seems stable, very tidy. I will be keeping it and updating it. Thanks, brother.
One question, though. When i power on, why do i get the seandroid message and root warranty bit? Anything to be conserned with?
Click to expand...
Click to collapse
It's all good
The Sickness said:
It's all good
Click to expand...
Click to collapse
I'm just noticing that the volume is basically double. Is there any way for me to revert this setting? the only reason I want to it's because of the system sounds. I like to hear my keyboard and the button presses at the lowest possible value. I've tried the exposed modules but none of them help me with system sounds.
---------- Post added at 03:27 PM ---------- Previous post was at 03:01 PM ----------
BrockliRob said:
I'm just noticing that the volume is basically double. Is there any way for me to revert this setting? the only reason I want to it's because of the system sounds. I like to hear my keyboard and the button presses at the lowest possible value. I've tried the exposed modules but none of them help me with system sounds.
Click to expand...
Click to collapse
Thank you for all the help, i found the mods. I will make a better effort to search before asking lol.
hm after flashing i am still getting dropped data at work and randomly only my commute. the signal will show no bars while i am on a call but the call doesn't drop - however the data ceases to work until the bars show LTE while i am on the call.
help?
dys4ea said:
hm after flashing i am still getting dropped data at work and randomly only my commute. the signal will show no bars while i am on a call but the call doesn't drop - however the data ceases to work until the bars show LTE while i am on the call.
help?
Click to expand...
Click to collapse
Does your baseband still show as m919uvuamdl?
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.