yashsingh1/xdaforums huggingface dataset:
[Android Software Development] realbbb:
Should work with all samsung devices.

realBBB

Monitoring Well
[Android Software Development] realbbb:
Odin will flash both devices. Whether that is a path to root remains to be seen.

realBBB

Slippy Dive
[Android Software Development] mormopterus:
Thanks, I will have another go at it at some stage. If I can get the PIT from the CSC, it's certainly worth another shot....
[Android Software Development] cstucker:
Someone please help! I flashed SM-N986U1 to my t-mobile locked Note 20 Ultra. How to I get back to the original model#(SM-N986U)? my current model number is SM-N986U1.

Please help
[Android Software Development] cstucker:
Please help. Which Odin patched version will let me go from an unlocked model # to a carrier locked model. i flashed to sm-n986u1 and i want to go back to sm-n986u(t-mobile). Please help, I'm so lost.
[Android Software Development] realbbb:
Obtain tmobile U firmware and flash the same way you did U1.

Latest 3.14.1 will do the trick.

Realbbb

Hollow Chirp
[Android Software Development] JuanTamqd21:
hi on my sam a505gn one ui 3,

it shows:

SW REV check fail bootloader device 7 binary 5

pit flash binary unsuported odin
[Android Software Development] Wish39:
You tried to flash binary 5 firmware onto your phone which already has binary 7 firmware. You need to get firmware that has same or higher binary number.
[Android Software Development] rustamjon09098:
один

Взаимодействие с другими людьми
[Android Software Development] herbicide:
Thank you Realbbb for this work.

Should I expect this Odin to correctly operate on Samsung Galaxy S9 (SM-G960F)?
[Android Software Development] realbbb:
Works with the S9.

RealBBB

Low Flying
[Android Software Development] 3GJockey:
Is this relevant to you?

And, if you've solved your problem, please advise us how.

I have a Note 20 Ultra USA unlocked, and I'm trying to get it on Tmo firmware so I can do eSIM.

https://xdaforums.com/t/guide-odin-upgrading-flashing-and-n986u-to-n986u1-vice-versa.4182825/
[Android Software Development] :
I have a unlocked G9750 w/ android 11 that I want to flash to G975U, which version of Odin should I use? Thanks
[Android Software Development] realbbb:
3.14.1 is the most recent.

RealBBB

Chrome Flight
[Android Software Development] Vegetto32:
I mates, did anyone ever solved the issue with flashing SM-G970F Model over SM-G970N?

I am really puzzled at how can a seller sell this phone as a G970F Model when it's actually not?

and if they succeeded in flashing the F Variant why can't we do it?

I would appreciate any help in the matter,

thanks.

I was able to solve the Re-Partition Operation Failed error - It's quite simple since it's originally an G970N phone you should use the pit file from their Firmware.

however that's just was just the small problem the big problem is that even with modded Odin3 the flash just pending at the verification state (white boot) probably because it recognize the firmware to be different then the phone which it's trying to do the flash over.

i thought the all idea of the modded Odin was to bypass this issue wasn't it?
[Android Software Development] DEXXO:
Hey Thanks so much only this Patchen version worked to Flash the S7, i dont understan why the official Version of Odin dosent work (error SHA256) . anyway thank YOU !
[Android Software Development] djshakilexe:
I have Samsung A71 Global Version, i want to update firmware from different country, will it be ok?
[Android Software Development] allc0re:
I'm attempting to flash a Galaxy S7 back to stock firmware (Marshmallow version). It has worked on every S7 I've attempted as late as 2019. Now today it is not working on an S7. Did Samsung prevent this flash method somehow?

Here is my output from patched Odin:

<ID:0/003> Odin engine v(ID:3.1401)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 5192 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> emmc_appsboot.mbn

<ID:0/003> lksecapp.mbn

<ID:0/003> xbl.elf

<ID:0/003> FAIL! (Auth)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Android Software Development] davedes:
Hi

Please help

1. Would I be able to flash Samsung stock firmware on my S21 from the same CSC (XFA to XFE) using this patched version of Odin? XFE being on newer firmware, July update.

2. Will this permanently change the CSC on my S21 from XFA to XFE to receive future OTA updates?

3. Will knox be tripped?

