yashsingh1/xdaforums huggingface dataset:
[Android Software Development] realbbb:
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
[Android Software Development] dm_samsung:
Hi All,

Thank you @realbbb for patched Odin version 👍

Can I change Rom with patched Odin

from

Samsung SM-G977N (S10 5G Korea Snapdragon 855)

to

Samsung SM-G977U (S10 5G USA Verizon Snapdragon 855)

?

Thanks in advanced.
[Android Software Development] dm_samsung:
@topper89 Do you have Google services after switch only region from Chinese to Taiwan?
[Android Software Development] alecxs:
This looks like usage problem to me. Please check other thread

Please get approval to flash factory binaries - error, how to resolve?
[Android Software Development] realbbb:
Download both firmware, extract and compare PITs. Post QKEY and SRP from each.

RealBBB

Super Silver
[Android Software Development] realbbb:
Googling "Please get approval to flash factory binaries (pit)" comes up with people with similar issues. Looks to be needing a pit to flash, but could be other issues. Does not appear to be an odin problem.

realbbb

Dew Under
[Android Software Development] dm_samsung:
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?
[Android Software Development] realbbb:
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
[Android Software Development] dm_samsung:
How can I get this information from pit files?

Do I need any tool ?

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

Yes, sure. I'm waiting for parcel.

Thank you realbbb for answer.
[Android Software Development] realbbb:
A text editor will show the internal bytes. Near the end, the signature, contains what I am referencing.

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
[Android Software Development] Musthysani:
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
[Android Software Development] realbbb:
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
[Android Software Development] Musthysani:
I tried that yesterday but used home csc and it got stopped on system.img several times. I will try using the csc today
[Android Software Development] realbbb:
Not surprised. Try csc.

RealBBB

Cold Milk
[Android Software Development] Musthysani:
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.
[Android Software Development] realbbb:
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
[Android Software Development] Musthysani:
Okay thanks. I will let you know of the success within the next 5hrs.
[Android Software Development] Musthysani:
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?
[Android Software Development] realbbb:
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
[Android Software Development] Musthysani:
Okay please what do i need to know on re-partitioning incase if anything happens i can use this guide to solved it.
[Android Software Development] realbbb:
Have a copy of the current firmware that you know to work with your phone. Can flash back to it; as long as the security bits are not incremented. Consider looking to either generic tutorials or find the XDA threads for your specific device for more detail.

realbbb

Slim Bold
[Android Software Development] gunna35:
****Deleted by me for being incorrect and unhelpful****
[Android Software Development] shrihankp:
Is it possible to flash OTA update.zip using ODIN? I kinda have one from Samsung's FUS and don't wanna re-download the entire AP, BL, CSC combo...
[Android Software Development] realbbb:
Odin is for full partition programming. Recovery is for ota patches to partitions. Pass the zip to the recovery app.

Realbbb

Ba Start
[Android Software Development] cavarks:
Just wondering if I could get some advice from anyone here..

I have a SM-G965N (Korean) phone with what appears to be a stock firmware.

I wanted to change it to an Australian G965F (XSA) downloaded from Sammobile. Trying to get rid of all the Korean apps and characters.

So I have D/L Odin3 v3.13.3_3B_PatcheD and loaded G965FXXSHFUJ2_G965FOXMHFUJ1_XSA.

Selected all 5 file, BL, AP, CP, CSC, USERDATA.

In Odin got the following error "Re-Partition operation failed."

On the phone I get Secure Check Failed (PIT)

So I enabled the "re-partition" option in Odin.

Now I get ... "Can't open the specified file. (Line: 2057)"

Any suggestions?

Running Odin with admin...

No anti-virus running...

My S9+ uses a Exynos chip not a snapdragon. I wonder if this might be causing some issues.

----------------------------------------------------

G965N output:

----------------------------------------------------

ODIN MODE

DOWNLOAD SPEED: FAST

Product Name: SM-G965N

CURRENT BINARY: Samsung Official

KG STATE: Checking

FAP LOCK: ON

OEM LOCK: ON

Secure download: Enabled

CCIC= MAX77705 hw: 3 main:32

Warranty VOID: 0 (0x0000)

RP SWREV: B:5 K:5 S:5

DID = 2008F62fbed40011

EVT 1.0

LOT-ID = AB12N

CHIP_ID 08F62fbed400

nAsv_TABLE: 6

nAsv_CPUCLU0: 8, nAsv_CPUCL1: 7

nAsv_630: 5, nAsv_MIF: 6, nAsv_INT: 6

nAsv_CAM_DISP: 6, nAsv_CP: 9

nAsv_PMIC: 0, nAsv_PMIC_CP:7

nAsv_FSYS: 7

product_line: 2

asb_version: 9

ids_big: 62, ids_g3d: 36

PMIC_ID : 9 (c4)

LPDDR4 manafacturer = sumsung

LPDDR4 process ver = D18

LPDDR4size = 6GB

----------------------------------------------------

Odin output:

----------------------------------------------------

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<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/003> Odin engine v(ID:3.1303)..

<ID:0/003> File analysis..

<ID:0/003> skip file list for home binary

<ID:0/003> param.bin

<ID:0/003> dqmdbg.img

<ID:0/003> userdata.img

<ID:0/003> omr.img

<ID:0/003> Home Binary Download

<ID:0/003> Total Binary size: 6151 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> Can't open the specified file. (Line: 2057)

<OSM> All threads completed. (succeed 0 / failed 1)
[Android Software Development] realbbb:
Looks like Home csc was used. Home csc does not contain the pit file necessary for re-partitioning. Try the csc rather than home csc.

RealBBB

Hold Quick
[Android Software Development] cavarks:
I tried this after I first posted. I left out the USERDATA.

But I extracted the PIT file from the CSC file.

I then added pit to Odin and enabled re-partition, F.Reset time and Auto reboot.

I now get a "Secure check fail : pit" error on the phone.

This was where I was up to when you replied...

What did I miss?
[Android Software Development] cavarks:
Ok this is doing my head in.

I have a stock SM-G965N (Korean) Exynos phone.

I download both firmware for Australia:

- G965F (XSA) firmware from Sammobile. Android V10 (2021)

- G965F (XSA) firmware from Sammobile. Android V9 (2019)

I have tried both, with the same error below.

I have downloaded and tried Odin (Admin mode) v3.13.1_3B_PatcheD, Odin3 v3.13.3_3B_PatcheD and Odin3 v3.14.1_3B_PatcheD.

I have tried multiple cables. No antivirus running.

I have loaded the AP, BL, CP and CSC into Odin.

I have extracted the PIT file from the CSC file and loaded it into Odin's PIT tab.

In option's, I have enabled 're-partition'. 'F.Reset time' and 'Auto reboot' were already enabled, so left then enabled.

(Note, 're-partition' option make no difference to the error messages if enabled or not.)

I have tried variations of the listed above, nothing seems to work.

I still get (with the procedure listed above):

1) A "Secure check fail : pit" error on the phone.

2) A "Re-Partition operation failed." in Odin.

Is there a step I am missing, or should something on the phone be disabled?

I have turned these off, but that didn't help.

- FAP LOCK: ON / OFF

- OEM LOCK: ON / OFF

----------------------------------------------------

Odin output

----------------------------------------------------

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<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/003> Odin engine v(ID:3.1303)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 7287 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>

<ID:0/003> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

----------------------------------------------------

G965N output:

----------------------------------------------------

ODIN MODE

DOWNLOAD SPEED: FAST

Product Name: SM-G965N

CURRENT BINARY: Samsung Official

KG STATE: Checking

FAP LOCK: OFF

OEM LOCK: OFF

Secure download: Enabled

CCIC= MAX77705 hw: 3 main:32

Warranty VOID: 0 (0x0000)

RP SWREV: B:5 K:5 S:5

DID = 2008F62fbed40011

EVT 1.0

LOT-ID = AB12N

CHIP_ID 08F62fbed400

nAsv_TABLE: 6

