Develop Bugs

Flashing RETAIL Firmware Over TMO on Z2 Force

Hello everyone,
I've been perusing the threads on flashing the RETAIL firmware on Sprint and T-Mobile devices, and it's not clear to me how safe this is. I'd prefer to keep my bootloader locked (flash signed images) - do you guys know if you can flash the RETAIL signed images on top of a T-Mobile Z2 Force?
For example, here's the RETAIL folder for nash: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
If I take the latest signed oreo zip, can I simply flash as instructed by the XML inside? I've already used this technique to re-lock the bootloader on my Moto X Pure after I wanted to repurpose it as a hotspot on long trips. And I've used this same technique to save a weird Moto Z Play from Swappa.
But this is my primary device, so I wanted to know what everyone's experience here is. And hopefully, the RETAIL image gets Pie even though the non Verizon US phones will not.
Thanks!

Can anyone walk me through how to flash from G930u to G930v?

I purchased a Samsung S7 on Amazon, and it was listed as a G930V. However, when I received it, I was disappointed to see that in "Device Info"... it lists it as a Samsung G930U.
From what I understand, this is indicates Unlocked Firmware install, which will prevent me from using Verizon's Visual voicemail and also be unable to use the built in Video calling feature, where you can video call anyone in the Verizon Network.
What I don't get, is why the back panel of the phone has a Verizon Logo, even though apparently it is unlocked. I thought all Verizon branded phones, have the G930v firmware?
Anyways, is it possible to flash the phone to G930 firmware, so I can use the features I want to have access to? Or is it recommended I just return this item and try and buy another G930v? Does anyone have any detailed instructions on how to flash to G930v?
Interestingly, when I checked the IMEI online... it lists the device as a Verizon G930V. I guess someone has previously flashed these to U from V?
ETA: Are there any benefits to sticking with Unlocked firmware? Are there any advantages of G930U over G930v? I know the G930v comes with a bunch of bloatware... but wondering if there are other things that VZW's firmware might handicap?

JFox762 said:
I purchased a Samsung S7 on Amazon, and it was listed as a G930V. However, when I received it, I was disappointed to see that in "Device Info"... it lists it as a Samsung G930U.
From what I understand, this is indicates Unlocked Firmware install, which will prevent me from using Verizon's Visual voicemail and also be unable to use the built in Video calling feature, where you can video call anyone in the Verizon Network.
What I don't get, is why the back panel of the phone has a Verizon Logo, even though apparently it is unlocked. I thought all Verizon branded phones, have the G930v firmware?
Anyways, is it possible to flash the phone to G930 firmware, so I can use the features I want to have access to? Or is it recommended I just return this item and try and buy another G930v? Does anyone have any detailed instructions on how to flash to G930v?
Interestingly, when I checked the IMEI online... it lists the device as a Verizon G930V. I guess someone has previously flashed these to U from V?
ETA: Are there any benefits to sticking with Unlocked firmware? Are there any advantages of G930U over G930v? I know the G930v comes with a bunch of bloatware... but wondering if there are other things that VZW's firmware might handicap?
Click to expand...
Click to collapse
3 weeks late but here are my insights. U firmware has less bloatware than the VZW branded firmware. In general, most people prefer the U firmware over their branded firmware unless, as in your instance, there are certain features only available in branded versions. My guess would be that yours was a VZW that was flashed to U. In all likelihood it shouldn't be too difficult to convert back to VZW, if that's your preference. You'll need to familiarize yourself with Odin flashing and the particulars of matching bootloader numbers for firmware to flash. For an example see link: https://android.stackexchange.com/questions/202491/what-do-the-numbers-and-letters-in-the-samsung-firmware-mean
Hope this helps ...

Can I flash sm-N975U1 AT&T unlocked firmware over sm-N975U AT&T?

My sm-N975U AT&T note 10+ has never ever received any updates.
It's currently at Android 9, N975USQU1AS12, security patch: September 1, 2019. Since I got it in 2019.
I see that the unlocked version SM-975U1 AT&T receives updates frequently and I can easily get the firmware online.
I've not even seen any Android 10 firmware for SM-975U AT&T.
So is it possible to flash SM-975U1 AT&T unlocked over SM-975U AT&T.
Or even just to make it US unlocked with no carrier so I can receive updates from Samsung?

You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.

So this will unlock the phone? Does the same go for the Sprint version?

Nickdroid86 said:
So this will unlock the phone? Does the same go for the Sprint version?
Click to expand...
Click to collapse
You can flash the firmware from the N975U1 to the N975U (and vice versa). It doesn't matter the carrier, only the model number matters.
Just be sure to be mindful of the bootloader version.
Flashing the firmware from the N975U1 does not have any relation to the network/sim lock. For network/sim unlocking you will have to ask your provider to do this for you
The term (or name) "unlocked firmware" is derived from the phone it comes from.. The N975U1 is the carrier/network unlocked variant sold by Samsung.