For some reason S21 devices using XFE receive more frequent updates than XFA in my country.
[Android Software Development] kingrohan:
Just a noob question, I want to flash stock firmware on my phone, not changing csc or anything, my phone is international unlocked version G975F.

Should I use 3.14.1 patched version or clean original version..???
[Android Software Development] trivjednom:
Then you don't need a modified version of odin ... In my opinion, it will be best for you to use the last vision ..
[Android Software Development] realbbb:
Either 3.14.1 will work; The original 3.14.1 will make more sure your downloaded firmware is intended for your phone.

RealBBB

Bee Thing
[Android Software Development] realbbb:
Yes. As long as the bootloader version is the same or newer.

Phone is permanently marked the original csc. However, this does not mean you can't flash the other csc firmware. The phone will operate as if the csc firmware was the original csc. Tools will report originally XFA/XFA/XFA. Flashing the other firmware would report XFE/XFE/XFA.

It should not.

RealBBB

Zero Rocks
[Android Software Development] realbbb:
Likely a version issue. Could be phone's flash failing (s7 are getting old). Make sure you are flashing the correct security version (same or newer).

RealBBB

Up Left
[Android Software Development] realbbb:
It should, as long as the hardware is compatible.

RealBBB

Turn Nickle
[Android Software Development] realbbb:
Never seen an official Linux version to patch.

Realbbb

Water Beard
[Android Software Development] kingrohan:
Hello,

I am having a weird problem since last year.

I don't know if its the right place to ask for a solution but here goes.

Last year after the march update(Android 10) on my G975F (INS) I was having battery drain problems, so i decided to use Odin to flash the firmware downloaded via Sammobile.

A day after the flash, out of no where, the UI started stuttering. Like, swiping down from the notification panel, switching between apps, scrolling in app drawer etc.

So, I flashed the firmware again, factory reset but still the stuttering exists.

I thought it could be a hardware issue, so I flashed my then smooth AF tab s4, and the same thing happened, My tab s4 which was buttery smooth before also became stuttery.

Here is the bunch of things that I have tried,

Different cables

Different odin versions

3 Seperate Pc

made sure that I have the latest drivers

also used frija and samloader to download firmware.

and Uncountable number of factory resets via setting, recovery or using CSC in odin.

I am really disappointed seeing other people with same device having buttery smooth UI.

What did I do wrong, and how can I rectify it.
[Android Software Development] realbbb:
A quick search of the internet shows you are not alone with the S10+ or Tab S4 lag/stuttering issues. Even firmware releases call out attempts by Samsung to address the lag/stuttering of those devices.

That being said, it does not appear to be an issue with odin or patched odin. Odin and patched odin still transmit with verification in fidelity (failures can indicate cable or usb port issues, ie flash failures). You did not experience this.

Things to look into:

Double check your firmware downloaded. Obtain latest stock, that was originally on the devices.

Try booting safe mode. If it clears up the issue, it is likely 3rd party apps.

Fresh flash/installs are often optimizing at first boot up. Be sure to wait out this optimizing. Let the device settle before adding accounts, apps, etc.

Definitely follow up with the XDA threads that specifically address your hardware.

realbbb

Soft Falling
[Android Software Development] kingrohan:
I have downloaded the firmware from multiple sources, but they are all the same.

It happens even without apps, I have waited for months.

Last factory reset was in April but still the issue is there.

One thing I forgot to mention, updating through smart switch makes the stuttering go away by 50%.

But If I flash the same firmware again via odin, the heavy stuttering is back.

What could be the reason, doesn't smartswitch also uses odin..???
[Android Software Development] djshakilexe:
Thanks, It worked....
[Android Software Development] paux3:
hi, please help, it says secure check fail (PIT), what to do?

i have issue, i want to change to SM-A205U to SM-A205GN, is that possible

im using samsung a20
[Android Software Development] realbbb:
Make sure you have the correct firmware for your device.

Realbbb

Game Cola
[Android Software Development] realbbb:
As long as the hardware is compatible.

Check the XDA threads that specifically address your hardware.

Realbbb

Hold Greeny
[Android Software Development] topper89:
Hello, i try to switch from sm-g9810 (chinese) to sm-g981u1 (USA) to get all my Google and Samsung apps pre installed, because it seems that the Chinese version hadn't them installed, but the flash always failed.

