Search This thread
I misstated, the modem is CP. Last night I compared both file sizes for unlocked (U1) phones: S21's CP showed 62,361mb and Fold3's - 61,611mb. I used the PIT from the unlocked Fold3 (Q2Q_USA_SINGLEW.pit) along with CP from the unlocked S21 Ultra (SM-G998U1) and dared to flash them together. The result was "FAIL! (Auth). I used to flash different radios from the same chipsets before and was successful in doing so., however it was a good while ago. Definitely, patching Odin to bypass the (Auth) would help if is even possible.
really hope it has something to do with odin and not the phone.
 
  • Like
Reactions: mffu

realbbb

Senior Member
Dec 22, 2011
373
477
Amazon Fire TV
Samsung Galaxy Tab S
I misstated, the modem is CP. Last night I compared both file sizes for unlocked (U1) phones: S21's CP showed 62,361mb and Fold3's - 61,611mb. I used the PIT from the unlocked Fold3 (Q2Q_USA_SINGLEW.pit) along with CP from the unlocked S21 Ultra (SM-G998U1) and dared to flash them together. The result was "RQT CLOSE !!
I used to flash different radios from the same chipsets before and was successful in doing so., however it was a good while ago.

Why flash pit? Isn't the fold3 a legit u1?

The modem partition already exists in the stock firmware. Flash the s21 cp by its' lonesome. Resulting Odin output? Using original or patched odin? Try both.

Could just place the modem.bin in a tar without a md5. Original odin should reject. What is the patched odin output?


REALBBB
Tower Deep
 

mffu

Senior Member
May 9, 2006
120
11
US
Why flash pit? Isn't the fold3 a legit u1?

The modem partition already exists in the stock firmware. Flash the s21 cp by its' lonesome. Resulting Odin output? Using original or patched odin? Try both.

Could just place the modem.bin in a tar without a md5. Original odin should reject. What is the patched odin output?


REALBBB
Tower Deep
Thanks Realbbb! with Modem.bin only I can't get passed the "File Analysis". See attached.
 

Attachments

  • Odin-file analysis.png
    Odin-file analysis.png
    21.4 KB · Views: 41
Last edited:
Why flash pit? Isn't the fold3 a legit u1?

The modem partition already exists in the stock firmware. Flash the s21 cp by its' lonesome. Resulting Odin output? Using original or patched odin? Try both.

Could just place the modem.bin in a tar without a md5. Original odin should reject. What is the patched odin output?


REALBBB
Tower Deep
i'm thinking, is there really a need to repartition?? where does CSC flash to? is it system partition or user partition?

i'm thinking of flashing only CP and HOME_CSC. will this work??
hmm, seems CSC is not so straight forward. just had a look inside. attempt flashing CP alone.
 
Last edited:

realbbb

Senior Member
Dec 22, 2011
373
477
Amazon Fire TV
Samsung Galaxy Tab S
i'm thinking, is there really a need to repartition?? where does CSC flash to? is it system partition or user partition?

CSC contains a pit. It will modify the flash layout (ie re-partition).


i'm thinking of flashing only CP and HOME_CSC. will this work??
hmm, seems CSC is not so straight forward. just had a look inside. attempt flashing CP alone.

Home is csc without a pit. home will attempt to flash the components to the current partition layout.


realbbb
Slick Bench
 
  • Like
Reactions: mffu
CSC contains a pit. It will modify the flash layout (ie re-partition).




Home is csc without a pit. home will attempt to flash the components to the current partition layout.


realbbb
Slick Bench
thanks realbbb. current partition layout may not be enough for it since the AP and CSC is considerably larger in size, 900mb more. CP seems good =D. smaller in size than U1.

from your previous post, you mentioned flashing CP "lonesome" i would take it as alone excluding AP, BL and CSC. will attempt flash after backup!!
 
  • Like
Reactions: mffu
nope. same error as @mffu

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 96 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
 
  • Like
Reactions: mffu
could it be the odin version or samsung usb driver?

CP_F926U1UEU1AUG8_CP19729400_CL22146001_QB41581084_REV00_user_low_ship_MULTI_CERT.tar.md5

CP_F926BXXU1AUG8_CP19728596_CL22146001_QB41578985_REV00_user_low_ship_MULTI_CERT.tar.md5

could it be due to the bold version? the CP i'm flashing has a lower value.

flashing alone requires unlocked bootloader??

should i flash the new firmware instead?
SM-F926BAustralia2021-08-11F926BTBU1AUGB11

or

SM-F926BUnknown2021-09-05F926BXXU1AUHF11

or

