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

Search This thread

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
good day all. I have a flip 3 VZW looking for a 4.1 firmware download to flash back using Odin. cant seem to find any.. a point in the right direction is appreciated tks!
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
tks I tried both but they do not work tried the auto nothing when I plug in on either one just error not sure what Im doing wrong.. anything else out there I tired sammobile galaxy firmware couple others but running them on ODIN just gives me a failed.. Im just looking to go back to 4.1. not sure what else to do.. any help is greatly apprreciated
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,434
1
1,720
Twin Cities MN
tks I tried both but they do not work tried the auto nothing when I plug in on either one just error not sure what Im doing wrong.. anything else out there I tired sammobile galaxy firmware couple others but running them on ODIN just gives me a failed.. Im just looking to go back to 4.1. not sure what else to do.. any help is greatly apprreciated
In order for us to help you, YOU have to help US.

Saying "just error" and "just gives me a failed" tell us nothing. We need to know what the EXACT error is, in order to correctly diagnose the problem
 
  • Like
Reactions: naren12

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
In order for us to help you, YOU have to help US.

Saying "just error" and "just gives me a failed" tell us nothing. We need to know what the EXACT error is, in order to correctly diagnose the problem
you know your right sorry I will try it again when I get home to put all the info in that Im getting. been a while was not thinking str8..:) thanks again!! will post in about 2 hrs much appreciate you helping me.
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
In order for us to help you, YOU have to help US.

Saying "just error" and "just gives me a failed" tell us nothing. We need to know what the EXACT error is, in order to correctly diagnose the problem
1664230045894.png

Hello again iBow! so I have the phone plugged in open Frija have CSC info in that I found and hit check update and get the error below same error if I do it with out the CSC also. on a flip 3, 4.1.1 SM-F711U again tks my friend!
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
🤦🏻‍♂️🤦🏻‍♂️🤦🏻‍♂️🤦🏻‍♂️

No. That's the model. In the screenshot that you posted, the CSC field is blank - there's nothing there
sorry doing a little search not really sure what the CSC is but I saw this F711UOYN2DVF1 next to CSC on a firmware download so I assumed it was that. in the screen shot if you zoom a little you can actually see that is typed in there. unless its just completely wrong ..lol sorry again I have been out of the game since the galaxy 7..lol
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,434
1
1,720
Twin Cities MN
sorry doing a little search not really sure what the CSC is but I saw this F711UOYN2DVF1 next to CSC on a firmware download so I assumed it was that. in the screen shot if you zoom a little you can actually see that is typed in there. unless its just completely wrong ..lol sorry again I have been out of the game since the galaxy 7..lol
1. I'm talking about the box that's next to "Model", at the top of the program. The PDA, CSC, and PHONE fields down below don't become involved unless you have the "Manual" box checked. That's why they're greyed out and you can't type anything in them.

2. The top "CSC" box refers to the sales code of the firmware that you want: TMB, CCT, SPR, DSH, TMK, CHA, etc
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
1. I'm talking about the box that's next to "Model", at the top of the program. The PDA, CSC, and PHONE fields down below don't become involved unless you have the "Manual" box checked. That's why they're greyed out and you can't type anything in them.

2. The top "CSC" box refers to the sales code of the firmware that you want: TMB, CCT, SPR, DSH, TMK, CHA, etc
1664233579346.png
ok so then I'm VZW. ok I put that in TMB, on auto, hit check and now get this.. some progress ..lol I'll take it but unable to find . do you know where I can find the info to just enter manual? or I'm still doing something wrong? man total Noob again lol use to be just mega links everywhere with mad firmware.. alot has changed I see. again your help is much appreciated.
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
View attachment 5721155ok so then I'm VZW. ok I put that in TMB, on auto, hit check and now get this.. some progress ..lol I'll take it but unable to find . do you know where I can find the info to just enter manual? or I'm still doing something wrong? man total Noob again lol use to be just mega links everywhere with mad firmware.. alot has changed I see. again your help is much appreciated.
Also I'm not Rooted sorry forgot to mention that
 

bori1030

Senior Member
Aug 3, 2010
902
186
washington D.C.
Updates are never forced - they're always optional. You just updated to bootloader 3 and it's not possible to go back. So downgrade isn't possible
that was the case usually for me this has never happened .. I had auto updates blocked in dev options like always and after the notice sat for weeks about the update a pop up came up and said Auto update in 24 hrs and started a freaking count down there was nothing I could do to stop it.. freaking out the whole time man it was crucial lol
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,434
1
1,720
Twin Cities MN
that was the case usually for me this has never happened .. I had auto updates blocked in dev options like always and after the notice sat for weeks about the update a pop up came up and said Auto update in 24 hrs and started a freaking count down there was nothing I could do to stop it.. freaking out the whole time man it was crucial lol
That setting in Developer Options does not actually block OTA updates. But there are methods that do.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    (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
    3
    I downloaded the U1 firmware from Frija, successfully installed it on my Z Flip3 using Odin, and when I booted it up, it ended up being the "Thom Browne" edition firmware (to my horror) with custom Thom Browne theming. It looks like the download links in the OP are also the "Thom Browne" firmware.

    Where can I download and install the vanilla Samsung unlocked U1 firmware?

    Edit: Found the vanilla firmware here: https://samfw.com/firmware/SM-F711U1/XAA/F711U1UES2AUJ7

    The OP should probably warn readers that the download links he provided are for the Thom Browne customized firmware.
    2
    Can someone locate the thom browne fimware please?
    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
    2
    Thank you and always the best.
    Added, UGC build
    2
    so if im flashing my verizon carrier lock (60 days lock) device to u1 it will unlock it?
    No, flashing firmware will never magically SIM unlock a device, no matter which model it is or what carrier it's from. The SIM lock resides much deeper than firmware