So I tried to switch within the same region form Chinese to Taiwan an it worked without any problems, I used the patched Odin Version.

Can somebody help me?
[Android Software Development] realbbb:
Can not flash older bootloader. U1 currently on 2 and 0 currently on 3. Keep 0 at 3 and wait for u1 to release 3; then try again. Report back with specific error to rule out odin.

Be sure to check XDA threads for your specific hardware.

RealBBB

Falling Bear
[Android Software Development] ShAd0W_z0nE:
Hello I clicked on the link to donate and I can't. I got this error : "This recipient only accepts PayPal payments through its Web site. To complete this payment, go to the recipient's Web site and follow the instructions, or email the recipient for instructions."
[Android Software Development] Kamikaze01:
Hello.

Will there be a patched version of 3.14.4 ?!

Thank U :)
[Android Software Development] kingrohan:
3.14.4 is fake.

3.14.1 is the last known official version.
[Android Software Development] prince_72:
I have a small problem with the patched version. I am trying to cross flass a S20 FE 5G from the W model to the U1 model.

I have done that multiple times for s9, s10, s10+, note10+ but now it fails saying that the repartition failed. Both firmares for the W and U1 are on 4 security level. Do we know if odin works on those firmware releases and/or on that model S20 FE 5G?
[Android Software Development] realbbb:
Do not recall issues. Make sure to also add the proper pit in the pit tab.

Check out the device specific xda threads for additional pointers.

Bbb

Low Verticals
[Android Software Development] prince_72:
I am checking the other forums I just wonder if the patched version still works at the latest version of firmware

Also I have used a pit file and the result is the same
[Android Software Development] realbbb:
Does W stock firmware with repartition checked and pit entered, work with patched odin 3.14.1? Stock odin 3.14.1?

Realbbb

Side Delta
[Android Software Development] prince_72:
Good question. Let me check and come back to you
[Android Software Development] prince_72:
Reflashing the original firmware (G781WVLU4DUG8) with the patched version works just fine.

I am trying to reflash with the patched version the US unlocked U1 (G781U1UEU4DUG1) where both

firmwares are on the same security level does not work.

I extracted the PIT from the CSC and I added as well and again it did not work. I have the re-partition fail error
[Android Software Development] kingrohan:
Which version is the best to flash stock rom (Android 11) on S10 plus exynos..???
[Android Software Development] jemfalor:
will flashing F916B on a F916U1 work?

same as F926B on F926U1?
[Android Software Development] realbbb:
3.14.1 original will do the trick.

Realbbb

Arrow Up
[Android Software Development] realbbb:
Check the specific xda forum for the devices. As long as the hardware is the same; should be fine.

Realbbb

Soon Trooper
[Android Software Development] jemfalor:
thank you!

1. btw, since it's flashing different variant but the same model and hardware, do i still need to flash AP & BL & CP & CSC or i could simply just flash the CSC or HOME_CSC only?

2. OR can i selectively flash only the CP and HOME_CSC because it contains the configuration needed for the bands.

3. is there anything to take note of when flashing different variant? do i need to change the CSC first before flashing a different CSC region/variant?

thanks in advanced!
[Android Software Development] realbbb:
Recommended to flash all when changing models.

Flashing parts is possible, but it is hit and miss; usually not met with much success.

CSC changes with specific builds and sim cards. Flash the firmware with the desired csc support you want.

Be careful with security versions (ie bootloader, etc). Can only flash equal or higher; no going lower once incremented.

There also is a now utilized PIT implementation that is blocking some devices from model changes. It results with "Re-Partition operation failed". Have not found a solution for this one yet.

Realbbb

Deep Cloud
[Android Software Development] jemfalor:
regarding the above points, does it cause a brick? is it recoverable?

i understand i have to remove google and samsung account before flashing, including removing screen lock. is there anything else i need to take note besides this?

once all points are clear, i'll proceed with the flashing.. will return back with steps on how to do it =D (only if successful)

thanks again!
[Android Software Development] jemfalor:
just tried flashing with CSC, getting "Re-Partition operation failed."

unfortunately.
[Android Software Development] realbbb:
Would you extract the PIT from each of the firmwares and DM me them? F916B, F916U1, F926B, F926U1

Thanks!

realBBB

Pepper Car
[Android Software Development] jemfalor:
hi Pepper,

