I am writing this because I see several people are having problems getting their phone to work on certain carriers.
There are four MAIN parts to an Android phone communicating with a cell network:
1 - The hardware modem itself. All MSM CPUs (MSM8996 in our case) have the same modem. It is built into the CPU. From the factory it is capable of talking on all 2G, 3G and 4G bands. However, there are QFPROM qfuses that can disable parts of the modem. These can be blown by the OEM or the carriers (if the phone is carrier branded).
2 - The modem firmware. This runs in the TZ and receives calls from the RIL -- they are AT commands just like an old school modem.
3 - The RIL (Radio Interface Layer). This runs as rild inside the Android OS, and is what things like the dialer or your SMS app talk to. All commands and voice paths are sent to this.
4- The antenna. Even if you have the ability to enable all bands, you probably don't have the antennas needed.
So, how do you know what is the limiting factor for your phone talking on a particular band? Trial and error.
First the hardware modem. If there are qfuses blown that disable bands -- there is NOTHING you can do about it. There (currently) is no way to check this, so you won't know until you try some of the software methods.
Next, the modem firmware. It is signed, so you can't just flash ANY firmware from any vendors phone. Now, on the V20, since LG screwed up, we can flash the modem from pretty much any model V20 onto any other model V20 (H918 being an exception). However, modem is also checked for ARB. So, if you are ARB 0, and you flash an ARB 1 modem, your ARB will be incremented and then you MUST run a full ARB 1 firmware stack. In the case of the H910, there is NO ARB 1 firmware stack -- so you have just toasted your phone. If you are ARB 1, and you flash an ARB 0 modem, you will get the "green screen of death". It won't brick your phone, but it won't boot till you flash a KDZ (or recover it with some other means).
So next up with have the RIL. This is actually the safest thing to test. Carriers CAN block bands at the RIL level. Replacing the RIL is simple, and won't brick your phone. Now, I say they CAN, but you won't know till your try. Flashing the system partition from another model that you CAN talk on the bands you want is the easiest way. However, your phone may not boot till some tweaks are made. This is completely safe though as long as you have a FULL backup of your phone. I don't mean a TWRP backup. I mean a dump of EVERY SINGLE partition (you can leave our userdata).
That leaves antenna. Even if you can unlock the bands, if you don't have an antenna for that band, you aren't talking.
So, before you guys go breaking your phones trying to unlock bands, do yourselves a favor and try the safest method first. If you want to flash modem firmware, and you aren't sure, send me a PM with the modem you have, and what you want to flash. I will tell you if it is at least not going to brick your phone.
-- Brian
I have been searching on for trying to unlock bands and I can't seem to find any. Would you be kind enough to point me at a direction?
I have never needed to unlock bands, so I don't know the exact procedure. I know that in the service menu you can enable / disable bands. I don't know if it is the standard LGMENU dialer code, or some other code -- do a search, and you can find it.
As for replacing rild. That would require you to unpack the system images of your phone and the phone you want to replace it with. But (AFAIK) you can't just replace rild, there are shared libraries, and config files, and then your would probably have to update your audio path conf, and maybe even replace your dialer. It takes work
Flashing the modem firmware is the easiest, but you have to be careful as was stated above.
-- Brian
You cannot enable/disable bands on the H910 sadly using the LGMENU dialer code..
runningnak3d said:
Next, the modem firmware. It is signed, so you can't just flash ANY firmware from any vendors phone. Now, on the V20, since LG screwed up, we can flash the modem from pretty much any model V20 onto any other model V20 (H918 being an exception). However, modem is also checked for ARB. So, if you are ARB 0, and you flash an ARB 1 modem, your ARB will be incremented and then you MUST run a full ARB 1 firmware stack. In the case of the H910, there is NO ARB 1 firmware stack -- so you have just toasted your phone. If you are ARB 1, and you flash an ARB 0 modem, you will get the "green screen of death". It won't brick your phone, but it won't boot till you flash a KDZ (or recover it with some other means).
Click to expand...
Click to collapse
When you say H918 being an exception - are you saying you can't flash H918 on other phones, or can't flash other phones on H918?
I would very much like to flash the H918 modem on my H990DS to see if that gets VoLTE/WiFiCalling working, if that's possible.
Thanks!
You can't go either way. All models of the V20 (that I know of) have the same RSA key in the CPU to verify the signature of the firmware with the exception of the H918. If you flash any SIGNED H918 firmware onto any other model, then at best it won't boot, and at worst, it will brick your phone.
-- Brian
XblackdemonX said:
You cannot enable/disable bands on the H910 sadly using the LGMENU dialer code..
Click to expand...
Click to collapse
Agreed. At&t has disabled those options in this device.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
Can I flash the international varient modem firmware into this device? 91010i software here.
The hidden menu options are disabled at the OS level.
As I stated, it is perfectly safe to flash another model's system image and see if it will boot. Flash system from a model that you know has access to enable / disable bands. If you can get that much working, then you can work on hacking together a system image that is fully functional. Heck, you may be surprised and get what you want without having to make any other changes.
However, make SURE you have backups of modemst1 and 2, misc, persist, and persistent.
-- Brian
Question about modem/data
runningnak3d said:
I am writing this because I see several people are having problems getting their phone to work on certain carriers.
There are four MAIN parts to an Android phone communicating with a cell network:
1 - The hardware modem itself. All MSM CPUs (MSM8996 in our case) have the same modem. It is built into the CPU. From the factory it is capable of talking on all 2G, 3G and 4G bands. However, there are QFPROM qfuses that can disable parts of the modem. These can be blown by the OEM or the carriers (if the phone is carrier branded).
2 - The modem firmware. This runs in the TZ and receives calls from the RIL -- they are AT commands just like an old school modem.
3 - The RIL (Radio Interface Layer). This runs as rild inside the Android OS, and is what things like the dialer or your SMS app talk to. All commands and voice paths are sent to this.
4- The antenna. Even if you have the ability to enable all bands, you probably don't have the antennas needed.
So, how do you know what is the limiting factor for your phone talking on a particular band? Trial and error.
First the hardware modem. If there are qfuses blown that disable bands -- there is NOTHING you can do about it. There (currently) is no way to check this, so you won't know until you try some of the software methods.
Next, the modem firmware. It is signed, so you can't just flash ANY firmware from any vendors phone. Now, on the V20, since LG screwed up, we can flash the modem from pretty much any model V20 onto any other model V20 (H918 being an exception). However, modem is also checked for ARB. So, if you are ARB 0, and you flash an ARB 1 modem, your ARB will be incremented and then you MUST run a full ARB 1 firmware stack. In the case of the H910, there is NO ARB 1 firmware stack -- so you have just toasted your phone. If you are ARB 1, and you flash an ARB 0 modem, you will get the "green screen of death". It won't brick your phone, but it won't boot till you flash a KDZ (or recover it with some other means).
So next up with have the RIL. This is actually the safest thing to test. Carriers CAN block bands at the RIL level. Replacing the RIL is simple, and won't brick your phone. Now, I say they CAN, but you won't know till your try. Flashing the system partition from another model that you CAN talk on the bands you want is the easiest way. However, your phone may not boot till some tweaks are made. This is completely safe though as long as you have a FULL backup of your phone. I don't mean a TWRP backup. I mean a dump of EVERY SINGLE partition (you can leave our userdata).
That leaves antenna. Even if you can unlock the bands, if you don't have an antenna for that band, you aren't talking.
So, before you guys go breaking your phones trying to unlock bands, do yourselves a favor and try the safest method first. If you want to flash modem firmware, and you aren't sure, send me a PM with the modem you have, and what you want to flash. I will tell you if it is at least not going to brick your phone.
-- Brian
Click to expand...
Click to collapse
Brian,
You seem fairly knowledgeable so I'll see if you have an answer for me. I rooted my ls997 when it was on zv7 which involved flashing a KDZ using patched LGUP. After that I was not able to connect to LTE. I have looked at numerous settings, flashed the zv5 modem image file, flashed several roms, updated profile and PRL. I'm currently on a stock ls997 rom with a custom kernel and mms, calls, and 3g data work fine but no LTE. Any ideas?
Hopefully you backed up your phone like the Zv7 root procedure said
If you have modemst1 and st2 -- flash those. You can flash them from fastboot:
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
Part of the root procedure for Zv7 involves flashing the VS995 KDZ. When the phone boots, there is data that gets written to those two partitions.
Restore them from backup, and LTE will be back.
-- Brian
runningnak3d said:
Hopefully you backed up your phone like the Zv7 root procedure said
If you have modemst1 and st2 -- flash those. You can flash them from fastboot:
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
Part of the root procedure for Zv7 involves flashing the VS995 KDZ. When the phone boots, there is data that gets written to those two partitions.
Restore them from backup, and LTE will be back.
-- Brian
Click to expand...
Click to collapse
Unfortunately I didn't back up. Checking the procedure I followed it didn't tell me to (https://www.google.com/amp/s/forum.xda-developers.com/v20/how-to/root-ls997-to-zv9-t3696488/amp/) I'll make a post in the thread asking the op to update the procedure so others will not be in my situation. At least now I know which files I need to find. Thank you.
wren2k said:
Unfortunately I didn't back up. Checking the procedure I followed it didn't tell me to (https://www.google.com/amp/s/forum.xda-developers.com/v20/how-to/root-ls997-to-zv9-t3696488/amp/) I'll make a post in the thread asking the op to update the procedure so others will not be in my situation. At least now I know which files I need to find. Thank you.
Click to expand...
Click to collapse
On that note if anyone reading this forum happens to have those files so I can flash them if you would upload them I would greatly appreciate it.
@wren2k Those files are unique to your phone, and I have no idea how to recreate them.
-- Brian
@runningnak3d
can you check pm of the modems im using.
@runningnak3d
Could you please share with me the QCN of the H910 or tell me where I could find it?
My computer has no signal or bluetooth, but imei and baseband are fine.
They told me that you only need to flash that to make it perfect.
Thank you very much and I hope you save me ....
Modem bands
I have lg stylo 3 plus tp450 do you have the please let me know I have absolutely stock firmware 10c thanks
spacebound88 said:
I have lg stylo 3 plus tp450 do you have the please let me know I have absolutely stock firmware 10c thanks
Click to expand...
Click to collapse
This is the v20 forum, suggest you search your models forum for modem files
Sent from my LG-H910 using XDA Labs
Lg vs995 no coverage in Ireland
runningnak3d said:
I am writing this because I see several people are having problems getting their phone to work on certain carriers.
There are four MAIN parts to an Android phone communicating with a cell network:
1 - The hardware modem itself. All MSM CPUs (MSM8996 in our case) have the same modem. It is built into the CPU. From the factory it is capable of talking on all 2G, 3G and 4G bands. However, there are QFPROM qfuses that can disable parts of the modem. These can be blown by the OEM or the carriers (if the phone is carrier branded).
2 - The modem firmware. This runs in the TZ and receives calls from the RIL -- they are AT commands just like an old school modem.
3 - The RIL (Radio Interface Layer). This runs as rild inside the Android OS, and is what things like the dialer or your SMS app talk to. All commands and voice paths are sent to this.
4- The antenna. Even if you have the ability to enable all bands, you probably don't have the antennas needed.
So, how do you know what is the limiting factor for your phone talking on a particular band? Trial and error.
First the hardware modem. If there are qfuses blown that disable bands -- there is NOTHING you can do about it. There (currently) is no way to check this, so you won't know until you try some of the software methods.
Next, the modem firmware. It is signed, so you can't just flash ANY firmware from any vendors phone. Now, on the V20, since LG screwed up, we can flash the modem from pretty much any model V20 onto any other model V20 (H918 being an exception). However, modem is also checked for ARB. So, if you are ARB 0, and you flash an ARB 1 modem, your ARB will be incremented and then you MUST run a full ARB 1 firmware stack. In the case of the H910, there is NO ARB 1 firmware stack -- so you have just toasted your phone. If you are ARB 1, and you flash an ARB 0 modem, you will get the "green screen of death". It won't brick your phone, but it won't boot till you flash a KDZ (or recover it with some other means).
So next up with have the RIL. This is actually the safest thing to test. Carriers CAN block bands at the RIL level. Replacing the RIL is simple, and won't brick your phone. Now, I say they CAN, but you won't know till your try. Flashing the system partition from another model that you CAN talk on the bands you want is the easiest way. However, your phone may not boot till some tweaks are made. This is completely safe though as long as you have a FULL backup of your phone. I don't mean a TWRP backup. I mean a dump of EVERY SINGLE partition (you can leave our userdata).
That leaves antenna. Even if you can unlock the bands, if you don't have an antenna for that band, you aren't talking.
So, before you guys go breaking your phones trying to unlock bands, do yourselves a favor and try the safest method first. If you want to flash modem firmware, and you aren't sure, send me a PM with the modem you have, and what you want to flash. I will tell you if it is at least not going to brick your phone.
-- Brian
Click to expand...
Click to collapse
Hi Brian,
Thanks for your informative post you seam to be very knowledgeable on this subject unfortunately I am not. Would you be able to help me or point me in the right direction I bought an lgv20 vs995 and I live in Ireland, the phone is lovely but I can't seam to get 2g signal on it. I can get 3g and 4g but its not great when I do if I compare to my lg g5. I have tried unlocking the bootloader and flashing lineage 14.1 but didn't help. Would you be able to tell me which version of the lg v20 would work best in my country and how would I go about flashing to its baseband?
Thanks a million,
Marc
Since you have a VS995 that has a KDZ so you can return to stock very easily, try them all, just make sure you backup modemst1 and 2, and misc before you start.
Also, do not flash H918 or any zips from LS997. Other than that, grab a KDZ, flash it, and see.
I would start with the H915, or US996. Then try the F800. If you don't care about root for now, you can use the F800 Oreo KDZ if you want Oreo.
The H990 is another one, not the H990DS.
If you find one that works, I can help you make a flashable zip that will let you keep root if you decide to root again based on the model that works for you.
At the end of the day though, it could be the VS995 radio just isn't good for 2g in your area.
Let me know.
-- Brian
runningnak3d said:
Since you have a VS995 that has a KDZ so you can return to stock very easily, try them all, just make sure you backup modemst1 and 2, and misc before you start.
Also, do not flash H918 or any zips from LS997. Other than that, grab a KDZ, flash it, and see.
I would start with the H915, or US996. Then try the F800. If you don't care about root for now, you can use the F800 Oreo KDZ if you want Oreo.
The H990 is another one, not the H990DS.
If you find one that works, I can help you make a flashable zip that will let you keep root if you decide to root again based on the model that works for you.
At the end of the day though, it could be the VS995 radio just isn't good for 2g in your area.
Let me know.
-- Brian
Click to expand...
Click to collapse
Hi Brian,
Thanks for the fast reply i will try over the next few days and il update as to what works and what doesn't . Aslo quick 1 im a bit confused with this ARB0 and ARB1 is there an easy way of checking whice one my phone is?
Thanks again,
Marc
Related
This also applies to Lg G Flex 2,so I literally copy and paste it here
This was not written anywhere specifically on the LG G4 forums that I could find. But every flash-addict needs to be warned. It is something you want to know before you continue tinkering.
Several users (myself included) have made the unfortunate mistake of attempting to downgrade their bootstack (for various reasons) to a former version.
DO NOT DO THIS (at least for the USA T-Mobile H811 version, and possibly other USA versions, per @autoprime)! It will result in a hard brick! Specifically, this results in the "Qualcomm QDLoader HS-USB port ( 9008 )" error. Connecting your phone to a PC will pop up with this active connection, but nothing else. There is no download mode. There is no publicly available fix as of yet.
There are reports of this happening both through KDZ restore as well as flashing bootstack .zips.
Yes, an official KDZ image can BRICK your USA phone, if you try to rollback.
This is in stark contrast to other manufacturers (i.e. Samsung), where the attempt to flash an older bootloader/modem/radio will simply fail, but your phone is not bricked.
I have conferred with @autoprime, who confirmed that with each OTA firmware release (on T-Mobile it was 10H, and now 10N), the version # increments. Flashing a lower version # will result in brick.
I have searched far and wide for a DIY fix. Without the proper firmwares in the right format, as well as the right flashing software, your phone is done and must be sent in for LG repair.
Click to expand...
Click to collapse
Autoprime says:
I have checked the most recent international builds and all are still on "v0". Tho that could always change in the future... but as of today... "v0"
The original out of box Tmo h811 version was "v0"... after the first forced OTA it became "v1"... as of 10N it is now "v2".
I do not have access to the latest AT&T, Sprint, US Cellular or Verizon bootstacks (seems there are no new KDZ's for them and no one has dumped the files) so I cannot confirm if AT&T, Sprint, US Cellular or Verizon's latest OTAs also move it up to "v2" or if still on "v1".
Actually.. I'm not even sure if Sprint, US Cellular or Verizon got a 2nd OTA yet.. but I know AT&T has "10i". If any 10i users who are rooted could dump the bootstack for me and send it over I can confirm.
Latest I know of for Sprint is ZV5.. thats "v1". US Cellular.. not sure.. but 10C was "v1". Verizon... again.. not sure what latest is.. but 11A is "v1".
Click to expand...
Click to collapse
OP
http://forum.xda-developers.com/g4/general/psa-warning-try-to-downgrade-g4-t3197675
Hi guys!
I live in Canada and I bought an V20 ATT version on eBay, the H910.
I was a bit uncomfortable with ATT apps and services, but when I looked up the information I found that the H910 model and the H915 had the same FCC certification number.
So, after I first rooted the H910, I changed the model name to H915 in BuildProp and porting the H915's rom with LGUP.
How was the result? I succeeded without problems.
It does not matter who is using the ATT in the US, but I think it will be helpful for those who use the ATT model in other carriers. As you know, the update itself is impossible without the ATT sim card.
However, I know that there is no KDZ file or TOT file of H910 right now. So after uploading the H915 ROM, you may not be able to go back to the previous.
I hope you will note this!
Would bee interested in the complete process to do this
And not sure what u mean by AT&T sim card
Sent from my LG-H812 using XDA-Developers Legacy app
in the process of unlocking the bootloader via DirtySanta, you also carrier unlock the phone for use on other cellular carriers.
the majority of v20 variants benefit from this, your variant included.
this has naught to do with FCC certification numbers being the same. its due to the phone having all bands available, and then being unlocked.
there are other routes to unlocking your phone, but those typically include paying off the device/keeping the bill current/etc.
this is a loophole of sorts.
Linenumber3 said:
Hi guys!
I live in Canada and I bought an V20 ATT version on eBay, the H910.
I was a bit uncomfortable with ATT apps and services, but when I looked up the information I found that the H910 model and the H915 had the same FCC certification number.
So, after I first rooted the H910, I changed the model name to H915 in BuildProp and porting the H915's rom with LGUP.
How was the result? I succeeded without problems.
It does not matter who is using the ATT in the US, but I think it will be helpful for those who use the ATT model in other carriers. As you know, the update itself is impossible without the ATT sim card.
However, I know that there is no KDZ file or TOT file of H910 right now. So after uploading the H915 ROM, you may not be able to go back to the previous.
I hope you will note this!
Click to expand...
Click to collapse
My only question is if when you reboot do you still have access to TWRP? If you do then LGUP only updated the ROM itself which you could have done with the ROMs available here. However, if it got rid of your recovery and you had to re-root then I could see this being a real benefit to those trying to change model numbers. I tried flashing a US996 entire firmware and ROM package to my device via TWRP and essentially locked myself out of the device because the partition sizes were different. If I could get my hands on an US996 PIT file I might be able to do a full transition but I don't know that it is worth it.
Linenumber3 said:
I was a bit uncomfortable with ATT apps and services, but when I looked up the information I found that the H910 model and the H915 had the same FCC certification number.
Click to expand...
Click to collapse
Hello
I'm interested in what you have done here.
How exactly did you determine that those models had the same certification number? I am looking here https://fccid.io/ZNF and I see H918, H910 etc. but not H915 and US996.
So I assume those last two are, well, like you said H915 is H910. But what is US996?
I would be very interested to know which other models correspond exactly to the ZNFH918.
Edit: Ok, so I checked around some more, and it seems H918 is the same as H910PR. Though I'm not completely sure.
Hello,
For some days I had a thread where my audio suddenly cut off or some weird noises appeared.
https://youtu.be/a1TaBH11bTI
What I´ve seen the problem is not uncommon and it is software related. So I wanted to ask you about your experience, could you fix the problem by flashing a custom Rom?
Stop making dupe threads, mods have already closed one
http://forum.xda-developers.com/showthread.php?t=3673744
*Detection* said:
Stop making dupe threads, mods have already closed one
http://forum.xda-developers.com/showthread.php?t=3673744
Click to expand...
Click to collapse
It is different because I think it software related and I want to know if it is possible to fix it throught different Roms.
My prior thread was different I didn´t know why it happend.
No, it's exactly the same, with the exact same problem and exact same video
*Detection* said:
No, it's exactly the same, with the exact same problem and exact same video
Click to expand...
Click to collapse
Because my problem is not solved
alecander said:
Because my problem is not solved
Click to expand...
Click to collapse
So what? Making multiple threads isn't going to fix it, make 1 thread and wait for an answer
Happens to me whenever my phones swaps from WiFi to LTE or vice versa. Otherwise if it is a software issue it's most likely a bootloader/modem mismatch. Have you been jumping between 6.x and 7.x Android? Because if you use a 6.x bootloader/modem with a 7.x android or the other way around, it will break vibration and other aspects of the software.
Beanvee7 said:
Happens to me whenever my phones swaps from WiFi to LTE or vice versa. Otherwise if it is a software issue it's most likely a bootloader/modem mismatch. Have you been jumping between 6.x and 7.x Android? Because if you use a 6.x bootloader/modem with a 7.x android or the other way around, it will break vibration and other aspects of the software.
Click to expand...
Click to collapse
No, I stayed on android 6 never updated or downgraded but what do you mean with modem? or bootloader/modem. Maybe I should add that I rooted the phone to gain twrp and root. And vibration and other stuff works well besides this sound problem
There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.
Beanvee7 said:
There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.
Click to expand...
Click to collapse
And that is how you fix your problem? Update the bootloader and modem? But after the flash I can still keep twrp or do I need to do the process anew?
Beanvee7 said:
There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?record=163A32D2CBDF11E69215FA163EE8F90B
So thats the version with the correct AP, CP and CSC when I flash the modem and bootloader everything should be fine I hope.
Yea my problems were fixed doing this, and if you only flash BL and CP you won't lose any data or TWRP.
I can't guarantee it will fix it, but it's a good start.
Beanvee7 said:
Yea my problems were fixed doing this, and if you only flash BL and CP you won't lose any data or TWRP.
I can't guarantee it will fix it, but it's a good start.
Click to expand...
Click to collapse
I flashed it but the sound problem remains it didn't make that aggressive sound cut off and noises like in my video but the sound still cuts off
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
what baseband are you currently on?
why would you want T-mobile modem? anything wrong with U-version?
turbozapekanka said:
why would you want T-mobile modem? anything wrong with U-version?
Click to expand...
Click to collapse
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
InsanePostman said:
what baseband are you currently on?
Click to expand...
Click to collapse
Mr. _Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Software version is the same. G930PVPS4BQE1 it's from May 2017.
Mr._Happy said:
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
Click to expand...
Click to collapse
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Mr._Happy said:
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Click to expand...
Click to collapse
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
turbozapekanka said:
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
Click to expand...
Click to collapse
Mr._Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Sprint is currently on bootloader 6, actually. Crappy obstructionist commercialism specifically to block people converting.
I have been denying and rejecting the software updates since May of 2017 which is when I got that software version, so your G930UUEU4APL2 firmware from January would not work on this phone as my Sprint firmware is more recent.
I should be able to flash the most recent version of G930U, however. I just can't seem to download one that will extract the AP portion. It's really frustrating.
Try this https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
You should be able to flash any firmware as long as the bootloader version is the same
For newer firmwares you may need to use the latest Odin version (3.13.x)
---------- Post added at 12:15 PM ---------- Previous post was at 12:07 PM ----------
I wonder why did you choose XAS version.
I also remember back in time I downloaded two versions of U-firmware (SPR and XAA) and compared the files they appeared identical.
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
What ROM have you been running?
Looks like slim pickins for the snapdragon chipset.
I assume all Exynos ROMs would obviously not work .
I have a SM-G930VL that I flash the G930U firmware . Much better
Stock
turbozapekanka said:
You should be able to flash any firmware as long as the bootloader version is the same
Click to expand...
Click to collapse
This is what I was saying. The last Sprint update I did on the phone was May 2017. I have been dismissing the update nag since then. Which means I could flash any G930U firmware with a date later than May 2017 with the same bootloader number.
Sprint has been trying to block this: their bootloader number is currently on 6, all the other carriers are on 4.
turbozapekanka said:
For newer firmwares you may need to use the latest Odin version (3.13.x)
Click to expand...
Click to collapse
Yep. The link I used to download the latest version was in the first post of this thread. 3.13 worked just fine.
The problems I was having had to do with the my computer, but I solved them and was able to to flash the latest version of G930U.
The phone is snappy and without the annoying lag.
Call quality improved immediately. With the Sprint firmware on the T-Mobile network there was a glitch with using the voicemail icon on the dial screen - it would fail to call the voicemail and give an incomplete call error; the workaround was to call myself from contacts and enter my pin to get to my voicemail. Now the voicemail icon on the dialer takes me to voicemail without a hitch. When calling it doesn't have a 15 - 20 second wait before ringing the number (the top left of the status bar would read "Attempting"). Internet reception is also better especially in the NYC subway.
Also as soon as my phone went from Sprint to T-Mobile I could no longer send or receive pictures via text. Apparently Sprint firmware wasn't interested in sending MMS messages anymore, but with the U firmware they work just fine and regular texts go through more quickly as well.
So far battery life is about the same as far as I can tell, maybe a marginal improvement. Nothing to call home about.
But mostly I seem to get the overall desired reception improvement: it stopped dropping calls, and the call quality is solid and the undersea world that had been happening with the Sprint firmware is gone.
Also the fingerprint scanner is working better.
It's much improved.
I REALLY like how it seemlessly goes from voice on network to voice on WiFi.
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
I am interested in testing the various towers, most frequent LTE bands, signal strength, and handset radios. Is there a thread for that or any apps you know of?
Mr._Happy said:
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
Click to expand...
Click to collapse
Yes it will get OTA updates including Oreo. U-version lags behind branded versions in this regard though.
i'm just got the oreo update - installing right now (us cellular)
i have tmobile g930t
if i shift to U , will volte work?
because i am unable to use volte in india now
Hey guys so I am brand-new to all this but need to convert my g930p to g930u. I just want to clear this up: because my software version is Q930PVPU6CRE7, I won't be able to flash the version OP used but must find a version with a 6 in it?
I'm in the same boat with my wife's phone. Limited bands available meaning it's on 3G more often than not, and MMS won't work if connected to WiFi. Not to mention the sprint junkware... is there any way to change from G930P to a G930U firmware if the phone is currently on bootloader version 6? I don't mind rooting...
I flashed G930U on G930P but network still not working. It shows unknown network and Radio Off. Mobile can read SIM menu and Contacts but no signal. Any help please?
EDIT: Now I know that changing ROM or rooting does not network unlock.
Mr._Happy said:
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
Click to expand...
Click to collapse
if i try this method to convert smg930u to smg930f will it work cuz meh need root ?
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
What MSM specifically? If it is the TMo one, then you won't get OTAs from 1+, they come from TMo. 11.2.8.8 is the latest from TMo
Phoenix47 said:
And the tmo to global conversion msmtool is not good. You get sim issue after updating to global oos12.
Click to expand...
Click to collapse
What SIM issues?
Phoenix47 said:
I was on TMO oos 11.2.9.9 before and got oos12 ota update with 5gb size. But now I only get ota till 11.2.8.8 on tmobile rom after using tmobile msm 11.2.2.2 available on xda.
.
.
Regarding sim issue, the global oos12 convert my single sim LE2117 to dual sim LE2115 which cause NO SIM bug.
Click to expand...
Click to collapse
Interesting, I never got 12 when I was TMo, only 11.2.8.8. Maybe different areas get different stages? It is weird the TMo ROM is so far behind though...
Did you follow step 9 of the conversion guide?
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Ah, I am not sure then how you'd fix the issue as I have an unlocked bootloader and root.
And I have not flashed the file yet or the Magisk fix. I have to send the phone off for screen repair, so I haven't popped a SIM in it since converting.
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
I'm also facing this issue
It's been over a week and still no updates after 11.2.8.8
My device was previously on OOS12 C.19 before i bricked it and uses the MSM tool
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
Did you run into SIM card issues after updating to C.48 using this method?
I'm just wondering if i can use the TMO-GLO MSM tool to get 11.2.2 them use the local update to 11.2.10.10 then go to C.48 to hopefully retain Cell service/SIM Card, any help on the matter would be appreciated!
Phoenix47 said:
It is weird that global rom shows dual sim on oos12. I mean there is single sim global model also.
.
And that magisk fix don't work on custom roms.
Click to expand...
Click to collapse
The T-Mobile model is actually dual SIM but with a single SIM tray from my understanding, hence the software bug.
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Flashing modem is only required on the 9 Pro because it has an mmWave modem.
Phoenix47 said:
So you are saying that adding dual sim tray will fix the NO SIM CARDS issue ?
Click to expand...
Click to collapse
No because it doesn't work right either.
EDIT: Looks like I misspoke anyway because it's only the LE2127.
ENABLE DUAL SIM ON TMO 9 PRO ONLY!!!
Frist off I'm not Responsible for anything that happens to your phone!!! THIS HAS BEEN TESTED AND WORKING 100% ON TMO 9PRO LE2127!!ALSO MODEM RETENTION. (THIS IT NOT FOR THE UNLOCKED 9PRO LE2125) DO THIS AT YOU OWN RISK!! THIS METHOD IS...
forum.xda-developers.com
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Does anyone have the TMO 11.2.8.8 or anything around there? I've heard of 11.2.9.9. I was on EU 11.2.10.10. it was mostly ok but I was having a few communication issues*. I want to compare to a stock TMO later-11 version. I'm currently on 11.2.3.3le5acb
I tried searching the forum but it doesn't allow searching for "11.2.8.8" type strings. Or short strings.
*Wifi stopped connecting to some of my APs. Until I toggled Mac randomization, then it was fine. It's no problem in my 7TP5G.
5G would drop off to LTE, no problem... But then, LTE would drop off into no data. SMS would sometimes get stuck until reboot. Visual voicemail worked when it wanted to. None of these were consistently happening but all more than once.
Overall it wasn't too bad really but I want to try a late-11 and see how it goes.
Thanks
EtherealRemnant said:
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Click to expand...
Click to collapse
i can agree with him. i was one of the first people to try this method on the thread he created. works wonderfully. hence why his thread was stickied to the top of xda oneplus 9 page.
I did look through bunch of threads but cant seem to find an answer . . Is there a way to enable dual sim on the LE2115 and if someone has tried successfully (with or without any known issues) ?
If someone can point me to the right steps to follow ?
TIA
centifanto said:
2.10.10. I quickly downloaded that, and lo and behold the upda
Click to expand...
Click to collapse
bguzz said:
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Click to expand...
Click to collapse
how you did the local update? did you have to unlock your bootloader?
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
why when i try to install 11.2.10.10 my phone reset and keep saying is LE2117, it won't let me install LE2115_11.F.16. Pls help
After all procedure I'm on latest global A13 with December security patch but I have very strange issue, after airplane mode or restart my sim stop working and I have to eject and re-insert the sim for network service any solution