so if i put the, U1 firmware to n975u and i'm out USA. now I will receive all the new updates automatically via OTA?
Excuse me, I am new to the forum, I have a question for you, I have an at & t SM-N975U, this at & t firmware does not update outside the USA, I am in Mexico, which firmware should I use, I want it to update automatically via OTA here in Mexico? t-mobile firmware or U1 firmware, I really appreciate your answer,

hello, my question is similar but regarding the carrier. My Note 10 Plus is AT&T locked, if I flash the SM-N975U1 over the SM-N975U, will that unlock the carrier so i can use anyone outside USA?

No. It won't. You'll have to have AT&T unlock it.

scottusa2008 said:
You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.
Click to expand...
Click to collapse
Hello can you please help me too
I'm super new here
So i have the N975U and i live in Europe and i don't get any updates cuz my Note 10+ is the AT&T version and now i want to change it to N975U1 so i can get updates from Samsung themselves.. from Sammobile i downloaded The N975U1OYM7GULD-(XAA) model and also N975U1OYM7GULD-AT&T model while the current one i have is N975USQS7FUI7 so both of them i think should work because they have the same bootloader so my question is since i want to get updates to which one should i flash my phone with? I heard the XAA is better because u get updates directly from Samsung themselves ( even when I'm in Europe ) and the AT&T version is also N975U1 but I'm not sure if i will be getting updates because now I already have the N975U ( probably AT&T model that's why I'm not getting anything ) So what do you think i should do?
I'd appreciate ur help
And sorry for my broken ass English hope you understood..

scottusa2008 said:
You can flash the N975U1 firmware onto the N975U (and vice versa) so long as the bootloader is the same version (or higher) then what is currently installed on the phone.
Three things to keep in mind:
No way exists to downgrade the bootloader... So if you flash firmware with a newer bootloader and you decide you want to go back you will not be able too.
Bootloader version can be found by doing the following. Looking at your About Phone > Software Version look at the baseband version info.. Start at the far right and count 5 characters to the left (with the first character being the far right one). The number that is the 5th character in will be the bootloader version that is currently on the phone.
The USERDATA isn't always included with the U1 firmware should you desire the AT&T version of it. You should be able to find that in this thread,
For an example the red number is the bootloader version:
N975U1OYM3CTE7
For anything else this question has been discussed here a lot so you won't have any issues finding information about it.
Click to expand...
Click to collapse
And should i use Odin patch or just the normal odin? I actually wanted to flash my phone with the Germany version but i don't know if it will work!!? ( You'd use odin patch you want to change region! ) so idk if it would work if i change it from N975U to N975F which is Germany model !!?

How To Guide F926U and F926U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, F926U is the model number of all of the US carrier versions of the Z Fold3. The F926U1 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=327754
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327755
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

Is there a T-Mobile version available yet?

ruthlessnature said:
Is there a T-Mobile version available yet?
Click to expand...
Click to collapse
Yep, firmware has been on Samsung's servers since last week

iBowToAndroid said:
Yep, firmware has been on Samsung's servers since last week
Click to expand...
Click to collapse
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.

ruthlessnature said:
I downloaded the file from samefirm, and frija but did not get the carrier bloat or T-Mobile boot screen from either one. I have an unlocked version.
Click to expand...
Click to collapse
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too

iBowToAndroid said:
You need to make sure your CSC shows as TMB, and need to make sure you're flashing USERDATA too
Click to expand...
Click to collapse
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?

ruthlessnature said:
That's strange, neither one I downloaded has TMB in the csc, do you have a link ?
Click to expand...
Click to collapse
I'm not talking about the firmware. I'm talking about the phone itself, in the Settings

Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.

ruthlessnature said:
Oh, I see, it doesn't change, shows xaa/xaa/xaa I downloaded the ATT userdata to flash and see if it changes it.
Click to expand...
Click to collapse
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA

iBowToAndroid said:
If you want T-Mobile bloatware, you need to insert a T-Mobile SIM so that the CSC changes to TMB. And then you need to flash a U firmware with T-Mobile USERDATA
Click to expand...
Click to collapse
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.

ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
You're welcome!

ruthlessnature said:
Thanks for the info, I couldn't get it to flash back to the u1 firmware until I downloaded the patched Odin. Then I was able to I put my Sim, the csc showed TMB and then I was able to flash the u firmware with the TMB userdata. Thanks again for your help.
Click to expand...
Click to collapse
For anyone looking for that it's here: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/

I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on

wschamps42 said:
I'm getting a weird Complete(Write) Operation Failed error when flashing any tips?
NVM gotta have USB Debugging on
Click to expand...
Click to collapse
Uhhhh what? Flashing is done in Download mode, not Normal mode

can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now

Drnms said:
can we flash a different region firmWARE (UK / EUROPE) to the U1? Given the phones are all Qualcomm SD now
Click to expand...
Click to collapse
Nope

I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.

sllong said:
I appologize for being the super noob. A couple questions.
Does using this process disable the cameras as mentioned in https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/page-.
You stated that there are tons of beginners guides. In doing searches I find multiple different guides with different completely different processes. Is there one that you recommend or works best?
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
You will not lose the cameras as you are flashing firmware not unlocking the bootloader.

