Develop Bugs

[Q] Tmobile update on stock rooted rom

Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2

When it is rooted even if you try to use the OTA update it won't let you, while rooted, you could alternatively flash the update via ODIN w/ root support. Or try some of the sweet ROMs available , the reason I switched to a custom ROM because I was going to have to erase my phone anyway if I wanted to update, so I thought why not just try a custom ROM?
I use LiquidSmoothRC7, but if you want a more stock feel with touchwiz you can try Wicked, Wicked stays true to the "official stock ROMs" and just adds roots and tweaks the ROM to make it as stable as possible

If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
OR you could listen to this dude

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA

cobraboy85 said:
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
Click to expand...
Click to collapse
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app

Towle said:
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Some of those 10 partitions that are getting rewritten are... for one, your recovery... so that makes 9 actually...
My point is, and I'm not trying to be argumentative in any way, merely objective, is that unless it is reformatting the ext4 partition to new file structure (for example) there should be no need to do this. I suppose I would ask somebody to define in depth "rewritten" and how exactly this is being done and why. Every single update we have had since the release of this device I have not once updated my own device with odin merely to put it back to stock. And I have run into zero issues. Seems like a waste of time to me unless there is something highly critical being restructured entirely. In the end, its all the same disk, and disk size for any given partition.
---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------
neim81094 said:
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you are on LH2, with that same baseband, I would go ahead and update your baseband via docs packaged update in his thread, and just reboot, then move on to the jelly bean updates. Do a factory reset through recovery before you flash the JB ROM tho since you are coming from a completely different version of android.

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.

Just stating my experience, I was rooted stock ics and ran the ota update. I was able to update, keep root and ran stock jelly bean without any problems at all.
Now I am running frosty jelly and still no problems at all. I am not saying for you to do it (dont want anyone blaming me) just stating that it can be done. Do whats most comfortable for you.
Sent from my SGH-T999 using xda app-developers app

jcbofkc said:
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Click to expand...
Click to collapse
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice

cobraboy85 said:
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
Click to expand...
Click to collapse
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.

jcbofkc said:
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
Click to expand...
Click to collapse
Totally dig it. And yeah, just want to know what exactly is being done differently in odin

cobraboy85 said:
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
Click to expand...
Click to collapse
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999

neim81094 said:
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
Click to expand...
Click to collapse
Sorry, I will clarify, I am curious to know why Odin is such a critical issue. I know how it works as far as it being a flashing tool

I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999

neim81094 said:
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
Click to expand...
Click to collapse
The file used to flash with Odin is much larger because it is a complete rom. The OTA is a patch that attempts to patch and modify existing files.

I basically said that on the last post not the one you quoted
Sent from my SGH-T999

Finally got the time to Odin Route66 Jelly bean.
Sent from my SGH-T999 using Tapatalk 2

Everything good?

ZV8 to ZVA Modified OTA (Flash in TWRP)

Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
(Added 10:50 CST)
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

Awesome! Testing this now, I'll post my own results too.
Sent from my LG-LS980 using xda app-developers app

One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.

garwynn said:
Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
Click to expand...
Click to collapse
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!

Any chance this will for stock based ROMs?
Sent from my LG-LS980 using xda app-developers app

@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
If you have debloated the ROM, it probably won't work. I ended up flashing the TOT (pure stock) to get it to flash.
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

youdug said:
@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.
Click to expand...
Click to collapse
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.

garwynn said:
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.
Click to expand...
Click to collapse
im not sure if ill need it but might as well grab it just in case before i start.
thanks man.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
Sorry, didn't clarify the second. I tried stock odex ROM and didn't work. That's why I went the TOT route.

Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
i flashed testupdate 2 no problems here

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on?
latoso said:
i flashed testupdate 2 no problems here
Click to expand...
Click to collapse
and what rom were you on?

mrrogers1 said:
What rom were you on?
and what rom were you on?
Click to expand...
Click to collapse
i was on stock rom

latoso said:
i was on stock rom
Click to expand...
Click to collapse
Stock rooted with just TWRP or Stock rooted Odex or Deodex that @youdug provided here >>> http://forum.xda-developers.com/showthread.php?t=2560115?

