Search This thread

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
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.

Variants, like u1 and u, can't be cross flashed except with patched odin.
Now methods are blocking variant cross flashing; even with patched odin.
This block is enabled by the use of values embedded in the signing of the pit. As long as the values match, cross-flash can happen (ie the first two below). If values differ, no dice (ie the remaining variants).

For instance:
G781U - ATT - QKEY1 - SRPTF19A
G781U1 - XAA - QKEY1 - SRPTF19A
Original odin will not cross flash; patched odin will. Win!

G781U1 - XAA - QKEY1 - SRPTF19A
G781V - VZW - QKEY0 - SRPTF02B
G781B - XX - QKEY3 - SRPTG02C
G7810 - CHC - QKEY2- SRPTF24A
G781W - XAC - QKEY5 - SRPTG08A
Original odin will not cross flash; patched odin will not cross flash. Bummer!

Do your due diligence with variant selection. At least till a new patched method is worked out.


realbbb
Crystal Blob
 
Last edited:

dm_samsung

Member
Oct 6, 2021
8
2
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?
@topper89 Do you have Google services after switch only region from Chinese to Taiwan?
 

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S

dm_samsung

Member
Oct 6, 2021
8
2
Download both firmware, extract and compare PITs. Post QKEY and SRP from each.
I attached PITs file, because I don't know how to read QKEY, SRP.

BEYONDX_KOR_SINGLE.pit - Korean version
BEYONDXQ_USA_SINGLE-TMB-TMobile.pit - USA T-Mobile
BEYONDXQ_USA_SINGLE-VZW-Verizon.pit - USA Verizon

How I can read QKEY and SRP from those files?
 

Attachments

  • S10 5G PITs.zip
    29.1 KB · Views: 12

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
I attached PITs file, because I don't know how to read QKEY, SRP.

BEYONDX_KOR_SINGLE.pit - Korean version
BEYONDXQ_USA_SINGLE-TMB-TMobile.pit - USA T-Mobile
BEYONDXQ_USA_SINGLE-VZW-Verizon.pit - USA Verizon

How I can read QKEY and SRP from those files?

BEYONDX_KOR_SINGLE.pit - G977NKSU5FUF5 - KOR_KX_KOR0 - SRPRK21D005
BEYONDXQ_USA_SINGLE-TMB-TMobile.pit - USA T-Mobile - G977TUVS7FUG6 - NA_TMO_USA1 - SRPSA08A007
BEYONDXQ_USA_SINGLE-VZW-Verizon.pit - USA Verizon - G977UVRU8FUI4 - NA_VZW_USA0 - SRPRK12A008

Ugh. New QKEY marker. Now KOR0, USA1, and USA0. All different SRP values. I would imagine that this will not cross-flash with current methods.

Keep in mind that the bootloader versions are all different. Bootloaders can only be the same or above. Once incremented you may NOT return to an older bootloader version. KOR Bit 5, TMB Bit 7, VZW Bit 8.

You could try flashing; BUT make sure you have firmware for each with all bit 5. Or all bit 7. Or all bit 8. You will not be able to flash back to a lower bit version once upped.

Good luck. Report back on your findings.


realbbb
Wait Date
 
Last edited:
  • Like
Reactions: dm_samsung

dm_samsung

Member
Oct 6, 2021
8
2
BEYONDX_KOR_SINGLE.pit - G977NKSU5FUF5 - KOR_KX_KOR0 - SRPRK21D005
BEYONDXQ_USA_SINGLE-TMB-TMobile.pit - USA T-Mobile - G977TUVS7FUG6 - NA_TMO_USA1 - SRPSA08A007
BEYONDXQ_USA_SINGLE-VZW-Verizon.pit - USA Verizon - G977UVRU8FUI4 - NA_VZW_USA0 - SRPRK12A008

How can I get this information from pit files?

Do I need any tool ?

Keep in mind that the bootloader versions are all different. Bootloaders can only be the same or above. Once incremented you may NOT return to an older bootloader version. KOR Bit 5, TMB Bit 7, VZW Bit 8.

The same question as above :) how can I get information about bootloader version from pit?

Good luck. Report back on your findings.

Yes, sure. I'm waiting for parcel.
Thank you realbbb for answer.
 

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
How can I get this information from pit files?

Do I need any tool ?

A text editor will show the internal bytes. Near the end, the signature, contains what I am referencing.

The same question as above :) how can I get information about bootloader version from pit?

G977NKSU_5_FUF5
also in the SRP.. SRPRK21D00_5_
bootloader bit 5

G977TUVS_7_FUG6
SRPSA08A00_7_
bit 7

G977UVRU_8_FUI4
SRPRK12A00_8_
bit 8


REALbbb
Hold Loose
 
Last edited:
  • Like
Reactions: dm_samsung

Musthysani

Member
Nov 6, 2021
7
0
Nigeria
Good morning. I am using s9 dual sim. Yesterday at night i installed the stock firmware smg960n version 10 on my s9 only to find out that i it is a single sim firmware and i can't install the smg960f firmware back using the normal odin.
I currently have the smg960f firmware named G960FXXSCFTK2_G960FOXMCFTJ2_ECT
can i possibly cross flash using the latest patched odin to make it dual sim again and does it need any special requirement?

Thank you
 

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
Good morning. I am using s9 dual sim. Yesterday at night i installed the stock firmware smg960n version 10 on my s9 only to find out that i it is a single sim firmware and i can't install the smg960f firmware back using the normal odin.
I currently have the smg960f firmware named G960FXXSCFTK2_G960FOXMCFTJ2_ECT
can i possibly cross flash using the latest patched odin to make it dual sim again and does it need any special requirement?

Thank you
Patched is the way to crossflash. Since you are going back, it should be fine. Be sure to flash csc and not home csc.


RealBBB
Lumpy Level
 

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
Okay thanks. But which version of patched odin should I use.
And incase it wasn't successful can i use the BL of smg960n then use the AP, CP, CSC and USERDATA of smg960f.
I would use 3.14.1
Success varies with mixed firmware components. Try and see if it works. If not, try a different mix. Personally I would stick to all of the same set.


RealBBB
Slippery X-ray
 

Musthysani

Member
Nov 6, 2021
7
0
Nigeria
I would use 3.14.1
Success varies with mixed firmware components. Try and see if it works. If not, try a different mix. Personally I would stick to all of the same set.


RealBBB
Slippery X-ray
I have tried using the csc file but it still hanged on the image attached and am sure of not ticking re-partition.
I even interchange the csc only.
Please is there any alternative way to make my phone dual sim again?
 

Attachments

  • 20211107_193245.png
    20211107_193245.png
    36.2 KB · Views: 156

realbbb

Senior Member
Dec 22, 2011
376
479
Amazon Fire TV
Samsung Galaxy Tab S
I have tried using the csc file but it still hanged on the image attached and am sure of not ticking re-partition.
I even interchange the csc only.
Please is there any alternative way to make my phone dual sim again?
You should be allowing re-partition for device cross flashing. That is what the csc attempts to do versus the home-csc.


Realbbb
Flies Puddle
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Have anyone tried the latest Odin version with Galaxy A55? It's Samsung's very first phone with seamless updates (AB partitions) and Odin 3.14 came out a long time ago ...
    Latest confirmed version is 3.14.1. Never seen an original 3.14.4 (all fakes). Nothing newer has been found in-the-wild.

    Have not heard whether any version of Odin is compatible or not with seamless updates. Nothing special may be needed if the device auto selects the correct flash partition. Might want to have a look at the XDA threads specifically about that device. Maybe someone has tried and reported it there. Do let us know what you find out.


    RealBBB
    Playable Billing
  • 288
    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