attached the zip with F926U1 and F926B pit files.

XAA for F926U1

XSP for F926B

XAA is using Q2Q_USA_SINGLEW.pit

XSP is using Q2Q_EUR_OPENX.pit
[Android Software Development] realbbb:
Newer PIT files have a number of signature variables that are currently of interest: firmware build, qkey, continent, csc, and srp

Q2Q_USA_SINGLEW.pit - F926U1UEU1AUG8, QKEY0, NA, XAA, SRPUA13A001

Q2Q_EUR_OPENX.pit - F926BXXU1AUG8, QKEY1, EUR, XX, SRPUC12A001

As you can see the firmware builds are now embedded in the pit. Currently that does not stop things. Neither does the continent or csc code currently stop things. However, that is not the case when the qkey and srp differ (coincidence?).

So far I have seen QKEY and SRP being different always results in "Re-Partition operation failed". Would like to hear about one or the other being the only one being different to cause a fail (who knows at this point, never seen it). Though they may always change when the other changes?

Considering that this detail is in the signature of the latest firmware components (not just PIT), this could make things exceedingly difficult in the future. Especially if sam has the checking done on the phone side and not odin. eol

realbbb

Heavy Float
[Android Software Development] jemfalor:
hi realbbb,

thanks for the analysis and info. seems like sam has the upperhand now, restricting phones regionally.

i supposed this is their method of keeping cost price low while maintaining profit margin. like how Nintendo have their peripherals using Bluetooth tech but not labeling as such to avoid royalties.

if flashing variant stock rom is difficult in future, may have to venture into rooting once again.
[Android Software Development] mffu:
I just discovered that Fold3 doesn't have CDMA portion enabled in the radio whereas S21 being on the same 888 chipset does. Would it be possible to tweak Odin to be able to flash radios made for the same chipsets? (e. g flash AP from S21 on Fold3)
[Android Software Development] realbbb:
The modem is in CP.

It has been years since I have frankenstein'd firmware. A pieced together firmware may work? And as long as download mode is available, one can flash back to stock (keeping security levels the same). Do let us know of your success or failure.

Have you checked with the xda thread for the fold3?

I may need to obtain a testing phone to work out if this can be patched in odin. Time will tell.

Realbbb

Cleverly Frogged
[Android Software Development] jemfalor:
hi Realbbb,

didn't know this can be done. everywhere i read, everyone was saying you have to flash everything.

hopefully this can be done. i too believe it's possible as long as the required files are not distributed across the binaries, AP, BL etc.

any idea where esim is located? while extracting the binaries, i see esim in the extraction.

I'm sure the snapdragon 888 x60 modem supports every 5g bands just restricted regionally via configuration. the omission of esim in US models can be activated via some software.

apk comparison between xaa and xsp firmware, respectively.
[Android Software Development] mffu:
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.
[Android Software Development] jemfalor:
really hope it has something to do with odin and not the phone.
[Android Software Development] realbbb:
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
[Android Software Development] mffu:
Thanks Realbbb! with Modem.bin only I can't get passed the "File Analysis". See attached.
[Android Software Development] jemfalor:
i think he meant by modem.bin in a tar without md5
[Android Software Development] jemfalor:
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.
[Android Software Development] realbbb:
Should be a tar archive with modem.bin inside.

realbbb

Heavy Balloon
[Android Software Development] realbbb:
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
[Android Software Development] jemfalor:
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!!
[Android Software Development] jemfalor:
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!!
[Android Software Development] jemfalor:
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)
[Android Software Development] jemfalor:
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.

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
[Android Software Development] jemfalor:
do you think it would work if i unlock my bootloader then flash a variant firmware then relock it?
[Android Software Development] Andrew x3:
Can I use this to flash my f711u to f711B ? They're both snap dragon.
[Android Software Development] realbbb:
If the firmware is compatible; yes, the patched is the way to accomplish it.

Realbbb

Deep Step
[Android Software Development] Andrew x3:
If I try it, it should result in at worst softbrick if incompatible I would think.
[Android Software Development] realbbb:
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
[Android Software Development] jemfalor:
not sure that model will fail but it will probably fail when it attempts to repartition using CSC
[Android Software Development] realbbb:
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
[Android Software Development] jemfalor:
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.