Develop Bugs

[Q] Note 3 User - Moving to LG G3 - Please Help?

Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!

Any input guys?

ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt

itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !

ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.

itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!

ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way

itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?

Guide: How to upgrade/downgrade/restore official firmware on your V30.

Guide: How to upgrade/downgrade/restore OFFICIAL firmware on your V30.
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Only fully official, LG signed and blessed, unmodified firmware can be flashed using this method. No custom roms or recoveries!
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)

Thanks for the guide.

thank you. I would love to try the MIUI ROM on this device.

padmanek said:
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)
Click to expand...
Click to collapse
My apologies if I misunderstood. Is this a way to apply alternative ROMs even on models with locked bootloaders and the ADB Commands stripped out such as the H 933? I know you said already that it will work on any variant but I had lost hope that this model would ever allow modding of the rum. I just want to make sure I'm not misunderstanding the intention of your guide.
Sent from my LG-H933 using Tapatalk

Mad Medik said:
My apologies if I misunderstood. Is this a way to apply alternative ROMs even on models with locked bootloaders and the ADB Commands stripped out such as the H 933? I know you said already that it will work on any variant but I had lost hope that this model would ever allow modding of the rum. I just want to make sure I'm not misunderstanding the intention of your guide.
Click to expand...
Click to collapse
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
astikv said:
thank you. I would love to try the MIUI ROM on this device.
Click to expand...
Click to collapse
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.

padmanek said:
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.
Click to expand...
Click to collapse
Oh well, wishful thinking amd my mistake. I read it as upgrade or downgrade (eg various images) or restore stock.
Sent from my LG-H933 using Tapatalk

padmanek said:
It clearly says in the title of the thread and in the requirements that you can only flash full official (stock) firmware using this method...
Nothing custom. Everything needs to be RSA signed by LG.
Like above, only official (stock), LG signed and blessed firmware can be flashed using this method.
Click to expand...
Click to collapse
I meant in 1 future.

padmanek said:
Requirements:
LG V30
Windows PC
Official Firmware file for your V30 ending with .kdz. You can find it here https://forum.xda-developers.com/lg-v30/development or here https://lg-firmwares.com/
Bootloader does not need to be unlocked. All variants can be flashed using this method.
Only fully official, LG signed and blessed, unmodified firmware can be flashed using this method. No custom roms or recoveries!
Lets go:
Download and install LG USB drivers from here.
Download and install LG UP 1.14.3 from here.
Download .dll file for our V30, attached at the bottom of this post.
Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
Create folder called "common" and unzip the .dll file inside of it.
Connect the phone to your PC
[Optional]Open Device Manager and verify if under Ports you can see LGE Mobile USB Serial Port (COM...) to make sure the LG driver was installed correctly and the phone is visible.
Launch LGUP.exe
Select process called "UPGRADE" Warning: Selecting Refurbish will wipe user data.
Select the firmware file.
Click Start!
Your phone will automatically reboot into Download mode and upgrade firmware.
There's no need to do a factory reset afterwards but you can if you encounter any issues ofc. (I haven't)
Click to expand...
Click to collapse
Out of interest, will this work on a rooted V30. I seem to struggle to get LGUP to boot my phone into download mode. Is it because I have twrp as recovery?
Sent from my LG-H930 using Tapatalk

thenoble06 said:
Out of interest, will this work on a rooted V30. I seem to struggle to get LGUP to boot my phone into download mode. Is it because I have twrp as recovery?
Sent from my LG-H930 using Tapatalk
Click to expand...
Click to collapse
It will work as long as your /laf partition is in tact. It containts the DL mode. It has nothing to do with /recovery partition where you most likely flashed TWRP.
Read this: https://forum.xda-developers.com/v20/how-to/laf-download-mode-how-root-t3676011

Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?

sasc said:
Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?
Click to expand...
Click to collapse
Probably not but feel free to try it and let us know how that goes.

sasc said:
Just so I don't brick my device, I have an H930DS, therefore any firmware marked for this model (https://lg-firmwares.com/lg-h930ds-firmwares/), regardless of region, would work on my phone? My phone is currently on HK region version, can I flash the Indian firmware for the same model?
Click to expand...
Click to collapse
I have no idea about cross region firmware flashing. I have not found any official documentation about how each of LG UP's functions exactly works, it's all user experience here on XDA. Supposedly, every region has firmware signed with different RSA key which is verified upon trying to flash and it will reject you if it's a mismatch. Also I doubt Indian region has the same bands as HK so you might cripple your mobile signal if you happen to be on a band that is not supported in Indian firmware. Personally I don't recommend trying it but its up to you Please share your experience if you do
I know for sure that all H930 sold in EU, regardless of what carrier can be flashed with the same H930 unbranded EU firmware, which removes all carrier bloat and branding.

@sasc Check the RSA signature of your firmware and compare it to the firmware you want to flash. If they match, then it won't brick your phone. Your phone may not work, but at least your will have access to DL mode. If they don't match, you will definitely brick your phone..
-- Brian

padmanek said:
I have no idea about cross region firmware flashing. I have not found any official documentation about how each of LG UP's functions exactly works, it's all user experience here on XDA. Supposedly, every region has firmware signed with different RSA key which is verified upon trying to flash and it will reject you if it's a mismatch. Also I doubt Indian region has the same bands as HK so you might cripple your mobile signal if you happen to be on a band that is not supported in Indian firmware. Personally I don't recommend trying it but its up to you Please share your experience if you do
I know for sure that all H930 sold in EU, regardless of what carrier can be flashed with the same H930 unbranded EU firmware, which removes all carrier bloat and branding.
Click to expand...
Click to collapse
India and HK are both global GSM regions. The bands are the same, just like Europe.

runningnak3d said:
@sasc Check the RSA signature of your firmware and compare it to the firmware you want to flash. If they match, then it won't brick your phone. Your phone may not work, but at least your will have access to DL mode. If they don't match, you will definitely brick your phone..
-- Brian
Click to expand...
Click to collapse
Could you please tell us what's the best way to check the signatures?

Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!

spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
Thats great news ?. One question - to get VoWifi working, person at the other end should also have VoWifi? Or we can call VoWifi to VoLte. I have never tried VoWifi so just curious to know.

manishvy said:
Thats great news . One question - to get VoWifi working, person at the other end should also have VoWifi? Or we can call VoWifi to VoLte. I have never tried VoWifi so just curious to know.
Click to expand...
Click to collapse
VoWiFi does not need the person at the other end to have any special call options.

spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
Thanks amazing news! I will try this asap to get Volte on my HG 930DS (India carrier)

spacebar2011 said:
Okay.. I bring good news! You can definitely flash any KDZ as long as the model number is exactly the same. I flashed the HK Reginal kdz on my H930DS from India and I now have working VoLTE and VoWiFi.
In short, get the CORRECT kdz of the desired region for your model number, use LGUP, Upgrade option, and let it do its thing. Simple. This keeps the device official and under warranty.
PS - Please backup all data before doing this. Even though it is just an upgrade, play it safe. Just in case!
Click to expand...
Click to collapse
So...kind of didn't work.
I used the H930DS marked India in lgfirmwares. The flashing process went fine, except for the phone getting stuck right after the last restart and the screen went blank. Waited a couple of mins and forced a restart using the power button..booted fine but all data was gone. Thankfully i did backup some stuff, but not all..
Checked the Software version, it says V11i-GLOBAL-COM, which is obviously not the India version. And, I still dont have Volte!! So, this was futile..
Can anyone point me to a certified H930DS India KDZ?

Software update for Boost Mobile

I got the notification today.

guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
Same Here
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
have you saved the 66 mb zip ota update ? can you share it

If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.

sidgallup said:
If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.
Click to expand...
Click to collapse
YES

Welp... today i updated stock ROM to the latest version, after that i unlocked bootloader on Motos website, flashed TWRP, installed LineageOS and coudlnt get signal to connect to GSM, then flashed Resurrection Remix and same problem, everything works except calls, signal bars at at 0, no service.
This reminds me of some issues i had years ago and i needed to flash an older modem for calls to work.
Is anyone else having issues after updating to the latest stock ROM version?
EDIT: just confirmed theres something in the latest OTA that blocks GSM funcionality on custom ROMS, i did the exact same proccess with my brother's phone which is the same as mine, Boost E4, but this time without updating the stock ROM, just went directly to unlocking bootloader out of the box and this time is working perfectly.
I need some help now on how to go back to stock ROM and unlock mine.

It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?

nookin said:
It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?
Click to expand...
Click to collapse
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.

MotoJunkie01 said:
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.
Click to expand...
Click to collapse
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.

nookin said:
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.
Click to expand...
Click to collapse
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.

MotoJunkie01 said:
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.
Click to expand...
Click to collapse
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.

nookin said:
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.
Click to expand...
Click to collapse
Oh okay. That makes things clearer. With Boost Mobile being a Sprint owned subsidiary, and Tello being a Sprint affiliated MVNO, you are correct that with voice being functional, your data connection should likewise work. (Contrary to popular belief, Boost Mobile is not an MVNO and never has been.) I believe that, in your situation, the last OTA is likely not the problem, but rather with your ability -- or lack thereof -- to edit the APN settings. But, on a positive note, with root of the stock OS, using a root file editor can be used to manually modify your apns-config.xml file to add the 4G/LTE data and MMS parameters for Tello. I believe there are also root dependent apps which can edit APN settings.
Since your xt1766 is the Boost Mobile variant, your default APN & telephony parameters are configured specifically for Boost Mobile. I'm making an educated guess that using root permissions to add Tello data and MMS parameters should fix your issue.

No OTA update after converting Unlocked to TMB

I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.

live_in_the_sky06 said:
I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
Click to expand...
Click to collapse
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.

Yeah I did that. I'll back up my data and flash the old update, factory reset, and then see if it'll pull the latest update. Thanks. I've read where a couple of people are having issues with ota updating

I brought my Sprint Note 9 to TM. I didn't flash anything, but couldn't get OTA updates. I know I could have flashed TM, but I was lazy. I called my TM experts. They called Samsung. Samsung looked up to see where the nearest Samsung tech was. It was at a Best Buy. She was in the Geek Squad area. She evidently flashed the TM firmware. After that I was able to get the TM OTAs. There was no charge for this. I happily upgraded to the 10+ 5G when TM got it. I love it! It also came with Android 10 on it.

scottusa2008 said:
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Click to expand...
Click to collapse
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.

live_in_the_sky06 said:
... In the T-Mobile app my device shows as "Unknown device".....
Click to expand...
Click to collapse
This is normal since you brought your own device and didn't purchase it from T-Mobile.
live_in_the_sky06 said:
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
Click to expand...
Click to collapse
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1

scottusa2008 said:
This is normal since you brought your own device and didn't purchase it from T-Mobile.
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
Click to expand...
Click to collapse
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.

live_in_the_sky06 said:
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
Click to expand...
Click to collapse
Yes

scottusa2008 said:
Yes
Click to expand...
Click to collapse
Thanks for your help

Question Verizon factory image vs. Global

I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.

I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"

stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
What bloatware (and stuff) are you referring to regarding the VZW image?

stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
The Verizon firmware isn't a "Verizon owned" firmware, it's just a variant that Google has released because when Google sent out the "global" firmware for testing Verizon reported issues with it, and it was too late to incorporate the fixes and send out another firmware to all carriers for testing.
The variants in firmwares have nothing changed in them other than the radio/modem/network files and maybe app versions if the variant had to be built at a later date and picked up a new app version in the build process. The firmwares are exactly the same. They don't come with any additional bloatware, because Verizon's networking specific apps are actually already included in the base firmware and are enabled/disabled on the presence of a Verizon SIM. The bloatware you are delivered is when setting up the phone and the setup wizard will offer the carrier bloatware to be installed depending on the carrier of the SIM.
Run the firmware designated for your carrier. You might have service issues if you don't, but it will run almost the same.
I ran the Verizon variant on my phone with T-Mobile and I got service just fine, however it appears that Verizon wanted the scaling for network strength to be changed because it reported 0 bars even though I had service. It also wanted to try really hard to latch onto mmWave, so it appears that Verizon wanted that and potentially more changed.
Just run the online flash tool from Google to get updated, or follow the tutorial threads in the help section.
cmh714 said:
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
Click to expand...
Click to collapse
You'll have to flash more. There's also the modem inside the image and there are also APNs and other files for networks on the system image or vendor image too, so it's really just best to take the whole firmware.

Ok so I should just flash over the global and so as usual then right?

stalls said:
Ok so I should just flash over the global and so as usual then right?
Click to expand...
Click to collapse
You mean flash the Verizon firmware over the global firmware you already have on your phone? Yes, it will be fine. You don't need to wipe the phone.