• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Andrew x3

Member
Nov 29, 2013
26
2
Pasco Washington
LG Wing
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
Me too I'm wondering what is stopping me from either flashing the honkong snapdragon or uae firmware? Then unlocking my bootloader? Is it csc? What if I change it?
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,700
1
1,460
Twin Cities MN
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
Nope, all North American models have been bootloader locked for years now. If you want an unlockable bootloader, you need to buy an international model
 
The core premise is a Linux-based mobile operating system with Google services integrated.

You may not like OneUI but the core premise is still there

I wasn't talking about OneUI. I was talking about the reason Android was originally established. Part of the motivation was Danger (the people behind the Sidekick) having a very closed ecosystem. Google purchased Android, they didn't create it.
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,700
1
1,460
Twin Cities MN
I wasn't talking about OneUI. I was talking about the reason Android was originally established. Part of the motivation was Danger (the people behind the Sidekick) having a very closed ecosystem. Google purchased Android, they didn't create it.
The reason it was originally established was to create a mobile operating system with Google services integrated.

So.... not much has changed.
 
The reason it was originally established was to create a mobile operating system with Google services integrated.

So.... not much has changed.

I think you may have confused premise with purpose.


What I was trying to say was that it was a shame Samsung feels the need to prevent unlocking bootloaders in some regions, restrict cameras when unlocking bootloaders on some devices, and generally prevent free access to the hardware of their devices. Android was established to be an open platform.
 

iBowToAndroid

Senior Member
Nov 9, 2010
4,700
1
1,460
Twin Cities MN
I think you may have confused premise with purpose.


What I was trying to say was that it was a shame Samsung feels the need to prevent unlocking bootloaders in some regions, restrict cameras when unlocking bootloaders on some devices, and generally prevent free access to the hardware of their devices. Android was established to be an open platform.
Just because it's open source doesn't mean that devices should inherently be insecure.

Vote with your wallet. If you want a bootloader-unlockable model, then buy one of those.
 
  • Haha
Reactions: twistedumbrella

apatcas

Senior Member
May 25, 2007
602
156
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.
Hey man, how did you get the flip 3 into download mode?
I restarted into recovery but whenever i select to reboot into bootloader, it just boots normally.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    1
    I think you may have confused premise with purpose.


    What I was trying to say was that it was a shame Samsung feels the need to prevent unlocking bootloaders in some regions, restrict cameras when unlocking bootloaders on some devices, and generally prevent free access to the hardware of their devices. Android was established to be an open platform.
    Just because it's open source doesn't mean that devices should inherently be insecure.

    Vote with your wallet. If you want a bootloader-unlockable model, then buy one of those.
    1
    Hey man, how did you get the flip 3 into download mode?
    I restarted into recovery but whenever i select to reboot into bootloader, it just boots normally.
    Standard procedure for the past couple years has been to (while powered off) either hold all 3 buttons together, or hold both Volume buttons while plugging in USB
  • 3
    (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
    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
    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
    1
    Thank you and always the best.
    Added, UGC build
    1
    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?
    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