How To Guide F711U and F711U1 Firmware Links and Flashing Discussion Here

[herzzreh]

Did AT&T completely give up on updating their version?!

 

[leo_hacker82]

(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

Can i flash internacional firmware. I mean flash u1 to B versión? Cuz my u1 unlocked no bloatware dont have esim option

 

[iBowToAndroid]

Can i flash internacional firmware. I mean flash u1 to B versión?

Nope

 

[cpufrost]

I flashed AIO to my Verizon Flip 3, all is well with no bloat and June 1 patch level.
It does have the Thom Browne theme and start screen though. Is there a firmware on 2DVEE without the TB stuff?

 

[iBowToAndroid]

I flashed AIO to my Verizon Flip 3, all is well with no bloat and June 1 patch level.
It does have the Thom Browne theme and start screen though. Is there a firmware on 2DVEE without the TB stuff?

Yep

 

[cpufrost]

Yep

Care to point me in that direction? I use Frija to fetch them.

 

[iBowToAndroid]

Care to point me in that direction? I use Frija to fetch them.

Hmm, looks like Frija is defaulting to pulling the "branded" firmware when looking for U1, if that sales code has gotten the VEE update already. It's done that in the past.

To pull unbranded firmware, you'll need to change to manual entry, and replace the "TB" with "UE" and change the Z in "OYZ" to an M

 

[cpufrost]

Hmm, looks like Frija is defaulting to pulling the "branded" firmware when looking for U1, if that sales code has gotten the VEE update already. It's done that in the past.

To pull unbranded firmware, you'll need to change to manual entry, and replace the "TB" with "UE" and change the Z in "OYZ" to an M

This is fetched in AUTO
F711U1TBU2DVEE/F711U1OYZ2DVEE/F711U1TBU2DVEE

I cannot change it when switching to manual. If I check update after switching to manual that field becomes blank but it does not allow me to enter anything in there.

 

[iBowToAndroid]

I cannot change it when switching to manual. If I check update after switching to manual that field becomes blank but it does not allow me to enter anything in there.

If you can't type anything in the PDA, CSC, or PHONE fields after changing it to Manual, then something is very very wrong.

What version are you using?

 

[cpufrost]

If you can't type anything in the PDA, CSC, or PHONE fields after changing it to Manual, then something is very very wrong.

What version are you using?

1.4.4.0

I can change those fields on top but not below where it shows version.

Here's a screen shot with the updated PDA/CSC/Phone in manual mode.

Clicking on check update doesn't throw an error but doesn't fill in the below fields either.

If I switch back to AUTO and click check update it fetches the version I have now with TB stuff.

 

[iBowToAndroid]

1.4.4.0

I can change those fields on top but not below where it shows version.

Here's a screen shot with the updated PDA/CSC/Phone in manual mode.

Clicking on check update doesn't throw an error but doesn't fill in the below fields either.

If I switch back to AUTO and click check update it fetches the version I have now with TB stuff.

Then I have no idea what's wrong because it pulls it fine for me when I fill everything out and click Check Update

 

[cpufrost]

Success!

I removed the XML file in %userprofile%\AppData\local\Frija\
Ran Frija, entered everything manually and it fetched the file correctly.
Flashed using HOME for CSC is everything is working well.

Not only is the TB version screwy with the splash screen, the outer display has a funky font that I hated.

Thanks again!

 

[Dylusion]

Hi. Sorry if I may have made any mistakes, I am new to this. I have a Verizon SM-F711U Flip 3 that I bought second-hand recently. I tried to use my existing AT&T sim card inside it but it rejected it with a "carrier change" message. I contacted Verizon and they told me the device was unlocked and fully paid off. Based on what happens it seems like the device isn't unlocked, but even after contacting them multiple times, they all say on their servers the device's IMEI is shown as unlocked.

I've flashed U1 firmware which removed the Verizon bootscreen and bloatware, and initially it seemed like it accepted the sim card considering it connected to 4G and allowed me to make calls and messages, but about 5 minutes later it displayed the same message saying "carrier change not supported" and disconnected from network. The service provider software version still shows VZW/VZW/VZW

Would flashing ATT U firmware fix this by any chance, or is there something else I could try?

 

[cpufrost]

When you flashed (ODIN) did you select HOME or CSC (Full wipe)?
Sounds like AT&T is rejecting this device.

 

[Dylusion]

When you flashed (ODIN) did you select HOME or CSC (Full wipe)?
Sounds like AT&T is rejecting this device.

I flashed with CSC

 

[cpufrost]

I would flash ATT FW, let it settle in and see if you don't get knocked offline.
If the service provider refreshes with ATT it should be good and you can flash back to U1 to get rid of the carrier bloat.

 

[Dylusion]

I would flash ATT FW, let it settle in and see if you don't get knocked offline.
If the service provider refreshes with ATT it should be good and you can flash back to U1 to get rid of the carrier bloat.

Alright I'll try that and see if it works. Thanks

 

[Dylusion]

I would flash ATT FW, let it settle in and see if you don't get knocked offline.
If the service provider refreshes with ATT it should be good and you can flash back to U1 to get rid of the carrier bloat.

I flashed ATT fw following the same procedure iBowToAndroid provided a bit ago to someone else trying to flash TMB to VZW, however after starting the phone it still showed the Verizon boot screen, and after initial setup the device still kicked me offline. I rebooted the phone many times, did a factory reset, and the service provider is still on VZW and kicking me off the network.

It's possible I could've done something wrong while trying to flash ATT fw, but from what I know I did everything as the steps mentioned. I might try to contact Verizon again to see if the phone is still unlocked

 

[cpufrost]

That's strange (especially the VZW splash screen!)...

Do you know someone with Verizon service that you can use their sim card? Perhaps if you put that in and let the phone connect to (VZW) it may unlock it. Sounds weird but the phone may need to communicate on VZW to be updated to unlocked status. Afterward, flashing to U1 would let you run it on any network without issues.

 

[Dylusion]

That's strange (especially the VZW splash screen!)...

Do you know someone with Verizon service that you can use their sim card? Perhaps if you put that in and let the phone connect to (VZW) it may unlock it. Sounds weird but the phone may need to communicate on VZW to be updated to unlocked status. Afterward, flashing to U1 would let you run it on any network without issues.

Yeah I was thinking about that possibly being a solution but unfortunately at the moment I don't know anyone who uses Verizon (At least anyone who would let me borrow their sim card)