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.
I've seen many threads about this issue originating because the apparent H900 model for some people turned out to be a different model somehow converted to look like this, and everyone had the exact same issues as me, namely
1. LG VPN has stopped working error
2. Fingerprint/security tab causes settings to crash
3. Attempting to uninstall apps causes instant soft reboot
Some folks mentioned fixing their phones by finding the actual model of their phone and flashing the correct firmware. But AFAIK, no flashing software allows flashing of a different model. And none of them was clear about the actual steps they did to fix it.
Since I'm on Marshmallow, I cannot root, and I cannot rollback to the firmware I had in my phone.
Can anyone please share how they fixed their phone or someone expert in the matter?
Warranty/Motherboard replacement are out of question for me.
Any help is appreciated.
Same here please somebody help.
Same, did you find a solution? :/
same problems
Same probleme... Any update for this?
I see on AT&T website they have been rolling out the software update ver. H900z in USA only?
So we out side USA cant get OTA update?
There some one can give the backup rom?
LIKELY NO CAN'T HELP US ON LG V10 H900W AT&T:crying::crying::crying:
no
behhaja said:
Same probleme... Any update for this?
I see on AT&T website they have been rolling out the software update ver. H900z in USA only?
So we out side USA cant get OTA update?
There some one can give the backup rom?
Click to expand...
Click to collapse
you can't get ota att outside USA becasue you need to be connected in ATT bridge or IDK but you can't the only way you can by KDZ or TOT FILES
Finally Found 1000% fix for all this type of issues. Security Menu to App Uninstall all-everything OK. Just need to flash an special modified firmware based on VS990 Hardware. The current Firmware version is Android 6.0.
NB: This is not for free and not for individual one. $150 will cost this type of firmware. So, this solution is for Service Personnel or Professional's only. Contact me for details on Skype or Gmail (rassel2k). Goodluck.
Too bad the price of the phone itself, 2nd hand (H900,H901,VS990,F600), is around $100 here.
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.
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
I'm running MetroPCS software on a Amazon device
I'm running Cricket software on a MetroPCS device &
I'm running Amazon software on a MetroPCS device
Cons on both I've come across so far.
Cricket software on a MetroPCS device I get Boot screen says Bad key in top left corner before loading the device.
Amazon software on a MetroPCS device I get a Boot screen says untrusted device before loading the device.
Pros is they both work great.
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
Since you did that when you have the time, try to go back a lower build or your OG Build and check if you still have data and sim accses. I ask because (I have a RETUS) and since I flashed the latest one available "PPO29.114-108 May 1 Security Update" can't go back to OG Build it came with without losing data and sim detection. Something was updated in that build that even if you flash back it broke that. I even flashed the modem to check but no still no data or SIM detected at all. Only all fine in the most recent build.
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
I am guessing that it is still sim locked to metropcs after flashing this?
twfs said:
I am guessing that it is still sim locked to metropcs after flashing this?
Click to expand...
Click to collapse
Flashing a Carrier or Retail ROM won't ever unlock a Carrier Lock device. If it were that simple don't you think we will ever have this issue. Hell the term network lock won't even exist in a perfect world.
---------- Post added at 03:24 AM ---------- Previous post was at 03:22 AM ----------
twfs said:
I am guessing that it is still sim locked to metropcs after flashing this?
Click to expand...
Click to collapse
And yes there are several Motorola Devices that are firmware interchangeable. Been doing it since the first Moto X times. Only benefit from this procedure no bloatware and faster updates that's it. Oh and better performance since it doesn't include crappware
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
PartyDroid said:
I'm running Cricket software on a MetroPCS device &
I'm running Amazon software on a MetroPCS device
Cons on both I've come across so far.
Cricket software on a MetroPCS device I get Boot screen says Bad key in top left corner before loading the device.
Amazon software on a MetroPCS device I get a Boot screen says untrusted device before loading the device.
Pros is they both work great.
Click to expand...
Click to collapse
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
disobey said:
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
Click to expand...
Click to collapse
PSA. If you flsh Cricket, Metro etc Roth the RETUS Latest firmware you won't be able to go back to you LG firmware. That firmware updates the Bootloader and that preventa going back to a lower workifn version. You can doing what I posted earlier by while flashing back to OG Firmware skip flashing modem and fsg bins and don't execute the modem erase commands.
disobey said:
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/official/AMZ/
Ok I bricked my phone via magisk update, I was on MetroPCS variant of Ocean firmware. Now I manually flashed RETUS PPO 29.114-108; It seems to be running fine other than saying my device is not certified....is there a custom recovery that will work for Ocean RETUS using twrp? Should I try to re root using magisk systemless-ly copying boot.img? Thanks for info and any input would be greatly appreciated! Thanks
PartyDroid said:
https://mirrors.lolinet.com/firmware/moto/ocean/official/AMZ/
Click to expand...
Click to collapse
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
nashi20002003 said:
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
Click to expand...
Click to collapse
I'd like to know as well, I got 2 of these Moto G Power 7's from Metro PCS and would love a stock ROM without all the metro bloat. Not sure on Metro's unlocking policy if they will unlock it and what bands this all has if it has CDMA or is it GSM only?
chennault05 said:
Ok I bricked my phone via magisk update, I was on MetroPCS variant of Ocean firmware. Now I manually flashed RETUS PPO 29.114-108; It seems to be running fine other than saying my device is not certified....is there a custom recovery that will work for Ocean RETUS using twrp? Should I try to re root using magisk systemless-ly copying boot.img? Thanks for info and any input would be greatly appreciated! Thanks
Click to expand...
Click to collapse
If I were you I will stay away from Magisk until they update the app, still damaging the boot.img files..
Omar04 said:
Flashing a Carrier or Retail ROM won't ever unlock a Carrier Lock device. If it were that simple don't you think we will ever have this issue. Hell the term network lock won't even exist in a perfect world.
---------- Post added at 03:24 AM ---------- Previous post was at 03:22 AM ----------
And yes there are several Motorola Devices that are firmware interchangeable. Been doing it since the first Moto X times. Only benefit from this procedure no bloatware and faster updates that's it. Oh and better performance since it doesn't include crappware
Click to expand...
Click to collapse
Do you know if there is a way to sim-unlock a Metro device? Searched on eBay, no luck... thanks.
edwardxi said:
Do you know if there is a way to sim-unlock a Metro device? Searched on eBay, no luck... thanks.
Click to expand...
Click to collapse
Note to Admin: I am not sure if this link is allowed if not please remove this message..
https://www.ebay.com/itm/264407271128?ViewItem=&item=264407271128
PartyDroid said:
Note to Admin: I am not sure if this link is allowed if not please remove this message..
https://www.ebay.com/itm/264407271128?ViewItem=&item=264407271128
Click to expand...
Click to collapse
thanks, I found one on eBay for $38... too expensive, used to around $10
nashi20002003 said:
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
Click to expand...
Click to collapse
Instructions are in the thread back to stock.
Secondly, I'm on MetroPCS and flashed the retus2 firmware (BestBuy versions) no MetroPCS bloatware. Flash the retus2 and you'll be fine.
edwardxi said:
thanks, I found one on eBay for $38... too expensive, used to around $10
Click to expand...
Click to collapse
You probably won't find one cheaper. $10 ones are ones that give you a code to unlock. Unlocking a MetroPCS/TMO G7Power with the Server unlock app requires a person to remotely connect to your phone and edit your NV files. Currently they are changing the imei to a different model phone that they can generate the unlock codes for. Since they are using a different model phone imei, activating on Sprint Network could be an issue since Sprint is picky as to what phones they put on their network.
If I flash "retail" firmware on a TMO Sim locked Moto G7 power will it ask me for an unlock code that I don't have? Bought it on eBay and TMO says its eligible to unlock but refuses because I'm not the original owner. Bootloader is unlocked.
EDIT: Figured out my issue. Was my fault. Flashed the RETAILUS firmware on my MetroPCS model.
Thanks OP!
Also to add to this, the Metro model is NOT supposed to be compitable with Verizon due to lack of CDMA.... Well Magically the phone now supports CDMA so it has a CDMA radio in it!
(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available