TMoblify - SM-G935F Nougat with T-Mobile WiFi Calling, VoLTE, RCS - Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec

Update (2018-06-13): This project is discontinued. I no longer have any interest in debugging device-specific issues related to this CSC (like the modem sometimes failing to initialize on the SM-G955F). In addition, the risk of emergency calls not working is too great for me.
With the release of the Nougat beta for the S7 Edge, Samsung finally upgraded their IMS framework from 5.0 to 6.0 in the international ROMs. This gives the international ROMs almost all the functionality needed to support WiFi calling, VoLTE, RCS, and other carrier features on the SM-G935F. This project provides a flashable support package to add the T-Mobile specific components.
Enjoy!
---
NOTE: Because the telephony stack is modified, please ensure that emergency/E911 calls still work. Contact your local authorities to find out how to test emergency calls. Even though modding your device may be fun, a phone is still a phone, and you'll never know if you'll need it in an emergency situation.
---
Current versions:
T-Mobile components:
System: G935TUVS4BQC1
CSC: G935TTMB4BQC1
Flashing instructions
Back up the EFS partition and save it outside of the device. This zip will modify the EFS partition in order to switch to the "TMB" CSC.
Flash TMoblify. This includes the files necessary for the T-Mobile carrier features. It includes a modified copy of the T-Mobile CSC where the network lock is removed.
Reboot.
Downloads:
All downloads are available at: https://mega.nz/#F!VxZhHSiY!MU4N3wk3OFOqvWTJsExZGw
---
All of the files are signed and can be verified with the .asc signature files. To verify the signatures, use your favorite PGP tool or run:
Code:
gpg --recv-key 2233C479609BDCEC43BE9232F6A3B19090EFF32C
gpg --verify filename.zip.asc filename.zip
If the file is valid, a message similar to the following will be printed:
Code:
gpg: Signature made Wed 07 Dec 2016 01:09:33 AM UTC
gpg: using RSA key [b]2233C479609BDCEC43BE9232F6A3B19090EFF32C[/b]
gpg: [b]Good signature from "Xiao-Long Chen <[email protected]>"[/b] [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: [b]2233 C479 609B DCEC 43BE 9232 F6A3 B190 90EF F32C[/b]
XDA:DevDB Information
TMoblify, ROM for the Samsung Galaxy S7 Edge
Contributors
chenxiaolong
ROM OS Version: 7.x Nougat
Based On: TouchWiz
Version Information
Status: Testing
Created 2016-12-07
Last Updated 2018-06-13

Reserved

Reserved

can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??

Nice work :good:
Will this work with 930P sprint variant?

N4MI21 said:
can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??
Click to expand...
Click to collapse
I'm currently waiting for my AndroidFileHost dev account request to be approved. Once that happens, I'll will mirror the files.
As far as VoLTE goes, this is meant for people using the SM-G935F on T-Mobile (USA) only. It will not enable any network features for other carriers.

jkhan49 said:
Nice work :good:
Will this work with 930P sprint variant?
Click to expand...
Click to collapse
Thanks! This will not work with any of the US models, like the SM-G930P (it's a ROM for the Exynos models). However, if I remember correctly, I thought all the US models were compatible and you could simply flash the SM-G935T or SM-G935U firmware.

TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks

A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?

rp3 said:
A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
Click to expand...
Click to collapse
I personally don't know the answer to this. I haven't looked into the differences between the Flat and Edge variants.
rp3 said:
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
Click to expand...
Click to collapse
You should be able to use this in other TW 7.0 ROMs (both odexed and deodexed). The files are from the SM-G935T ROM, but are not device-specific.
rp3 said:
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?
Click to expand...
Click to collapse
SuperSU is currently broken with TW 7.0 due it's method of handling SELinux. You'll need to use Magisk + phh Superuser.
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Superuser: http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
It might be easiest to flash the T-Mobile support package on top of your existing ROM if you're already running TW 7.0.

cstark27 said:
TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks
Click to expand...
Click to collapse
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH

Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?

hollisnh said:
Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?
Click to expand...
Click to collapse
If the ROM is not modified too drastically, I'd imagine it would work just fine.

Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !

Sunnyschlecht said:
Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !
Click to expand...
Click to collapse
Yes, absolutely! I'll update to the latest beta either today or tomorrow. I'll check on the Samsung Cloud backup/restore with the new update.

Thank you so much. Just a heads up the WiFi calling gives me ER08 when trying to connect, so I'm hoping for your magical work.

chenxiaolong said:
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH
Click to expand...
Click to collapse
I haven't tried with Nougat, but that hasn't been an issue for MM.
I'm also using a G935FD with wifi-calling, VoLTE, etc. on T-mobile using Superman 1.17 and TMB CSC via CSC selector (1.8).
From what I've experienced, the second sim slot doesn't come into play unless you're actually using two sims; otherwise it just functions as an SD slot.

I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?

I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
aaronc_98 said:
I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?
Click to expand...
Click to collapse

rp3 said:
I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
Click to expand...
Click to collapse
I will give it a try... I believe that you said you flashed another rom with their default CSC then flashed the TMB support package, but I dont believe that you are saying you got it working with this ROM, is that correct?

Related

[NOVUS][INFO][JFLTESPR][Sprint/Boost Mobile APN-FLASH *SPARK*]

I spent the last few days on my phone learning all about flashing Cyanogenmod, the differences between SPH-L720/SPH-L720T and wanted to put everything I learned about my experience in one thread as it is pulled from countless sites.
I have the Boost Mobile Galaxy S4 SPH-L720T, rooted, flashed CM13(unofficial) with LTE Triband aka "Spark" working, confirmed.
Here is what I know:
1) Sprint Mobile and Boost Mobile are all on the same frequency's.
2) jfltespr Rom for the SPH-L720 also works on SPH-L720T. It's only a Rom, zero difference between the "T" version and regular in terms of the OS, the "T" is hardware.
3) The difference between SPH-L720 and SPH-L720T hardware wise is that the SPH-L720T can receive multiple channels for downloading on the LTE network and the SPH-L720 can only do one, This is the "Enhanced LTE" or "Spark" you hear about.
4) For Boost Mobile, Installing the jfltespr Sprint build for the SPH-L720 or SPH-L720T will not work out of the box. You need to flash the Universal_Boost_APN_Fix-R2.2.zip. After loading in the CM Zip, zip this as well. If you forget, no biggie go back and do it after. This will fix your APN's, label your carrier correctly, which in turn allow you to use LTE, MMS, Triband aka "Spark" (You will not see the spark spiny thing, but it will work, keep reading). Also, side note you may need to wait and/or restart your phone a few times after you are set up with CM. Basically your phone needs to send info to the carrier tower and it all needs to sync up. Mine was fully working in under 20 mins. It's like when you activate a phone for the first time is all.
5) To verify the Triband or "Spark" is working download LTE Discovery App. The Triband or "Spark" Network runs on 800mhz Band 26 for voice, 1900mhz Band: 25 for Up/Down Data, and 2500mhz Band 41 for Down Data but at a higher DL rate. See these articles for more details, Sprint Network Explained, Frequency Faq's
UPDATE: I changed a setting in the MMS, turns out Boost Mobile requires a Username for mobile data to work correctly. This is now Ver. 2.2.
ThomasJoseph315 said:
***Not responsible for your phones,.. follow at your own risk***
After loading in the CM Zip, zip this as well. If you forget, no biggie go back and do it after.
Click to expand...
Click to collapse
Hi there. What do you mean by "zip this as well"? Do you mean upon fresh installing CM we should also add the "Universal Boost APN" zip at the same time (in TWRP for example)?
I am guessing my issue is totally different, but thought I would ask anyways. I have a Samsung S4 on RingPlus (not Boost, but still an MNVO on Sprint). I have CM12 installed. everything works great except MMS. I can send normal text but cannot send (or receive) photos/multimedia. It complains about APN settings. I have a fresh CM installed so I'm willing to try anything to trial and error this thing.
Thanks for any ideas.
-Stephen
stephenphone said:
Hi there. What do you mean by "zip this as well"? Do you mean upon fresh installing CM we should also add the "Universal Boost APN" zip at the same time (in TWRP for example)?
I am guessing my issue is totally different, but thought I would ask anyways. I have a Samsung S4 on RingPlus (not Boost, but still an MNVO on Sprint). I have CM12 installed. everything works great except MMS. I can send normal text but cannot send (or receive) photos/multimedia. It complains about APN settings. I have a fresh CM installed so I'm willing to try anything to trial and error this thing.
Thanks for any ideas.
-Stephen
Click to expand...
Click to collapse
You can flash at the time you install the rom to save the APNs as default, or you can zip any time. However, if you flash after the install your default will be whatever CM's where.
This zip may not fully work for you then, but I did do some googling for you and found this below, if those apn settings work, let me know and I'll try to make a zip for you for future roms and quick flashing
https://bestmvno.com/apn-settings/ringplus-apn-settings/
Do you have a backup of the original Galaxy S4 Boost Mobile firmware?
mykehdoom said:
Do you have a backup of the original Galaxy S4 Boost Mobile firmware?
Click to expand...
Click to collapse
Flash the latest from http://www.sammobile.com and after a few minutes MobileID will run and it will pull and install Boost specific stuff for you.
Sent from my SPH-A120
Can you provide a quick tutorial? I'm not exactly sure what to get from there or how to.
I had to unzip this in Linux for some reason, but after that I got the MD5.
Here is my download if you want it sooner, Sam Mobile is often pretty slow,.... OK3.
https://www.androidfilehost.com/?fid=24438995911976694
SAM MOBILE
http://www.sammobile.com/firmwares/database/SPH-L720T/
Be sure to read the new thread about the Connections Optimizer
@ThomasJoseph315 Every time I flash this zip it says error 7 and will not flash is there a way to get this to work for me I have texts and calls but zero data and I need it for navigation. I am running official jfltespr cm13 on my boost Galaxy S4 thanks in advance.
Ions87l said:
@ThomasJoseph315 Every time I flash this zip it says error 7 and will not flash is there a way to get this to work for me I have texts and calls but zero data and I need it for navigation. I am running official jfltespr cm13 on my boost Galaxy S4 thanks in advance.
Click to expand...
Click to collapse
Did you clear the data, cache and delvik cache first? The only reason I ask is because I made that mistake trying to "test a flash" before I lost all my stuff. Remember, you'll only have the space for the micro Gapps without re-partitioning.
Also, the Boost APN fix didn't work for me, nor the other 9 or so that I tried. Then I came across an old thread where I made a fix for the APN on my old Cyanogenmod setup with my L720 piggybacked off the work of mopedryder. , and I'll be damned. Still works even on my replacement L720T.
Not sure why, but this isn't working with the "Official" build.... Looking into this..
Yea, I was having a bear of a time with the MMS and APN stuff. It looks like they pushed some changes that messed with the "Boost APN fix R2 and also my old fix. What I found works now was hand editing the apns-conf.xml file to just the basics. Nothing but a boost apn and a very cdma apns just in case. Flash rom, flash gapps. After it booted, I copied that in to the /system/etc folder over the old one with file explorer, fixed permissions to match the old file and boom... MMS and LTE after reboot. You can give it a try if you want. Just unzip and copy/paste where I said. Let me know what you get if you try it. Also, let me know if you can edit APN settings while on wifi with this. Just curious. If it works, we can throw it in a flashable zip to flash after gapps.
MMS and LTE working!
I used the flash link provided in this thread Universal_Boost_APN_Fix-R2-2.zip This got me LTE, but still no MMS.
I followed the instructions in the last post, but they didn't work. I kept trying, and had no luck...this was before trying the flash file above.
After getting LTE, I decided to see what I could find inside of the apns-conf file. I checked out the settings and then did some searches for APN settings and found that the line for APN type was potentially misconfigured, so I edited it manually in the apns-conf file, because I REALLY didn't want to flash my phone for the umpteenth time. I also changed the bearer number to "0"
The previous type was: "default,supl,mms,dun,fota"
The type I found through apn.gishan.net was: "default,admin,fota,mms,supl,hipri"
Once I changed that in both lines that the type appeared in and changed the bearer numbers to "0" my MMS started working, as well.
Hope this helps someone out there so they don't have to search as long as I did.
Sprint Samsung Galaxy s4 moved to Boost Mobile
Icky Samsung system, I will not miss you.
Hi everyone, kinda new to the S4 forums. (not Android dev) my current daily driver is a SPARK on boost (running cm13) and my wife has the L720 also on boost. So given that I have the rare opportunity to dig into both activated devices and collect all the radio/modem/APN data from them in order to help this thread and maybe actually contribute something instead of just lurking and reading
So after about 3 weeks of digging and testing and comparing, also trying the edits suggested above on what works for them I have found the proper network settings in the apn-conf.xml. my attempt was to get them as close to the stock ok3 apns as possible and they are very close. MMS works great, LTE shows up right after boot. I also found that after flashing Unerversal_Boost_APN_fix.zip, sometimes mobile data (LTE) would not come back after WiFi was on and then disconnected like when l left the house for work. Toggling airplane mode did no good. Only a reboot would get LTE back. That problem seems to be solved too.
I also took apart the Universal_Boost_APN_fix.zip provided in the op, studied and compared it to stock files and my ok3 modem logs.
In the fixprop.sh, the
sed -i 's/ro.telephony.default_network=.*$/ro.telephony.default_network=8/' /system/build.prop
Command sets the build.prop ro.telephony.default_network to =8
But in both L720 and SPARK, stock boost ok3 the network is =10 so I edited that.
Also I found that
sed -i 's/gsm.operator.numeric.*$/gsm.operator.numeric=311870/' /system/build.prop
Makes the build.prop call for the apns with the numeric tag =311870. but in the apn_conf.xml the apn numeric tag was = 310120 so I just changed the apn to =311870 so now the build.prop will set the right apns on boot.
Something else I found when reading modem logs from both the L720 and the spark is that in the spark, the modem actually calls for
ro.product.name=jflterefreshspr and ro.build.product=jflterefreshspr from the build.prop
I never could find out why it would need that ( and I tried) but my deductive reasoning tells me that it must have to do with initiating tri-band traffic somehow on the network. It only happens on boot but never after that. The L720 ok3 modem does not call for a name from the build.prop at all. So I added commands to the fixprop.sh to change some of the values to the =jflterefreshspr SPARK name and =L720T in the build.prop as well.
Of course, that makes the install.zip proprietary and not unerversal anymore and L720 users would need there own version so here's what I have guys.
All credits go to the original creators of these scripts. All I did was make a few changes.
Flash cm13, gapps(or not), then the APN.zip and reboot.
Note: You might notice after a reboot that the carrier will display as "sprint" but toggling airplane mode then displays "boost mobile" don't worry, it's just a display issue. network and mobile data work with no issues. I think it's something in cm13. started happening around 07/09 nightly
Sorry for the long drawn out post!! :silly:
Links removed... Updated links below
Will this work with other ROMs as well, or only CM?
I want to flash Wicked X, but I'm on boost.
The apn.zips should work on any AOSP ROM.
Not for TouchWiz ROMs
You don't need it for WickedX.
WickedX will install BoostID and set your apn settings right after it boots the first time just like stock boost ROM. After all, it is just the stock Samsung firmware with a bunch of mods added to it.
AOSP(CyanogenMod) is NOT Samsung firmware. It is compiled completely from a different source which is why the .zips are needed
If you're running CM13 stock, CM doesn't use muppets, with my build I did, so might be tempted to do a build soon, might not, truth be told I kinda gave up because of how much of a pain in the ass CDMA and MVNO's are becoming.
ThomasJoseph315 said:
If you're running CM13 stock, CM doesn't use muppets, with my build I did, so might be tempted to do a build soon, might not, truth be told I kinda gave up because of how much of a pain in the ass CDMA and MVNO's are becoming.
Click to expand...
Click to collapse
I totaly agree
UPDATED
These have been tested extensively on both models.
Cell network, MMS, and switching between wifi & cell 3G and LTE work flawlessly.
I've edited them so they can be dirty flashed with ROM updates. They actually seem to work better after a dirty flash now.
Instructions:
In recovery,
Wipe: system, data, cache
Install/flash cm13 nightly.zip
Install/flash Gapps
Install/flash Boost_APNs_(your device).zip
Reboot
Boost_APNs_L720T.zip
Boost_APNs_L720.zip

