• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Change CSC

Search This thread

Zmantech

Senior Member
Aug 21, 2017
132
20
I was wondering if I changed the CSC on a Korean Note 20 Ultra if I would unlock US bands or if the hardware simply does not exist. Or could I just *#BAND# to activate them?
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
15,103
3
5,235
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
How would I extract the modem.img (I have a US version for now) and install it?
Use 7zip to extract the firmware file on PC, then, extract the files that are inside the firmware. I can't remember where the modem.img file is located inside the firmware, just extract the firmware files, then extract the files that come out of the firmware, then look through the files that come out of those files and you should see a modem.img or a modem.bin file somewhere.
 

Zmantech

Senior Member
Aug 21, 2017
132
20
Use 7zip to extract the firmware file on PC, then, extract the files that are inside the firmware. I can't remember where the modem.img file is located inside the firmware, just extract the firmware files, then extract the files that come out of the firmware, then look through the files that come out of those files and you should see a modem.img or a modem.bin file somewhere.
I found this would this work https://samfirms.com/samsung-note-20-ultra-5g-sm-n986u1-eng-modem-. Then I just flash via odin but which slot do I put the modem file in?

Should I just flash the CP from an unlocked US firmware
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
15,103
3
5,235
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I found this would this work https://samfirms.com/samsung-note-20-ultra-5g-sm-n986u1-eng-modem-. Then I just flash via odin but which slot do I put the modem file in?

Should I just flash the CP from an unlocked US firmware
I suggest only flashing the modem. When you extract the copy of modem.img, convert it to an Odin flashable .tar file using 7zip with the highest level of compression. Then flash the modem.img.tar via Odin, place the modem.img.tar in the AP slot then click start.
 

Zmantech

Senior Member
Aug 21, 2017
132
20
I suggest only flashing the modem. When you extract the copy of modem.img, convert it to an Odin flashable .tar file using 7zip with the highest level of compression. Then flash the modem.img.tar via Odin, place the modem.img.tar in the AP slot then click start.
This is what I get. I turned OEM unlock on

<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 97 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 

Droidriven

Senior Member
Jan 27, 2014
15,103
3
5,235
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
This is what I get. I turned OEM unlock on

<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 97 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What version of Odin are you using?

Do you have USB debugging enabled in the device's system settings?
 

Droidriven

Senior Member
Jan 27, 2014
15,103
3
5,235
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Try 3.12 or 3.13

Do you know if the binary version of the modem is equal to or higher than the binary version of your currently installed modem? To check, look at the firmware build number of your currently installed firmware, the 5th character from the right end of the build number is the binary version. Then look at the build number of the firmware that you extracted the modem from, look at the 5th character from the right, if this number is equal to or higher than the number from your current firmware then the error isnt caused by a binary conflict.
 
Last edited: