For purpose of unlocking BL/Rooting/TWRP/CustomRom....which model would you recommend and why? Has one ease of these steps over the other?
Asking cos I'm new to LG, from Sammy Notes
jayinc11 said:
For purpose of unlocking BL/Rooting/TWRP/CustomRom....which model would you recommend and why? Has one ease of these steps over the other?
Asking cos I'm new to LG, from Sammy Notes
Click to expand...
Click to collapse
I'll go with the US997 since its officially supported for BL unlock. :good: although the H872 can be unlocked too. :good:
cheeze.keyk said:
I'll go with the US997 since its officially supported for BL unlock. :good: although the H872 can be unlocked too. :good:
Click to expand...
Click to collapse
I agree. Only I really suggest staying away from the H872 - if only because it's a pain in the ass to root correctly and you run the risk of accidentally loosing your LAF partition (download mode) making it next to impossible to KDZ back to a stock image later. US997 is much more straightforward.
Sobek5150 said:
I agree. Only I really suggest staying away from the H872 - if only because it's a pain in the ass to root correctly and you run the risk of accidentally loosing your LAF partition (download mode) making it next to impossible to KDZ back to a stock image later. US997 is much more straightforward.
Click to expand...
Click to collapse
totally agree with this. :good:
And staying away would also include the US Cellular version, yes? Not the same hootie, right?
cheeze.keyk said:
totally agree with this. :good:
Click to expand...
Click to collapse
cheeze.keyk said:
I'll go with the US997 since its officially supported for BL unlock. :good: although the H872 can be unlocked too. :good:
Click to expand...
Click to collapse
I came across a phone seller says it's a us997. Only more info he has given is LGUS997AUSAPL, GSM, nothing else.
Guys with that is there a way to know if this is the unlocked us997 and not the US cellular nor the Amazon version.
jayinc11 said:
I came across a phone seller says it's a us997. Only more info he has given is LGUS997AUSAPL, GSM, nothing else.
Guys with that is there a way to know if this is the unlocked us997 and not the US cellular nor the Amazon version.
Click to expand...
Click to collapse
This is the model of the (correct) 997 at best buy: Model:LGUS997.AUSABK SKU:5870305
That's the one I have, but the phone itself says only: On my phone it says just US997BK
I'd suggest asking them to run the imei number on this website: http://www.imeipro.info/check_lg.html
All you need to know from the results is (one the esn is clean, of course) what the Buyer Code / Buyer name is - it will either be USA or AMZ (AMAZON).
They should be able to do that for you, you'd think.
AsItLies said:
This is the model of the (correct) 997 at best buy: Model:LGUS997.AUSABK SKU:5870305
That's the one I have, but the phone itself says only: On my phone it says just US997BK
I'd suggest asking them to run the imei number on this website: http://www.imeipro.info/check_lg.html
All you need to know from the results is (one the esn is clean, of course) what the Buyer Code / Buyer name is - it will either be USA or AMZ (AMAZON).
They should be able to do that for you, you'd think.
Click to expand...
Click to collapse
Owner sent me this below. I just need to confirm that some US Cellular devices don't necessarily have a letter at the end of 997, such as this one, and that they are NOT the BL unlockable units, correct? That this is clearly a cdma unit, correct?
Brand: LG
Phone model: G6 US997
Serial number: 708KPGS0077615
Product model: LGUS997
Manufacture date: August 18, 2017
Shipped from factory: September 01, 2017
Estimated phone age: 1 year(s) 2 month(s) 3 week(s) 5 day(s)
Buyer code: UCL
Buyer name: U.S. Cellular
jayinc11 said:
Owner sent me this below. I just need to confirm that some US Cellular devices don't necessarily have a letter at the end of 997, such as this one, and that they are NOT the BL unlockable units, correct? That this is clearly a cdma unit, correct?
Brand: LG
Phone model: G6 US997
Serial number: 708KPGS0077615
Product model: LGUS997
Manufacture date: August 18, 2017
Shipped from factory: September 01, 2017
Estimated phone age: 1 year(s) 2 month(s) 3 week(s) 5 day(s)
Buyer code: UCL
Buyer name: U.S. Cellular
Click to expand...
Click to collapse
That device does not allow for bootloader unlock. Only the 997 purchased by buyer USA is bootloader unlock.
Is it cdma? Not sure there, I'd check the LG website to verify that. I had an Amazon one that was cdma, but I'm pretty sure the ones for t-mo are gsm only. US Cellular? I have no idea..
Related
My phone LG V30 H931 black AT&T model
i bought in dubai as 2nd hand phone and now
im trying to update OTA it says " Your device is already updated " . i have checked in AT&T software official site and the device has available update for July 2019 security patch. My phone security patch is still last July 2018 since i purchased it.
I also tried LG bridge computer update but it shows " LG bridge cannot detect your device O.S. " does it mean im stuck in 8.0 Oreo ? weird, i have a korean version LG V40 and connecting to Lg bridge has no problem it detects the current OS of my V40 LGU + model.
So i realized it maybe because my phone is AT&T model , USA based phone and im not using at&t sim nor network since im in Dubai now
Now question ,is there any other solution to update into android Pie 9.0? or should i just. sell my phone and better buy another V30 or V35 korean version which has no problem in updating O.S. rather than USA based phones which are restricted . thanks
zeusforever27 said:
My phone LG V30 H931 black AT&T model
i bought in dubai as 2nd hand phone and now
im trying to update OTA it says " Your device is already updated " . i have checked in AT&T software and device has available update for July 2019 security patch.
I also tried LG bridge pc update but it shows " LG bridge cannot detect your device O.S. " im stuck in 8.0 Oreo
So i realized it maybe because my phone is AT&T model and im not using at&t sim nor network since im in Dubai now
Now question ,is there any other solution to update into android Pie 9.0? or should i just. sell my phone and better buy another V30 or V35 korean version which has no problem in updating O.S. rather than USA based phones which are restricted . thanks
Click to expand...
Click to collapse
But h931 don't have pie yet right?
yes ,but im curious why LG bridge cannot detect the current O.S. of my lg v30? im just worried that my phone might not receive android update after long time of waiting.
Last question sir, if the AT&T phone is unlocked already like my LG V30 case, i can insert dubai sim now and it is working to other sim as well, does it mean that i can update as well the software android in any country i go? because this is AT&T US based phone ,does it really require AT&T sim ? or no need since the phone is already unlocked? thanks
zeusforever27 said:
My phone LG V30 H931 black AT&T model
i bought in dubai as 2nd hand phone and now
im trying to update OTA it says " Your device is already updated " . i have checked in AT&T software official site and the device has available update for July 2019 security patch. My phone security patch is still last July 2018 since i purchased it.
I also tried LG bridge computer update but it shows " LG bridge cannot detect your device O.S. " does it mean im stuck in 8.0 Oreo ? weird, i have a korean version LG V40 and connecting to Lg bridge has no problem it detects the current OS of my V40 LGU + model.
So i realized it maybe because my phone is AT&T model , USA based phone and im not using at&t sim nor network since im in Dubai now
Now question ,is there any other solution to update into android Pie 9.0? or should i just. sell my phone and better buy another V30 or V35 korean version which has no problem in updating O.S. rather than USA based phones which are restricted . thanks
Click to expand...
Click to collapse
Months ago, I wrote a Guide for AT&T H931 and Sprint LS998 which can't update, if you are not AT&T or Sprint customer. It tell HOW to update them.
It's a sticky:
H931 & LS998 -- How to Update to Latest Android Firmware!
https://forum.xda-developers.com/lg-v30/how-to/ls998-h931-how-to-update-t3927155
Got tired of answering the same questions over and over so I made it into a sticky. Please read it.
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Mrxyzl said:
But h931 don't have pie yet right?
Click to expand...
Click to collapse
No, doesn't have Pie yet, but soon will. They will get Pie. But this question is not really about Pie, this is about updating H931 at all. There's only one way to do that, if you are not an AT&T customer. I tell how in the Sticky.
I've answered this question two or three dozen times and people just keep creating new threads to ask again. Thought sure the Sticky would help and maybe it has.
zeusforever27 said:
Last question sir, if the AT&T phone is unlocked already like my LG V30 case, i can insert dubai sim now and it is working to other sim as well, does it mean that i can update as well the software android in any country i go? because this is AT&T US based phone ,does it really require AT&T sim ? or no need since the phone is already unlocked? thanks
Click to expand...
Click to collapse
Device being carrier unlocked (by some code) has nothing to do with getting carrier-approved updates only allowed for that carrier's customers.
AT&T and Sprint don't want you using their devices on other networks, and if you do, they punish you. They also don't care about AT&T/Sprint customers who may sell their phones on eBay to non-customers.
There is a solution. Read the sticky.
zeusforever27 said:
better buy another V30 or V35 korean version which has no problem in updating O.S. rather than USA based phones which are restricted . thanks
Click to expand...
Click to collapse
Only AT&T H931 and Sprint LS998 are ostensibly restricted. There's a way around the restriction, explained in the sticky.
Neither carrier release public KDZ for their updates. They will only do FOTA (Firmware Over The Air) for customers who have their SIM cards.
This is why LG Bridge won't work for H931 or LS998, because you can capture the URL to the LG Server and post it publicly. We do this all the time in the OTHER variant KDZ threads, where you can download KDZ straight from LG Servers. AT&T and Sprint won't allow that.
zeusforever27 said:
yes ,but im curious why LG bridge cannot detect the current O.S. of my lg v30? im just worried that my phone might not receive android update after long time of waiting.
Click to expand...
Click to collapse
You will have to manually install updates. See the sticky.
Guys i have h93120d software version in my at&t v30
and I have the same problem
I am asking if there's a way to get the latest official update
or how to crossflash the phone without broke the phone ?.
3xper said:
Guys i have h93120d software version in my at&t v30
and I have the same problem
I am asking if there's a way to get the latest official update
or how to crossflash the phone without broke the phone ?.
Click to expand...
Click to collapse
I've already answered. Read the sticky.
H931 & LS998 -- How to Update to Latest Android Firmware!
https://forum.xda-developers.com/lg-v30/how-to/ls998-h931-how-to-update-t3927155
ChazzMatt said:
I've already answered. Read the sticky.
H931 & LS998 -- How to Update to Latest Android Firmware!
https://forum.xda-developers.com/lg-v30/how-to/ls998-h931-how-to-update-t3927155
Click to expand...
Click to collapse
thanks I'll try
3xper said:
thanks I'll try
Click to expand...
Click to collapse
be carefull and read the article for 4 times at least i also have the same problem before and i fix it with the same method
pls read carefully
Thanks for all the responses sir, i decided to sell my at&t used phone, manual upgrading software is too much hectic and risky for me as an ordinary user.
So this is a lesson learned from me and i strongly advised to all foreigners like me who wants to buy 2nd hand LG phones ,better buy korean variants or international version, avoid US based carrier brand phones.
Sk telekom, LG U + this korean variants are way better ,no restriction any country u go u can update the O.S.
Using my LG V40 korean variant thanks
zeusforever27 said:
Thanks for all the responses sir, i decided to sell my at&t used phone, manual upgrading software is too much hectic and risky for me as an ordinary user.
So this is a lesson learned from me and i strongly advised to all foreigners like me who wants to buy 2nd hand LG phones ,better buy korean variants or international version, avoid US based carrier brand phones.
Sk telekom, LG U + this korean variants are way better ,no restriction any country u go u can update the O.S.
Using my LG V40 korean variant thanks
Click to expand...
Click to collapse
* I've already explained it's not all U.S. carrier phones. However, if you research you will know AT&T and Sprint LG phones do not give updates to non-customers, nor do they publicly release KDZ update files. Those two carriers only release FOTA (firmware over the air) to customers.
* Most everyone here in this forum uses or has used LGUP. It's not risky if you just read the directions.
Many people on different LG variants don't get OTA updates (like India H930DS) and even my wife's native US998 -- and it's not because they aren't U.S. carrier customers. So they come here to get updates, and manually install them via Dev Patched LGUP.
For everyone else with AT&T H931 or Sprint LS998, here's the answer:
H931 & LS998 -- How to Update to Latest Android Firmware!
https://forum.xda-developers.com/lg-v30/how-to/ls998-h931-how-to-update-t3927155
XT1710-01 (USA Retail - RETAIL) = Download
ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT-regulator-DEFAULT_CFC.xml.zip
XT1710-07 (Brazil Retail - RETBR) = Download
XT1710-07_ALBUS_RETBR_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Please donate to this website to help support the archiving of android firmwares, thanks!
It's interesting that the RETAIL rom didn't work for me. I bought my Z2 directly from motorola in the US, and yet my phone is apparently designated albus_c, not just albus, so the update doesn't go through.
Knuxyl said:
XT1710-01 (USA Retail) = Download
ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT-regulator-DEFAULT_CFC.xml.zip
XT1710-07 (Brazil Retail) = Download
XT1710-07_ALBUS_RETBR_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Please donate to this website to help support the archiving of android firmwares, thanks!
Click to expand...
Click to collapse
Should it working in moto z2 play xt1710-02 Verizon?? @knuxxyy
euskalzabe said:
It's interesting that the RETAIL rom didn't work for me. I bought my Z2 directly from motorola in the US, and yet my phone is apparently designated albus_c, not just albus, so the update doesn't go through.
Click to expand...
Click to collapse
If you boot into your bootloader, it will tell you albus or albus_c. Not sure why you received the albus_c if you bought directly from motorola.
In that case, your phone is considered RETUS, not RETAIL. The link below will take you to the RETUS firmware listing, but Pie for this version has not been released yet.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
euskalzabe said:
It's interesting that the RETAIL rom didn't work for me. I bought my Z2 directly from motorola in the US, and yet my phone is apparently designated albus_c, not just albus, so the update doesn't go through.
Click to expand...
Click to collapse
Sherzaman Khan said:
Should it working in moto z2 play xt1710-02 Verizon?? @knuxxyy
Click to expand...
Click to collapse
I do not know, but from what I understand the bootloader cannot be unlocked on Verizon model so I doubt you can fastboot flash your device.
If you want the answer to that question your going tohave to try it.
Knuxyl said:
I do not know, but from what I understand the bootloader cannot be unlocked on Verizon model so I doubt you can fastboot flash your device.
If you want the answer to that question your going tohave to try it.
Click to expand...
Click to collapse
I tried already now my device stuck at bootloader saying start up failed now install stock rom oreo saying security version downgrade what i do? @knuxyl
Sherzaman Khan said:
I tried already now my device stuck at bootloader saying start up failed now install stock rom oreo saying security version downgrade what i do? @knuxyl
Click to expand...
Click to collapse
download latest vzw firmware and flash it
https://mirrors.lolinet.com/firmware/moto/albus/official/VZW/
I was and still am confused...I never knew what ALBUS meant. I thought it had something to do with another country Upgrade channel knowing that US is RETUS.
Seeing the 2nd post above-- I also bought my US Retail version from Moto and its the XT1710-01. When looking at phone settings - it mentioned RETUS somewhere. So I just booted to recovery- and Product/Variant is: albus XT1710-01. Does this mean that I can do the Fastboot method from OP?
Thx
Chris
Each Android device has it's code name. For Moto Z2 Play it is albus, although for some American devices it is albus_c. XT-1710-something is model number. In different countries, different models are sold. RETUS, RETAIL, RETEU, RETBR and so on are update channels. I believe that if your bootloader is locked, you can only flash update from the same channel and only update, not downgrade. If your bootloader is unlocked, you can flash also firmwares from other channels to update and downgrade but it still does not change your device's update channel.
So if you are not unlocked and your channel is RETUS, I don't think you can flash RETAIL or anything else than RETUS. And you will have to wait for Pie for RETUS to be released.
Klen2 said:
If your bootloader is unlocked, you can flash also firmwares from other channels to update and downgrade but it still does not change your device's update channel.
So if you are not unlocked and your channel is RETUS, I don't think you can flash RETAIL or anything else than RETUS. And you will have to wait for Pie for RETUS to be released.
Click to expand...
Click to collapse
Wait, wait. I'm on an Albus C, which uses RETUS. Are you telling me that by simply unlocking the bootloader I could use the RETBR official ROM and just update my phone already? It's that simple? Cos it's been 2 months already and I'm quite tired of this stupid unnecessary wait.
I've had my Pixel 6 for less than a month, bought it in Canada and updated in November to SD1A.210817.037, then rooted with Magisk. All is fine.
Now, I'm in Mexico with it, on Telcel, and the December updates have come out, but I have no idea which one to flash. Does anyone know?
The options are:
12.0.0 (SQ1D.211205.016.A1, Dec 2021)
12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers) *** I'm pretty confident it's not this one***
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)
I'm thinking that it's the first option, but I'm not sure...
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers) <--- I used this since T-Mobile is a US carrier
Probably for you, your best option is to flash the first option
I'm asking myself the same question. I've a Canadian model too. Once I bought it I flashed "12.0.0 (SD1A.210817.019.C2, Oct 2021, T-Mobile (US), USCC, Google Fi, CA, & TW carriers)" with magisk. I didn't even update to the November one because I wasn't sure, but I would like to do this one and see if that solve some bugs that I have. I just would like to be sure about the first option (which would make sence).
basily said:
I've had my Pixel 6 for less than a month, bought it in Canada and updated in November to SD1A.210817.037, then rooted with Magisk. All is fine.
Now, I'm in Mexico with it, on Telcel, and the December updates have come out, but I have no idea which one to flash. Does anyone know?
The options are:
12.0.0 (SQ1D.211205.016.A1, Dec 2021)
12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers) *** I'm pretty confident it's not this one***
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)
I'm thinking that it's the first option, but I'm not sure...
Click to expand...
Click to collapse
I'm from Monterrey, currently using Telcel and AT&T. I already flashed the dec update, go for the 1st one (12.0.0 (SQ1D.211205.016.A1, Dec 2021)).
=)
Kimbaroth said:
I'm from Monterrey, currently using Telcel and AT&T. I already flashed the dec update, go for the 1st one (12.0.0 (SQ1D.211205.016.A1, Dec 2021)).
=)
Click to expand...
Click to collapse
Thank you friend
sorry y'all. Im in California, bought my P6P unlocked from Google directly. Should I use the 1st one (or the US carrier one (3rd)?
Thanks very much!
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
AliasGprime said:
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
Click to expand...
Click to collapse
Can you link to said post, please?
I know that the right thing to do is to wait, but... well... ok, I'll wait :-|
basily said:
Can you link to said post, please?
I know that the right thing to do is to wait, but... well... ok, I'll wait :-|
Click to expand...
Click to collapse
Sure, it's a post that explain how to update without losing root.
Method to upgrade every month, without wiping data and retaining root
Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling...
forum.xda-developers.com
But most recent posts says they wont keep root after the update. Saw the same reports on a Telegram and a discord server.
I'm wondering the same thing as well. I'm running Mint Mobile (T-Mobile MVNO) on an Unlocked P6P in the US. I assume the US Carriers is the one I need to flash but I'm not positive.
I'm getting corrupted data and stuck on google screen can anyone assist?
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
I have not put a SIM in it yet, but it is in Europe.
Why did it not update to the A4 (EMEA Carriers) version ?, which is supposed to be for UK, IE, FR, DE.
And which EMEA carriers are we talking about, only from these countries: UK, IE, FR, DE, or also other from Europe ?
I wonder if I can install the A4 full OTA package over the A1 version ?
Vio281 said:
I'm getting corrupted data and stuck on google screen can anyone assist?
Click to expand...
Click to collapse
You'll find some colleagues here:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
andreipaval said:
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
Click to expand...
Click to collapse
Check the support page again -- it's been updated and now says the 016.A1 version is the global unlocked version. I was told something similar by a Google chat rep through the in-phone support function.
You're on the right build.
I'm in the US. Google is telling me I can be either on SQ1D.211205.016.A1 or SQ1D.211205.017. Doesn't seem like a reliable answer. I have an unlocked P6P and I'm on Verizon. Did anyone get a clear answer?
This is nuts.
Why would Google not have one image that adapts to the carrier in-play? After all, folk can change carriers/regions during the life of their phone. What happens then? The phone doesn't work properly until it somehow figures out it needs a different image and then somehow flips to it?
What about if you temporarily travel to a different region and roam onto a different operator? Is your phone not 'right for that region' and doesn't work properly?
So do these different images relate to different hardware variances of the phone?
lpkallia said:
I'm in the US. Google is telling me I can be either on SQ1D.211205.016.A1 or SQ1D.211205.017. Doesn't seem like a reliable answer. I have an unlocked P6P and I'm on Verizon. Did anyone get a clear answer?
Click to expand...
Click to collapse
I don't think anyone knows at this point. There are some major issues with network connectivity some are blaming on the December update and some are saying ongoing from previous builds. I'm in the latter group. They will have to come out with a new update sooner rather than later since this is widespread across the globe.
AliasGprime said:
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
Click to expand...
Click to collapse
Magisk is running perfect on the december update. And no problems with 4G ,, I did a clean install on de December update.
Used the A1 version and no problems at all.
andreipaval said:
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
I have not put a SIM in it yet, but it is in Europe.
Why did it not update to the A4 (EMEA Carriers) version ?, which is supposed to be for UK, IE, FR, DE.
And which EMEA carriers are we talking about, only from these countries: UK, IE, FR, DE, or also other from Europe ?
I wonder if I can install the A4 full OTA package over the A1 version ?
Click to expand...
Click to collapse
Hmm, looks interesting. i have a spare Nexus device, so i can easily try it.
ok i've successfully updated SQ1D.211205.016.A4 (EMEA) over SQ1D.211205.016.A1 (global) using full ota. Storeage remains intact. Sim works (Spusu / Austria / Sub carrier using Hutchison Drei Austria).
But upgrading to SQ1D.211205.017 failed with "Build newer than timestamp 1638904347 but package has timestamp 1638280743 and downgrade not allowed". The same if you try to revert back to .A1 Image, so you have to unlock the bootloader and reflash the stock image. Of Course, all data will be lost.
sakerhetz said:
Magisk is running perfect on the december update. And no problems with 4G ,, I did a clean install on de December update.
Used the A1 version and no problems at all.
Click to expand...
Click to collapse
Yeah, I did it yesterday too. i was waiting for a Magisk-Alpha update before, which we got yesterday. I need this one specially for Denylist to work without zygisk.
I'm at my wit's end on this. Calls stopped working the other day due to 3G disablement as far as I can tell. AT&T model unlocked and using with Simple Mobile on T-Mobile network. Calls would just say "Calling" for a long time and then eventually disconnect. I could switch to GSM and make calls again, but slow data. Simple told me to get a new SIM and when trying to activate, it shows ineligible IMEI due to no Volte it seems.
I'm trying to get that fixed, but running into various issues.
LM-G850UM
I tried to crossflash (https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/)
I flashed G850QM30c_00_NAO_US_OP_0224.kdz but it didn't ask me to change the model, so it still shows LM-G850UM software G850UM30c. IMEI is the same.
Since this didn't get calls back or Volte, I tried updating the MBN (https://forum.xda-developers.com/t/...ther-qualcomm-powered-lg-devices-too.4343655/)
Data shows 4G. Calls don't even try to connect.
I don't know what to do next and don't have much time to try to figure it out. I like the G8X, so I'm hoping there's a way to save it.
Any thoughts from the experts?
Brando81 said:
I'm at my wit's end on this. Calls stopped working the other day due to 3G disablement as far as I can tell. AT&T model unlocked and using with Simple Mobile on T-Mobile network. Calls would just say "Calling" for a long time and then eventually disconnect. I could switch to GSM and make calls again, but slow data. Simple told me to get a new SIM and when trying to activate, it shows ineligible IMEI due to no Volte it seems.
I'm trying to get that fixed, but running into various issues.
LM-G850UM
I tried to crossflash (https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/)
I flashed G850QM30c_00_NAO_US_OP_0224.kdz but it didn't ask me to change the model, so it still shows LM-G850UM software G850UM30c. IMEI is the same.
Since this didn't get calls back or Volte, I tried updating the MBN (https://forum.xda-developers.com/t/...ther-qualcomm-powered-lg-devices-too.4343655/)
Data shows 4G. Calls don't even try to connect.
I don't know what to do next and don't have much time to try to figure it out. I like the G8X, so I'm hoping there's a way to save it.
Any thoughts from the experts?
Click to expand...
Click to collapse
Make a back up,and cross flash it with T-Mobile firmware.Problem solved.
Thanks Surge!
I crossflashed to general firmware. Where's the best place for the TMobile firmware? Just off their website? Will that lock the phone again, or will I still be able to use the Simple Mobile Service?
Brando81 said:
Thanks Surge!
I crossflashed to general firmware. Where's the best place for the TMobile firmware? Just off their website? Will that lock the phone again, or will I still be able to use the Simple Mobile Service?
Click to expand...
Click to collapse
It shouldn't lock the device if it's already unlocked.You can also use G8 firmware as well.(same device)Look here,this should get you the firmware you need.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
Thanks again, Surge.
That's where I got my KDZ before. I used the one here: https://lg-firmwares.com/lg-lmg850qm-firmwares/ and used the 3/24/22 version for Android 11. When I flashed it with LG UP, it didn't ask me to change models, which I'm not sure if that's why it didn't trigger it to start working again.
Brando81 said:
Thanks again, Surge.
That's where I got my KDZ before. I used the one here: https://lg-firmwares.com/lg-lmg850qm-firmwares/ and used the 3/24/22 version for Android 11. When I flashed it with LG UP, it didn't ask me to change models, which I'm not sure if that's why it didn't trigger it to start working again.
Click to expand...
Click to collapse
Most are using the international firmware for the G8 and G8x models.Which is what the qm firmware is.If you're carrier is T-Mobile or any T-Mobile MVNO,I would solely use T-Mobile firmware.My G8x is AT&T branded and factory unlocked,and I tried using Tmobile service about 2 months ago and was having issues sending text messages.I could place and receive calls and get text but couldn't send them period.
Yeah, so my G8X is AT&T unlocked. AT&T didn't activate VOLTE on this model, so when T-Mobile shut down their 3G network, Simple Mobile calls won't work and the current IMEI shows it's not eligible (because of the model.) At least that's my understanding so far.
So for the G8, is this the firmware I should crossflash? https://lg-firmwares.com/lg-lmg820tm-firmwares/ or I could try the QM which may or may not work. Is that correct? Basically going to the 820 firmwares instead of the 850?
Brando81 said:
Yeah, so my G8X is AT&T unlocked. AT&T didn't activate VOLTE on this model, so when T-Mobile shut down their 3G network, Simple Mobile calls won't work and the current IMEI shows it's not eligible (because of the model.) At least that's my understanding so far.
So for the G8, is this the firmware I should crossflash? https://lg-firmwares.com/lg-lmg820tm-firmwares/ or I could try the QM which may or may not work. Is that correct? Basically going to the 820 firmwares instead of the 850?
Click to expand...
Click to collapse
I would go with the T-Mobile firmware since you're on their network.It wouldn't make a difference with VoLTE enabled with an AT&T sim.Once you pull the sim,and swap it it defaults back and turns the IMS settings off until it receives the configuration from their servers.Yes,820 firmware.It at least has the higher android builds,and better security patches.Once you put T-Mobile firmware on the device it should all work regardless of IMEI.
Edit:Make a back-up.Don't forget to do that first!
OK Surge....you've been helpful and seem to know what you're doing. What did I mess up?
I followed the cross flash instructions. I flashed the 820QM firmware first, and System loaded but the touchscreen wouldn't respond. I could only use the hard phone buttons. Decided to go to what you recommended with 820TM and it wouldn't boot at all - black screen - but I could still get to QFIL and LGUP.
I reflashed 850QM and touchscreen works again and I'm back to where I started.
When I flashed 820s, It did ask me if I wanted to change model numbers this time and I said Yes. And it asked it said it was changing some partitions on the 820 loads.
I may have been working on this too late. I appreciate your help so far.
Brando81 said:
OK Surge....you've been helpful and seem to know what you're doing. What did I mess up?
I followed the cross flash instructions. I flashed the 820QM firmware first, and System loaded but the touchscreen wouldn't respond. I could only use the hard phone buttons. Decided to go to what you recommended with 820TM and it wouldn't boot at all - black screen - but I could still get to QFIL and LGUP.
I reflashed 850QM and touchscreen works again and I'm back to where I started.
When I flashed 820s, It did ask me if I wanted to change model numbers this time and I said Yes. And it asked it said it was changing some partitions on the 820 loads.
I may have been working on this too late. I appreciate your help so far.
Click to expand...
Click to collapse
I think someone else encountered this once before,and it was caused by certain manufacturering dates of the device.Some models can use 820 firmware,and some can only use 850.Looks as if yours is kind of stuck with 850 firmware only.I think the AT&T version I have I could go either way it worked with no problems.I still have my G8x but never really used it.I bought it because it came with the dual screen attachement,and $125 I took it.Here's my Sprint copy if you want to give it a try.It's a LUNS copy minus LUNS 5 for IMEI information etc.I was in the same boat as you on certain features not working with AT&T at one point myself and had to crossflash the Sprint version of the device.With that being said,try this one from LG Fans first.If that doesn't work,try my LUNS Sprint copy and let me know which ones works the best.
LG G850UM | LG G8X ThinQ | Version: G850UM30a_00_0901 | Firmware for Region: CAN from - Lg-firmwares.com
LG G850UM Download the latest version of firmware | OS Version: Android 11 R | Firmware version: G850UM30a_00_0901 | CAN - Fan club LG-firmwares
lg-firmwares.com
Sprint LG G8x Last Update - Google Drive
drive.google.com
So interesting news....I obviously didn't try making calls last night at 2AM, but apparently reflashing with the same exact 850QM software I used before seems to have fixed the issue. Maybe changing the model to 820 and then changing back to 850? Who knows? That's like the 3rd thing that happened with this process that I have no idea why it started working differently, but hey I'm happy and back up and rolling.
Thanks for all of your help, Surge! I was truly at wits end, and had already ordered a new phone, even though I'm happy with the G8X overall. Now I can return that and keep rolling with the G8X.
Thanks again, you were a huge help and its much appreciated!
Brando81 said:
So interesting news....I obviously didn't try making calls last night at 2AM, but apparently reflashing with the same exact 850QM software I used before seems to have fixed the issue. Maybe changing the model to 820 and then changing back to 850? Who knows? That's like the 3rd thing that happened with this process that I have no idea why it started working differently, but hey I'm happy and back up and rolling.
Thanks for all of your help, Surge! I was truly at wits end, and had already ordered a new phone, even though I'm happy with the G8X overall. Now I can return that and keep rolling with the G8X.
Thanks again, you were a huge help and its much appreciated!
Click to expand...
Click to collapse
Glad you got it working!I run in to a same similar issue with a Note 8 I have,and it being an international unlocked AT&T phone.No calls would work period,and swapped firmware over and over and finally started to give up and flashed the stock firmware back and it worked.It's something that hangs in Android with the changed IMS settings that are sent to the device.It's all odd at the moment with carriers,but nothing surprises me anymore..lol..
"G850QM30c_00_NAO_US_OP_0224.kdz" Is a BPT kdz and is not truly open even though it says, "NAO US OP".
I got the phone working by using "G850QM30b_00_NAO_US_OP_0902.kdz", the "real" open kdz. Everything worked fine after that.
BereiBlue said:
"G850QM30c_00_NAO_US_OP_0224.kdz" Is a BPT kdz and is not truly open even though it says, "NAO US OP".
I got the phone working by using "G850QM30b_00_NAO_US_OP_0902.kdz", the "real" open kdz. Everything worked fine after that.
Click to expand...
Click to collapse
Can someone please explain to me the different versions of the firmware
BPT and CCT and USA
are they really different
there is also the 40A now which is android 12?
G850QM40b_00_NAO_US_OP_0805.kdz
https://lg-firmwares.com/lg-lmg850qm-firmwares/
most of these firmwares are are 4GB in size, the newer KDZ are just 1GB
G850QM30c_00_NAO_US_OP_0224.kdz
My ATT G8X just got the update to G850QM40A which is android 12
how is android 12? do the firehose , root and bootloader unlock apply
doctorman said:
Can someone please explain to me the different versions of the firmware
BPT and CCT and USA
are they really different
there is also the 40A now which is android 12?
G850QM40b_00_NAO_US_OP_0805.kdz
https://lg-firmwares.com/lg-lmg850qm-firmwares/
most of these firmwares are are 4GB in size, the newer KDZ are just 1GB
G850QM30c_00_NAO_US_OP_0224.kdz
My ATT G8X just got the update to G850QM40A which is android 12
how is android 12? do the firehose , root and bootloader unlock apply
Click to expand...
Click to collapse
Yes,the firehose will always work regardless of the Android version.Also from what I have read,yes the same procedures work for A12 for root and unlocking the bootloader.As always,backup your firmware before rooting and attempting to unlock the bootloader just in case something goes wrong!
Surgemanxx said:
Yes,the firehose will always work regardless of the Android version.Also from what I have read,yes the same procedures work for A12 for root and unlocking the bootloader.As always,backup your firmware before rooting and attempting to unlock the bootloader just in case something goes wrong!
Click to expand...
Click to collapse
Do you think there is any point to crossflash
USA G850QM40b_00_NAO_US_OP_0805.kdz
on ATT G8X to be used on Tmobile network? I can do the VOLTE patch after rooting it . is it worth the headache?
doctorman said:
Do you think there is any point to crossflash
USA G850QM40b_00_NAO_US_OP_0805.kdz
on ATT G8X to be used on Tmobile network? I can do the VOLTE patch after rooting it . is it worth the headache?
Click to expand...
Click to collapse
QM versions are international unlocked versions of the firmware.My branded AT&T G8x had issues sending text messages with T-Mobile service I do remember.I crossflahed my variant with the QM version and it worked flawless after that.But,I do have a full backup copy of the AT&T firmware if I ever decide to put it back.
Surgemanxx said:
QM versions are international unlocked versions of the firmware.My branded AT&T G8x had issues sending text messages with T-Mobile service I do remember.I crossflahed my variant with the QM version and it worked flawless after that.But,I do have a full backup copy of the AT&T firmware if I ever decide to put it back.
Click to expand...
Click to collapse
May I ask how did you back it up?
also if I have androind 11 ATT can I crossflash to android 12? that should not be an issue right?
the partitioning is not changed in the update?
I'm just collecting some info
What are all of the different models for the OnePlus Nord N200 5G?
The codename of the device is "dre".
DE2118 is the T-Mobile model when you buy through them (or Metro, I think).
I think DE2117 is the unlocked USA model? I'm not completely sure what the difference is between it and the DE2118.
DE17AA is apparently the global unlocked model.
Are there other models?
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
DE2117 is OEM unlocked USA. It's SIM unlocked / carrier unlocked and bootloader unlocked.
DE2118 is SIM locked / carrier locked to T-mobile or Metro-by-T-mobile. Some have reported that a DE2118 purchased from T-mobile or Metro also accepts Mint mobile (without needing to SIM unlock). It's possible they may also accept other MVNOs that use the T-Mobile network.
DE2118 is bootloader locked, "OEM unlocking" is off and greyed-out, not toggle-able. It becomes an option after the phone is SIM unlocked. Many have also been able to enable OEM unlocking with a bypass, using adb shell pm uninstall --user 0 com.qualcomm.qti.uim which a debloater script will also do for you. OnePlus might "fix" this loophole at some point. But if they do we can probably reverse it by downgrading.
I understand the DE2118 you get from either T-mobile or Metro loads the appropriate branded apps based on which SIM it first sees.
The different models are also listed in this guide Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
dre is the general device codename, but you may also see dre9 (DE2117) or dre8t (DE2118).
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform. [1] [2]
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
Click to expand...
Click to collapse
I believe DE18CB is just from the build number. You have that actually in the Model field? Here's a picture of it in the build number, with in the Model field showing DE2118.
Lots of extremely helpful hints. I already knew most of them from reading today, but thanks!
That notes daboross/oneplus_dre8t_dre9_holi_notes link was perfect. That's what I was assembling for myself.
blueberry.sky said:
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform
Click to expand...
Click to collapse
Ahha! Now that's new to me. I had seen it in fastboot and was wondering about it. Thanks!
Further reading seems to confirm my previous assumption that there are only three models, but sometimes people are refering to software versions in the model numbers, which might just be part of the file names for those releases/recoveries.
I've seen the "DE17AA" model also referred to as "DE2117AA". I don't know which is true or what the best nomenclature is, since I don't actually have one of these international unlocked models.
"DE17AA" I believe is just from software build numbers. And not a model number. DE17AA seems to be in the build numbers intended for the DE2117 model. Whereas DE18CB is in build numbers intended for the DE2118 model.
OnePlus Nord N200
Contribute to OnePlusOSS/OpenSourceReleases development by creating an account on GitHub.
github.com
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
Click to expand...
Click to collapse
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Sprunglicious said:
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Click to expand...
Click to collapse
How do you convert DE2118 to DE2117
Tranken587 said:
How do you convert DE2118 to DE2117
Click to expand...
Click to collapse
Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
CHANGELOG: Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware. Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first. There are THREE firmware versions for the N200...
forum.xda-developers.com