latoso said:
i was on stock rom
Click to expand...
Click to collapse
All stock with twrp right?
Sent from my LG-LS980 using xda premium

mchlbenner said:
All stock with twrp right?
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
yes stock rom with twrp

Flashed from stock rom with TWRP 2.6.3.3 using testupdate.zip with no issues. Did not need to use update 2.

If someone that has NOT ran this yet could, please post or PM me their build.prop from the stock + TWRP rom before doing the update?
Thanks:good::good:

garwynn said:
One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.
Click to expand...
Click to collapse
RIP @dougie187
:victory:

[Q] Wi-fi issues across the board. What should I do?

Hello XDA community, my brother has been having wi-fi and bluetooth issues on his T-MO Note II ever since applying the 4.3 OTA. Before I go on, the first thing I did was use CF-auto root and flash both agni pure stock and devil kernel and neither of them have worked. In addition, I have used dr.ketans patch as well as flashing some AOSP based ROMs such as AOKP and SlimKat and neither of them have yielded any results. I have tried almost everything I can find via XDA and I am truly stumped.
Do you guys have any solutions to the wifi issues? Any help would be greatly appreciated! :good:

Can you elaborate, what wifi issues ?
Frequent disconnects ?
Battery drains ?
Sent from my SGH-T889 using xda app-developers app

Wi-fi wil not turn on whatsoever. I can press the icon to turn it on and it will slide to the on position greyed out, and then go back to off right away. The same for bluetooth as well.

If the phone was already on 4.3 then wifi patch was not needed.
I would advise to flash stock image and start fresh. Make sure to wipe dalvik-cache after flashing stock ROM.
Sent from my SGH-T889 using xda app-developers app

Thanks, I will try that when I can. By any chance do you know where I can find a 4.3 image? I've tried looking into the stickies over at the Dev section and they don't have 4.3 as far as I can recall. The only 4.3 image I see is the stock root injected one from Mr.Robinson.

You can download one from sammobile.com. You will have to register though, make sure you download the file for sgh-t889.
Sent from my SGH-T889 using xda app-developers app

Thank you very much. I will do that tomorrow as I do not have the device with me at the current moment. I will let you know how it goes!

to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download

Squilchi said:
to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download
Click to expand...
Click to collapse
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.

leikamkei said:
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.
Click to expand...
Click to collapse
Cool cool just wanted to make sure you got the right tar file. Best of luck
Sent from my N7105 using Tapatalk

I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?

leikamkei said:
I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?
Click to expand...
Click to collapse
Glad to know issue was resolved. By default it's highly unlikely that these problems will return on a stock ROM but if they do then flashing back to stock is the most optimal solution.

Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app

leikamkei said:
Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So close! Hmm it could be hardware I'm not sure either. What are the wifi settings? Also are there any error messages? Did you wipe data after Odin?
Sent from my N7105 using xda app-developers app

I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app

leikamkei said:
I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app

Squilchi said:
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app
Click to expand...
Click to collapse
Just a little update, I booted to stock recovery and performed a factory reset and wipe cache partitions but still nothing after it booted. To answer your question, I did use Odin 3.09 and it was already on MK7 prior to my first flash of the tar file in Odin. This is so frustrating.

Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....

leikamkei said:
Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....
Click to expand...
Click to collapse
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?

Squilchi said:
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?
Click to expand...
Click to collapse
Prior to all this madness, I did try flashing JediMasterX2(I think) and AOKP, two ROMs that I would heavily associate with being stable and basically have everything work. Unfortunately, they didn't work. After all that went down and I restored my backed-up OTA all the way to now, it has been on MK7 stock kernel since then. I'm about to flip a table or something.

[Q] What do I flash to get SGH-M919 working again?

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.

[Q] 4.4.2 No gps fix after update and CM11

Ok where's what I've done.
Went from 4.3 to 4.4 CM11 and since then I have no GPS fix at all, no detection of satelite with gps status.
Even after 1h gpsfix gets not location.
I've tried a wipe
Réinstallation of cm11
New Kernel.
Installation of the stock 4.4 rom still having the same problem!
New Kenel
Flashing the most updated modem.
Here's my info
AP: M919VVLUFN1
CP: M919VVLUFN1
CSC: M919VYVLFNE2
I'm goind nuts!
Any idea?

