Database Info

[TIP][5.0.1]How to change CSC without root using Odin

Spent a buttload of time trying to find this info on the internets, it seems like every method required root or other warranty-voiding methods, this one (which iv'e stumbled upon on a foreign website) works without any tinkering at all, very easy to do.
Say my device is currently on CSCTR (carrier) on a rom that also contains the non-carrier CSC:ILO, which i wanted to switch to.
If I burn any rom that has PTR the device will stay on that particular CSC.
However if you install a rom that doesn't have the current CSC in it, the device's setting will reset to the rom's default.
(BEFORE DOING ANYTHING PLEASE BACKUP YOUR FILES AND SETTINGS, CHANGING ROMS AND CSC WIPES ALL OF YOUR DATA)
Here's how I did it:
1) Backup your stuff
2) Boot into recovery and do a full wipe
3) Wait for the device to boot
At this stage the device is running my target rom I9500XXUHOC5 but with CSCTR
4) Download a similar-version firmware that surely does not contain your current CSC, I downloaded firmware I9500ZSUHOC2 which defaults to CSC:BRI (taiwan)
5) Turn off the device, Boot in Download mode
6) Bring up Odin, load the new rom in AP and make sure that only "auto reboot" and "f. reset time" are checked
7) Click Start, go make coffee
8) One the device finished burning and booting, reboot back into recovery
9) Do a full wipe, reboot, drink cup of coffee from step 7
Now device booted up with CSC:BRI (or whatever default CSC of the rom you just installed)
10) Once the device finishes booting, turn it off, boot in Download mode
11) Bring up Odin, now load the rom with the CSC that you actually want, in my case it was I9500XXUHOC5 with default CSC:ILO
12) Make sure only "auto reboot" and "f. reset time" are selected, click Start
13) Wait for it to finish and boot up, continue drinking coffee
14) Turn it off and start in Recovery
15) Do a full Wipe and reboot
Congratz! I am now running CSC:ILO, without ROOT, without triggering Knox, keeping my "official" status and my warranty
(Note that most of the wipes can probably be skipped, It just felt somewhat "cleaner" to do it like that)
This exact method worked for me on a stock S4 9500 with Lollipop 5.0.1, I imagine it also works on KitKat/JellyBean and other devices
Hope this helps.
-D

Man, that's just great :good: I tried it on dad's N7100 aaaand it's worked! Thank you!

You're most welcome! Glad to hear this helped!
Guess I have my answer now; this method works on other devices and older firmwares awell.

i lost my backup no more csc changing

So I think you meant to install two different android....... The first that can be for any country and the second one that for the country I want..... Is that right?

Yep, one completely different and then the one you actually want to use

I want to go from UFN (Carrier, Argentina) to ARO (Argentina, no carrier). I first flash, for example SER (Russia), and the ARO. Is that right?
Two questions:
1) Will i be able to update via OTA and KIES after this with the new CSC?
2) How risky is flashing with ODIN if i don't have an EFS backup?
Thanks.

Always find installing the one I want and doing 2 factory resets works for me.

tom_car said:
I want to go from UFN (Carrier, Argentina) to ARO (Argentina, no carrier). I first flash, for example SER (Russia), and the ARO. Is that right?
Two questions:
1) Will i be able to update via OTA and KIES after this with the new CSC?
2) How risky is flashing with ODIN if i don't have an EFS backup?
Thanks.
Click to expand...
Click to collapse
Yeah that's the general idea. if both UFN and ARO are in the same firmware - first thing flash something that has neither like SER or SAE and then go ARO.
1) ofcourse, this method doesn't root or temper with /system or anything of that sort.. you are 100% stock at all times, OTA remains as long as you use official FW
2) I have personally flashed using Odin i believe over 50 times using various phones, none of them ever bricked, im very confident that as long as you follow the normal Odin directions - nothing bad will happen
Ofcourse, as always; your mileage may vary. don't blame me if your phone bursts in divine flames :silly:

Hi.
This method is not working anymore I think. Because it caused my S4 to work on opposite. Last year, Samsung didn't release official Lollipop for Turkey. And I upgraded to Russia Lollipop a that does not contain TUR CSC code. When the Turkey Lollipop released, I installed it and the device confused and set the CSC code to default of OJV, KSA which is Saudi Arabia. I had to rollback to 4.4.2 and root using kingroot and changed CSC to TUR and flashed Turkey Lollipop and that's it! I got the TUR CSC on LP.
Sent from my GT-I9500 using Tapatalk

At previous, I installed SER firmware because official Lollipop isn't released yet on my country and the CSC become SER. I flashed OLB firmware, and the phone was confused and instead changed the CSC code to XXV, not XSE (where my phone should).
Next time I flashed ARO firmware, where I intended to stay on Latin American one, and again, the phone was confused and instead changed the CSC to TTT. How pity.
Sent from my GT-I9500

The idea itself is nice but for some reason it gives me FAIL on my phone whenever I try to reflash with a different CSC. I downloaded the correct version, data wipe + cache wipe. It gives me FAIL in ODIN and gets stuck in Recovery Mode. I got back to Download Mode and reflashed my own CSC. No fails.
I'm currently on XEF (Open France). I tried 2 different CSCs which are not in my available CSC list: COA (Cosmote Romania) and DBT (Open Germany). None of them are in my available CSC list. I guess I have to root my phone and just get it over with.

this is not real. iwant aro one that was "argentina" but every time iaflashed is going to "UPO" paraguay. no matter wich rom i installed. i explain what i do first ARO to BTU, BTU to ARO and then ARO to ARO that i want ARO "argentina" and nothing happened. of course with this tutorial.

DenisF said:
Spent a buttload of time trying to find this info on the internets, it seems like every method required root or other warranty-voiding methods, this one (which iv'e stumbled upon on a foreign website) works without any tinkering at all, very easy to do.
Say my device is currently on CSCTR (carrier) on a rom that also contains the non-carrier CSC:ILO, which i wanted to switch to.
If I burn any rom that has PTR the device will stay on that particular CSC.
However if you install a rom that doesn't have the current CSC in it, the device's setting will reset to the rom's default.
(BEFORE DOING ANYTHING PLEASE BACKUP YOUR FILES AND SETTINGS, CHANGING ROMS AND CSC WIPES ALL OF YOUR DATA)
Here's how I did it:
1) Backup your stuff
2) Boot into recovery and do a full wipe
3) Wait for the device to boot
At this stage the device is running my target rom I9500XXUHOC5 but with CSCTR
4) Download a similar-version firmware that surely does not contain your current CSC, I downloaded firmware I9500ZSUHOC2 which defaults to CSC:BRI (taiwan)
5) Turn off the device, Boot in Download mode
6) Bring up Odin, load the new rom in AP and make sure that only "auto reboot" and "f. reset time" are checked
7) Click Start, go make coffee
8) One the device finished burning and booting, reboot back into recovery
9) Do a full wipe, reboot, drink cup of coffee from step 7
Now device booted up with CSC:BRI (or whatever default CSC of the rom you just installed)
10) Once the device finishes booting, turn it off, boot in Download mode
11) Bring up Odin, now load the rom with the CSC that you actually want, in my case it was I9500XXUHOC5 with default CSC:ILO
12) Make sure only "auto reboot" and "f. reset time" are selected, click Start
13) Wait for it to finish and boot up, continue drinking coffee
14) Turn it off and start in Recovery
15) Do a full Wipe and reboot
Congratz! I am now running CSC:ILO, without ROOT, without triggering Knox, keeping my "official" status and my warranty
(Note that most of the wipes can probably be skipped, It just felt somewhat "cleaner" to do it like that)
This exact method worked for me on a stock S4 9500 with Lollipop 5.0.1, I imagine it also works on KitKat/JellyBean and other devices
Hope this helps.
-D
Click to expand...
Click to collapse
To change the csc with the odin which I have to add the csc in the option AP or in the option CSC?