AT&T Wifi Calling Port?

Hi everyone,
I heard that the AT&T Note5 got an update today to include WiFi calling and the works. I am on AT&T with an n920i model and was wondering if it's possible to rip the WiFi calling from the new AT&T rom and get it working on other variants. I only ask this because I've seen T-Mobile based roms that work on other variants but include T-Mobile's WiFi calling in them.
Just wondering if someone might know or be willing to take a crack at it
abde27 said:
Hi everyone,
I heard that the AT&T Note5 got an update today to include WiFi calling and the works. I am on AT&T with an n920i model and was wondering if it's possible to rip the WiFi calling from the new AT&T rom and get it working on other variants. I only ask this because I've seen T-Mobile based roms that work on other variants but include T-Mobile's WiFi calling in them.
Just wondering if someone might know or be willing to take a crack at it
Click to expand...
Click to collapse
I am almost positive it would have to be a ATT based rom running on our device for it to work
I'm sorry to drag this back up but I found CSC files based for AT&T and used them to replace the CSC files on my N920I. I feel like it's a step in the right direction. Anybody have any ideas?
I've been playing around trying to change csc on my 920i as well.
1. What rom are you on. I'm using Dr. Ketan's nougat rom version n8.
2. Where did you get your At&t CSC files.
I got them off this thread :
https://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911
3. Can you post the CSC AT&T FILES that you are using.
The one's I got work but is buggy! Not sure if it's something I did or that the files are from the At&t note7.
TIA
LouK said:
I've been playing around trying to change csc on my 920i as well.
1. What rom are you on. I'm using Dr. Ketan's nougat rom version n8.
2. Where did you get your At&t CSC files.
I got them off this thread :
https://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911
3. Can you post the CSC AT&T FILES that you are using.
The one's I got work but is buggy! Not sure if it's something I did or that the files are from the At&t note7.
TIA
Click to expand...
Click to collapse
I performed all my csc file changes on stock Marshmallow firmware, originally XSA I believe. I used files from this dev's tool: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
The actual tool will not work on the Note5. It performs a device check and fails to proceed after identifying the model we're using. I ripped the actual CSC files out (Marshmallow ones, not Nougat) and manually replaced them using the TWRP file manager on my device.
My device booted up, and identifies as an N920I with an AT&T CSC. I even have the option to enable Enhanced LTE services, but selecting the option doesn't actually activate it. (I also have an S8+ that is the AT&T variant so I do have WiFi calling and HD Voice activated on my account) I think it's because of the actual ROM, but I'm not sure. I'll have more time to test things out now that I'm done with exams.
abde27 said:
I performed all my csc file changes on stock Marshmallow firmware, originally XSA I believe. I used files from this dev's tool: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
The actual tool will not work on the Note5. It performs a device check and fails to proceed after identifying the model we're using. I ripped the actual CSC files out (Marshmallow ones, not Nougat) and manually replaced them using the TWRP file manager on my device.
My device booted up, and identifies as an N920I with an AT&T CSC. I even have the option to enable Enhanced LTE services, but selecting the option doesn't actually activate it. (I also have an S8+ that is the AT&T variant so I do have WiFi calling and HD Voice activated on my account) I think it's because of the actual ROM, but I'm not sure. I'll have more time to test things out now that I'm done with exams.
Click to expand...
Click to collapse
Thanks for reply.
Did same - ripped - files from devs files.
Though the files I got are from a nougat Rom and I'm using on nougat Rom.
Experience is mostly same as you somethings work some don't.
If you have the At&t S8+ can you roo the csc files from there?
LouK said:
Thanks for reply.
Did same - ripped - files from devs files.
Though the files I got are from a nougat Rom and I'm using on nougat Rom.
Experience is mostly same as you somethings work some don't.
If you have the At&t S8+ can you roo the csc files from there?
Click to expand...
Click to collapse
I'm afraid I can't do any modifications to my S8+ because of a legal obligation to Samsung's Insights program, but I can trying finding the firmware itself online and attempt to rip CSC files from that.
On the other hand, it may not be worth the hassle. Reading up on the S8 forums, it seems how the handle CSC for the S8 devices is different, adding a new partition called userdata which holds the files for the carriers (not sure if I understood that right though). If I had more technical know-how, I would try to port a full AT&T rom that can be flashed through TWRP and try that on my device, but I have no real idea how to approach that.
abde27 said:
I'm afraid I can't do any modifications to my S8+ because of a legal obligation to Samsung's Insights program, but I can trying finding the firmware itself online and attempt to rip CSC files from that.
On the other hand, it may not be worth the hassle. Reading up on the S8 forums, it seems how the handle CSC for the S8 devices is different, adding a new partition called userdata which holds the files for the carriers (not sure if I understood that right though). If I had more technical know-how, I would try to port a full AT&T rom that can be flashed through TWRP and try that on my device, but I have no real idea how to approach that.
Click to expand...
Click to collapse
I hear you ...
Still It was an idea......
Just FYI carrier wifi calling has never ever been successfully (or even remotely working that I've ever seen or recall) ported to another device (same device or not) or firmware. It's been attempted since day one of tmo releasing their wifi calling. So can tell you CSC edits are a waste of time along with ripping all the WiFi calling bits from att firmware and throwing it in yours. Pretty sure even the CM guys tried porting it to tmo devices running cm and got no where with it way back in the day.
Trying to flash an att firmware (minus the Crap that'll fail, bootloader,etc) *might* work as long as you have an att sim but it might even rely on modem.bins too which would most likely fail to flash since you couldn't do it in the past via odin either. Not sure on that one because I use to always have tmo devices and service so never had to bother with that.
ShinySide said:
Just FYI carrier wifi calling has never ever been successfully (or even remotely working that I've ever seen or recall) ported to another device (same device or not) or firmware. It's been attempted since day one of tmo releasing their wifi calling. So can tell you CSC edits are a waste of time along with ripping all the WiFi calling bits from att firmware and throwing it in yours. Pretty sure even the CM guys tried porting it to tmo devices running cm and got no where with it way back in the day.
Trying to flash an att firmware (minus the Crap that'll fail, bootloader,etc) *might* work as long as you have an att sim but it might even rely on modem.bins too which would most likely fail to flash since you couldn't do it in the past via odin either. Not sure on that one because I use to always have tmo devices and service so never had to bother with that.
Click to expand...
Click to collapse
I think I've seen some users on the s7 forums saying they actually got it working. Maybe it was T-Mobile though...
Regardless, you've given me an idea regarding the CSC. The files I used were from the s7, but they were the qualcomm variant. The Note5 is all exynos variants, so using qualcomm files may cause incompatibility.
But if I pull CSC files from the AT&T Note5 rom, then it might work.
Everything is a long shot. The Note5 isn't my primary device anymore which is why I feel alright taking risks and flashing different things. It's like how that saying goes, you'll miss all the shots you never take.

LOST IMEI - Please Help

I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Geekser said:
I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Click to expand...
Click to collapse
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
d.cortez said:
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
Click to expand...
Click to collapse
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
michelino159 said:
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Click to expand...
Click to collapse
Neither Option worked for me - ODIN Flashes got stuck halfway thru the flash - and Smart Switch just didn't work
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
d.cortez said:
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
Click to expand...
Click to collapse
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Geekser said:
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Click to expand...
Click to collapse
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
d.cortez said:
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
Click to expand...
Click to collapse
I have an IMEI number from a Note 9 that was an aTT Phone - I had purchased the snapdragon varient at Best buy and then returned it when I got the N960F . I copied the IMEI number before I turned it in - I suppose I could use that. Can you offer a link to the thread you are referring to?
thanks for the tip my friend.
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
dev base is Alexander rom in the development section.
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
If I am not mistaken, it was something like this https://forum.xda-developers.com/galaxy-note-9/development/test-s2arh6-devbase-v5-9-encryption-t3847061
you do need to have TWRP installed in order to flash
hope that helps
still need help
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
Do you still need help here is the link to the firmware that I used to flash stock ROM make sure you read what and how it is to be done the first time i flashed it i got stuck in bootloop and then i read it again and got it right now my phone works and is fine hope you have your phone working https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478

How to get SM-N920I to detect VoLTE in india without root

Hi fellow XDA members,
I own a Galaxy Note 5 (SM-N920I) which was bought in Singapore under operator Starhub (STH). I happen to use this phone in India and I later realized the phone supports VoLTE but the firmware didn't so I stuck with using the Jio4GVoice app for a long time now and I'm done with it due to lot of bugs and call drops.
I looked online for solutions and found many that involved root or custom recovery to flash the so-called VoLTE fix. I have read articles that said the Indian firmware supports VoLTE so I So, I tried the following:
Download the Indian firmware and flashed via odin. But it fails with error specified file not found. Did a research and i unchecked the Re-partition and again tried and it fails at flashing system . So I re-flashed the STH firmware to get the phone boot up. I learnt that CSC is responsible for getting the region specific network to work.
Extract CSC from Indian firmware and simply flash it on odin. But, as articles say that I'll have 4 files for each boxes to place in odin I only had one tar (<firmware_HOME_tar.md5). Then I read, extracting the modem.bin file and ziping that to a tar file and flash it via odin will help. I tried that but no luck (should I factory reset it?).
Both the firmwares have a single file and articles say that there will be CSC_<firmware>.tar and CSC_HOME_<firmware>.tar.
I don't know where I'm getting wrong. Is this even possible or i'm simply wasting my time? I use samsung pay and S health extensively so I don't wanna trip knox.
Update:
I read that cache.img is CSC from here. So extracted the cache from Indian firmware and flashed that to my phone that has STH firmware. I used the Phone info app and found baseband has been changed and available CSC shows INS but active CSC is STH. Now I guess i just need to activate that CSC. I tried the steps mentioned here but it doesn't work.
https://imgur.com/9Fiy4W4
https://imgur.com/vVe6LDQ
ksbalajee said:
Hi fellow XDA members,
I own a Galaxy Note 5 (SM-N920I) which was bought in Singapore under operator Starhub (STH). I happen to use this phone in India and I later realized the phone supports VoLTE but the firmware didn't so I stuck with using the Jio4GVoice app for a long time now and I'm done with it due to lot of bugs and call drops.
I looked online for solutions and found many that involved root or custom recovery to flash the so-called VoLTE fix. I have read articles that said the Indian firmware supports VoLTE so I So, I tried the following:
Download the Indian firmware and flashed via odin. But it fails with error specified file not found. Did a research and i unchecked the Re-partition and again tried and it fails at flashing system . So I re-flashed the STH firmware to get the phone boot up. I learnt that CSC is responsible for getting the region specific network to work.
Extract CSC from Indian firmware and simply flash it on odin. But, as articles say that I'll have 4 files for each boxes to place in odin I only had one tar (<firmware_HOME_tar.md5). Then I read, extracting the modem.bin file and ziping that to a tar file and flash it via odin will help. I tried that but no luck (should I factory reset it?).
Both the firmwares have a single file and articles say that there will be CSC_<firmware>.tar and CSC_HOME_<firmware>.tar.
I don't know where I'm getting wrong. Is this even possible or i'm simply wasting my time? I use samsung pay and S health extensively so I don't wanna trip knox.
Update:
I read that cache.img is CSC from here. So extracted the cache from Indian firmware and flashed that to my phone that has STH firmware. I used the Phone info app and found baseband has been changed and available CSC shows INS but active CSC is STH. Now I guess i just need to activate that CSC. I tried the steps mentioned here but it doesn't work.
https://imgur.com/9Fiy4W4
https://imgur.com/vVe6LDQ
Click to expand...
Click to collapse
here is another method you can try. but this only works if your phone supports it.
For firmware that uses a multi-csc code, you need to select a sales code before attempting to connect to a cellular network. This is especially true for 3G and 4G connections.
There are two ways to select a sales code:
1. Enter *#06# in the phone dialer to obtain the IMEI number for the device. You can then enter *#272*Device IMEI# to select a sales code. If your Samsung device does not return a menu, the product code is not a multi-csc code.
OR
2. Install an CSC changer app, such as the "Phone INFO" app. CSC changer apps do require root access, and they do not work on all phones and all versions of Android.
Hit thanks if it helps !
P.S. IT ONLY WORKS ON STOCK ROM ...! so you need to be on Stock Rom.
dark_phoenix said:
here is another method you can try. but this only works if your phone supports it.
For firmware that uses a multi-csc code, you need to select a sales code before attempting to connect to a cellular network. This is especially true for 3G and 4G connections.
There are two ways to select a sales code:
1. Enter *#06# in the phone dialer to obtain the IMEI number for the device. You can then enter *#272*Device IMEI# to select a sales code. If your Samsung device does not return a menu, the product code is not a multi-csc code.
OR
2. Install an CSC changer app, such as the "Phone INFO" app. CSC changer apps do require root access, and they do not work on all phones and all versions of Android.
Hit thanks if it helps !
P.S. IT ONLY WORKS ON STOCK ROM ...! so you need to be on Stock Rom.
Click to expand...
Click to collapse
Thanks for your help. I tried solution 1 and it Worked
However, before trying out your solution, my device was in this state:
1. Flashed Singapore ROM
2. Extracted every file from Indian rom and repacked the tar except the system.img (as this was failing to flash in odin)
3. After booting I got a notification from SupportAgent telling me that unauthorized changes have been made, tap here to reboot to undo those changes
4. I then read your solution and updated the CSC to INS from STH. And device got factory reset and for the first time I saw VoLTE logo on my phone :victory:
5. I finished the setup and still getting the same error in notification from SupportAgent. So I tapped on it, and device rebooted to a new blue screen with sim card logo on it and then boot up to system.
6. Now, in the quick settings, VoLTE toggle is gone and I got WiFi Calling toggle instead. However I still have the VoLTE icon on the status bar.
7. So later that day, I redo all the steps.
- Flashed Singapore firmware (This time, the CSC Country was Singapore and the active CSC was XTH instead of STH. There was VoLTE toggle)
- Flashed Cache from Indian Firmware (CSC Country changed to India the active CSC was INS automatically. Now got WiFi Calling toggle)
8. I noticed other changes in the software:
- The gallery App doesn't show Grid view so I'm stuck with List view
- The Samsung Pay says, its not supported for this device
What do you think about this?
ksbalajee said:
Thanks for your help. I tried solution 1 and it Worked
However, before trying out your solution, my device was in this state:
1. Flashed Singapore ROM
2. Extracted every file from Indian rom and repacked the tar except the system.img (as this was failing to flash in odin)
3. After booting I got a notification from SupportAgent telling me that unauthorized changes have been made, tap here to reboot to undo those changes
4. I then read your solution and updated the CSC to INS from STH. And device got factory reset and for the first time I saw VoLTE logo on my phone :victory:
5. I finished the setup and still getting the same error in notification from SupportAgent. So I tapped on it, and device rebooted to a new blue screen with sim card logo on it and then boot up to system.
6. Now, in the quick settings, VoLTE toggle is gone and I got WiFi Calling toggle instead. However I still have the VoLTE icon on the status bar.
7. So later that day, I redo all the steps.
- Flashed Singapore firmware (This time, the CSC Country was Singapore and the active CSC was XTH instead of STH. There was VoLTE toggle)
- Flashed Cache from Indian Firmware (CSC Country changed to India the active CSC was INS automatically. Now got WiFi Calling toggle)
8. I noticed other changes in the software:
- The gallery App doesn't show Grid view so I'm stuck with List view
- The Samsung Pay says, its not supported for this device
What do you think about this?
Click to expand...
Click to collapse
are you still able to use voLTE ?? after these steps.
about Support agent. Ignore it if you can. or skip it. you do not need this as there aren't any official updates after this. (this is only because now system knows that you have modified it, and it will not receive any update. if you can the disable the Support agent app via settings or if possible via root.)
samsung pay will Not work. as knox should have been tripped to 0x1, so Samsung pay like apps will NEVER work after knox trip.
ksbalajee said:
Thanks for your help. I tried solution 1 and it Worked
However, before trying out your solution, my device was in this state:
1. Flashed Singapore ROM
2. Extracted every file from Indian rom and repacked the tar except the system.img (as this was failing to flash in odin)
3. After booting I got a notification from SupportAgent telling me that unauthorized changes have been made, tap here to reboot to undo those changes
4. I then read your solution and updated the CSC to INS from STH. And device got factory reset and for the first time I saw VoLTE logo on my phone :victory:
5. I finished the setup and still getting the same error in notification from SupportAgent. So I tapped on it, and device rebooted to a new blue screen with sim card logo on it and then boot up to system.
6. Now, in the quick settings, VoLTE toggle is gone and I got WiFi Calling toggle instead. However I still have the VoLTE icon on the status bar.
7. So later that day, I redo all the steps.
- Flashed Singapore firmware (This time, the CSC Country was Singapore and the active CSC was XTH instead of STH. There was VoLTE toggle)
- Flashed Cache from Indian Firmware (CSC Country changed to India the active CSC was INS automatically. Now got WiFi Calling toggle)
8. I noticed other changes in the software:
- The gallery App doesn't show Grid view so I'm stuck with List view
- The Samsung Pay says, its not supported for this device
What do you think about this?
Click to expand...
Click to collapse
i need to know too.. did volte worked after all? im doing the same thing but not working
prasadmanjulago said:
i need to know too.. did volte worked after all? im doing the same thing but not working
Click to expand...
Click to collapse
I have dropped that phone the very next day and got my screen shattered and entire display turned dark. I'm not sure whether it worked
ksbalajee said:
I have dropped that phone the very next day and got my screen shattered and entire display turned dark. I'm not sure whether it worked
Click to expand...
Click to collapse
There was a enfenforceskippingpackages.xml file.. deleted every line in there..it worked after..if anyone need more info, pm me or mail [email protected]

Help ... no network

Hello guys,
So I have a galaxy note 9 n960f that was rooted with magisk and twrp on android 9.
Today I flashed android 10 Q via Odin.
Everything is perfect except now I have no network.
IMEI information is also correct but still no network.
Any help would be very appreciated.
Thanks
snanahmd said:
Hello guys,
So I have a galaxy note 9 n960f that was rooted with magisk and twrp on android 9.
Today I flashed android 10 Q via Odin.
Everything is perfect except now I have no network.
IMEI information is also correct but still no network.
Any help would be very appreciated.
Thanks
Click to expand...
Click to collapse
did u flash the proper country CSC and proper version?
was your phone originally a network locked phone or unlocked phone?
where did u download the files?
did you flash with your network sim inside?
pheonixxdark said:
did u flash the proper country CSC and proper version?
was your phone originally a network locked phone or unlocked phone?
where did u download the files?
did you flash with your network sim inside?
Click to expand...
Click to collapse
Yes i downloaded files from sammobile for my country.
my phone is n960f and it was rooted with magisk before i flashed the files.
and yes i don't remember exactly but i think my sim was inside when i flashed.
i had this kind of problem before when i had note 4 and i used to flash a patched modem and it worked but i don't know if there are patched modems for note 9.
snanahmd said:
Yes i downloaded files from sammobile for my country.
my phone is n960f and it was rooted with magisk before i flashed the files.
and yes i don't remember exactly but i think my sim was inside when i flashed.
i had this kind of problem before when i had note 4 and i used to flash a patched modem and it worked but i don't know if there are patched modems for note 9.
Click to expand...
Click to collapse
ah yes.. i remember that too with the note4. but since this is stock its a problem. im not sure but try and flash a multi CSC file like OXM downloaded via frija without the sim and see what would be the outcome. then phone will be on its original CSC im assuming..
Similar issue. Network connectivity was perfect with stock (rooted) N960f/DS running Android 10, though as soon as I flashed havoc, evolution, or crDroid I lost the ability to talk to my network (Verizon in the US), tried flashing my csc which worked fine with rooted android 10, no help, tried manually connecting to Verizon's APN, switching network mode, and manually selected my network, nothing seemed to fix it besides reflashing my android 10 software
Working Android 10 software -
Ap - N960FXXU5ETF5
CP - N960FXXU5ETEC
CSC - N960FOXM5ETEC
nbgorman said:
Similar issue. Network connectivity was perfect with stock (rooted) N960f/DS running Android 10, though as soon as I flashed havoc, evolution, or crDroid I lost the ability to talk to my network (Verizon in the US), tried flashing my csc which worked fine with rooted android 10, no help, tried manually connecting to Verizon's APN, switching network mode, and manually selected my network, nothing seemed to fix it besides reflashing my android 10 software
Working Android 10 software -
Ap - N960FXXU5ETF5
CP - N960FXXU5ETEC
CSC - N960FOXM5ETEC
Click to expand...
Click to collapse
yeah usually this happens if you have a rooted phone and you flash something via odin.
unfortunately there no patched modem/ baseband for android 10 on note 9. i got it fixed from a local shop, they had a developer patch the rom manually.
so i am basically stuck with this rom until i can get a patched rom to upgrade.
with the note 4 i had a patched modem file and i had my efs folder backed up so if this happened or my IMEI got corrupted, i would just restore IMEI and flash the modem file via recovery and everything was perfect.

Categories

Resources