Develop Bugs

(Q) can some help with this!!!!

Okay, Heres the thing. I was on TW Stock 4.3 Debloated Odex v1.0. I wanted to try something different plus the TW was getting old, so I wanted to go to a CM based ROM. I tried to flash Liquids ROM and it didnt go through. Ive tried Task's ROM and that didnt work. I want to try and flash the bootloaders but Im scared to brick my phone can someone give me some advice?

I personally have tried everything I know to flash something other than TW on my phone since I got it, with no luck finding anything that will flash and it never made any difference when I was on 4.1.1 or now that I am on 4.3, I really like my SIII but the lack of freedom enforced by Samsung and the carriers has turned me totally against Samsung, my next phone will be a Nexus 5, I am even having trouble with the TW roms I make with now with Android Kitchen, maybe someone else will be able to explain and why nothing, I can find that's being developed for I747M, in the 8 months I had this phone have not been able to find 1 working rom that will flash on the I747M, I am not in Canada though I am in Mexico
Sent from my SGH-I747M using Tapatalk

jimchee said:
I personally have tried everything I know to flash something other than TW on my phone since I got it, with no luck finding anything that will flash and it never made any difference when I was on 4.1.1 or now that I am on 4.3, I really like my SIII but the lack of freedom enforced by Samsung and the carriers has turned me totally against Samsung, my next phone will be a Nexus 5, I am even having trouble with the TW roms I make with now with Android Kitchen, maybe someone else will be able to explain and why nothing, I can find that's being developed for I747M, in the 8 months I had this phone have not been able to find 1 working rom that will flash on the I747M, I am not in Canada though I am in Mexico
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
My thing is, I flash a ROM containing 4.3 cause my phone has TWRP installed. I want to ODIN the bootloaders and see if I want can flash CM ROMs but I dont know if Ill brick my phone. which I hope I dont, Im not going to try it. I guess Im stuck on 4.3 till I figure out something

Ljdd said:
Okay, Heres the thing. I was on TW Stock 4.3 Debloated Odex v1.0. I wanted to try something different plus the TW was getting old, so I wanted to go to a CM based ROM. I tried to flash Liquids ROM and it didnt go through. Ive tried Task's ROM and that didnt work. I want to try and flash the bootloaders but Im scared to brick my phone can someone give me some advice?
Click to expand...
Click to collapse
"It didn't go through" is not giving us much information. You probably got an error, write it down.

polobunny said:
"It didn't go through" is not giving us much information. You probably got an error, write it down.
Click to expand...
Click to collapse
It didnt flash. I tried multiple times, but when I did Task's ROM, it kept saying bootloaders.

Ljdd said:
It didnt flash. I tried multiple times, but when I did Task's ROM, it kept saying bootloaders.
Click to expand...
Click to collapse
What bootloader do you have?

If I am not mistaken you have to update the bootloader to do it
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I assume you have the canadian samsung s3 i747m.
I had this problem as well but I managed to do some digging and fix the problem. The problem was that the developers forgot to add I747MVLUEMK5 as a bootloader in the "updater-script". The updater script is responsible to make sure you don't flash the wrong rom with the wrong samsung model. Since i747mvluemk5 was not added, the phone failed the inspection. To solve this, add the bootloader "I747MVLUEMK5" into the d2att cyanogenmod zip file. Basically, this is what you do:
1) Download the d2att stable 10.2 cyanogenmod
2) unzip the d2att stable 10.2 cyanogenmod
3)And then open META-INF>com>google>android>updater-script
4)Once you found updater-script, open it with notepad
5)Then you must add this bootloader script since it is missing: || getprop("ro.bootloader") == "I747MVLUEMK5"
6)Obviously, don't just copy exactly like mine, but make sure I747MVLUEMK5 is there. Not sure, but i think you can delete one of the bootloaders such as I747MUMBLL1 and replace it with I747MVLUEMK5 instead.
7)after you made your change of the updater-script, rezip the files and flash it.

polobunny said:
What bootloader do you have?
Click to expand...
Click to collapse
I remember one of the 4.3 Roms needed to flash the boot loader, kernel and the Rom.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I went to custom 4.4 ROM and never did the ota so I'm not really sure. Dig through the forums you'll find the solution.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[Q] New User Question Help!!! AT&T S3