nAsv_CPUCLU0: 8, nAsv_CPUCL1: 7

nAsv_630: 5, nAsv_MIF: 6, nAsv_INT: 6

nAsv_CAM_DISP: 6, nAsv_CP: 9

nAsv_PMIC: 0, nAsv_PMIC_CP:7

nAsv_FSYS: 7

product_line: 2

asb_version: 9

ids_big: 62, ids_g3d: 36

PMIC_ID : 9 (c4)

LPDDR4 manafacturer = sumsung

LPDDR4 process ver = D18

LPDDR4size = 6GB

Secure check fail : (PIT)
[Android Software Development] realbbb:
I would use v3.14.1_3B_PatcheD.

Is your bootloader unlocked? If not, you need to consider bootloader increments. What version firmware is currently on the phone? What bootloader version is currently on the phone? What firmware are your going to? If G965FXXSHFUJ2_G965FOXMHFUJ1_XSA, then bootloader version H is it. Bootloader security can only increment. Going back may not be possible.

Please post the current stock firmware PIT and the desired firmware PIT. I am interested in seeing if there is a something going on in there.

Do not load home_csc, only use csc when cross flashing. No need to set pit, since the pit is auto set and included in the csc.

Are you able to flash stock firmware? If not, then some other issue is going on. Resolve that before you try to crossflash.

Do consider checking XDA thread specific to your hardware. There might be more insight to your specific crossflash. Even with the patched odin; there might be hardware incompatibilities that abort a crossflash.

realbbb

Deep Blue
[Android Software Development] seojaehyung:
I also trying SM-G965N to SM-G965F but Error always occurs in SET PIT FILE(Re-Partition operation failed.)

My stock frimware is SM-G965N_KOO_G965NKSU5FUJ1 and i tried to flash SM-G965F_XXV_G965FXXU5CSF2

frimware also i tried CSC but I couldn't cross flash

I tried flash with stock BL but also error in System partiton

What should I do?
[Android Software Development] realbbb:
Often system partition failures are attributed to

the usb cable, try a different cable..

the usb 3.0 ports, try a usb 2.0 ports instead..

the computer, try a different computer..

the version of windows, try a different version of windows..

the samsung drivers, try the latest drivers..

realbbb

Slam Site
[Android Software Development] Freeddi:
Is there anyone who is using Odin on the actually MacBook Pro 2021?
[Android Software Development] shrihankp:
Unless you emulate Windows or something, ODIN will not work on MacOS.
[Android Software Development] Ledzee:
Hi,

which version of Odin from OP's post should I use to flash a Galaxy A52s 5G (256GB/8GB RAM).
[Android Software Development] vincentdania:
It worked on my galaxy note10+. But the phone has stopped receiving mobile network signals. It has been on emergency calls mode since.

Any ideas on how this can be corrected?
[Android Software Development] realbbb:
v3.14.1 is the latest.

realbbb

Book Meal
[Android Software Development] realbbb:
Flash CSC not home. Try a factory default. Be sure to flash the correct firmware for your hardware. Toggle airplane mode?

Check the xda hardware specific threads.

RealBBB

Note Right
[Android Software Development] mohitgalaxy3:
Hi @realbbb ,

I have read all the pages in search of flashing a rom on SM-G998N however till now I haven't found anyone successful.

Please let me know if there is any new development on the same.

I am looking forward to flash SM-G998N LGU+ to Korean stock firmware or cross flash to SM-G998B.

Regards
[Android Software Development] realbbb:
Successful g998u to u1 has been done. Not sure about g998n or g998b.

Please reply with the pit from each firmware.

realbbb

Bright Wheel
[Android Software Development] mohitgalaxy3:
I am posting 3 PIT File's info, 1st is my current KTC ROM having CSC as KTC(this comes with multi-CSC, 2nd I have downloaded Korean non branded ROM with CSC as KOO, 3rd is SM-G998B model rom.

Let me know if flashing to even non branded korean rom will work though I doubt it since I have asked few in S21 ultra forums they said nothing can be done to SM-G998N. I think they meant since ROM is same flashing multi -CSC rom won't make any difference.