sllong said:
My goal is to make my unlocked fold3 more usable on ATT/firstnet. There are multiple features I cannot use and I don't receive same call quality service as my wife's locked att fold3.
Click to expand...
Click to collapse
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item?

iBowToAndroid said:
Under Settings-->About-->Software Information, what's the last line of your "Service provider SW ver" item
Click to expand...
Click to collapse
iBowToAndroid said:
/xaa/xaa/xaa
Click to expand...
Click to collapse

Question Flashing Generic Firmware on Unlocked ATT Pixel 6 Pro

Hi,
Can u pls let me know if it is possible to flash generic firmware(like firmware from Google Store's Pixel6 pro) on Unlocked ATT Pixel 6 Pro?
The reason I'm asking is, because i have ATT specific functionality on esim addition that prevents me to add Non- ATT esim.
Thanks

I would refer you to this link https://developers.google.com/android/images

@mindseye0803 If by unlocked you mean the bootloader is unlocked, then yes. If you merely mean it's carrier unlocked, then no - not unless you are able to unlock the bootloader as well. Keep in mind, unlocking the bootloader will fully wipe your phone including internal storage so be prepared.

roirraW edor ehT said:
@mindseye0803 If by unlocked you mean the bootloader is unlocked, then yes. If you merely mean it's carrier unlocked, then no - not unless you are able to unlock the bootloader as well. Keep in mind, unlocking the bootloader will fully wipe your phone including internal storage so be prepared.
Click to expand...
Click to collapse
Yeah, since it is carrier unlocked and ATT one, i can unlock the bootloader. Do i need to unlock bootloader before flashing generic firmware? Can i lock bootloader back after flashing generic firmware?
I'm ok with wiping the phone.

mindseye0803 said:
Yeah, since it is carrier unlocked and ATT one, i can unlock the bootloader. Do i need to unlock bootloader before flashing generic firmware? Can i lock bootloader back after flashing generic firmware?
I'm ok with wiping the phone.
Click to expand...
Click to collapse
When you say generic firmware, you just mean the official Pixel firmware Google provides, correct?
As far as I know, all the carriers use the same official firmware, and would be the same as Google provides for manual flashing.
Yes, you need to unlock the bootloader before manually flashing.

roirraW edor ehT said:
When you say generic firmware, you just mean the official Pixel firmware Google provides, correct?
As far as I know, all the carriers use the same official firmware, and would be the same as Google provides for manual flashing.
Yes, you need to unlock the bootloader before manually flashing.
Click to expand...
Click to collapse
Yes, when i say generic firmware, i mean Official Pixel firmware Google provides.
Yeah, i know currently there is just same official firmware but initially there were individual versions. The leftover from individual version is that while adding esim , it shows ATT specific messages and might be limiting the additon of non ATT esims.

Nothing can be "left over". If your phone has been updated to 12.1, then you have the universal/only factory firmware build available. But note that there ARE carrier specific packages installed in that firmware, the specifics of which will be selected based on whatever criteria they've decided on. Might be whose sim card is installed, or could be some hardware model code.
In other words, the procedure you are attempting to follow will not yield the results you're looking for.

Are you certain that it is SIM-unlocked? If you put in a physical sim from a different carrier, does it work?

96carboard said:
Nothing can be "left over". If your phone has been updated to 12.1, then you have the universal/only factory firmware build available. But note that there ARE carrier specific packages installed in that firmware, the specifics of which will be selected based on whatever criteria they've decided on. Might be whose sim card is installed, or could be some hardware model code.
In other words, the procedure you are attempting to follow will not yield the results you're looking for.
Click to expand...
Click to collapse
Ok, i was looking at options as I'm having trouble porting to US Mobile. Since this was sold as ATT branded Pixel 6 pro, carrier specific packages installed in the firmware based on hardware model code makes more sense.

96carboard said:
Are you certain that it is SIM-unlocked? If you put in a physical sim from a different carrier, does it work?
Click to expand...
Click to collapse
Yeah, it is SIM unlocked. I'm using ATT as physical sim and Tmobile as e-sim. Earlier I had ATT as e-sim.

If you find the Att version of the Pixel 6pro, please tell me how to unlock the OEM.
如果您找到 Pixel 6pro 的 Att 版本，请告诉我如何解锁 OEM。

决明55 said:
如果您找到 Pixel 6pro 的 Att 版本，请告诉我如何解锁 OEM。
Click to expand...
Click to collapse
Translated
If you find an Att version of the Pixel 6pro, please tell me how to unlock the OEM.

Nergal di Cuthah said:
Translated
If you find an Att version of the Pixel 6pro, please tell me how to unlock the OEM.
Click to expand...
Click to collapse
It has to be unlocked by ATT after device payoff and 6 months of continuous service.

决明55 said:
如果您找到 Pixel 6pro 的 Att 版本，请告诉我如何解锁 OEM。
Click to expand...
Click to collapse
Unlock a Phone or Device - AT&T Device Unlock Portal
www.att.com