Related
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.
As of this writing (11/29/2017) this is the latest firmware for the G950U1 att unlocked S8 . I'm leaving this here for reference so people can return to it if/when they need it.
Download, extract, remove .md5 file name off the end of each file, flash.
G950U1UEU2AQK2 (This WILL update your bootloader so after this, no going to QH3 or before. Not that you'd have a reason to)
https://drive.google.com/open?id=1gvQ0kaZTwbEYe2jvuIa05pCvwkS4ddtg
joe3681 said:
As of this writing (11/29/2017) this is the latest firmware for the G950U1 att unlocked S8 . I'm leaving this here for reference so people can return to it if/when they need it.
Download, extract, remove .md5 file name off the end of each file, flash.
G950U1UEU2AQK2 (This WILL update your bootloader so after this, no going to QH3 or before. Not that you'd have a reason to)
https://drive.google.com/open?id=1gvQ0kaZTwbEYe2jvuIa05pCvwkS4ddtg
Click to expand...
Click to collapse
you donnt need to remove the .md5
you will need modded odin though.
mweinbach said:
you donnt need to remove the .md5
you will need modded odin though.
Click to expand...
Click to collapse
You don't need to no, but it speeds up the process. I'm just posting firmware not making a hand holding tutorial. There's enough of those around
Thanks Joe I was tired of returning all the way back to the beginning and getting all those new updates on my unlocked S8
joe3681 said:
You don't need to no, but it speeds up the process. I'm just posting firmware not making a hand holding tutorial. There's enough of those around
Click to expand...
Click to collapse
Yeah and on a Mac you do need to, or it freezes Odin completely
If I flash unbranded FW on a carrier specific device, loke tmo or att for example, would it sim unlock the phone?
If I flash tmo FW on an att s8 would it in turn allow me to use the att original device on tmo? I ask these questions because I feel like it would work for both my questions since flashing the FW flashes both boot, kernel and baseband/radio. The which is needed for signal. Just some theories but would love to know the answers.
Btw, I have a F model S8+ and was planning on buying some US branded devices so I was curious.
this.guy.lol said:
If I flash unbranded FW on a carrier specific device, loke tmo or att for example, would it sim unlock the phone?
If I flash tmo FW on an att s8 would it in turn allow me to use the att original device on tmo? I ask these questions because I feel like it would work for both my questions since flashing the FW flashes both boot, kernel and baseband/radio. The which is needed for signal. Just some theories but would love to know the answers.
Btw, I have a F model S8+ and was planning on buying some US branded devices so I was curious.
Click to expand...
Click to collapse
No, it will not unlock the phone (Note: Verizon phones are factory unlocked and remain that way after a firmware flash)
Yes, you can flash any carriers FW to a US S8 and use it with a different carrier.
So I understand, your saying if I flash att FW to a T-Mobile s8 I can use it on tmobile? If that is the case, to me that's an unlock of sorts tiny book lol. Just wanna make sure is all
Deleted
this.guy.lol said:
So I understand, your saying if I flash att FW to a T-Mobile s8 I can use it on tmobile? If that is the case, to me that's an unlock of sorts tiny book lol. Just wanna make sure is all
Click to expand...
Click to collapse
You can flash att firmware and use it on TMobile but it will still be locked to TMobile. Just running att firmware.
joe3681 said:
You can flash att firmware and use it on TMobile but it will still be locked to TMobile. Just running att firmware.
Click to expand...
Click to collapse
Just realized the typo.....what I meant was, if I flash ATT on a TMO variant I can use ATT while locked to tmo? I'm very unfimiar with combination fw and always opted for the UK models for alot of reasons. Sorry for the confusion of my op question. I know on the s7 and edge if you flashed the US unlocked firmware it not only removed AOL bloat but it unlocked the device. So that is why I ask.
this.guy.lol said:
Just realized the typo.....what I meant was, if I flash ATT on a TMO variant I can use ATT while locked to tmo? I'm very unfimiar with combination fw and always opted for the UK models for alot of reasons. Sorry for the confusion of my op question. I know on the s7 and edge if you flashed the US unlocked firmware it not only removed AOL bloat but it unlocked the device. So that is why I ask.
Click to expand...
Click to collapse
I had a TMobile S7 edge and flashing unlocked firmware never unlocked the device. That's handled by TMobile servers so...
Flashing unlocked firmware will give you just that. The smoother, bloat free firmware from another device but not the actual sim unlock.
I bought an unlocked device and wanted wifi calling so I flashed the g950usqs1aqf7 att firmware with Odin and it worked to enable wifi calling but I'm unable to get any ota updates and I hate the bloat. Is it possible to get WiFi calling with an unlocked firmware like this one? Also what is the difference between the U and U1 firmware variants?
maquino1985 said:
I bought an unlocked device and wanted wifi calling so I flashed the g950usqs1aqf7 att firmware with Odin and it worked to enable wifi calling but I'm unable to get any ota updates and I hate the bloat. Is it possible to get WiFi calling with an unlocked firmware like this one? Also what is the difference between the U and U1 firmware variants?
Click to expand...
Click to collapse
There are plenty of threads on this, but I don't think anyone was ever successful. I flashed att Oreo to my u1 and got the options, but can't get my company to change my imei back.... My personal phone sim works fine. Quit at that point since it's an Ims registration error. You can try merging the wifi calling apks, but I'm pretty sure it's baked pretty deep in the os. The Verizon guys got some of it working. You can try their threads and see if any of it applies to us.
twizt3d said:
There are plenty of threads on this, but I don't think anyone was ever successful. I flashed att Oreo to my u1 and got the options, but can't get my company to change my imei back.... My personal phone sim works fine. Quit at that point since it's an Ims registration error. You can try merging the wifi calling apks, but I'm pretty sure it's baked pretty deep in the os. The Verizon guys got some of it working. You can try their threads and see if any of it applies to us.
Click to expand...
Click to collapse
Thanks. Some threads made it sound possible but inconclusive. I'll just assume it doesn't work.
BTW, can you link to the att oreo fw? And what do u flash that with Odin or comsey?
The thread right below this one entitled Oreo ota has all the details and it needs to be side loaded through adb. Not Odin. But you will need to Odin the 950u base to get off u1
twizt3d said:
The thread right below this one entitled Oreo ota has all the details and it needs to be side loaded through adb. Not Odin. But you will need to Odin the 950u base to get off u1
Click to expand...
Click to collapse
Ok thanks. I need to flash anyways because I'm having terrible battery issues and just debating whether to go to a newer version of 950u or back to U1 and losing WiFi calling. In your opinion is oreo beta worth it
So just to confirm, I have read everything, but I am just a bit confused. If I flashed the unlocked firmware via modified odin on a locked AT&T S8 it will remove a lot of the carrier bloat and give my my wifi hotspot back, but remove wifi calling. Similar to when I flashed the T-Mobile firmware on my AT&T S7 and got rid of a ton of the AT&T bloatware but was able to activate my wifi hotspot but lost wifi calling. I stay locked to AT&T which is fine that is not my purpose for flashing
---------- Post added at 07:03 AM ---------- Previous post was at 07:01 AM ----------
and can you re-upload the link is dead now
The links don't work. Any chance you've still got the firmware? I've been overseas since october. I have an unlocked AT&T phone that I intend to keep using when I get back, so I want to keep it AT&T FW.
Hi.
I have a G955U Galaxy S8+ AT&T Factory Unlocked on Android 7.0
Baseband Version: G955USQU1AQD9
Android Security Patch Level - April 1, 2017
I no longer live in the US, and currently in the Philippines. Phone works great and the signal is too and all, but I cannot get OTA updates.
Can I just download the firmware file in this thread and flash straight through ODIN, or do I need to follow another guide?
Just FYI, it appears with the new Blv3 firmwares, the device will only accept official firmware. Meaning, no more flashing U1 firmware on the carrier models, or vice versa. No more flashing U or U1 firmware to the Canadian W models. Flashing between carrier firmwares is fine as long as it's on a carrier branded device (running TMB on a VZW device, etc). But running 950U firmware on a 950U1 will result in a brick, that is this far unrecoverable.
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3. Currently the S series is still on BlV2, but may go to Blv3 like the Note series just did.
This has been tested and confirmed.
Credit goes to @me2151, @FatalONEM8 for discovering this and warning people. I didn't find the issue or test, it just passing on the info to hopefully save some bricks.
Update from @mweinbach:
"EDIT: After being tested by XDA Senior member me2151, it turns out cross region flashing does work. Prince Comsy Odin is working, but we can not test if the factory binary flashing will hard brick your phone. So flashing US unlocked onto a US carrier device should work."
To expand a bit on what @mweinbach*just said, @me2151*did some more testing, and he was able to successfully carrier switch from a 950U to 950W using Comsey ODIN. So it looks like Comsey ODIN is not patched as we originally thought. Not sure exactly what caused the tester's phone to brick, but it HARD BRICKED and had to be RMA'd at his expense. So we jumped on the forums here to warn others until more testing could be done. @mweinbach*wrote the article and @xdanilvaand I began posting here.*
We may have overreacted, but wanted to err on the side of caution to protect people from hard bricks.*
The Blv3 factory binary has not been tested, so still unsure if/how we will be able to use it, or if it will cause issues.*
For now, carry on as usual, but understand we still don't know the full implications of the Blv3 patches. One person has already HARD BRICKED, and @me2151*almost hard bricked testing all of this for us.
There is currently a group working on a fix for bricked devices, but for now consider it a hard brick. Don't chance it.
Is Oreo for the S8/S8+ a Blv3 firmware or is it BLV2?
just curious as I flashed my Verizon branded GS8 to U1 firmware to take the Oreo beta..
So If I own a Sm-G950U1 but I have been running G950U Tmobile Oreo beta and upgrade to the stable oreo I'll brick my phone? In order to prevent this I'll have to first go back to G950U1 on nouget and then go up to oreo?
I don't really want to do this because I am loving using the T-Mobile variant because it gives me multiuser (digits) since it's built in.
Does the same apply to exynos devoces?
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
ironbesterer said:
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
Click to expand...
Click to collapse
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
vimerate said:
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
Click to expand...
Click to collapse
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
ironbesterer said:
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
Click to expand...
Click to collapse
My question is I have an ATT unlocked device on Cricket Wireless running the oreo beta since I flashed it to unlocked firmware. Should I revert back to Nougat before the final oreo build or just stick with it?
Mr. Orange 645 said:
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3.
Click to expand...
Click to collapse
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
raduque said:
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
Click to expand...
Click to collapse
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Mr. Orange 645 said:
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Click to expand...
Click to collapse
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
raduque said:
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
Click to expand...
Click to collapse
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Mr. Orange 645 said:
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Click to expand...
Click to collapse
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
raduque said:
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
Click to expand...
Click to collapse
No on a U1. They tried to carrier switch on either a U or a W.
Ok... so they tried to go from a device running a Carrier fw on blv3 to... what? A carrier fw on blv2?
I know this is still early, but the more questions and answers I see, the more confused I am.
Do we know if all of these scenarios will have the same result?
a) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. A BLv3 OTA will brick the device. True/false/not yet known?
b) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. Assuming a) is FALSE. Device will operate as normal U1 phone, but I will never be able to put 950U carrier branded software on it (via modded Prince Comsy), because that will brick it. True/false/not yet known?
c) I have a AT&T (950U) branded device. I flashed it to become TMobile (950U) device. It now get updates via Tmobile. Future OTAs will continue as normal and I can even use Odin to flash other carrier software (950U), but I can NEVER use modded Odin to flash unlocked software (950U1)? True/false/not yet known.
Based on what I've read right so far. It seems that the answers all remain theoretical, thus not yet known, but based on the Note8 update, the answers would be a) False. b) True. c) True.
Am I far off base???
The thing right now that I understand the least is the scenario a). I don't understand why if I have a phone that was 950U but is now 950U1, why it would get bricked. I do understand that attempts to change it once BLv3 hit are currently DOA, but that's different than simply keeping your phone in the stream that it is currently.
There are some good questions in this thread, I realize that its an evolving situation... So I have to ask directly... I have a Verizon branded 950U that I followed https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817 to switch to XAA and flash the U1 firmware, and I have taken part in the Oreo beta.
Currently my phone has Baseband Version G950U1UEU2ZRA8. There is an OTA update pending right now that is G950U1EUE2ZRAE/G950U1OYM2ZRAE/G950U1UEU2ZRAE. From what I understand, and what I am reading about this BLV2 vs BLV3 issue, based on the numbers in this, if I take this update, I'll still be BlV2, and be ok? If I should want to return to stock Verizon firmware, I can still do it safely?
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
KidJoe said:
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
Click to expand...
Click to collapse
I am basically the same as you except AT&T beginning rather than Verizon. I currently have the ZRAE Oreo beta software running on my phone. Based on everything said so far, there is no danger yet in downloading that OTA because it is still BLv2. The danger would be if the final Oreo version drops with BLv3 and you apply it. Then we're left with these different scenarios that are still being figured out.
Absent any concrete info, I'm going to just avoid the Jan security patch on my Note8.
If I have to flash back the Verizon software to have a non-brick device, well I'll just sell this thing and buy a cheap unlocked phone with microsd, wireless charging and a nice screen.
Ok, so my question ha a few points here. I have been flashing roms for many years but never really though of this until recently as I now have an unlocked phone.
1. As my Sprint Note 5 is unlocked, can I flash say the Unlocked Version of software to the phone taking away carrier branding? I manage a store from another carrier and I hate that when I boot my phone it shows Sprint. I know it will not trip knox as long as it is Official Stock software.
2. If I do flash said Unlocked version software replacing Sprint software, will it change my connection at all? I have seen that flashing ATT software on a Verizon device did manage to improve ATT tower connection however I wonder if this is maybe a placebo effect as opposed to actually changing the bands and connections the device makes.
If you guys could help me out that would be great. :good:
Cheers
There is no unbranded firmware for the Sprint model because well, it is a exclusive model so even if you flash XAS instead of SPR firmware some or all apps will still appear. The only way to get rid of everything Sprint is via custom ROM= tripped KNOX. The SM-N920P cannot run another firmware.
Good day everyone!
so i got an LG V20 for a sale price in AliExpress.
I bought the H910 variant, which is ATT
After 20 days on shipment, i got the phone as described, but after i did a little digging it turns out to be a confusing variant
Here's what i found:
> The phone boots with a Claro animation, Claro is from Puerto Rico, Right?
> on the "about device" the appearing model is an H910PR. PR is, again, puerto rico
> LG Bridge can't identify the model, will try soon on LGUP
To settle things, i looked up the hardware instead...but it just got more confusing
> I ordered an H910 ATT variant, the back label behind the battery of the phone also shows H910
> looked up the IMEI and it shows as H910 ATT LG V20, both IMEIs from the firmware and the back of the phone is the same
> i teardown the phone to look for the board model number of the device, and it says "VS995"...... the board is a Verizon variant
> again, i bought an ATT variant, the model says it is H910, but the back cover of the phone is written Verizon (i know it's not solid proof that this phone is Verizon or not cuz you can swap back covers, but still)
My purpose for this phone is to unlock and root it, but sadly i can't cuz i might end up bricking it for flashing the wrong stuff because of the confusing models
And even just restoring the firmware could be risky
So how can i root this phone?
Will DirtySanta work?
What firmware should i flash in case i need to restore it?
Any kind people out there to help would be greatly appreciated
MEMO#22 said:
Good day everyone!
so i got an LG V20 for a sale price in AliExpress.
I bought the H910 variant, which is ATT
After 20 days on shipment, i got the phone as described, but after i did a little digging it turns out to be a confusing variant
Here's what i found:
> The phone boots with a Claro animation, Claro is from Puerto Rico, Right?
> on the "about device" the appearing model is an H910PR. PR is, again, puerto rico
> LG Bridge can't identify the model, will try soon on LGUP
To settle things, i looked up the hardware instead...but it just got more confusing
> I ordered an H910 ATT variant, the back label behind the battery of the phone also shows H910
> looked up the IMEI and it shows as H910 ATT LG V20, both IMEIs from the firmware and the back of the phone is the same
> i teardown the phone to look for the board model number of the device, and it says "VS995"...... the board is a Verizon variant
> again, i bought an ATT variant, the model says it is H910, but the back cover of the phone is written Verizon (i know it's not solid proof that this phone is Verizon or not cuz you can swap back covers, but still)
My purpose for this phone is to unlock and root it, but sadly i can't cuz i might end up bricking it for flashing the wrong stuff because of the confusing models
And even just restoring the firmware could be risky
So how can i root this phone?
Will DirtySanta work?
What firmware should i flash in case i need to restore it?
Any kind people out there to help would be greatly appreciated
Click to expand...
Click to collapse
Sounds like you got a H910 with Claro firmware on it, could be a refurb phone
Sent from my LG-H910 using XDA Labs
I'm not surprised that the board says vs995, heck my first v20, a us996 I unlocked through LG (means it was indeed a legit unlocked us996, which I bought new) said vs995 on it inside. The single sim v20s are all nearly identical, mostly its just modem and cpu fuse configuration, note that we can't super easily change the actual modem config now that its actually assembled and fuses are popped, but there is some degree that modem firmware sorta works even with cross flashed firmware).
It might just be that the imei tool used couldn't bother to distinguish h910 and h910pr and just labeled them both ATT.
cnjax said:
Sounds like you got a H910 with Claro firmware on it, could be a refurb phone
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
So is it ok if i flash a regular H910 firmware on this phone? and even use dirty santa?
Phoenix591 said:
I'm not surprised that the board says vs995, heck my first v20, a us996 I unlocked through LG (means it was indeed a legit unlocked us996, which I bought new) said vs995 on it inside. The single sim v20s are all nearly identical, mostly its just modem and cpu fuse configuration, note that we can't super easily change the actual modem config now that its actually assembled and fuses are popped, but there is some degree that modem firmware sorta works even with cross flashed firmware).
It might just be that the imei tool used couldn't bother to distinguish h910 and h910pr and just labeled them both ATT.
Click to expand...
Click to collapse
so basically LG is using the same single sim board but with different modems? That's something
Phoenix591 said:
I'm not surprised that the board says vs995, heck my first v20, a us996 I unlocked through LG (means it was indeed a legit unlocked us996, which I bought new) said vs995 on it inside. The single sim v20s are all nearly identical, mostly its just modem and cpu fuse configuration, note that we can't super easily change the actual modem config now that its actually assembled and fuses are popped, but there is some degree that modem firmware sorta works even with cross flashed firmware).
It might just be that the imei tool used couldn't bother to distinguish h910 and h910pr and just labeled them both ATT.
Click to expand...
Click to collapse
So would it be fine if i flashed a regular ATT firmware on this variant?
MEMO#22 said:
So would it be fine if i flashed a regular ATT firmware on this variant?
Click to expand...
Click to collapse
Most likely.
Att decided to be special snowflakes and did otas in a way that means theres no firmware files that can be flashed through the regular lg up/lgbridge tools though. So the best way imo to get att firmware is to downgrade to the dec 2016 security patch and root and grab an att rom. If you cant find an old enough h910pr firmware then just follow the regular h910 guide involving crossflashing to h910. Regardless I'd at least follow the bit about dumping your modem related files (because if anything is going to get funky, it will be the cell service)
MEMO#22 said:
So would it be fine if i flashed a regular ATT firmware on this variant?
Click to expand...
Click to collapse
Follow Phoenix's advice and back up your modem, others who flashed att firmware on the pr variant others had issues with cellular service, also you might want to verify what bands that variant supports to see if it will work with your carrier
Sent from my LG-H910 using XDA Labs
cnjax said:
Follow Phoenix's advice and back up your modem, others who flashed att firmware on the pr variant others had issues with cellular service, also you might want to verify what bands that variant supports to see if it will work with your carrier
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Will do, thank you all for your response