Develop Bugs

[GUIDE] How to enable LTE on the Mobilicity / Wind / Vidéotron T889V

Hello everyone,
If you're using an SGH-T889V (originally from Vidéotron, Wind or Mobilicity) on a carrier that runs LTE on the AWS band, e.g.: Rogers, Bell, Telus, Fido, Virgin Mobile Canada, Koodo, AT&T or T-Mobile; this will allow you to enable LTE.
Note: Vidéotron has launched their LTE network in September 2014. As of writing this, it is unclear whether there will be a new T889V modem released with LTE enabled in the coming weeks, much like there was with T-Mobile USA when they launched their LTE network.
If you're using a T-Mobile USA SGH-T889, this guide isn't for you.
The usual disclaimers apply.
Actually, let me rephrase that: This mod permanently damages your phone, and irrevocably voids your warranty.
No one has been able to flash back to a T889V modem (be it ALJ4, BMA3, CMK4 or DNE7) without encountering bootloops afterwards.
Interestingly, T889VVLUDNH2 did not bootloop, it simply showed an "unknown" IMEI and baseband with no network connection.
Some background:
A rather lengthy post explaining what I did and what happened
TL;DR version of same
Additional relevant threads:
Getting LTE to work on fido
Need Help Please WIND 889V Borked
You'll need:
LTE - Coverage, known working microSIM, proper plan and system provisioning, etc...
Proper APN settings for your carriers on hand. (Better yet if you're running TouchWiz ROMs: proper CSC files and knowledge on how to modify and apply those.)
ADB
Clockworkmod/TWRP recovery
CWM/TWRP flashable I317M modem image. (I originally used the BMA3 modem, although the mod should work with any of them.)
Bell/Rogers/Telus I317M modem files
I317MVLALJ2 4.1.1 initial release (This one could be of interest for unlock purposes...)
I317MVLBMA3 4.1.2
I317MVLUCMK5 4.3
I317MVLUDNF1 4.4.2
I317MVLUDNF3 4.4.2 (I haven't downloaded the full Odin image and prepared a zip for this one.)
I317MVLUDNH2 4.4.2
Mobilicity/Vidéotron/Wind T889V modem files.
T889VVLALJ4 4.1.1 initial release - CAUTION: flashing this on top of a working ALJ4 modem installation has been known to cause bootloops and NV item corruption.
T889VVLBMA3 4.1.2
T889VVLUCMK4 4.3
T889VVLUDNE7 4.4.2
T889VVLUDNH2 4.4.2
Once you've downloaded the above files:
Backup your NV settings (in CDMA Workshop text format) as per this thread. You can also use the EFS Professional Tool (currently at version 2.1.61) almost identically to the older NV_reader_writer tool. (It also contains the IMEI NV item generator functions that Peoplearmy's tool had, apparently gone missing too.)
The only things I'll add are that:
RMNET + DM + MODEM is not available, you'll have to use RNDIS + DM + MODEM instead.
Finding the COM port can be done in device manager, you may need to refresh devices or disconnect and reconnect the USB port. If it's been properly detected, you can also click the Port text to the left of the droplist, there's an autodetect function there.
Also use this guide to backup (in QPST/QXDM .qcn format): http://forum.xda-developers.com/showthread.php?t=1946915
Optional: Backup the raw mk9efs partitions too, as per @connexion2005's suggestion: http://forum.xda-developers.com/showthread.php?t=2079705 (they're not necessary for the mod itself, and are only made as an additional precaution)
Optional: Backup the raw mk9efs and efs partitions with this CWM or TWRP "flashable" zip based on the Synergyrom team's work. It outputs the dumps in a ready-to-flash restore zip.
Consider backing up other files and data from your phone with the usual complement of Titanium Backup, nandroid and so on. Copy those off the phone.
If you're running an AT&T or T-Mobile ROM: you may have to flash another ROM as well. The stock T889V ROM has a "Network Mode" setting that lets you toggle between LTE/WCDMA/GSM, WCDMA only and GSM only. The I317M and N7105 ROMs also have this, while the I317 and T889 probably don't.
On the T889V ROMs: to see LTE become an option, you'll need to edit your CSC files and remove the <CscFeature_Setting_DisableNetworkMode>lte</CscFeature_Setting_DisableNetworkMode> line in /system/csc/others.xml. This setting is only cosmetic: the notification bar icon will show "4G" and you won't see LTE in the network mode settings. However, the phone will still use LTE, which can be confirmed by looking in Settings / About Phone / Status. (I've come across this while flashing ROMs with unaltered CSC files.)
Let's proceed with the actual modification:
Reboot to recovery, flash the 317M BMA3 modem. Wipe /cache and Dalvik cache for good measure.
Reboot phone. No bootloops? Good.
Check in Settings / About Phone that you still have a valid IMEI. (It's possible you still do at this point.)
Reboot the phone. This time the IMEI and service should be lost.
Using the same procedure you did to back them up, restore your NV items.
Reboot the phone.
Confirm your IMEI is correct and that you have service.
Check in Settings: Wireless and networks -> More settings -> Mobile Networks -> Network Mode that LTE/WCDMA/GSM is selected. Another menu worth mentioning here is the "Band Selection" menu accessed through the *#2263# dialer code. Note that if you force the phone onto the LTE bands, you will only have data service, and no voice calls or SMS.
I'd like to thank the following users for their help and feedback in writing this guide: @Byangmang, @deeznutz1977, @dspkeff, @hkfan, @rail205, @TEKHD
Good luck,
Darkshado

Thank you so much. I have been waiting for this day to come. All the best, Darkshado! :beer:
Sent from my SGH-T889 using xda app-developers app

Works. Thanks allot. Only thing I didn't do is restore the 3 files backed up via adb.

jfive74 said:
Works. Thanks allot. Only thing I didn't do is restore the 3 files backed up via adb.
Click to expand...
Click to collapse
Those are very much a belt and suspenders bit. They're not to be restored in the instructions, and my inclusion here is mostly because connexion2005 had requested a set for a JTAG repair. I'm taking a guess here, but if there's any calibration data or other phone specific parameters in there, having those from your device on hand can't be bad.

What if I suffer boot loops, didn't do any backups, and my IMEI is already Zeroed out on my T889V? How can I fix this?
I have my IMEI still since it's written on the purchase box of the phone.
I used to be wind, now virgin mobile with LTE sim. I flashed tmobile modem. No love. Flashed T889V modem back, then got boot loops.
Please help!!!
edit:
Hi Darkshado, really hoping you can help.
I've done more reading. I can't seem to make the boot loops stop.
I've done odin to factory rom image. No luck.
I tried i317 custom modem you have here on XDA, no luck. Also Tmobile modem, etc... no luck.
I used CWM and permission fix, etc.. no luck.
My boot loop is a little weird. It will boot and stay live (working - no signal though) for about a min, then it will say some android.media.process is not responding and reboot.
So I can't get NV to inject my IMEI as it will reboot too soon. From what I read, NV needs 5-10 min??
basically, I did JEDIX-15 tmobile rom install with latest tmobile modem. That's how I got into this mess. I have a T889V and virgin LTE sim such as yourself.
I just can't seem to make the boot loops end so I can move forward....

Try writing flashing back the T889 baseband and restoring a T889 or T889V NV items backup.
http://www.mediafire.com/download/p5025pxtp9vgk4k/NV_items.7z

Will this do?
T889UVBMD1
from: http://forum.xda-developers.com/showthread.php?t=2102380
I'm going to try and odin the factory image and see if that stops the reboots.
I'm guessing baseband is the same as modem correct?
I'll go give it a try now and use CWM to inject it first before I odin.
I've never done an NV restore let alone backup, so that seems to be my hick up. I'll do some research and get that done then and get back to you.
Thanks for the assistance.
edit:
I'll try to write NV, but that might be an issue since I need the phone not to reboot, and it does in under a minute usually.
Any suggestions, or specific rom I can try to write so I can eliminate the reboots so I can do the nv?
edit2:
ok, the tmo modem from that link above worked. It's not boot looping after a min now!
There is still zero signal. Does not connect. When I do *#2263# and choose automatic, it says menu does not exist, etc...
going to to try inject my IMEI with NV.
Will report back.
Edit 3
Ok, just used nv read/write to inject your t889v nv file. Then generated my imei and injected that.
reboot, and got signal! yay.
thank you so much!\
When I go to settings. I only see WCDMA/GSM/AUTO. No LTE option. I think I read somewhere that is cosmetic?
If I NV write the T889 NV file from deeznutz1977 will that fix it cosmetically?
Thanks again!
Darkshado said:
Try writing flashing back the T889 baseband and restoring a T889 or T889V NV items backup.
http://www.mediafire.com/download/p5025pxtp9vgk4k/NV_items.7z
Click to expand...
Click to collapse

20% More Awsomeness
I switched over to Telus sine Mobilicity is going under . I could only get HSPA+ @ 5Mbps, Now I too have fully working LTE. Albeit with weaker signal strenth due to higher band freqency. But I can just toogle LTE when needed. I must admit that second reboot with IMIE 0 and no service was a bit nerve racking, but the backup was flawless. Thanks a million OP. ^_^

i edited the csc called other....
and the LTE line was already not present.
The LTE option is still not in the mobile settings however.
When I do the *#2263# menu and set it to LTE the data does keep working. And I do see it in the system info. Also using a tmobile radio with the JEDI-X15 rom. yay.
But I'd like to solve the cosmetics side of it.
I did inject the t889V nv setting.... could that affect it? Would the t889 NV settings fix it?
edit:
still no luck getting LTE option to appear, although it works, I'd like to solve the cosmetic side of it.
Any help?

You can also get confirmation that LTE is active by checking in About phone / Status.
I don't feel like going through the 664 pages of the Jedi X ROM thread to see if they've altered the network icons or not. Being based on the N7105 ROMs icons with either "4G" or "LTE" captions should be present. Are you editing the active CSC files? Namely those in /system/csc/ ?
I should mention that some CSC edits only apply upon factory reset, e.g. activating WB-AMR, (a.k.a. HD Voice). One neat trick is to make a backup in recovery (nandroid or TWRP), factory reset, then reboot to recovery and restore the backup. I don't recall if this applies to the network icon related lines or not.

Older Modems
Question?
As I stated before it was a smooth transition. But... Some claim the older modem worked better (I317M-I317MVLALJ2). I tried through TWRP as before but the return status says FAILED. No changers are thus made. Any ideas? Thanks.

I've been able to flash back and forth between ALJ2 and BMA3. You're saying the linked ALJ2 zip refuses to flash? I'll have to check, but this might take a few days as I'm:
-rather busy IRL
-stuck using my old laptop (mushy, thoroughly worn out keyboard with an overzealous enter key that fires the moment you hint at touching it and a dead left shift key) while the other is in warranty repair (failing PSU seems to have damaged the motherboard and/or dGPU)
Goodbye,
Darkshado

Darkshado said:
You can also get confirmation that LTE is active by checking in About phone / Status.
I don't feel like going through the 664 pages of the Jedi X ROM thread to see if they've altered the network icons or not. Being based on the N7105 ROMs icons with either "4G" or "LTE" captions should be present. Are you editing the active CSC files? Namely those in /system/csc/ ?
I should mention that some CSC edits only apply upon factory reset, e.g. activating WB-AMR, (a.k.a. HD Voice). One neat trick is to make a backup in recovery (nandroid or TWRP), factory reset, then reboot to recovery and restore the backup. I don't recall if this applies to the network icon related lines or not.
Click to expand...
Click to collapse
yep, I edited those CSC files as per your original write up.
I did not factory reset. And yes, you are right. A good example is the Nexus 4. It needs a factory reset to keep the LTE settings ( unless you go to the "INFO" menu, and then you need to reset again.
Okay, I'll try the reset tonight. See what happens. And yes, I see LTE in system info.
Also, when I use speedtest, it records it as lte.
Honestly, I'm just happy it works again...

Darkshado said:
I've been able to flash back and forth between ALJ2 and BMA3. You're saying the linked ALJ2 zip refuses to flash? I'll have to check, but this might take a few days as I'm:
-rather busy IRL
-stuck using my old laptop (mushy, thoroughly worn out keyboard with an overzealous enter key that fires the moment you hint at touching it and a dead left shift key) while the other is in warranty repair (failing PSU seems to have damaged the motherboard and/or dGPU)
Goodbye,
Darkshado
Click to expand...
Click to collapse
Problem Solved. The issue was I am using SDCard encryption. For some reason TWRP can SEE the cards files, but not use them. When I moved the modem to internal it installed fine. Sorry bout that.

If I enable lte using this method then will aws still works for WindMobile?
Sent from my SGH-T889 using Tapatalk 2

hkfan said:
If I enable lte using this method then will aws still works for WindMobile?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Probably Not? There are threads of people trying to get there i317 to work with AWS. http://forum.xda-developers.com/showthread.php?t=2068041
Then again this is a t989v. Don't risk it unless your prepared to not go back.

hkfan said:
If I enable LTE using this method then will AWS HSPA still work for WindMobile?
Click to expand...
Click to collapse
It should. My data in this department is very limited, since I don't have an active Videotron account on hand. With that said, I got a working speed test on Videotron's AWS HSPA shortly after sorting my phone out this winter. (I simply dropped by one of their stores while at a shopping mall and nicely asked a sales rep to borrow an active SIM card. Showed her the menu unlock method as a thank you.)
I also got to use the phone with T-Mobile USA earlier this year, getting both HSPA (some of it likely AWS, though I didn't get the time to check) and LTE.

@Darkshado thank you very much for the T889VVLUDNE7 modem. I just flash the zip in cwm and it work perfect for my Videotron T889V.

Thanks for putting this together!!
Quick question - I have a t889v from Wind Mobile. I switched carriers to Rogers, and in the process screwed up my phone and had no IMEI/Baseband. Had to send it in for repair to replace the board. It came back with the baseband T889UVUCMK7.
Do you think I can still use this method? I'm currently running a T-mobile Touchwiz 4.4.2 ROM (Test Rom v1.2).

What does download mode give as product ID? You may well have a U.S. board in there now.
The later T-Mobile T889 basebands support LTE out of the box. Make sure your APN settings, plan and SIM card are correct, and that the modem you have does support LTE; if not, you might just need to update that.
I know some people here followed essentially the steps I did, but with the T889 modem instead, but I don't think it applies here.
Good luck,
Darkshado
Sent from my T0LTE using XDA Free mobile app

US998 to LS998 *Sprint LTE + Root*

If you mess up your device I'm not responsible, it works for me, and for others. I will help as much as i can, but it is on YOU, the user to follow the prerequisites and read carefully. This zip was created in collaboration with @TxanMoe and myself
This zip can be used to return to the stock rom(for the most part, you'll still have fastboot,root,twrp) as long as you can get into TWRP recovery on the device. It also flashes the modem bands needed for working Sprint LTE(bands 25,26,41, ect.."all the Sprint bands")
Prerequisites:
1. Activate with Sprint first if you intend to use the converted US998 on Sprint!
2. You already crossflashed to US998 if not follow the guide here "Frankenstein method" [https://forum.xda-developers.com/lg...sflashing-t3780969/post76510671#post76510671]
3. You followed the bootloader unlock, root, TWRP "WTF" thread here https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
(US998 to LS998) Downloads: (Sprint LS998 system,boot,modem)* MAKE SURE TO FLASH MAGISK, NO-VERITY OPT ENCRYPT, AND RCD DISABLER BEFORE LEAVING RECOVERY!!*
Sprint 20b
https://drive.google.com/file/d/1aQojUcchnEruHwnecfaVGToxZbmj-UX3/view?usp=drivesdk
Sprint 21a(may security patch)
https://drive.google.com/file/d/1JCalyu7mt8DW6wMWbgGViqj0oi9eUSr7/view?usp=drivesdk
*Instructions*:
a. Make a backup in TWRP of system,boot,and data before proceeding!
b. Reboot to TWRP and wipe data (factory data reset)
c. Install the SPRINTLS998.zip (20b or 21a)from TWRP (Do NOT leave recovery yet)
d. Flash Magisk, no verity encrypt, and RCD disabler(you should already have these files if you followed the WTF thread)
e. Reboot
d. Once booted up you need to connect to WiFi. go to settings, update profile and prl. Reboot
quantemplation said:
For anyone who flashes back to Sprint but needs to edit the APNs still, you can type this in command prompt(from PC)
Code:
adb shell
su
am start -n com.lge.hiddenmenu/com.lge.hiddenmenu.ModemProtocol.ModemProtocolMain
Then go to PDP Setting
Then go to APN setting
Click to expand...
Click to collapse
be sure to thank his post here
https://forum.xda-developers.com/showpost.php?p=76633700&postcount=45
JonnyTrulove said:
@JWnSC thanks to the help of some of you great people in this thread I have had the chance to do this conversion twice now. Both times it worked great but I did have to update the APN settings before getting mobile data to work for me. I know you were kind enough to include screenshots of the right APN settings but I just wanted to share that both times I used the ##SCRTN## dialer code to force OTA provisioning and it worked, so I thought you may want to add that option to your first post. Might be a good option for someone that's in hurry to get connected.
Only negative I can think of is that you would not have tethering unless you were subscribed or you manually added the "Dun" provision to the APN later.
Just wanted to share in case you thought it was worth adding to your original post. If not, no biggie. Thanks
Click to expand...
Click to collapse
Special thanks:
@TxanMoe for finding the bootloader exploit and helping me along the way
@ChazzMatt for his in depth Guides and help in this forum
@SGCMarkus for TWRP recovery for this device and all the roms he provides
@quantemplation
@JonnyTrulove
and to any others I may have missed..

Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP(wipe data) install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it

I'll give this a real-world run-through tomorrow when my new LS998 arrives.

SilverZero said:
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
Click to expand...
Click to collapse
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.

JWnSC said:
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
Click to expand...
Click to collapse
Yeah...it sucks we need this...sprint not allowing access to kdz is a load of bs...it is much appreciated that we have you helping to support us sprint users...i am looking back at my past lg phones now to see if i can find the process of creating a working kdz...one of the people i think in the g2 or g3 forums actually created a kdz using the untouched signed lg files and it was fully flashable to get back to 100% stock...i don't know if too much has changed since then to do this again...but it would be nice to have for some...me...i won't be doing anything that removes my bootloader unlock and root...but those with warranty may want to have that ability...thanks to all that have contributed to making this a great device...i missed root on a level people outside these forums may never understand

Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?

cre4per said:
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
Click to expand...
Click to collapse
Right. change "_COM#" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa

JWnSC said:
Right. change "_ whatever com #" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
Click to expand...
Click to collapse
perfect will give it a try, hoping this will let me get volte back on mydevice

JWnSC said:
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
Click to expand...
Click to collapse
Could you lock the bootloader after this? Or will it show an error?

guapinoy said:
Could you lock the bootloader after this? Or will it show an error?
Click to expand...
Click to collapse
Bootloader would still be unlocked but the message after every boot would disappear and you won't be able to enter fastboot. (After you do the system update)
I thought after installing the latest update it would lock the bootloader...it didn't, but it did remove the text after every boot saying to lock bootloader and you won't be able to enter fastboot after. Activating developer options will show the boot is still unlocked. It does change the software info to LS99821a instead of US99820a
To lock the bootloader, you could probably flash the other Sprint zip(without flashing magisk ect..) and just sprint recovery or the factory zip. Reboot to bootloader from twrp and lock it that way. Then do the Sprint system update *I have to do more testing tho I don't recommend doing this until it's tested*

I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.

Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
You can't update profile/ prl on US998 firmware(or at least I couldn't). Backup your setup and try DotOS if you already have working lte. This thread is mainly for users to get lte back. I'm not running the stock Sprint firmware. I switched to stock firmware first to get lte working and switched back to us998 rom.
If you wipe data and flash the SprintLS998.zip you won't have any issues. It already contains the Sprint modem, system, and boot. No need to flash the modem from the other thread.

Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.

Lurien said:
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Click to expand...
Click to collapse
???
If you flash the Sprint modem you'll have all the Sprint bands.
It's just the US998 does not have LTE bands 26 & 41. So you have to flash the Sprint modem to get them. If the LS998 normally has LTE band 13, then you'll have that.

Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...

jamesd1085 said:
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
Click to expand...
Click to collapse
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.

JWnSC said:
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
Click to expand...
Click to collapse
How did you install? Because twrp is there it failed on mine

jamesd1085 said:
How did you install? Because twrp is there it failed on mine
Click to expand...
Click to collapse
I flashed the factory back to stock.zip and went to settings, system update.
Not worth it imo...I was testing the factorysprint.zip to make sure it worked. I can make a flashable zip later(to only include system, modem,boot)..I don't think much changed. Looks like it was just an update to disable fastboot and access to recovery

Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).

SilverZero said:
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
Click to expand...
Click to collapse
I had to connect to wifi when i updated profile...it kept telling me to contact carrier when i tried to update through data connection

Request advice from the experts on troubleshooting or install stock rom

Hi all,
Would like to thank you in advance in taking your time in reading this post. Its my first time (and post) with the XDA forums. I have a few questions I am not sure if Im doing the correct thing so Im hoping for advice for the experts here in the forum to point me in the right direction.
Technical skills - never flashed a phone before but reading the step by step instructions available in the forums.
A few information with my phone to help with troubleshooting
- Purchased with no warranty overseas because they dont sell it here in the Philippines
- Phone came with the following specs
- Android 8 with Nov 1, 2018 patch
- unlock bootloader
- software channel - retcn
- Build number - OPXS27.109-52-10
- Baseband version - M8988_20207.117.02.41-01.01R NCD
Issue:
1. 4G Network - not working at all on the local network. It seems to be able to go to 4G but cannot make outgoing or incoming phone calls/ text or mobile data.
- troubleshooted by resetting phone, changing apn with no luck. Changing it to 3G only seems to make the phone work to make voicecalls/text and mobile connection
2. Random apps crashing - namely - grab (like uber) and spotify.
- tried resetting the phone (and installed just grab app only after reset but still not working) and cleared partition cache boot mode but still no change.
Proposed solution
- installing a new stock rom - should fix the apps crashing issue and 4g issue
- installing custom rom like lineage (discarded this solution because it will disable audio mods) - i bought the moto mods JBL accessory.
questions:
1. Based on this thread - (https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783)
- I wish to install stock rom but Im not sure which rom to use. Do I use USC version based on the phones current build number? - OPXS27.109-52-10 or can I change to a different US carrier like verizon ?(related to next question)
2. Is there anyway to change/fix the carrier frequency so it will start accepting 4g locally here?
- will installing a stock rom with a different carrier (i.e. verizon), will that change baseband and accept other frequencies or will I brick my phone?
- Or hope the stock rom with a different patch will fix it? Ive read in forums it could just be the newer patches that giving me issues. The one available for USC is version OPXS27.109-40-7. Upon checking my local carrier and USC band frequencies, both have 5 band with 850ghz frequency available. So Im beginning to think it could be a software rather than carrier issue
3. Because the phone came with a unlocked bootloader, does that mean I will never receive OTA updates from the stock rom? I will have to manually update it when android 9 comes out?
4. software channel - retcn - does that have to do with anything with baseband or installing stock rom? Does this help in any trouble shooting? Ive seen a few threads in the forums with builds with specific software channel in other threads with specific models xt1789 - 02 or 03 or 06. I dont know if that affects stock roms?
-----------------------------------
Maybe it would also help to show my local 4g frequencies and band number
Smart Band is here below
Frequency Protocol Class Band Number
700MHz FDD-LTE/LTE-A 4G 28
850MHz FDD-LTE/LTE-A 4G 5
1800MHz FDD-LTE/LTE-A 4G 3
2100MHz FDD-LTE/LTE-A 4G 1
2300MHz TDD-LTE 4G 40
Sorry for some newb questions and I welcome any other methods of troubleshooting or suggestions you guys can give me. I feel installing stock rom USC carrier is the solution to the problem after all the research I have done, but would like confirmation first from the experts.
Regards
Rj

On mirror.lolinet.com, 109-52-10 belongs to Retail Apac. The newest rom was uploaded is 109-52-12.
If your unlocked bootloader phone is still running the stock firmware, it will be notified when OTA comes.
I'm using an ATT with carrier unlocked so everything is fine to me. With unlocked carrier, you can use any mobile network if the phone baseband supports.
According to basic theory, if the phone was unlocked bootloader, it can be flashed fw from other variants (but there will be problem for each variant situation). It seems none of us here has done this yet.
- Check your phone model, it's on the right of the charger port.
- Open Phone, and type: *#*#4636#*#*. Choose Phone info. Check the preferred network type. If you can receive sms but cannot send, just update your SMSC number.
Most problems can be solved by flashing the stock fw.
Good luck!!!

Thank you
I didn't even know that site until you pointed it out.
I would be definitely be using the APAC software and try and flash the stock rom. I hope it would work and if not I'll try and flashing the older patch version.
Thank you
Will update you hopefully in a week as soon as I fully understand the details of flashing.

Radioband Issue, RETCN and Stockrom app Fix
mr_5kool said:
On mirror.lolinet.com, 109-52-10 belongs to Retail Apac. The newest rom was uploaded is 109-52-12.
If your unlocked bootloader phone is still running the stock firmware, it will be notified when OTA comes.
I'm using an ATT with carrier unlocked so everything is fine to me. With unlocked carrier, you can use any mobile network if the phone baseband supports.
According to basic theory, if the phone was unlocked bootloader, it can be flashed fw from other variants (but there will be problem for each variant situation). It seems none of us here has done this yet.
- Check your phone model, it's on the right of the charger port.
- Open Phone, and type: *#*#4636#*#*. Choose Phone info. Check the preferred network type. If you can receive sms but cannot send, just update your SMSC number.
Most problems can be solved by flashing the stock fw.
Good luck!!!
Click to expand...
Click to collapse
Just giving people update incase anyone is interested. I decided to follow this guide Step E (reflashing back to stock). It worked perfectly for me.
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
As you guys know the original Build number was OPXS27.109-52-10. It turns out that was meant for model XT1789-06. It wouldnt be a big deal except my model that arrived was for XT1789-05
Regardless I followed the instructions and installed the latest firmware for OPSC27.109-52-14 for XT1789-06 (https://mirrors.lolinet.com/firmware/moto/nash/official/RETAPAC/)
Installation went fine and all the apps crashing issues went away. However 4G still didnt work.
I decided to see if installation the latest build for XT1789-05 under the link below would help.
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
It felt more stable, apps not crashing, moto mods still working, and I was able to get get 4G working for internet and sms however phonecalls (both outgoing and incoming) still didnt work. 3G seems to be still stable and working fine at the moment in the Philippines. (note: I have updated APN)
I have decided to leave it alone as I got half my problem sorted (apps crashing) and moto mods still working. Can live without 4G as its mostly connected to WIFI at home and occasionally going out. Crashing apps was more important win for me.
Maybe once Android 9 officially comes out for the phone, it may fix the issue.
I have explored the option of changing the radioband but I heard of nightmares for some users when they switched to USA. I dont know what will happen if I switch to Australia radioband. (i left it to automatic at this time).
Maybe if someone else found the solution, would be happy to try it out.

I'm sorry for you when you still have some problems. My friends mostly use Z2F form T-mobile and Sprint. ATT and Verizon are less. But they work well for all functions.
There's another way you can try. It's the method for dual sim. For eg, you've a Sprint one. You modded the hardware and the 2nd SIM slot is now available. But current Sprint fw only supports single SIM. You can download a dual sim fw, extract it and copy-replace the modem from Sprint fw to dual sim one (I dont remember exactly what modem should keep, sorry). Then, flash the combination fw and the phone runs with dual sim. You can try a stable system and retcn modem or vice versa.

mr_5kool said:
I'm sorry for you when you still have some problems. My friends mostly use Z2F form T-mobile and Sprint. ATT and Verizon are less. But they work well for all functions.
There's another way you can try. It's the method for dual sim. For eg, you've a Sprint one. You modded the hardware and the 2nd SIM slot is now available. But current Sprint fw only supports single SIM. You can download a dual sim fw, extract it and copy-replace the modem from Sprint fw to dual sim one (I dont remember exactly what modem should keep, sorry). Then, flash the combination fw and the phone runs with dual sim. You can try a stable system and retcn modem or vice versa.
Click to expand...
Click to collapse
Nothing to be sorry about, actually really grateful for your input.
Already had a big win by:
1. flashing for the first time ever to stock rom and not bricking my phone in the process
2. all apps are now working
3. moto mods are working
4. alternative solution to 4g issue is available
Just letting you know the my variant already is on dual sim, and I was pretty sure the modem was wiped and reinstalled when I reflashed back to stock. I did find another thread of similar issue. Only solution was really to either change to 3G or fix APN.
https://forums.lenovo.com/t5/Moto-Z...ing-Incoming-and-outgoing/td-p/4068998/page/2
One user commented it could be a carrier issue. (see below)
-------
07-13-2018 08:41 AM
Hello, guys.!
I've been following this inquiry very close and I've arrived into a very accurate conclusion:
1. This is not a device problem! Motorola devices are not the problem. I've found that Samsung and Huawei devices also have the same problems.
2. This is definitely about service provider network. In my investigation, AT&T is the one having this issue alone.
3. This issue happens only in certain Mexican areas. For example, in Monterey this happens. I went to Chihuahua and CD Juarez just last 3 days and I was able to use 4G and calls without problems.
4. Based on the idea that only happens in certain areas at certain networks, I can only concluded that happens to certain devices as well. Brands, perhaps, as unlocked iPhone does not present this issue.
------
It could be something to do with Volte 4G calls. It has been disabled for the Xforce 1789-05 european models.
I think waiting to Android 9 may be my best solution though I may start try to start troubleshooting and focusing on simcards to see if 4g will work with other carriers.

I've got an ATT Flipout. I could make call and sms normally. But the network could only rise to E+, cannot be up to 3G (several years ago). The problem was phone hardware. The baseband was only available for US.
Z2F was the flagship, so its modem supported many 4G band for other regions.
As you mentioned, I think you should find out what carrier's band would suit your Z2F. Luckily, all Z2F variants have our bands.
Good luck, guy! And hope you'll give us good news!

You have the (05) dual sim variant correct? You're also in the Philippines right? If you look at this link you'll see all the bands supported for your variant, also you can check carriers in your region to see what bands they are using.
If you look carriers in Philippines like Smart you can see what bands they use.
A comparable carrier is Claro in Brazil.
They use the same bands on a GSM network. I would assume that Retail firmware would open those bands, but I'm not 100% sure and maybe the firmware you flashed doesn't. I do see firmware for RETBR (retail Brazil) and I know that (05) variants are used there. So maybe flashing a retbr firmware will open the bands needed since Brazil and Philippines use some of the same bands. I'm not 100% sure on this, it's just my best guess. You're welcome to verify the info linked and do what you will. I'd think the worst case scenario would be borking your imei and having to blankflash, but those tools are around here as well and so long as you DO NOT relock your bootloader you'll find that it is pretty hard to actually brick this phone. That's the best I can come up with to help.

Thank you
41rw4lk said:
You have the (05) dual sim variant correct? You're also in the Philippines right? If you look at this link you'll see all the bands supported for your variant, also you can check carriers in your region to see what bands they are using.
If you look carriers in Philippines like Smart you can see what bands they use.
A comparable carrier is Claro in Brazil.
They use the same bands on a GSM network. I would assume that Retail firmware would open those bands, but I'm not 100% sure and maybe the firmware you flashed doesn't. I do see firmware for RETBR (retail Brazil) and I know that (05) variants are used there. So maybe flashing a retbr firmware will open the bands needed since Brazil and Philippines use some of the same bands. I'm not 100% sure on this, it's just my best guess. You're welcome to verify the info linked and do what you will. I'd think the worst case scenario would be borking your imei and having to blankflash, but those tools are around here as well and so long as you DO NOT relock your bootloader you'll find that it is pretty hard to actually brick this phone. That's the best I can come up with to help.
Click to expand...
Click to collapse
Your correct, its the dual sim 05 variant. I flashed the retail and I do get LTE data. It just the LTE wont work on 4G. So I dont think its purely a band issue because based on your link I have 3 supported LTE bands with the smart network. Its possible its something to do with carrier communicating with the phone. (APN? Volte?)
Question: will flashing a retbr on a retcn cause issue? Does software channel matter? Maybe I can give it a go, but my wife (who i gave the phone to) has been pretty happy with it. I dont think she wants another wipe on her phone. (i think i already reformatted at least 5 times already)

Update
I found this thread with moto z play.
Maybe this will work? It a method to open all baseband channels.
https://forum.xda-developers.com/moto-z-play/how-to/enabling-basebands-mzp-qualcomm-phone-t3684962

harkoliar said:
I found this thread with moto z play.
Maybe this will work? It a method to open all baseband channels.
https://forum.xda-developers.com/moto-z-play/how-to/enabling-basebands-mzp-qualcomm-phone-t3684962
Click to expand...
Click to collapse
I don't know about all that, looks like a recipe for trouble. Are you able to make or receive voice calls? FYI you can go to apn settings, click the 3-dot menu and reset to default. That should pull your apn info from your sim so you should be good to go apn wise.

There was an old method called RadioComm. It used to unlock carrier for Razr HD (and maybe others Motorola phones). But it is more danger than flashing fw.
On my Verizon phones, no APN profile was showed. But on ATT Z2F, APN was automatically set (and showed) for each carrier.

Inbound and outbound calls affected
41rw4lk said:
I don't know about all that, looks like a recipe for trouble. Are you able to make or receive voice calls? FYI you can go to apn settings, click the 3-dot menu and reset to default. That should pull your apn info from your sim so you should be good to go apn wise.
Click to expand...
Click to collapse
Unfortunately still a no go.
I have reset the network settings and used default apn as per your suggestion. I even copied settings from another phone using same carrier and used different calling apps. It's weird but when at 4g
1. Text work
2. Data works
3. Inbound and outbound phone calls doesn't work
Swap to 3g everything works
I'm still trying to convince my wife if I should flash to retbr.

harkoliar said:
Unfortunately still a no go.
I have reset the network settings and used default apn as per your suggestion. I even copied settings from another phone using same carrier and used different calling apps. It's weird but when at 4g
1. Text work
2. Data works
3. Inbound and outbound phone calls doesn't work
Swap to 3g everything works
I'm still trying to convince my wife if I should flash to retbr.
Click to expand...
Click to collapse
Well if everything works on 3g then it sounds like your bands are fine. Sounds more like a volte issue. 4g works, 3g works, calling works, it's just no calls when 4g is on. Are you using an old sim? Have you tried the sim in another phone to see if you experience the same problems with 4g? Some carriers use different sim for different services. What is your preferred network type set to? If it's exclusively LTE, try setting it to LTE/GSM. It sounds more like a sim issue, setting issue, or maybe a registration issue.

41rw4lk said:
Well if everything works on 3g then it sounds like your bands are fine. Sounds more like a volte issue. 4g works, 3g works, calling works, it's just no calls when 4g is on. Are you using an old sim? Have you tried the sim in another phone to see if you experience the same problems with 4g? Some carriers use different sim for different services. What is your preferred network type set to? If it's exclusively LTE, try setting it to LTE/GSM. It sounds more like a sim issue, setting issue, or maybe a registration issue.
Click to expand...
Click to collapse
I dont think its a old sim issue because its only a year old. But I am getting another simcard from another local network to test it out.
Will update with details.

Hello harkoliar, it looks like both you and I share the exact problem. And best of all, or worst depending on how you view it, I am in Malaysia with the same problems, Grab keeps crashing, among other apps just failing to work period.
Software Channel reads RETCN. 05 phone running an 06 firmware.
I noticed you tried to flash a RETAIL firmware, may I know which was the file you used, was it OPXS27.109-34-21?
I don't have much problems with the connectivity and using 4G. Perhaps it may be a difference between telcos in Malaysian and the Philippines.
Oh... And I bought mine from Lazada, where did you get yours. LOL

frozero said:
Hello harkoliar, it looks like both you and I share the exact problem. And best of all, or worst depending on how you view it, I am in Malaysia with the same problems, Grab keeps crashing, among other apps just failing to work period.
Software Channel reads RETCN. 05 phone running an 06 firmware.
I noticed you tried to flash a RETAIL firmware, may I know which was the file you used, was it OPXS27.109-34-21?
I don't have much problems with the connectivity and using 4G. Perhaps it may be a difference between telcos in Malaysian and the Philippines.
Oh... And I bought mine from Lazada, where did you get yours. LOL
Click to expand...
Click to collapse
Same Lazada. Lol. We must have gotten from the same supplier.
Your right, I installed OPXS27.109-34-21. Worked like a charm after that. Please follow the steps provided in the guide - Step E.
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
note: be mindful just what version of android your using. Im assuming its also android 8 like mine. If its currently Android 7, i heard its best to install the android 7 rom first then upgrade to 8. You can tell by the versions.
Another user also having the same problems and reinstalled the latest Retail ROM for XT1789-05 - latest version, worked for him as well
https://forum.xda-developers.com/z2-force/help/internet-issue-apps-xt1789-05-t3924795/page2
Please let us know how you go.

harkoliar said:
Same Lazada. Lol. We must have gotten from the same supplier.
Your right, I installed OPXS27.109-34-21. Worked like a charm after that. Please follow the steps provided in the guide - Step E.
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
note: be mindful just what version of android your using. Im assuming its also android 8 like mine. If its currently Android 7, i heard its best to install the android 7 rom first then upgrade to 8. You can tell by the versions.
Another user also having the same problems and reinstalled the latest Retail ROM for XT1789-05 - latest version, worked for him as well
https://forum.xda-developers.com/z2-force/help/internet-issue-apps-xt1789-05-t3924795/page2
Please let us know how you go.
Click to expand...
Click to collapse
Just finished flashing! So far so good, installing apps as we speak! Super excited!
Was your seller named Aukey? I left them a stinker of a review, lol.
Thank you so much for your experience and detailed breakdown of what you did to get right with your, now, wife's phone. :laugh::fingers-crossed::victory:

Different seller but same source most likely
Different seller but same source most likely.
Happy to help and hopefully that did fix all your app problems. :good:
Still credits and thanks to the actual guys who did the guide.

frozero said:
Just finished flashing! So far so good, installing apps as we speak! Super excited!
Was your seller named Aukey? I left them a stinker of a review, lol.
Thank you so much for your experience and detailed breakdown of what you did to get right with your, now, wife's phone. :laugh::fingers-crossed::victory:
Click to expand...
Click to collapse
AUKEY owns coolicool. Same supplier keeps making the same mistake

5GHz WiFi for UK models?

Hi all,
Been troubleshooting slow WiFi on my G6 play compared to PC and I found that it only appears to support 2.4GHz frequency.
It's a UK model XT1922-2.
Have seen a few posts saying that the chipset should be capable of 5GHz and by rooting and changing some setting it may be possible to enable.
I've been OK on stock firmware so far, I didn't want to root as I thought that gpay and bank apps would stop working, although it appears that's no longer the case.
Before I start I just wanted to ask:
Has anyone with this model got 5GHz WiFi working, if so which ROM are you using?
Which ROMs are recommended? I prefer the closest to vanilla and good battery life.
Can some custom ROM users confirm that gpay and banking apps (Monzo, HSBC) can be made to work through magisk?
Thanks!

To check for 5ghz support, navigate to /vendor/etc/wifi and open WCNSS_qcom_cfg.ini with a text editor. (You need root for this.) Find the line that says;
#Preferred band (both or 2.4 only or 5 only)
BandCapability=0
Change BandCapability=0 to BandCapability=2, then toggle WiFi off/on. This will force you to only scan for, and connect to 5ghz networks.
Reference
BandCapability=0 (Both 2.4 & 5ghz.)
BandCapability=1 (2.4ghz only.)
BandCapability=2 (5ghz only.)

Thanks Spaceminer.
After a few issues I have now rooted and changed that setting from 0 to 2, I still only get 2.4GHz connection so I guess that means my device does not support 5GHz?

dink-x10 said:
Thanks Spaceminer.
After a few issues I have now rooted and changed that setting from 0 to 2, I still only get 2.4GHz connection so I guess that means my device does not support 5GHz?
Click to expand...
Click to collapse
Yep, unless they also have a flag in the build.prop that's forcing 2.4ghz. Can you send me your build.prop? I don't mind taking a look.
It's also possible that your firmware just doesn't have the drivers for it. If you want to check if it's a driver issue, you could try flashing the firmware for RETUS. If you do try that, skip the bootloader, gpt.bin, and NON-HLOS.bin. Worst case scenario, it'll just loop, or send you back to fastboot. I can flash any G6 Play firmware to my Virgin branded variant and it'll boot up, so the same is probably true for you too.

Spaceminer said:
Yep, unless they also have a flag in the build.prop that's forcing 2.4ghz. Can you send me your build.prop? I don't mind taking a look.
It's also possible that your firmware just doesn't have the drivers for it. If you want to check if it's a driver issue, you could try flashing the firmware for RETUS. If you do try that, skip the bootloader, gpt.bin, and NON-HLOS.bin. Worst case scenario, it'll just loop, or send you back to fastboot. I can flash any G6 Play firmware to my Virgin branded variant and it'll boot up, so the same is probably true for you too.
Click to expand...
Click to collapse
Thanks, I will get the build.prop uploaded in a day or 2.
I am now running a GSI rom (lineage) can I just flash the /vendor and not the /system from the RETUS, will it work?
Sent from my Phh-Treble vanilla using Tapatalk

@Spaceminer, my build.prop is attached. Couldn't see anything obvious in there but I'm not an expert
I did try flashing the RETUS but did not see 5GHz networks. It gave me some odd screen rotation behaviour so I went back.

File Request: modem.img from US Unlocked Pixel 3/XL

TL;DR: I have an Australian unlocked Pixel 3 XL (disabled eSIM), and want to try flashing the US unlocked modem firmware to my phone to see if it will unlock the eSIM.
I believe that the command
Code:
adb pull /dev/block/by-name/modem_a modem.img
(or modem_b for boot slot b) will work from a connected computer w/ ADB and a rooted phone. (Please let me know if this command wouldn't work!)
Full post:
Hey guys, new to XDA, been browsing every now and then for a while though
I'm also no expert in modding, ROMs etc.
It appears that Google has disabled the eSIM on Australian unlocked models of the Pixel 3/3 XL. To my knowledge, there is only one hardware variant of the p3, meaning that the eSIM chip itself is present, but cannot be used, either due to firmware or software limitations.
I have a hunch that it's due to the modem firmware. Why? When it was still on Android 9, the eSIM setup was accessible through the Settings menu, although once a QR code was scanned, a generic error message would pop up - indicating that Android itself had no clue why it didn't work. In Android 10, the option has been removed from Settings.
This makes me think that flashing the modem driver from a model with working eSIM may enable its functionality in software - and there doesn't seem to be any harm in trying. It seems like cross-flashing modems was possible on the original Pixel XL, which similarly had only one hardware variant. This brings me to my issue; I've been unable to find a modem.img file anywhere for the Pixel 3. I've downloaded Google's factory system images, as well as the driver binaries, to decompress and poke around for a modem.img to no avail. I suspect this is because flashing a new image leaves the modem partitions untouched, and the modem firmware from factory remains on the device. (This also makes sense because Google only offers one system image version on its site)
So I'd like an image of the modem partition from a US unlocked pixel 3/3XL, preferably already running the latest version of Android 10 (QQ1A.191205.008) to try out on my phone. Who knows - if this works, maybe other features can be enabled, like FeliCa functionality on non-JP models! (Wishful thinking, I know)
If anyone has any other ideas or thinks I'm on the wrong track let me know - I'm sure we'll find some way to access these locked features
Thanks!
Sidenote: the images I mention above include a radio.img file - what's the difference between this and modem.img? There doesn't seem to be a partition named radio (when looking at `ls /dev/block/by-name`) - is this identical to modem.img??

BigBoy47 said:
So I'd like an image of the modem partition from a US unlocked pixel 3/3XL, preferably already running the latest version of Android 10 (QQ1A.191205.008)
Click to expand...
Click to collapse
I am US, unlocked, rooted - I flash the factory image monthly from https://developers.google.com/android/images
I can pull the files tomorrow but I can't imagine they will be different than what's included in the factory image you can download from the link.
Edit to add: I would suspect this is a regional limitation Google implements with the system based information about the devices location. Maybe on a combination of geo location, ip addresses, or cellular providers.

Thing is, I couldnt find the modem.img anywhere in the official factory images, leading me to believe that it never gets flashed/updated - meaning the factory version is there to stay. Again, just a hunch though.
I doubt it's Internet-based at all - as I mentioned, it seems like Android had no clue why eSIM registration was failing, making it seem like a firmware thing.
Regardless, thanks so much for the offer! I'll give it a shot when you upload your modem image.

BigBoy47 said:
Thing is, I couldnt find the modem.img anywhere in the official factory images, leading me to believe that it never gets flashed/updated - meaning the factory version is there to stay. Again, just a hunch though.
I doubt it's Internet-based at all - as I mentioned, it seems like Android had no clue why eSIM registration was failing, making it seem like a firmware thing.
Regardless, thanks so much for the offer! I'll give it a shot when you upload your modem image.
Click to expand...
Click to collapse
There is no modem.img in the factory image even if you extract the image .zip to get boot.img, etc. Clearly, it gets installed as part of one of the other files. I am not on stock, or I would try a pull.

BigBoy47 said:
Thing is, I couldnt find the modem.img anywhere in the official factory images, leading me to believe that it never gets flashed/updated - meaning the factory version is there to stay. Again, just a hunch though.
I doubt it's Internet-based at all - as I mentioned, it seems like Android had no clue why eSIM registration was failing, making it seem like a firmware thing.
Regardless, thanks so much for the offer! I'll give it a shot when you upload your modem image.
Click to expand...
Click to collapse
Radio.... img is the modem image you're looking for. You'll find it in the root folder after you've extracted the factory image.