SM-F926BVietnam2021-08-11F926BTBU1AUGB11
vietnam would be good. read that it has call recording and samsung pay
*update* nope still the same. even with the new CSC, i'm getting the same error.
CSC_OMC_OXT_F926BOXT1AUGB_CL22146001_QB41871774_REV00_user_low_ship_MULTI_CERT.tar.md5

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 11121 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

using back the first firmware i wanted to flash previously, selecting only CP and HOME_CSC, i'm getting this error now.

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 1060 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!


this time, will be trying F926B CP and F926U1 HOME_CSC
*update* nope still the same.

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 250 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

looking back at the logs above, we can see it did manage to write modem.bin over to the phone, except that it failed when it starts to write CSC contents.

Auth seems to suggest some form of authorization needed??

someone provided a solution to "FAIL! (Auth)"
nope, it doesn't work.. same error.

could be this reason,
 
Last edited:
  • Like
Reactions: mffu
seems like before ODIN is able to load the binary, it verifies the binary by checking the filename.

if you were to rename
CP_F926BXXU1AUG8_CP19728596_CL22146001_QB41578985_REV00_user_low_ship_MULTI_CERT.tar.md5
to
CP_F926U1UEU1AUG8_CP19729400_CL22146001_QB41581084_REV00_user_low_ship_MULTI_CERT.tar.md5

it will popup an error with message "md5 error! Binary is invalid"

tried extracting lz4 to modem.bin then tarring it to somename.tar
same error.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 96 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 
Last edited:
  • Like
Reactions: mffu
i figured, the first step is to analyze cache.img file since it's the smallest binary of them all and for some reason the phone is able to reject the binary if it doesn't match with some internal validation logic.

1631338637851.png


if we could figure a way to re-sign the binary. whoever familiar, pls help.

i'm not sure if we could simply replace them.
offset 0x0 296 bytes, some consistent headers and some bytes are so consistent which appears to be file signature.
offset 0x338

i believe if there is validation, it probably would break with error.

validation of the boot images is probably in the bootloader
 
Last edited:
  • Like
Reactions: mffu

realbbb

Senior Member
Dec 22, 2011
373
477
Amazon Fire TV
Samsung Galaxy Tab S
If I try it, it should result in at worst softbrick if incompatible I would think.
Generally a softbrick; always a risk of permanent damage with flashing. Be careful not to increment the bootloader (or security bits) further than available firmware to return back to. If you do, you will have to wait for the original firmware to increment to match, to flash back.


Realbbb
Jump Rock
 

realbbb

Senior Member
Dec 22, 2011
373
477
Amazon Fire TV
Samsung Galaxy Tab S
Was able to research the SM-G781 variants.

G781U - ATT - QKEY1 - SRPTF19A
G781U1 - XAA - QKEY1 - SRPTF19A
G781V - VZW - QKEY0 - SRPTF02B
G781B - XX - QKEY3 - SRPTG02C
G7810 - CHC - QKEY2- SRPTF24A
G781W - XAC - QKEY5 - SRPTG08A

Confirmed that U1 and W currently won't cross-flash.

Anyone have a U and U1? Would love to hear if a successful cross-flash. I would imagine, yes. Ex. ATT to XAA

Currently testing V and U1. Confirmed, currently won't cross-flash.


realbbb
Blue Holder
 
Last edited:
Was able to research the SM-G781 variants.

G781U - ATT - QKEY1 - SRPTF19A
G781U1 - XAA - QKEY1 - SRPTF19A
G781V - VZW - QKEY0 - SRPTF02B
G781B - XX - QKEY3 - SRPTG02C
G7810 - CHC - QKEY2- SRPTF24A
G781W - XAC - QKEY5 - SRPTG08A

Confirmed that U1 and W currently won't cross-flash.

Anyone have a U and U1? Would love to hear if a successful cross-flash. I would imagine, yes. Ex. ATT to XAA

Currently testing V and U1. Confirmed, currently won't cross-flash.


realbbb
Blue Holder
u1 and u are basically the same variant, with carrier sim lock etc so they are flashable.