Updated to nb4 modem?
Sent from my GT-I9505G using Tapatalk

Im running a M919V which is videotron based... I'm not in the right place im I?

joevirus563 said:
Ok where's what I've done.
Went from 4.3 to 4.4 CM11 and since then I have no GPS fix at all, no detection of satelite with gps status.
Even after 1h gpsfix gets not location.
I've tried a wipe
Réinstallation of cm11
New Kernel.
Installation of the stock 4.4 rom still having the same problem!
New Kenel
Flashing the most updated modem.
Here's my info
AP: M919VVLUFN1
CP: M919VVLUFN1
CSC: M919VYVLFNE2
I'm goind nuts!
Any idea?
Click to expand...
Click to collapse
Go here...
http://forum.xda-developers.com/showthread.php?t=1476962
Download the Google Specific No SSL version (first download link). Flash that in recovery. See if that helps.
If it doesn't, try the next one, the Google specific one with SSL
If that doesn't work, look further down the list and use the one specific to your carrier.
If that doesn't work...I dunno.
You will likely have to flash this again when you update the ROM. But no big deal. You can do it in recovery right after you flash the ROM update.

Skipjacks said:
Go here...
http://forum.xda-developers.com/showthread.php?t=1476962
Download the Google Specific No SSL version (first download link). Flash that in recovery. See if that helps.
If it doesn't, try the next one, the Google specific one with SSL
If that doesn't work, look further down the list and use the one specific to your carrier.
If that doesn't work...I dunno.
You will likely have to flash this again when you update the ROM. But no big deal. You can do it in recovery right after you flash the ROM update.
Click to expand...
Click to collapse
Tried it... not working.
I tried installing the 4.3 modem.bin still no go...

Haha. I just flashed a ROM and now my gps is gone. Any updates on this? Or should we just switch to a TW rom?
Sent from my SGH-M919 using Tapatalk

PostMeridianLyf said:
Haha. I just flashed a ROM and now my gps is gone. Any updates on this? Or should we just switch to a TW rom?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
You should read the thread and try the suggestions contained therein first
Sent from my GT-P5110 using Tapatalk

Have you tried allowing Google services permission to use your location? This could be the problem
Sent from my SGH-M919 using Tapatalk

joevirus563 said:
Ok where's what I've done.
Went from 4.3 to 4.4 CM11 and since then I have no GPS fix at all, no detection of satelite with gps status.
Even after 1h gpsfix gets not location.
I've tried a wipe
Réinstallation of cm11
New Kernel.
Installation of the stock 4.4 rom still having the same problem!
New Kenel
Flashing the most updated modem.
Here's my info
AP: M919VVLUFN1
CP: M919VVLUFN1
CSC: M919VYVLFNE2
I'm goind nuts!
Any idea?
Click to expand...
Click to collapse
Try this is worked 4 me.
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2

Yep. @kiruba8 is right. You have to delete the GPS cached data and give it some time and it will fix itself.
Sent from my SGH-M919

mrzhadow said:
Yep. @kiruba8 is right. You have to delete the GPS cached data and give it some time and it will fix itself.
Sent from my SGH-M919
Click to expand...
Click to collapse
Tried it. Still no go.

I did read the thread you Jerk. That's why I asked if op got it working...
Sent from my SGH-M919 using Tapatalk

PostMeridianLyf said:
I did read the thread you Jerk. That's why I asked if op got it working...
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
That was extraordinarily uncalled for.
I pointed to to where I had laid on detailed instructions on what you shoudl try first.
Why you are resorting to name calling because of it is beyond me. Good luck fixing your problem.....on your own.

PostMeridianLyf said:
I did read the thread you Jerk. That's why I asked if op got it working...
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Skipjacks said:
That was extraordinarily uncalled for.
I pointed to to where I had laid on detailed instructions on what you shoudl try first.
Why you are resorting to name calling because of it is beyond me. Good luck fixing your problem.....on your own.
Click to expand...
Click to collapse
I agree postmeridianlyf please go open your own tread as I don't wanna have name calling on mine, I want and answers...

Well see, I asked if op got it working. I appreciate your help in the thread but I'm not going to go flashing files without finding out if it worked or not... Seeing as it didn't, I'll gladly leave.
Sent from my SGH-M919 using Tapatalk