Odin 3 not getting past "NAND Write Start!!" (TWRP)

Hello,
I am new to this site so sorry if I'm doing something wrong. My Dad recently somehow (soft?) bricked his S7. Sometimes it gets to the lock screen, but then completely freezes after a few seconds and it has to be forced off. Other times it has given me a black screen with the error:
Bootloader exception
[ RST_STAT = 0x1000000 ]
Exception: do_handler_sync: UNKNOWN(esr: 0x2000000)
! @ @ @ @ D @
pc : 0x8f000a00 lr: 0x8f000048 sp: 0x0206f (cut off here)
'
And other times it has frozen at the boot screen and the screen has become pixelated.
So, after trying Kies (useless), waiting 24 hours and attempting to connect it to adb and fastboot (which I presume isn't really possible), I have resorted to using Odin to flash TWRP 3 onto the phone. However, when I try to flash the .tar (twrp-3.0.0-0-herolte.img.tar and also the latest one), no matter what USB port or cable or PC I use, it always goes straight to "NAND Write Start!!" and goes no further.
Any help would be appreciated as my Dad needs his phone back ASAP.
Thanks.
Side Note: I'm flashing it so I can recover his data, then I'm going to flash the factory firmware onto it.

MCSulphate said:
Hello,
I am new to this site so sorry if I'm doing something wrong. My Dad recently somehow (soft?) bricked his S7. Sometimes it gets to the lock screen, but then completely freezes after a few seconds and it has to be forced off. Other times it has given me a black screen with the error:
Bootloader exception
[ RST_STAT = 0x1000000 ]
Exception: do_handler_sync: UNKNOWN(esr: 0x2000000)
! @ @ @ @ D @
pc : 0x8f000a00 lr: 0x8f000048 sp: 0x0206f (cut off here)
'
And other times it has frozen at the boot screen and the screen has become pixelated.
So, after trying Kies (useless), waiting 24 hours and attempting to connect it to adb and fastboot (which I presume isn't really possible), I have resorted to using Odin to flash TWRP 3 onto the phone. However, when I try to flash the .tar (twrp-3.0.0-0-herolte.img.tar and also the latest one), no matter what USB port or cable or PC I use, it always goes straight to "NAND Write Start!!" and goes no further.
Any help would be appreciated as my Dad needs his phone back ASAP.
Thanks.
Side Note: I'm flashing it so I can recover his data, then I'm going to flash the factory firmware onto it.
Click to expand...
Click to collapse
Hi mate
First what s7 model do you have?
Make sure you are using the latest odin?
oding settings?
flash same or newer firmware on the phone
What files are flashing?
Check this thread is a nice guide for flashing stock firmware
O

MAX 404 said:
Hi mate
First what s7 model do you have?
Make sure you are using the latest odin?
oding settings?
flash same or newer firmware on the phone
What files are flashing?
Check this thread is a nice guide for flashing stock firmware
O
Click to expand...
Click to collapse
Hey.
I can't check the model as the phone is bricked. All I know is there are only two versions and I'm pretty sure it's not Korea. I'm not flashing any firmware, because I want to get his data off the phone and I'm pretty sure flashing firmware will erase user data. Just trying to get TWRP onto the phone. Odin settings: F. Reset Time ticked, nothing else. Odin version: Odin 3 v3.09. Flashing the .img.tar file as specified in my post.
Thanks.

MCSulphate said:
Hey.
I can't check the model as the phone is bricked. All I know is there are only two versions and I'm pretty sure it's not Korea. I'm not flashing any firmware, because I want to get his data off the phone and I'm pretty sure flashing firmware will erase user data. Just trying to get TWRP onto the phone. Odin settings: F. Reset Time ticked, nothing else. Odin version: Odin 3 v3.09. Flashing the .img.tar file as specified in my post.
Thanks.
Click to expand...
Click to collapse
hi mate
there are more than two versions of S7...... how you know you are flashing the right image? at least you know if you have an Exynos version?
If the phone is bricked how you plan to recover the data the recovery alone may not give you access to the rest of the system and with a custom rom you may have to wipe ( format) the data partition to get access to it ( to disable samsung encryption)
there is a newer odin 3.12.3 try that

MAX 404 said:
hi mate
there are more than two versions of S7...... how you know you are flashing the right image? at least you know if you have an Exynos version?
If the phone is bricked how you plan to recover the data the recovery alone may not give you access to the rest of the system and with a custom rom you may have to wipe ( format) the data partition to get access to it ( to disable samsung encryption)
there is a newer odin 3.12.3 try that
Click to expand...
Click to collapse
All I know is that this is shown when I boot into recovery:
Android Recovery
MMB29K.G930FXXU1BPHJ
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1BPHJ
user/release-keys
I don't know if that helps at all. In terms of recovering the data, the site I'm following instructions from says there is a Mount > USB Storage option in TWRP, which is why I am doing it.
Thanks

MCSulphate said:
All I know is that this is shown when I boot into recovery:
Android Recovery
MMB29K.G930FXXU1BPHJ
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1BPHJ
user/release-keys
I don't know if that helps at all. In terms of recovering the data, the site I'm following instructions from says there is a Mount > USB Storage option in TWRP, which is why I am doing it.
Thanks
Click to expand...
Click to collapse
Hi mate
Yes , you have a G930F (Exynos) the TWRP image you were using seem right , regarding this , if you install TWRP in order to access the System /data where all the user apps , info, pictures , mail , configurations ..... is you need to format it , that partition is encrypted only Samsung can access it , TWRP does not support it unless you disable it by formatting it ( AKA erasing everything), mount the phone as USB device it may give access to some partition but it will not give you access to the System/ data ( unless you had formated it before)
If you knew what was the phone CSC you could flash a stock firmware without loosing anything, you use home_csc instead of CSC

MAX 404 said:
Hi mate
Yes , you have a G930F (Exynos) the TWRP image you were using seem right , regarding this , if you install TWRP in order to access the System /data where all the user apps , info, pictures , mail , configurations ..... is you need to format it , that partition is encrypted only Samsung can access it , TWRP does not support it unless you disable it by formatting it ( AKA erasing everything), mount the phone as USB device it may give access to some partition but it will not give you access to the System/ data ( unless you had formated it before)
If you knew what was the phone CSC you could flash a stock firmware without loosing anything, you use home_csc instead of CSC
Click to expand...
Click to collapse
Ah ok. So there's no way for me to get the data off it without knowing the CSC?

MCSulphate said:
Ah ok. So there's no way for me to get the data off it without knowing the CSC?
Click to expand...
Click to collapse
Not that i know, can you boot at all? if so install this app
Open it and under the CSC code tab it will tell you the active CSC ( country code)
Which country are you from, Netherlands ?

MAX 404 said:
Not that i know, can you boot at all? if so install this app
Open it and under the CSC code tab it will tell you the active CSC ( country code)
Which country are you from, Netherlands ?
Click to expand...
Click to collapse
I'm from England. Can't boot to anything apart from recovery and download mode.

MCSulphate said:
I'm from England. Can't boot to anything apart from recovery and download mode.
Click to expand...
Click to collapse
Ok , and the phone you got it from an specific carrier? or it was unbranded ( no carrier specific)

MAX 404 said:
Ok , and the phone you got it from an specific carrier? or it was unbranded ( no carrier specific)
Click to expand...
Click to collapse
Specific carrier, EE.

MCSulphate said:
Specific carrier, EE.
Click to expand...
Click to collapse
Ok mate.......
based on what you showed me, this should be the firmware installed on your phone, only BTU , XEU and EE had a BPHJ firmware in UK
http://www.sammobile.com/firmwares/download/95186/G930FXXU1BPHJ_G930FEVR1BPH1_EVR/
is up to you ..... there should be safe almost 100% sure you should not lose any data.....but there is always a chance
Download firmware from the above link , extract ( un rar , use winrar 7zip) 5 files from the zip file , should be AP, BL, CP, CSC and home_csc , DO NOT USE CSC use all the other 4 files and flash them with Odin ( use the latest download link in the next link i will give you) with the same home_csc as is on your phone there should not be a factory reset .....all data is preserved........hopefully we have it
Follow instructions on this thread read post 1 and 2

MAX 404 said:
Ok mate.......
based on what you showed me, this should be the firmware installed on your phone, only BTU , XEU and EE had a BPHJ firmware in UK
http://www.sammobile.com/firmwares/download/95186/G930FXXU1BPHJ_G930FEVR1BPH1_EVR/
is up to you ..... there should be safe almost 100% sure you should not lose any data.....but there is always a chance
Download firmware from the above link , extract ( un rar , use winrar 7zip) 5 files from the zip file , should be AP, BL, CP, CSC and home_csc , DO NOT USE CSC use all the other 4 files and flash them with Odin ( use the latest download link in the next link i will give you) with the same home_csc as is on your phone there should not be a factory reset .....all data is preserved........hopefully we have it
Follow instructions on this thread read post 1 and 2
Click to expand...
Click to collapse
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?

MCSulphate said:
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
Click to expand...
Click to collapse
Anytime mate
Your father did not have any pin or password set up before? if that is so use this password default_password when asked for
home_csc goes in the CSC slot in Odin , Country Specific Code it has specific information and or configuration for special services offered by your carrier plus determines when you get an OTA , when you change CSC you have to factory reset if you keep the same CSC ( home_csc) is not mandatory

MAX 404 said:
Anytime mate
Your father did not have any pin or password set up before? if that is so use this password default_password when asked for
home_csc goes in the CSC slot in Odin , Country Specific Code it has specific information and or configuration for special services offered by your carrier plus determines when you get an OTA , when you change CSC you have to factory reset if you keep the same CSC ( home_csc) is not mandatory
Click to expand...
Click to collapse
Thank you so much for your help I'm waiting 2 hours for the firmware to download because of free account speed restrictions. I'll update this post when I've tried it.
Wish me luck!

MCSulphate said:
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Click to expand...
Click to collapse
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Download the firmware from sammobile ( first link) extract the 5 files as i told , then you you have two options
1 Extract files ( sammobile) , use the home_csc ( plus the other 4) from them and flash with odin
2 Extract files ( sammobile) save home_csc , go to the second link ( guide) download the firmware from there BUT use the home _csc file you saved ( extracted) from the firmware from sammobile , this is key to not lose any data
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
MCSulphate said:
Thank you so much for your help I'm waiting 2 hours for the firmware to download because of free account speed restrictions. I'll update this post when I've tried it.
Wish me luck!
Click to expand...
Click to collapse
fingers cross !!!

MAX 404 said:
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Download the firmware from sammobile ( first link) extract the 5 files as i told , then you you have two options
1 Extract files ( sammobile) , use the home_csc ( plus the other 4) from them and flash with odin
2 Extract files ( sammobile) save home_csc , go to the second link ( guide) download the firmware from there BUT use the home _csc file you saved ( extracted) from the firmware from sammobile , this is key to not lose any data
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
fingers cross !!!
Click to expand...
Click to collapse
Hey.
So I downloaded the firmware from the site, flashed it using Odin, it flashed successfully, but I'm still getting the same issue. Won't boot up at all :/ is it more likely in this case to be hard bricked?

MCSulphate said:
Hey.
So I downloaded the firmware from the site, flashed it using Odin, it flashed successfully, but I'm still getting the same issue. Won't boot up at all :/ is it more likely in this case to be hard bricked?
Click to expand...
Click to collapse
hey mate
Sorry to hear that , try something else , see if you can boot in safe mode
1. Power off the phone by holding down the power button for a few seconds.
2. Press and hold the power button until the Galaxy logo appears on screen.
3. Press and hold the volume down button and release the power button.
4. Hold volume down until the phone has fully booted.
5. You should see ‘Safe mode’ in the bottom left of the screen.
if that does not work my last oftion woul be a factory reset before of thinking on a hardware problem.....

Is my phone bricked?

Hi guys,
I'm posting searching for some assistance. I have a Galaxy S6 SM-G920i that I've been trying to flash a stock rom using Odin with no success.
I've tried flashing 5.02 versions, but read here that it won't work since it has an older bootloader.
Tried flashing 5.11 versions, but get stuck in boot screen/samsung logo.
Tried 6.01 versons, but get a DRK error after flashing.
Aldo tried with different versions of Odin, to no avail.
What else can I do to get my phone to work? I've tried ZTA and ZTO rom versions, but there seem to be no difference.
Also, I didn't make a backup of any folder, unfortunately. Read about many people that managed to get their phone working again, can anyone shed some light?
Thank you very much.
Edit: some more details:
- Odin v3.09 apparently gets stuck at "NAND Write Start!!" everytime. I'm trying with v10.6 and 12.3.
- Already tried changing the USB port, but I don't have another PC to try it.
- Tried flashing these roms already:
5.02
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
5.11
G920IDVU3DOJ6_G920IZTO3DOJ6_G920IDVU3DOJ6_HOME.tar
G920IDVU3DOJ6_G920IZTA3DOJ6_G920IDVU3DOJ6_HOME.tar
6.01
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPK2_G920IZTO3EPIF_G920IDVU3EPIF_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPG4_G920IZTO3EPFC_G920IDVU3EPG3_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar

Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920I
Region: INU
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Once it finished, you'll have DRK problem again.
To fix that, download and extract this;
https://download.chainfire.eu/736/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltedv-smg920i.zip
Open the "Odin3-v3.10.6" file in extracted zip folder, then press AP and select "CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5"
Once you've set the file to Odin, connect your phone to your PC in download mode and click "Start" on Odin.

Thanks for the help, I'm going to follow those steps!
But one question: why should the region be INU? Shouldn't it be ZTO or ZTA (I live in Brazil, it's a brazilian model)?

Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?

luckysquall said:
Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?
Click to expand...
Click to collapse
Is your IMEI still intact?

No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?

luckysquall said:
No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?
Click to expand...
Click to collapse
I think the IMEI was written with a box (like Z3X) and it needs a patched modem firmware. You flashed stock modem while flashing the stock ROM, thats why the "IMEI" can't read by modem.
So, you need a box (like Z3X) to patch the modem again.

I see... so there's no way to change the IMEI without a box?

luckysquall said:
I see... so there's no way to change the IMEI without a box?
Click to expand...
Click to collapse
Yes, there's no way to change the IMEI without a box.

ahh the ole efs corruption. Seems to be common on this phone, and is essentially the worst thing that can go wrong from flashing :/

Samsung Galaxy S7 - Germany (DBT) - Custom Binary FRP Lock workaround

Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!

Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.

Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.

Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock

*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?

The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835

audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?

Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related

*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day

I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.

audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!

Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?

Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £

Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993

Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for my late reply!

Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.

Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2

Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware

Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers

*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates

How To Guide Guide to root Galaxy S22 Ultra (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)

Code:
Your warranty is now void.
If you root your device, Your KNOX status will be tripped.
You can still pass the safety net after you root if you follow the instructions.
Sorry for USA models, you can't root unless you can unlock your bootloader
You will lose ALL your data if you unlock your bootloader. Do back up your data.
I am not responsible for bricked devices, or dead SD cards although it is not possible
Please do some research if you have any concerns about doing this to your device
How to flash official firmware? (not the root and unlock bootloader part!)
You will need:
A Galaxy S22 Ultra and common sense
Samsung Odin (the flashing tool of the official firmware)
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
You need to extract the zip file and you are going to use the file Odin3_v3.14.1.exe inside the folder.
Samsung Android USB Driver for Windows
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Double-click and install the exe file.
Optional: If you just want to change CSC, /efi/imei/mps_code.dat is where you can edit after rooting the phone
Replace the CSC you would like to be in the file
If you like to download the firmware of your carrier, follow the instructions bellow
Release 1.0.3 · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Download the platform you want to download to. (Windows)
You need to extract the zip and double-click open the file Bifrost.exe inside the folder.
You need to fill in the Model, and Region, press the Check for Updates button and the Download button.
How to find the Model: on your phone → Settings → About Phone → The third row says the Model number and you need to remove the part with the part of /xx, for example, SM-S908B/DS and you only need to type SM-S908B
How to find the Region: You can check the Region at this link https://samfrew.com/model/SM-S908B/
You need to find find a three-letter word depending on your carrier and country and type it in Bifrost, for example, EVR
Press the Check for Update button and download it with the Download button.
Put it to a place you can easily find, ie. Desktop.
After downloading it, find the file SM-xxxxx_x_xxxxxxxx_xxx.zip.enc4 on the place you put it and change the document format from .enc4 to .zip. Then, double-click and extract the file.
Open Odin3_v3.14.1.exe and turn off your phone. Connect a side of your USB to your PC/Laptop, and keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrive at Download Mode press volume up. Go back to Odin3_v3.14.1.exe:
-Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select AP_xxxxxxxxxxx.tar.md5
-Click on CP and select CP_xxxxxxxxxx.tar.md5
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
Optional: add PIT file if you have to repartition.
Press Start to flash the firmware, after that is done, your device will automatically reboot to the system.
How to unlock the bootloader?
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, press Vol Up + Down and then plug in the USB while keeping Vol Up+Down pressed.
When you arrive at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
How to root your phone?
After you unlock your bootloader, you set up your phone and ensure you do not sign in to your Google account first. Install Magisk https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk on your phone. You need to allow the app to install other apps so that you can install the apk.
Transfer AP_xxxxxxxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go and find the AP_xxxxxxxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, and keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrive at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_xxxxxxxxxx.tar.md5
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
Optional again: add PIT file if you have to repartition
When it finishes flashing, it will automatically reboot and you can gain root access.
Optional: If you want to have the safety net passed (most of the banking apps use it), then you need to install the zip
as a Magisk module in Magisk https://github.com/kdrag0n/safetynet-fix/releases
How? Go to Magisk → Modules → install from storage and select the zip you downloaded.
How to update the system without losing roots and data?
Download the new firmware of the phone and update the Magisk App if it is not up to date. Unzip the firmware you download and transfer the AP file to your phone. Patch your AP file and transfer it back to your PC (in /sdcard/Download)
Power off the phone and reboot to Download mode
Open Odin and put the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do its stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power
As soon as the screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Credits to:
Magisk and all the develpers
jult for informing me about the errors

Thanks, still waiting for s22u and firmware(BRI/sm-s9080).
Edit: The firmware has come up.

donkeyman1234 said:
Thanks, still waiting for s22u and firmware.
Click to expand...
Click to collapse
The time of downloading the firmware is quite long, please be patient

It gives me an error when I try to check for updates. It's the EUX version.

acbdo6 said:
It gives me an error when I try to chek for updates. It's the EUX version.
Click to expand...
Click to collapse
I am looking into the problem, please wait

acbdo6 said:
It gives me an error when I try to check for updates. It's the EUX version.
Click to expand...
Click to collapse
I think you may need to download the file at this link, although it will be slower. Usually, the app always works. Sorry
Download Samsung Galaxy S22 Ultra SM-S908B EUX Europe S908BXXU1AVA7 firmware
Fast download latest Samsung Galaxy S22 Ultra firmware SM-S908B from Europe with S908BXXU1AVA7 and Android version 12
www.sammobile.com

This will work on the Verizon version?

lucky_strike33 said:
This will work on the Verizon version?
Click to expand...
Click to collapse
I have a look at the internet and I think maybe you will need some service like that https://forum.xda-developers.com/t/sampwnd-usa-model-bl-unlock-info-u-u1-w.4201689/ if you cannot unlock the bootloader by following the guide

My s22ultra is SM-S908B EUX and I want to flash the Indonesian XID firmware which is OLE and SM-S908E. Is this possible?

gpap2004 said:
My s22ultra is SM-S908B EUX and I want to flash the Indonesian XID firmware which is OLE and SM-S908E. Is this possible?
Click to expand...
Click to collapse
you need to use the firmware of the same model number but you can use the firmware from different country

Williamtung said:
you need to use the firmware of the same model number but you can use the firmware from different country
Click to expand...
Click to collapse
Looks like Samsung changed some things there. XID firmware was available for flashing to my ex - S21 ultra . Now , in S22 ultra, I see different types of regions (SM-S908E and SM-S908B).

gpap2004 said:
Looks like Samsung changed some things there. XID firmware was available for flashing to my ex - S21 ultra . Now , in S22 ultra, I see different types of regions (SM-S908E and SM-S908B).
Click to expand...
Click to collapse
emmm... i'm not really sure about it now. maybe you can have a try then
[edit]: I have a look at the internet and I think it is all right if you use firmware of a different model. Of course, the spec should be similar/the same

Williamtung said:
emmm... i'm not really sure about it now. maybe you can have a try then
Click to expand...
Click to collapse
Yeah, but I'm afraid. I would not like to brick the phone. Except the all procedure stops from Odin and avoid bricking.

gpap2004 said:
Yeah, but I'm afraid. I would not like to brick the phone. Except the all procedure stops from Odin and avoid bricking.
Click to expand...
Click to collapse
you won't likely brick your device because I have taken a look and both devices are identical. So, I think it is fine to flash

Williamtung said:
you won't likely brick your device because I have taken a look and both devices are identical. So, I think it is fine to flash
Click to expand...
Click to collapse
This is great! Thanks ! Because XID ( Indonesian) firmware supports fully native call recording. Samsung's OTA updates are also available every month.

gpap2004 said:
This is great! Thanks !
Click to expand...
Click to collapse
you are welcome

I just made a research to the internet and I found that SM-S908E is probably different variant from SM-S908B .
SM-S908E is a snapdragon edition while SM-S908B is Exynos.
So , I think I cannot flash XID firmware for snapdragon edition to an Exynos version
I'm sad now

gpap2004 said:
I just made a research to the internet and I found that SM-S908E is probably different variant from SM-S908B .
SM-S908E is a snapdragon edition while SM-S908B is Exynos.
So , I think I cannot flash XID firmware for snapdragon edition to an Exynos version
I'm sad now
Click to expand...
Click to collapse
Oh, sorry. I haven't noticed about the SoC. The SoC in Europe is Snapdragon. So I don't think you should change it.
If you just want to change CSC, /efi/imei/mps_code.dat is where you can edit. Both firmware is the same except the CSC, no difference between them

My preordered s22u will come with snapdragon (sm-s9080 BRI ), I will use CHC csc, also like to have call recording.

gpap2004 said:
Looks like Samsung changed some things there. XID firmware was available for flashing to my ex - S21 ultra . Now , in S22 ultra, I see different types of regions (SM-S908E and SM-S908B).
Click to expand...
Click to collapse
S908E = snapdragon
S908B = exynos
Some countries have both version listed, you needs to to download one according your device
You can check about phone model number to see which one you own