Current Carrier PIT : COM_TAR2LSI9830 BOOTLOADER ul_key.bin BOOTLOADER2 vddcal_fw.bin VDDCAL_DATA sec_efs.img steady.bin up_param.bin KEYSTORAGE keystorage.bin VENDOR_BOOT vendor_boot.img recovery.img modem_debug.bin nad_refer.bin PERSISTENT dqmdbg.img vbmeta.img VBMETA_SYSTEM vbmeta_system.img metadata.img fmp_selftest optics.img userdata.img SignerVer03 G998NKSU3BULF 20220107195130 SM-G998N_KOR_KX_EKEY1 SRPTI16C003 SRPTI16C003

Korea stock PIT : COM_TAR2LSI9830 BOOTLOADER ul_key.bin BOOTLOADER2 vddcal_fw.bin VDDCAL_DATA sec_efs.img steady.bin up_param.bin KEYSTORAGE keystorage.bin

VENDOR_BOOT vendor_boot.img recovery.img modem_debug.bin nad_refer.bin PERSISTENT dqmdbg.img vbmeta.img VBMETA_SYSTEM vbmeta_system.img metadata.img fmp_selftest optics.img userdata.img SignerVer03 G998NKSU3BULF 20211224154208 SM-G998N_KOR_KX_EKEY1 SRPTI16C003 SRPTI16C003

SM-G998B PIT : COM_TAR2LSI9830 BOOTLOADER ul_key.bin BOOTLOADER2 vddcal_fw.bin VDDCAL_DATA sec_efs.img steady.bin up_param.bin KEYSTORAGE keystorage.bin

VENDOR_BOOT vendor_boot.img recovery.img modem_debug.bin nad_refer.bin PERSISTENT dqmdbg.img vbmeta.img VBMETA_SYSTEM vbmeta_system.img metadata.img fmp_selftest optics.img userdata.img SignerVer03 G998BXXU4BULF 20220103221135 SM-G998B_EUR_XX_EKEY0 SRPTH19D004 SRPTH19D004
[Android Software Development] soopx:
Hi, I'm trying to flash my S21 FE with the latest stock ROM, patched with Magisk, which should be one newer than the ROM on there, but I'm coming back with write failed. I tried using odin 1.13.1 and 1.14.1 patched and non-patched.

the ROM is BTE-G990bxxu1bul5. I'm actually not sure what carrier it is, but I'm not sure that matters.

The phone is in download mode, OEM unlock and USB debugging is enabled, and I've installed the latest USB drivers. Anything else I can try?

*edit*

This is the guide I'm following: https://www.samsungsfour.com/tutorials/root-galaxy-s21-fe-5g.html

*edit 2* nvm, it was just the guide. found another one and got it working, bootloader wasn't unlocked.
[Android Software Development] mohitgalaxy3:
@realbbb did u get time to check on this.
[Android Software Development] realbbb:
G998NKSU3BULF 20220107195130 SM-G998N_KOR_KX_EKEY1 SRPTI16C003 SRPTI16C003

G998NKSU3BULF 20211224154208 SM-G998N_KOR_KX_EKEY1 SRPTI16C003 SRPTI16C003

G998BXXU4BULF 20220103221135 SM-G998B_EUR_XX_EKEY0 SRPTH19D004 SRPTH19D004

The issue has been showing up on recent devices. The security that once was found in odin has been moved to the secure chain on the phone.

EKEY1 SRPTI16C003 <-does not match-> EKEY0 SRPTH19D004

This appears to stop the crossflash ability. However, I am still researching a solution. It will take time..

REALbbb

Purple Dome
[Android Software Development] mohitgalaxy3:
Thanks for the info @realbbb.

Also, since my ROM supports 2 CSC KOO and KTC and active CSC is KTC(Carrier based). Is it possible somehow to change it to KOO.
[Android Software Development] realbbb:
I have read that there are ways to change some CSC values via a factory image and some typing commands. Please look for xda threads for those instructions; if they will work for you.