Hi,
So here's what I've done.
First Im pretty sure its related to the modem or radio? is it the same? I remember flashing a 4.3 rom from 4.2 and the network wasnt working so I had to flash a md5 modem.
Now I tried flashing official 4.2.2
No go.
Upgrading official to 4.3
No go
Upgrading official to 4.4
No go
Now I'm back on CM 11 because I like the rom.
I don't know what to do next...

joevirus563 said:
Hi,
So here's what I've done.
First Im pretty sure its related to the modem or radio? is it the same? I remember flashing a 4.3 rom from 4.2 and the network wasnt working so I had to flash a md5 modem.
Now I tried flashing official 4.2.2
No go.
Upgrading official to 4.3
No go
Upgrading official to 4.4
No go
Now I'm back on CM 11 because I like the rom.
I don't know what to do next...
Click to expand...
Click to collapse
If you have flashed official firmware then it is not radio/modem related. It would be hardware related. This is the reason I stay away from CM. It works perfect while you use it but once you go back to TW it causes conflicts for me most of the time. I have used GPS status and cleared the cached GPS data and downloaded the GPS data and it fixes itself within minutes. I also have at least 2 users that had your same issue use the app and followed the instructions and confirmed the method to be working. I believe that CM leaves remnants of the system that cause a conflict with any other system. I had a full wipe file in my extsd but deleted it somehow. I can't remember where I got it from but it does wonders. It wipes everything and prevents leftover crap from the previous ROM or system so there is no conflicts. For example there is a folder in my internal SD called wicked ROM that I cannot delete for the life of me! The only way that I could get rid of it would be going back to stock or flashing the full wipe zip that I no longer have because I lost it. Anyway I will try to find this zip and share with you and you can flash you ROM after. Hopefully it will work for ya.
Sent from my SGH-M919 using XDA Free mobile app

mrzhadow said:
If you have flashed official firmware then it is not radio/modem related. It would be hardware related. This is the reason I stay away from CM. It works perfect while you use it but once you go back to TW it causes conflicts for me most of the time. I have used GPS status and cleared the cached GPS data and downloaded the GPS data and it fixes itself within minutes. I also have at least 2 users that had your same issue use the app and followed the instructions and confirmed the method to be working. I believe that CM leaves remnants of the system that cause a conflict with any other system. I had a full wipe file in my extsd but deleted it somehow. I can't remember where I got it from but it does wonders. It wipes everything and prevents leftover crap from the previous ROM or system so there is no conflicts. For example there is a folder in my internal SD called wicked ROM that I cannot delete for the life of me! The only way that I could get rid of it would be going back to stock or flashing the full wipe zip that I no longer have because I lost it. Anyway I will try to find this zip and share with you and you can flash you ROM after. Hopefully it will work for ya.
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
That would we awesome.
Let me know when you find it.

mrzhadow said:
If you have flashed official firmware then it is not radio/modem related. It would be hardware related. This is the reason I stay away from CM. It works perfect while you use it but once you go back to TW it causes conflicts for me most of the time. I have used GPS status and cleared the cached GPS data and downloaded the GPS data and it fixes itself within minutes. I also have at least 2 users that had your same issue use the app and followed the instructions and confirmed the method to be working. I believe that CM leaves remnants of the system that cause a conflict with any other system. I had a full wipe file in my extsd but deleted it somehow. I can't remember where I got it from but it does wonders. It wipes everything and prevents leftover crap from the previous ROM or system so there is no conflicts. For example there is a folder in my internal SD called wicked ROM that I cannot delete for the life of me! The only way that I could get rid of it would be going back to stock or flashing the full wipe zip that I no longer have because I lost it. Anyway I will try to find this zip and share with you and you can flash you ROM after. Hopefully it will work for ya.
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
Any news about that file?
Thanks.

joevirus563 said:
Any news about that file?
Thanks.
Click to expand...
Click to collapse
I'm in the exact same boat as the op... And I've tried all the same steps to fix it (including the gps app) but with no luck. Only difference being that I'm not on CM. I'm on the 4.4.2 GE ROM (aosp)
Any help here would be GREATLY appreciated! Thanks fellas
Sent from my GT-I9505G using XDA Premium 4 mobile app