Hello everyone,
I have searched far and wide for this and found no answer, so any help is appreciated.
I have a:
AT&T S3 i747
Baseband: i747UCDLK3
I installed CM 10,2 stable the latest version, but unfortunately it gives me a few problems here and there (Front camera problem, and somethings while using data with whatsapp or facebook it freezes and reboots.
My question is, Can I install the latest AT&T firmware Android 4.3 even if it's for a different baseband, or in any case is there a solution for the problems above.
Thanks in advance for any help

kamusa001 said:
Hello everyone,
I have searched far and wide for this and found no answer, so any help is appreciated.
I have a:
AT&T S3 i747
Baseband: i747UCDLK3
I installed CM 10,2 stable the latest version, but unfortunately it gives me a few problems here and there (Front camera problem, and somethings while using data with whatsapp or facebook it freezes and reboots.
My question is, Can I install the latest AT&T firmware Android 4.3 even if it's for a different baseband, or in any case is there a solution for the problems above.
Thanks in advance for any help
Click to expand...
Click to collapse
Nop, you can't. If you need 4.3, you definitely need bootloader update. Atleast to MJ2.
CM require certain bootloader updates for things work perfectly. Check their site. Here they clearly said need an update to bootloader. http://review.cyanogenmod.org/#/c/37696/.
One thing, read before flash. yeah, time matters, but when bricked; again time matter for new device with lot of hard earned $$$.

Native7i said:
Nop, you can't. If you need 4.3, you definitely need bootloader update. Atleast to MJ2.
CM require certain bootloader updates for things work perfectly. Check their site. Here they clearly said need an update to bootloader. http://review.cyanogenmod.org/#/c/37696/.
One thing, read before flash. yeah, time matters, but when bricked; again time matter for new device with lot of hard earned $$$.
Click to expand...
Click to collapse
I found this post http://forum.xda-developers.com/showthread.php?t=2321310
So I should flash the latest bootloader I747UCUEMJB - Oct 11, 2013, so I can install the AT&T firmware?
I was just a little confused because I couldn't find anything on the subject (going from CDLK3 to CUEMJB)
I just want to make sure so I dont brick the phone.
Thanks alot

kamusa001 said:
I found this post http://forum.xda-developers.com/showthread.php?t=2321310
So I should flash the latest bootloader I747UCUEMJB - Oct 11, 2013, so I can install the AT&T firmware?
I was just a little confused because I couldn't find anything on the subject (going from CDLK3 to CUEMJB)
I just want to make sure so I dont brick the phone.
Thanks alot
Click to expand...
Click to collapse
If you ever need to return to stok rom; stick to MG2 for safe. But make sure odin won't update your bootloader afterwards.

Native7i said:
If you ever need to return to stok rom; stick to MG2 for safe. But make sure odin won't update your bootloader afterwards.
Click to expand...
Click to collapse
^ This. There is really no need to go past MG2. And you will still be able to downgrade if needed. I am running MG2 and CM 11 works fine.

Native7i said:
If you ever need to return to stok rom; stick to MG2 for safe. But make sure odin won't update your bootloader afterwards.
Click to expand...
Click to collapse
I can confirm this. I'm on CM 10.2.1 and MG2 bootloader and have no issues. Stick with MG2.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yea, stay away from MJB. My phone just like others works fine on MG2. 4.3 and MJB has only caused headaches around here without very many answers. Of course you are going to have exceptions whose phones are just fine with MJB, but you will have a lot of those headaches if your phone is not one of them.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[BootLoader] [MODEM] Test Odin UVUCNB4

UPDATED BOOTLOADER POSTED.
********************** THIS IS A TEST FIRST. DO NOT, I REPEAT DO NOT TRY TO ODIN THIS BOOTLOADER IF YOU ARE NOT EXPERIENCED. BRICKING YOUR PHONE, FLASH FLOODS, AUDITS, AND EX-GIRLFRIENDS KEYING YOUR CAR ARE NOT MY FAULT. YOU TRY TO ODIN BL OF YOUR OWN FREE WILL. **********************************************
ANY WHO,
Can somebody please flash this via Odin and make sure that it finishes the process. I'm still researching to see if you need a pit to flash the BL by itself.
THanks guys.
DOWNLOAD
LOAD bootloader.tar.md5 INTO BL ON ODIN
START
BL_N900TUVUCNB4
MD5SUM:b9424697d6a75dba43f019825c45a006
CP_N900TUVUCNB4_Modem This CP only contains modem.bin
MD5SUM:52d72b098819991ab88101757d8e2a8a
CP_N900TUVUCNB4_modem2x This CP contains both modem.bin and Non-Hlos
MD5SUM:82ec4cdaff1492439673391902439604
Dev-Host
cp_N900TUVUCNB4_modem.tar.md5 - 53.49 MB​

I'm getting stuck at the first part sli.mbn, but i already have the updated bootloader. From what i've been reading, this new bootloader my not let you downgrade as it's locked (or partially locked, not sure)
So somebody on old baseband looking to upgrade to new baseband should try this out.

has anyone tried this? id do it myself but i'm in the middle of the gulf with slower than slow internet ,took me five min just to write this reply

dragonstalker said:
I'm getting stuck at the first part sli.mbn, but i already have the updated bootloader. From what i've been reading, this new bootloader my not let you downgrade as it's locked (or partially locked, not sure)
So somebody on old baseband looking to upgrade to new baseband should try this out.
Click to expand...
Click to collapse
It's not locked. It's rollback-protected.
Read this whole thread and you will understand why (except in a few unique situations) you cannot downgrade the bootloader: http://forum.xda-developers.com/showthread.php?t=2642207
Upgrading the bootloader and stock ROMs is a one-way street for the majority of us.

dragonstalker said:
I'm getting stuck at the first part sli.mbn, but i already have the updated bootloader. From what i've been reading, this new bootloader my not let you downgrade as it's locked (or partially locked, not sure)
So somebody on old baseband looking to upgrade to new baseband should try this out.
Click to expand...
Click to collapse
Ill try it for you
edit: failed sdi.mbn

deeznutz1977 said:
Ill try it for you
Click to expand...
Click to collapse
I doubt it will work for you either Deezothernutz. You will probably get the same (cannot xmit) error i ended up getting.
However, i did not change the file to a .zip and try running it in recovery

dragonstalker said:
I doubt it will work for you either Deezothernutz. You will probably get the same (cannot xmit) error i ended up getting.
However, i did not change the file to a .zip and try running it in recovery
Click to expand...
Click to collapse
Im still on the old bootloader

deeznutz1977 said:
Im still on the old bootloader
Click to expand...
Click to collapse
Awwww ok. well hopefully it works. It will take some of the strain off the people that can't get the full update.zip. Although, they know eventually they will need to download a rom based off NB4. Don't know what's going to happen when they try to update bootloader while still being on an MI7 rom.

What's the benefits of the new bootloader anyway?

^^^what he said
Sent from my SM-N900T using XDA Premium 4 mobile app

I think the focus is on the wrong thing . Everyone wants the modem not the bootloader. And from past experince with note 2 specifically the modem was made into a flashable zip.
The Demon Galaxy!

diamantericos said:
I think the focus is on the wrong thing . Everyone wants the modem not the bootloader. And from past experince with note 2 specifically the modem was made into a flashable zip.
The Demon Galaxy!
Click to expand...
Click to collapse
no,
some of us need the updated bootloader because the current wave of custom kernels doesnt play nicely with wifi calling and you cant run a KitKat kernel without the KitKat bootloader

3/7/14
dragonstalker said:
OK, people have been asking me for this, and I said I would extract the Bootloader and post it.
********************** THIS IS A TEST FIRST. DO NOT, I REPEAT DO NOT TRY TO ODIN THIS BOOTLOADER IF YOU ARE NOT EXPERIENCED. BRICKING YOUR PHONE, FLASH FLOODS, AUDITS, AND EX-GIRLFRIENDS KEYING YOUR CAR ARE NOT MY FAULT. YOU TRY TO ODIN BL OF YOUR OWN FREE WILL. **********************************************
ANY WHO,
Can somebody please flash this via Odin and make sure that it finishes the process. I'm still researching to see if you need a pit to flash the BL by itself.
THanks guys.
DOWNLOAD
RENAME BY REMOVING THE .md5
LOAD INTO AP ON ODIN
START
BL_N900TUVUCNB5
MD5SUM:ed3330d84eb5893f1235c71d581dfdda​
Click to expand...
Click to collapse
not finishing-fails

XmentalX said:
no,
some of us need the updated bootloader because the current wave of custom kernels doesnt play nicely with wifi calling and you cant run a KitKat kernel without the KitKat bootloader
Click to expand...
Click to collapse
I don't know about Wi-Fi calling but you can run Kitkat kernels with the old bootloader. Everything seems fine to me.

Techniques said:
I don't know about Wi-Fi calling but you can run Kitkat kernels with the old bootloader. Everything seems fine to me.
Click to expand...
Click to collapse
That kernel does not work with wifi calling
Sent from my SM-N900T using Tapatalk

Techniques said:
What's the benefits of the new bootloader anyway?
Click to expand...
Click to collapse
The only "benefit" is running the new TouchWiz kitkat builds with WiFi calling on the TMO network. The new bootloader is otherwise considered a downgrade.

diamantericos said:
I think the focus is on the wrong thing . Everyone wants the modem not the bootloader. And from past experince with note 2 specifically the modem was made into a flashable zip.
The Demon Galaxy!
Click to expand...
Click to collapse
+1
Would like to run the new modem if possible on the old bootloader.
If I have to update the bootloader to run the new modem, then I will do so...but MY main desire is to have the new modem. - I run AOSP, and those all work for either bootloader.

idtheftvictim said:
+1
Would like to run the new modem if possible on the old bootloader.
If I have to update the bootloader to run the new modem, then I will do so...but MY main desire is to have the new modem. - I run AOSP, and those all work for either bootloader.
Click to expand...
Click to collapse
i'll look into the flashable modem then sense people only want that. still trying to figure out why forcing the bootloader is not seeming to work

would like to see this bootloader working as I am planning to flash 4.4.2 via mobile odin and this bootloader via odin pc and hope that knox is not tripped while retaining root. Currently on 4.3 rooted with RDLV.
Sent from my SM-N900T using Tapatalk

hamsup1o said:
would like to see this bootloader working as I am planning to flash 4.4.2 via mobile odin and this bootloader via odin pc and hope that knox is not tripped while retaining root. Currently on 4.3 rooted with RDLV.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I keep seeing that mobile odin says it will trip the counter. Can anybody confirm that for me please.

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

Latest Modem and Kernel from COH4 update

Since I didn't see anyone pull the modem and kernel from the last stagefright update in Sept., thought I'd do it for the few of us that still have this old device.
T889UVUCOH4 Modem: http://www.mediafire.com/download/85es0yrteawo879/T889UVUCOH4_Modem_9_28_15.zip
T889UVUCOH4 Kernel: http://www.mediafire.com/download/w6wdyb3fut6t8c6/T889UVUCOH4_Kernel-9_28_15.zip

Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk

James62370 said:
Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yeah, but you need to be on a stock ROM to get the OTA, or you can download the whole ROM from sammobile.com. It's a security fix for stagefright. I just wanted to try the new modem and see if it made any difference. I won't be able to test the kernel, since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.

Appreciate the info, have you notice better signal with the new radio?

James62370 said:
Appreciate the info, have you notice better signal with the new radio?
Click to expand...
Click to collapse
Maybe a little better signal (?), but basically the same. Haven't been on it real long, I'll have to see if the standby improves after I've been on it a while.

kozmo21 said:
since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.
Click to expand...
Click to collapse
Are you dual booting? Is it possible?

Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.

xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
yikes.. ok thanks. I was going to do this today. I'll wait

xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
Working fine on mine. Did you maybe get a bad download? You could maybe try downloading again?
Which modem did you go back to?

Flashed fine and so far no issues. Previous user might have a bad download or different device.

Flashed via TWRP today.. I had no service after reboot but did another restart and it was working.
Don't know if its any better than the previous modem version but will give it a try. thx

Working great here no issues
With old bootloader md1 4.1.2 with ROMofTHRONESv1.0
Sent from my SGH-T889 using XDA Premium 4 mobile app

My wife's note 2 got this OTA and now the phone won't even turn on....:crying:

tsiah said:
My wife's note 2 got this OTA and now the phone won't even turn on....:crying:
Click to expand...
Click to collapse
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately

kozmo21 said:
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately
Click to expand...
Click to collapse
That's kinda what I was thinking had happened.
I suppose I shouldn't blame the OTA. I just noticed someone else had issues with it too.

so to the people that actually flashed this new modem and kernel, is it working better than previous iterations?

question:
I flashed the C0H4 modem on note 2 (nameless lollipop rom) seems ok...
DO I have to also flash the Kernel ? is there an advantage to flashing the kernel? thx

Hello! Thanks for this! I flashed this over TWRP 2.8.7.1, and wiping my dalvik cache. My phone's originally T889UVALK8 (16gb SGH-T889 t0ltetmo) and the signal drops but after flashing this (C0H4) the signal greatly improved, although I'm having some signal instability since I'm supposed to have full bars because my house is just in line of sight, 2km from the tower. Also I think I'll do a clean install of another custom ROM since I'm using the CM12.1 t0lte nightly, and maybe this affects my signal (I know I'm stupid for doing it but it works).
Welp. After rebooting, the phone lost signal again. I have to do a wipe of dalvik cache to restore my signal. I guess I'll try using another ROM instead.
Upodate: I may be experiencing hardware issues. I have yet to flash back to stock since my phone's signal drops. I can't flash the firmware because it says 'zip signature verification failed.'

kozmo21 said:
Working fine on mine.
Click to expand...
Click to collapse
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!

AuralArch said:
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!
Click to expand...
Click to collapse
It's just the ROM I flashed that makes it say that. That ROM is in my signature... DN4