realbbb

Slippy Dippy
[Android Software Development] clipdawg05:
What do you get when you cross flash and have you made any progress?
[Android Software Development] mohitgalaxy3:
No...odin fails with persist error...searched all xda no solution till now without root. Samkey doesnt Support this model.
[Android Software Development] clipdawg05:
with root you could do it?
[Android Software Development] mohitgalaxy3:
With root people have changed it in the file manually...you need to search xda for the file name.
[Android Software Development] mohitgalaxy3:
@realbbb

I have found this article below to change CSC, are you aware of this method.

Also how exactly is combination firmware different from regular one as I coudn't find one for SM-g998N.

Trick Android - Hướng dẫn đỗi mã vùng (CSC) máy hàn để xoá ứng dụng nhà mạng [Free]

Lâu rồi mình mới chia sẽ với các bạn vài thủ thuật nhỏ để các bạn ở nhà có thể tự đổi mã vùng csc của các máy samsung xách tay từ hàn quốc về việt nam, và các nước khác, thậm chí các anh hàng quốc cũng muốn loại bỏ bớt các ứng dụng rác của nhà mạng hoặc là Bypass Gmail. I.) Chuẩn bị Samsung...

galaxyos-net.translate.goog
[Android Software Development] chimothecreator:
are there any extra thing to be done wen installing the odin v3.14.1_3bPatchedD?
[Android Software Development] realbbb:
Nothing extra. Unzip and run.

Realbbb

Winkle Time
[Android Software Development] luridphantom:
been reading about the secure pit errors using both this and prince comsy's 3.12.1 patched and i'd like to add to it

here are 2 csc pit files, one from an a530w canadian model and one from an a530f international model. tried everything including swapping pit files to the csc tars and either hit a secure pit error or stuck on file analysis

here are both pit files for further analysis. they're both the same bootloader rev (e). hope it helps you see if we can bypass the secure signature check someday. both devices have pretty much the same hardware and i'd like to do this without tripping knox/flashing through twrp like the other roms in the device forum
[Android Software Development] mohitgalaxy3:
Is this possible
[Android Software Development] realbbb:
G998N to G998B

I have read that N is exynos. B could be either snapdragon or exynos. Get the correct exynos firmware for your device and share the pit files.

I have personally done U to U1, so cross flash should be possible unless sam applied different protections to N and B.

Post up the pits and I can take a look.

realbbb

origami paper
[Android Software Development] realbbb:
Not seeing the recent type/key checks in the pit files that block recent phones.

Have you tried preloading the pit in the odin pit tab/field?

Can you flash the original stock firmware meant for the original device model?

Be sure to check xda threads for help on your specific device. Found this thread that said you can cross flash ap and csc. here

realbbb

Tree Leaf
[Android Software Development] luridphantom:
yup, set repartition to true and loaded the pit file but still fail with the secure check pit error

flashing original stock is no problem for the a530w. only when i wanna try flashing a530f firmware that i run into the repartition failed/secure check pit error

also found that thread earlier and tried flashing csc and ap individually but odin wouldnt let me do it. there's something in the pit file/csc that's blocking me. if only theres a way to spoof the model number or something, the hw is exactly the same but for some reason is partitioned differently
[Android Software Development] mohitgalaxy3:
I have already shared the pits and you said as of now cross flashing isn't working but you will try to find a way.

Still i have a doubt what that guy is claiming: SM-G998N is a single sim and SM-G998B is dual sim how 2nd IMEI will be generated and assigned to 2nd SIM.
[Android Software Development] shikado:
Hello, i use F926U (change F926U1)

can i change F926N?

i read many people change another country's model

this case need pit file?
[Android Software Development] kmdigital:
I'm a bit confused. You have 6 files at the link above. So I should download V3.14.1, as I see that's the larger file, and then the 3.14.1_3B patch? Sorry, I answered my own question. Just use the patch version. Not sure why it's a smaller file, but that seems to be the correct option.

Thx!
[Android Software Development] fishmurder:
Thank you!