Related
I've searched but can't find an UVUAMDL baseband file to flash anywhere, any idea why that is ?
I'm on rooted UVUAMDL stock rom but still on UVUAMDB baseband and I've been losing network connection 3 times today in areas where my gf's S4 on stock UVUAMDL has been rock solid, so I think having the modem mismatch the rom is probably the issue...
Sent from my SGH-M919 using Tapatalk 2
Another thread actually has info that this is an issue with the phone. I'm sorry, but I'm unable to locate the thread again.
I dont think its a issue....been flashable modems on every galaxy phone including both international s4 so irs just a matter of someone who knowshow to make it
Can someone with the know how make one?....thanks in advance
+1 for UVUAMDL baseband for some reason my device is still on UVUAMDB after updating
lazaro17 said:
+1 for UVUAMDL baseband for some reason my device is still on UVUAMDB after updating
Click to expand...
Click to collapse
I'm using the Wicked v2 ROM that is using MDB as the baseband and the only network issue I'm having is connecting to the LTE network. Phone connection is fine, 4G connection works great, but whenever I'm in an area that has the new T-mobile LTE network, my phone loses its data connection unless I force it to use the 4G connection.
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
weez101 said:
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
tried this twice. didnt work, yesterday and today
Deleted.
weez101 said:
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
Also tried this last night with no success. Still on older baseband. I believe its what breaks my WiFi. The only temporary solution I've found is to flash a custom kernel I found here. Its fixed my WiFi issues but I'd eventually would like to have my baseband upgraded too.
http://forum.xda-developers.com/showthread.php?p=41240723
lazaro17 said:
Also tried this last night with no success. Still on older baseband. I believe its what breaks my WiFi. The only temporary solution I've found is to flash a custom kernel I found here. Its fixed my WiFi issues but I'd eventually would like to have my baseband upgraded too.
http://forum.xda-developers.com/showthread.php?p=41240723
Click to expand...
Click to collapse
Yeah, same. Did not update baseband and I'm having some weird signal issues so hopefully someone figures out how to do this
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
mrvirginia said:
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
Click to expand...
Click to collapse
Updated baseband for me. Thank you! I was already on Matt's Kernel sobmy WiFi was already working. I would think this would fix any WiFi issues if i go back to stock.
Sent from my SGH-M919 using Tapatalk 2
lazaro17 said:
Updated baseband for me. Thank you! I was already on Matt's Kernel sobmy WiFi was already working. I would think this would fix any WiFi issues if i go back to stock.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
sweet :highfive:
mrvirginia said:
sweet :highfive:
Click to expand...
Click to collapse
You should make a flashable zip
xXchrizhurtyXx said:
You should make a flashable zip
Click to expand...
Click to collapse
i'll try to tmw. this is just what i had on hand and already uploaded
we now have a modem thread
http://forum.xda-developers.com/showthread.php?t=2282342
Wow, that was crazy. I tried heimdall flashing the modem at first and nothing. So I made one of my flashable update .zips I had made for T999 and still nothing!
Then I found this thread and tried something crazy:
(1) Download mode + heimdall flash of a few files w/o reboot, then hard reboot back to Download Mode
(2) heimdall flash of same files w/o reboot (it should error)), then hard reboot back to Download Mode
(3) heimdall print-pit (forces it to reboot cleanly)
I did this with all the firmware files including the bootloader but it was scary. I tried to do all the other firmware files at once and it wrote all but aboot.mbn and failed to write that one out. It was worrying since I the other bootloader files had succeeded and I was worrying I could possibly brick it. I repeated the above steps for aboot.mbn and got it to update as well. It seems the above steps can't be used for all the firmware files at once, but at least a few of them. It seems heimdall can get into a bad state with communicating with the device if too many flashes are pushed at once.
This was with a clean git checkout of heimdall from its github repo the other night. Unfortunately heimdall seems to have a bunch of bugs lately. 1.4rc1 (shipped with Debian and other distros) is broken for the S3. --no-reboot option suppresses reboot on S3 and S4 but further commands are not accepted, requiring manual hard reboot. Earlier versions don't work at all.
It worked out for me in the end but gosh I don't know how I'd modify the script to work short of someone having some sort of way of overriding the write protection. I tried dd manually in recovery and in CM and nothing... Seems like some sort of NAND write protection is going on. If I dd a modem to mmcblk0p1 and read it back, the content doesn't change
Maybe we need something like wpthis.ko from HTC Vision days ...
Anyway I got my wife's phone on UVUAMDL w/o Odin but boy it wasn't pretty. I made an updater script but it doesn't actually work do to the above reasons.
Anyone know what's up with the crazy write protection on the mmcblk0 partitions? It seems nothing ever gets written to mmcblk0p1 for example if I try to write NON-HLOS.bin out to it.
Major props for the modem-only Odin package for the S4, but unfortunately not all of us here have/want to use Windows, so I'd like to figure out a flashable update.zip solution to simplify this like I've done on the T999 S3.
Unfortunately my script was a no-op and only doing a bunch of crazy stuff through heimdall and hard rebooting the device several times over was the only way for me to achieve a full MDL firmware upgrade for S4 that included NON-HLOS.bin and modem.bin (the two modem firmwares on S4), rpm.mbn (Resource and Power Management), sbl{2,3}.mbn and aboot.mbn (MDL bootloader), and tz.mbn (MDL Trust Zone)
I noticed Download Mode had "Write Protect: On" -- I don't remember if my S3 says this or not.
Is anyone working on a way to get around this? Maybe the hack can be integrated into an update.zip script that updates the firmware. MDB radio / firmware seemed really bad on the S4. It would sometimes have trouble making 911 calls (!!!) and was overall really lame with power usage and data. I'm still playing with MDL to see how much improvement there is, but seems like a nice win.
mrvirginia said:
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
Click to expand...
Click to collapse
I flashed this & has the wifi working but my 4g lte doesn't come up at all.
Sent from my SGH-M919 using xda premium
sdizzy101 said:
I flashed this & has the wifi working but my 4g lte doesn't come up at all.
Click to expand...
Click to collapse
Does your area have LTE? I don't seem to get LTE in San Jose, California or at least where I live there. I haven't tried it at the office in San Francisco yet.
Before you guys read this thread, let me just go ahead and say that i AM in fact a XDA noob... so dont hate. I didnt come here for that, but i came for help. Now, i did notice that there were alot of people having similar problems as i was. And yes, i did read all those threads. BUT, the only difference was, they got that error while trying to unroot. I was trying to root mine. I simply tried flashing CWM (and yes i made sure it was the correct flash as well) and it failed. Tried rebooting the phone, and i got that error. I am honestly freaking out right now as to if i have lost my phone or not, so i wouldnt appreciate hate in the comments, that would not help. So please help if possible... Is there a way to fix this?
We're you on stock Rom. How did you try a put CWM on your phone?? Odin??
Best way to install a recovery is Odin or goo manger!!
If you can get the phone into download mode then you can just flash back to your stock firmware...
Unless you flashed the wrong recovery on your phone. Then your in store for brick city.
Start here: http://forum.xda-developers.com/showthread.php?t=1980644
TWRP thread: http://forum.xda-developers.com/showthread.php?t=1981198
All in ONE thread:
http://forum.xda-developers.com/showthread.php?t=1987541
Good luck with your problems.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Bajanman said:
We're you on stock Rom. How did you try a put CWM on your phone?? Odin??
Best way to install a recovery is Odin or goo manger!!
If you can get the phone into download mode then you can just flash back to your stock firmware...
Unless you flashed the wrong recovery on your phone. Then your in store for brick city.
Start here: http://forum.xda-developers.com/showthread.php?t=1980644
TWRP thread: http://forum.xda-developers.com/showthread.php?t=1981198
All in ONE thread:
http://forum.xda-developers.com/showthread.php?t=1987541
Good luck with your problems.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks, i was actually on odin. But i think i found the solution. You see, when i was trying to find a solution on my own, i accidentally ended up installing a verizon rom on my phone which is att. (i didnt know it was verizon) The rom works, but i cant use mobile data, because its not a verizon SIM card. However, i managed to install TWRP recovery with goomanager, and from that i will attempt to install the JediXP14 custom rom. Strangely, it seems the phone is rooted even though i was told it failed. I will let you know on the progress, should be done in an hour or so.
Oh boy..... I smell brick city.. You better be careful what ur doing with Odin... If u are flashing stock firmware in Odin it flashes the radio with it....
Ok guys, i SOMEWHAT resolved the issue. But there are alot better ways of doing it, i was just forced to do it the following way:
The only flash rom i could get to go in through odin was a Verizon rom. It was basically the stock Note 2 rom for verizon.
Now the only problem with this, is that obviously, my phone is ATT and this is a Verizon rom, but it WILL work, but with an exception. Wifi and all will work, you can call and receive messages, but you cannot access the internet via mobile data. So that was another issue that popped up. I tried flashing an att stock rom through odin, but it stayed stuck at "Setup Connection" so that didnt work. The only solution i could think of was to unlock the rom, so i could use data with my ATT sim card. Strangely, the phone thought that it was a Verizon phone when it was an ATT phone, so that was the only option. It required a root but that wasnt a problem. I installed Hidroid off the play store and unlocked it that way, and now everything works fine. There is still an error message in the status bar saying "Non-Verizon SIM" but despite that message, everything still is in working order. If anyone knows what to do once you first get that error message, you could post it below for anyone else having the same problem. And if there is a way to change it back to the normal ATT stock, that would be appreciated as well. Thanks
Nintendoassasin64 said:
Ok guys, i SOMEWHAT resolved the issue. But there are alot better ways of doing it, i was just forced to do it the following way:
The only flash rom i could get to go in through odin was a Verizon rom. It was basically the stock Note 2 rom for verizon.
Now the only problem with this, is that obviously, my phone is ATT and this is a Verizon rom, but it WILL work, but with an exception. Wifi and all will work, you can call and receive messages, but you cannot access the internet via mobile data. So that was another issue that popped up. I tried flashing an att stock rom through odin, but it stayed stuck at "Setup Connection" so that didnt work. The only solution i could think of was to unlock the rom, so i could use data with my ATT sim card. Strangely, the phone thought that it was a Verizon phone when it was an ATT phone, so that was the only option. It required a root but that wasnt a problem. I installed Hidroid off the play store and unlocked it that way, and now everything works fine. There is still an error message in the status bar saying "Non-Verizon SIM" but despite that message, everything still is in working order. If anyone knows what to do once you first get that error message, you could post it below for anyone else having the same problem. And if there is a way to change it back to the normal ATT stock, that would be appreciated as well. Thanks
Click to expand...
Click to collapse
Maybe you just need to flash att modem with ril for your device. Scroll down and dload the one for att then flash using cwm or twrp. After flashing modem try flashing att rom again via Odin.
http://forum.xda-developers.com/showthread.php?t=2016575
Sent from my SAMSUNG-SGH-I317M
Ok guys I resolved the problem. But it took more steps than it needed. This is for people who accidentally flashed the wrong type of recovery to your phone (example, gt-1700 version of cm what on sgh-I317) I'll be renaming this thread if I can. So here's all the steps I took. Now keep in mind that I didn't exactly know what I was doing so I kind of learned on the way, like I said in the beginning of this thread, I am a noob, and I admit such.
1. Install any rom that is in md5 format (preferably with your carrier modem but anything will do) I used a verizon rom. I can't exactly provide a link given my user status though, but I will when I can.
2. If you don't have wifi and downloaded rom under incorrect modem, then download hidroid on the play store and unlock it. It should be simple once getting the app. This will allow you to use mobile data. You'll need it.
3. Download goomanager
4. Press menu button
5. Install open recovery script
Now you should have TWRP installed on your device.
6. Install any custom rom compatible with your device, but make sure it comes with the correct modem as your phone originally had.
7. Flash it through TWRP (make a backup first)
You should be done from there. Now I don't recommend this. There has to be an easier way, so it would be great if anyone could provide that below. But the steps above are the steps I took. Thanks
Sent from my SGH-I317 using xda premium
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
cnote74 said:
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Agreed. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
but where o.o
cnote74 said:
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Umm guys, i ran into a similar problem. Where would i find the att rom to flash from odin?
I use the Sprint SlimBean ROM and I had no issues with it on my SCH-S960L. I had no issues with my mobile connection except for the fact that it it took some time to connect to mobile data services or even required a restart or Airplane mode toggled. This along with it sometimes did not switch between 3G and LTE when it should. Because of this I attempted to flash a newer Sprint Galaxy S3 modem. This completely disestablished any connection to services. It has 0 bars and cannot make calls, send texts, or use data. I have tried to reflash the ROM but of course, it did not help at all.
Now in the light of hope, I made a backup of the efs and firmware folders before flashing. I'm not sure how I can fix my issue with this but it was suggested to do so before flashing.
My baseband version was S960LWYAMD6. While I could reflash the old modem, (with help) I would prefer a better modem. (if there are any)
Any help is appreciated.
With best regards,
SirBenjamin
Well this just may be your day. Apparently chxnugs just posted the Modem for your particular device HERE. I would update PRL / Profile first just to see if that will help. Also have you tried ##72786# ?
prboy1969 said:
Well this just may be your day. Apparently chxnugs just posted the Modem for your particular device HERE. I would update PRL / Profile first just to see if that will help. Also have you tried ##72786# ?
Click to expand...
Click to collapse
chxnugs said:
i know this is sprint galaxy s3 section, but the straight talk s3 is basically the same phone and there is no section for it.
if you own this particular model, then you would know that its pure hell trying to find ANY files. this is the stock MD6 modem.bin ripped from my phone. ive seen people ask for this modem because they flashed the MD4 modem in hopes of getting their MSL and/or for the benefits of being able to use the 16-digit password. (which reminds me.. i have read of ways to port the 16-digit password from a .dll file in the phone? i have done loads of searching, but the password is NO WHERE to be found) and needed the stock modem. so for anyone that needs it here it is.
hopefully us ST S3 users will eventually gather up all the odin files to completely restore our phones when needed
Click to expand...
Click to collapse
I tried to flash the file chxnugs provided. I used both Mobile Odin and replaced the modem file in another flashable ZIP. Neither of them worked and I still get 0 bars/unknown baseband.
Honestly I have no idea what to do to fix this but it needs to work.
Again I say, all help is appreciated.
ok i extracted a fresh modem.bin straight from my phone. let me know if it works
Oh and just asking.. have you extracted the .bin file from the zip and tried it
Sent from my SCH-S960L using Tapatalk
chxnugs said:
Oh and just asking.. have you extracted the .bin file from the zip and tried it
Sent from my SCH-S960L using Tapatalk
Click to expand...
Click to collapse
chxnugs said:
ok i extracted a fresh modem.bin straight from my phone. let me know if it works
Click to expand...
Click to collapse
I got the same results. I extracted the .bin but renamed it to NON-HLOS.bin since Mobile Odin would not accept it as modem.bin. Am I flashing this wrong?
Sent from my SCH-S960L using Tapatalk
Did you try any of my other suggestions form post #2 ?
im sure your trying to flash it under phone section.. i managed to try to make a flashable CWM version. maybe you can try that and let me know if it works
prboy19648801865 said:
Did you try any of my other suggestions form post #2 ?
Click to expand...
Click to collapse
chxnugs said:
im sure your trying to flash it under phone section.. i managed to try to make a flashable CWM version. maybe you can try that and let me know if it works
Click to expand...
Click to collapse
Proby, I tried to do the other things you suggested. I can't update the PRL/Profile since I'm on a custom ROM. That is unless there is another way. I did not understand what you meant with the number you mentioned. If you wanted me to call that it did nothing.
As for chx, unfortunately it still did not fix it. This quick little modem update is turning into a nightmare. Not only that, but no sound plays, the microphone does not work, and DSP Manager crashes whenever I try to play media.
I really appreciate both of your support though.
Yay! I used Mobile Odin Pro and flashed a file from another thread. It may have been the file or using Mobile Odin Pro since it downloaded the correct driver. I appreciate all of your help, though.
Sent from my SPH-L710 using Tapatalk
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.
So I'm trying to fix my s4, I can't call or receive any calls. When I do it automatically goes to the call without ringing. I tried a factory reset and it worked for 10 minutes and it went back to no ringing. I tried to flash 4.4.2 on to it through odin and it gives me this error "complete(write) operation failed" from this point I didn't know what to do and I'm trying to go back on to stock.
As of right now, I'm using CM 11. However I did do a backup of my stock before I did anything to it.
Simplified: How to fix making calls and receiving calls and How to get pass the Odin error "complete(write) operation failed"
Flashing a current modem will/should fix the problem without going back to stock rom.
You can find a modem file for Odin in development section.
Pp.
I have no idea how to find the correct modem. I'm pretty new at this.
Here's a link for the NH7 modem https://www.androidfilehost.com/?fid=23622183712469692
This is courtesy of ShinySide in development section.
Use Odin to flash. Click PDA button to load modem file.
Pp.
This is a link to the d/l rooted samsung firmware https://www.androidfilehost.com/?fid=23622183712469704
Pda button in Odin.
Pp.
PanchoPlanet said:
This is a link to the d/l rooted samsung firmware https://www.androidfilehost.com/?fid=23622183712469704
Pda button in Odin.
Pp.
Click to expand...
Click to collapse
Odin won't let you put the zip file in though. Even when I unzip it.
Odin only takes a Tar MD5 type files. The zip you download has to be unzipped with a program like 7Zip on the PC, there you find the Tar file that goes into Odin.
The modem is a tar file, not zip.
There are some good youtube videos that you can look at for reference.
Pp.
PanchoPlanet said:
Odin only takes a Tar MD5 type files. The zip you download has to be unzipped with a program like 7Zip on the PC, there you find the Tar file that goes into Odin.
The modem is a tar file, not zip.
There are some good youtube videos that you can look at for reference.
Pp.
Click to expand...
Click to collapse
Will the NH7 modem you linked me work for the NK2 firmware I just flashed onto my s4?
Yes it will work. But if you flashed the stock firmware you should have a matching modem.
Nk2 is newer than Nh7.
Pp,
PanchoPlanet said:
Yes it will work. But if you flashed the stock firmware you should have a matching modem.
Nk2 is newer than Nh7.
Pp,
Click to expand...
Click to collapse
It didn't work either. Right now I'm just restoring everything through samsung kies, so hopefully it works out
If Kies connects to your phone you can update and it should fix the problem.
Pp.
PanchoPlanet said:
If Kies connects to your phone you can update and it should fix the problem.
Pp.
Click to expand...
Click to collapse
It didn't help either. Is it a glitch do you think?
What happened with Kies?
Did it connect? Did it run through the process?
Pp.
PanchoPlanet said:
What happened with Kies?
Did it connect? Did it run through the process?
Pp.
Click to expand...
Click to collapse
It connected and successfully reset it.
Still no sound during calls or no ability to make calls?
Pp.
PanchoPlanet said:
Still no sound during calls or no ability to make calls?
Pp.
Click to expand...
Click to collapse
Yup.
tv8961uy said:
Yup.
Click to expand...
Click to collapse
If your still with Tmobile stop by a Tmobile store and ask for a diagnostic, they will hook it up to there super duper diagnostic computer and find out if it's a firmware or hardware problem.
Let me know how you make out.
Pp.
PanchoPlanet said:
If your still with Tmobile stop by a Tmobile store and ask for a diagnostic, they will hook it up to there super duper diagnostic computer and find out if it's a firmware or hardware problem.
Let me know how you make out.
Pp.
Click to expand...
Click to collapse
I'm just going to sell it and buy an s5.
You can get more for it if it's working properly.
Pp.