different variant uses different signing keys thus its almost impossible to circumvent.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Trying to flash the SM-S921U CHA (S24 Spectrum) to U1 XAA, but I'm immediately hitting a "FAIL! (Auth)" error when trying to flash any of the files.

    As far as I can tell, the bootloader revisions match.
    Can you flash original successfully? If so, be sure to used PatcheD with U1 XAA firmware flash. Also, be sure to use CSC and not Home CSC.


    realbbb
    Metal Lick
    1
    Can you flash original successfully? If so, be sure to used PatcheD with U1 XAA firmware flash. Also, be sure to use CSC and not Home CSC.


    realbbb
    Metal Lick
    It was just me being dumb. Somehow I downloaded the S24 Ultra firmware instead of the base S24. It's flashing fine now.
    1
    Successfully flashed S911U1 on S911U and working perfectly. Thank you
    1
    please, can you update it to support newer versions? I need to downgrade my phone from binary 8 to 7 , android 11 to 9.
    Last official version is 3.14.1. All 3.14.4 have been fake and offer nothing over 3.14.1.

    You cannot downgrade binary versions. It is a fused flash forward only.


    realbbb
    Slinky Sky
    1
    I can confirm this tool works with a Galaxy S24 SM-S921U. I have a Verizon version that was unlocked after the standard 60 day wait. Bifrost 1.17.8 let me download the firmware for SM-S921U1 XAA. After putting the phone in Download mode and selecting all the files, including the HOME_CSC versus the standard CSC, the flash and reboot process took just a few minutes. It rebooted a third time to reconfigure the phone for MInt Mobile use.

    I did not have to remove any Samsung or Google account, not did I hard reset. Everything worked perfectly afterwards without any backup/restore. The phone no longer complains about the non-Verizon SIM every time I reboot and all the Verizon junkware is gone.
  • 287
    For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around.

    I patch recent Odin versions to offer similar functionality to the princecomsy; in that it ignores both the sha256 fails and the model mismatches.
    - Developed and successfully tested for my verizon samsung s8 g950u to g950u1 and combination firmware packages.
    - Confirmed working on an unlocked S9+ g965U1 to VZW g965u
    - additional confirmation: G950w from G950u
    - able to flash T727R4 firmware to T727V
    - confirmed working with S21 5G from G991U to G991U1
    - flashed G998U VZW to G998U1 XAA
    - confirmed S22 S901U VZW to S901U1 XAA
    - successful S23 S911U XAU to S911U1 XAA
    - reported S24 Ultra S928U TMB to S928U1 XAA success

    Ignores and bypasses the below stop conditions:
    "FAIL! Model mismatch fail" (all PatcheD versions)
    "FAIL! SHA256 is invalid" (all PatcheD versions)
    "FAIL! Blocked carrier" (PatcheD versions >= 3.14.1)

    Be careful flashing!

    +20180313 - Added Stock odin 3.13.1 sourced from pedant87 / Added PatcheD odin v3.13.1
    +20191211 - Added PatcheD v3.13.3 and original 3.13.3 for windows, Merry Christmas!
    +20191218 - Added the only clean and original v3.14.1 for windows
    +20200216 - Added ModdeD/PatcheD 3.14.1 for windows! Supports newer phone flashing methods. A new check method for a carrier flash halt has been removed!

    Caution #1 - There are many stock/mod/patch copies floating around the internet with redirected links and other misleading claims and changes. The XDA links below are the only source for clean originals and the original 3B files.

    Caution #2 - All v3.14.4 are hoax/fake versions of odin. It is version 3.14.1; same filesize (and one other variant in size, due to larger resource changes). All have internal resource modifications to report 3.14.4. Often includes a known cloud-based client-server communication dll (cpprest141_2_10.dll). I suggest that it be avoided. It adds no additional functionality over 3.14.1. See post here for more detail.


    When you donate, and this work was helpful to you, do consider donating to this effort by using the DONATE HERE link. Thanks for your support!

    For those that have asked for a digital currency way to donate.

    Bitcoin
    3A56AWxUvvGgWT8BcVJ3yeiqNdZVHaCaoj

    Ethereum
    0xb3bd522f067a89675ed2daae02f2db1dc9ec8c48


    ¡BBB!
    Walking Domestic
    11
    Hey mate,
    Just a quick question / concern .. Just ran an analysis on your file here -> link
    While I can't see too many differences after unzipping your exe and running a comparison with a hex editor against your original odin you provided .. still the online analysis results do make me ask the question
    "please explain?"
    Online analysis of your original odin provided is here -> link

    Please note that Eudummy did not run reverse it on the OP attached executable file. The sha256, executable type, and file size do not match the file he tested at his provided link. I am wondering why he would test a different file with the same filename? Just a plug for reverse it? Anywho... To help calm others...

    The patches/changes are:
    Operationally I patched as indicated in the OP (encryption and model fails).
    All other changes are visual. ie. main graphic bar, version code, and url text/address.

    That is it. Simple and has helped many to flash their phones!


    ¡realBBB!
    Not Your Mate
    7
    Thanks, thought my firmware was bad since it wouldn't flash with the previous odin. This worked perfect. I used this to flash my galaxy s9+ from U1 to VZW.
    6
    Thanks. I wanted to firmware back to G950w from G950u using Oreo and found it. Really appreciate your hard work
    5
    Added 3.13.3 3B Patched to the OP. Merry Christmas!


    realBBB
    Tix Under