Develop Bugs

[FIX][UPDATE: 19.Jan.2011][110% SAFE] 3-Button Combo FiX for Selected/ALL Firmwares

Changelog:
19.01.2011
-NEW links added
-Heimdall Method is now better explained
02.01.2011
-Added Italian tutorial (written by Z4kW0lf)
18.12.2010
-Added Spanish tutorial (written by Vvaleta, Vinclar and Lorse of HTCmania, thanks guys !)
17.12.2010
-Updated Odin3 solution to use md5 checksum - will NOT hang at boot.bin (Windows, thanks to Lorse and Intronauta of HTCmania)
09.12.2010
-Added the latest bootloaders from Samsung, optimized for Froyo on Galaxy S
-Added the Android dumping method (BML1) for my original FiX
-Files inside RAZ_P-SBL_SGS.tar will be flashed using Heimdall (Windows & UNIX)
-Removed the EXPERIMENTAL x0 FiX (redbend_ua self-flash for x0 Firmwares).
28.10.2010
-Initial Release
Hello FiXed World 3.0 by RazvanG .. in dedication to my beloved grandmother, Camelia Petrescu (05.SEP.1934 – 03.DEC.2010) I will always love you.
(because information should be free for all):
YOU MAY NOT, BY ANY MEANS, USE THIS SOLUTION/CODE OR PART OF IT FOR COMMERCIAL PURPOSES.
DO NOT USE THIS METHOD COMMERCIALLY
YOU ARE NOT ALLOWED TO USE THIS METHOD IN YOUR FREE SOFTWARE WITHOUT PROPER CREDITS ADDED TO IT.
YOU SHOULD ALWAYS MENTION MY NAME AND MY PAYPAL ACCOUNT FOR DONATIONS IN YOUR SOFTWARE IF YOU CHOOSE TO USE THIS SBL FiX
PLEASE give credit (and donations if you can) to RazvanG for finding The Solution, writing this Tutorial and the Automated Script (PayPAL Donation)
For those of you that have donated THANKS!
01. Ghioane Gino Cristian; Romania
02. Jimmie Knutas; Sweden
03. Jose Mendoza; USA
04. Anonymous; Norway
05. Reschi85; Austria
06. Ekin Tekbiyik; Australia
07. Salman Daha; USA
08. Jamie Sidford; UK
09. Stefano Passerini; Italy
10. Fabio Verardo; Italy
11. Radu Marian Enache; Romania
12. Haanstra Sander; Netherlands
13. Rares Alin Benea Nadaban; Romania
14. Alex Curtis; UK
15. James Darley; UK
16. Boris Lulic; Croatia
17. Pietro Rossin; Italy
18. Jonathan Scarfo; Argentina
19. Karl Sever; Austria
20. Markus Kaldenbach; Ireland
21. Wong Ling Choo; Singapore
22.
23.
.. and a bigger THANKS to those who will donate in the future !!
//IF YOU ARE ON FROYO (ANDROID 2.2/2.2.1) OR ON ECLAIR (ANDROID 2.1) WITH A x0 FIRMWARE (OFNI x0) USE HEIMDALL METHOD OR ODIN3 (V1.7) METHOD TO REFLASH YOUR BOOTLOADERS
//UPDATE
//17.DEC.2010
//ALL FIRMWARES
Since Richthofen didn't update his Odin3 solution to use the LATEST bootloaders (03.dec.2010), there you have it.
If Samsung Drivers are properly installed for Download Mode, the flashing process is just as safe to do so with Odin3 as with Heimdall.
When the Galaxy S is connected to the PC in Download Mode, you have to see in Device Manager: USB Composite Device Samsung and Samsung Mobile Modem.
If you see this, is 100% safe to use Odin v1.3 or v1.7 to flash the bootloaders.
{
"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"
}
Preparations: Make sure you have the drivers installed (i.e Kies is recognizing the phone) and "USB Debugging" is turned on in "Settings -> Applications -> Development" menu. Type *#0228# in the dialer and check Voltage value (without USB plugged in) is atleast 3800(mV).
HEIMDALL METHOD:
01. Unplug the phone from the computer (if connected)
02. Kill all Kies related software (tray agent, etc)
// if you don't have Heimdall's Drivers installed, skip only step 3 for now, and follow the tutorial until you get to step 6, then (with the mobile still connected in Download Mode) run zadig.exe from Heimdall's Driver folder to install proper drivers. After that, continue the tutorial with step 7
03. Start Heimdall Downloader (Heimdall-frontend.exe)
04. Plug in the phone to the computer
05. Download adbDownload.zip
06. Unpack adbDownload.zip and run/double click on Download.bat
07. Download RAZ_P-SBL_SGS.tar
08. Unpack RAZ_P-SBL_SGS.tar
09. Move to Heimdall-Frontend.exe (GUI) and select boot.bin and SBL.bin.
10. Flash the bootloaders
You can get the latest Heimdall, here
Please read the instructions and README files included in the archives.
NOTE: You must have the Microsoft Visual C++ 2010 redistributables installed on your system for Heimdall to work.
ODIN3 METHOD:
1. Unplug the phone from the computer (if connected)
2. Kill all Kies related software (tray agent, etc)
3. Start Odin3 v1.3 or v1.7 Downloader
4. Plug in the phone to the computer
5. Download adbDownload.zip
6. Unpack adbDownload.zip and run/double click on Download.bat
7. Download PSbl_stockJPU.tar.md5
8. Move to Odin3 v1.3 or v1.7 Downloader and select "PSbl_stockJPU.tar.md5" as PDA file. Make sure "Phone Bootloader Update" is ticked and re-partition is unticked. Do not select any other files but "PSbl_stockJPU.tar.md5".
9. Press "Start" button to launch the update process. It will take around three seconds to complete. After the update phone will reboot automatically.
// Romanian Tutorial translated HERE
// Spanish Tutorial translated HERE
// Italian Tutorial translated HERE
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
Many Orange users and other Branded Galaxy S users bricked or semi-bricked their E-Fused or U3 Phones while applying various 3-Button Combo FiXes.
NOW here is a real PROPER solution ! 110% SAFE ! for Selected Firmwares. NO Odin3 required !
HOW-TO check if your mobile is compatible (Windows):
Step 1: Download the XVI32 Hex Editor
Step 2: Dump your BML1 block (rooted phone needed):
Step 2 Explained:
on ANDROID:
Install "Terminal Emulator" (Market download)
Run "Terminal Emulator" and type:
su (a superuser request will be displayed on the phone screen, accept it).
dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
or WINDOWS:
Open a new command prompt and type:
adb shell
su (a superuser request will be displayed on the phone screen, accept it).
dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
Step 3: Open the bml1.dump file with XVI32.
Step 4: Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below starting with Step 1.
If it reads "x0" then STOP as this FiX will BRICK your phone if applied !!
HOW-TO check if your mobile is compatible (UNIX):
on UNIX, any hexdump (or od / ghex /etc...) programs will show, for what you call a bad "x0" dump:
Code:
hexdump -C bml1.dump | grep OFNI
000053e0 4f 46 4e 49 1c 02 d7 30 44 02 d7 30 00 48 2d e9 |OFNI...0D..0.H-.|
and for the "safe" dump:
Code:
hexdump -C bml1.safedump | grep OFNI
000053e0 4f 46 4e 49 1c 82 21 40 44 82 21 40 00 48 2d e9 |[email protected][email protected]|
Other output format, with od:
Code:
od -c bml1.dump | grep "O.*F"
0051740 O F N I 034 002 327 0 D 002 327 0 \0 H - 351
od -c bml1.safedump | grep "O.*F"
0051740 O F N I 034 202 ! @ D 202 ! @ \0 H - 351
If it reads "x0" then STOP as this FiX will BRICK your phone if applied !!
Why is this different? How come it is 110% Safe for Selected/ALL Firmwares containing the [email protected] block?
Well .. it uses redbend to self-flash a proper SBL, compatible with the Primitive one found on Selected firmwares
I want to thank my sweet little girlfriend, Georgiana Coman , for making this possible by supporting the geek inside me :* and also for helping me re-pack and upload the needed files.
Also, I want to welcome baby Vlad, into this wonderful world ! (23.nov.2010)
Step 1: Download RAZ-FiX-SGS.zip
Step 1.1: Place the file to the root of the INTERNAL phone's memory and rename it to: Update.zip
Step 1.2: Make sure USB debugging is enabled (Settings->Applications->Development->USB Debugging)
Step 1.3: Connect the Phone to the PC
Step 2: Download adbRecovery.zip
Step 2.1: Unpack adbRecovery.zip
Step 2.2: Run Recovery.bat
//for the next step to work, you need to be on Recovery 2e (Android 2.1). It will NOT work on Froyo (Android 2.2, Recovery 3e)
//to get the proper recovery menu back, follow the guide found HERE (thank you, Reschi85)
Step 3: Select on the phone's menu: apply sdcard; update.zip and press the Home button.
After a few seconds, the phone should restart and the FiX will have been applied.
Now, just use the regular 3-Button Combo to enter Download Mode (Volume Down + H0me + Power) or Recovery !!
Enjoy .
Very special thanks go to..
Georgiana Coman , the girl behind the legend
Special thanks go to..
Richthofen for giving me a place to start in developing this method.
DukeForever for providing the "bad" BML1 Dump (Orange Fr)
Tyxerakias for providind the BML4 (Sbl.bin) Dump
Lorse for writing the automated x0 script and providing the info about proper driver installation.
Intronauta for re-packing the needed files for Odin3 flashing
Vvaleta and Vinclar of HTCmania for translating/writing the tutorial in Spanish
Reschi85 for writing the instructions on how to get Recovery 2e on Froyo
NicDumZ for the UNIX output
Z4kW0lf for translating/writing the tutorial in Italian
.. and a F*ck YOU goes to the Authorized Romanian Orange Care Center Service Team, especially Cristian I.
Please use my PayPal account for donations. Thank You.
Razvan Ghituleasa

e-fused ??
i got a bell
I9000UGJG9
will this work for me...
does the lag fix have to be removed?
and how about if it's rooted?

you are my new hero if this works I'v allready bricked my phone twice with the other solution.

tb5... said:
e-fused ??
i got a bell
I9000UGJG9
will this work for me...
does the lag fix have to be removed?
and how about if it's rooted?
Click to expand...
Click to collapse
Here is how to check if the PBL is good or not for SBL update:
Download the XVI32 Hex Editor
Dump your BML1 block (rooted phone needed):
Open a new command prompt and type:
1. adb shell
2. su (a superuser request will be displayed on the phone screen, accept it).
3. dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
Open the bml1.dump file with XVI32.

stinger32 said:
you are my new hero if this works I'v allready bricked my phone twice with the other solution.
Click to expand...
Click to collapse
.. just take a leap of faith and post the results

RazvanG said:
.. just take a leap of faith and post the results
Click to expand...
Click to collapse
Hehe I wonder what the service center will say if I show up for the third time and blame Kies again they must think I'm an complete fool. The service-center didnt manage to fix it the second time, they have sent it back to Samsung so I'm waiting for it right now.

At last, a real good working solution.
THANKS YOU.

Would it be possible to adapt this method to all Phones ?
Even non e-fused phones had some bricks while flashing bootloader with Odin.
I made the mistake to flash Kies update without checking first if it was "e-fused" or not and that's what might led me into trouble (tried to flash with Kies, regedit method, no way to tell now about "efused", it's not booting at all, power button not working, Download mode combo not working.)

great tool, worked flawless on my SGS, thank you RazvanG, the other methods seemed to complicated or risky for me so i decided to wait until something safe appears and here it is the safest method.
Great work, greatly appreciated!

aureusz said:
Would it be possible to adapt this method to all Phones ?
Even non e-fused phones had some bricks while flashing bootloader with Odin.
I made the mistake to flash Kies update without checking first if it was "e-fused" or not and that's what might led me into trouble (tried to flash with Kies, regedit method, no way to tell now about "efused", it's not booting at all, power button not working, Download mode combo not working.)
Click to expand...
Click to collapse
It *should* work on any firmware (even non e-fused).. if you want to take a leap of faith, be my guest and post the results.

Thank you man!
And do you know if there is a technical operation to unbrick those who bricked their "orange" phones using various 3-Button Combo FiXes?

Worked like a charm for me. Thanks a lot RazvanG
@aureusz
Try the method with 301K resistor (you can find it here: http://forum.xda-developers.com/showthread.php?t=819551 ).
It works, if you have working boot loader, but blocked 3 button combos (i've tested it).

cyberdamienb said:
Thank you man!
And do you know if there is a technical operation to unbrick those who bricked their "orange" phones using various 3-Button Combo FiXes?
Click to expand...
Click to collapse
You can force the firmware update into the phone using the JTAG port (on the PCB) or you can make a JIG Tool using a modified USB Cable (see this thread) and force the phone to enter Download Mode and then reflash using Kies or Odin3

So, what makes this safer than the original one?
It uses the same SBL as I did with the Redbend release.
The SBL is incompatible with some old PBL versions, so to make it safe it is required to update the PBL too.
This is the reason I use Odin to flash PBL & SBL.
So this is identical with my GT-I9000_SBL_RCVDL_FIX_REDBEND.7z (released 9/19/2010).
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.

Richthofen said:
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.
Click to expand...
Click to collapse
Yea right...

Richthofen said:
So, what makes this safer than the original one?
It uses the same SBL as I did with the Redbend release.
The SBL is incompatible with some old PBL versions, so to make it safe it is required to update the PBL too.
This is the reason I use Odin to flash PBL & SBL.
So this is identical with my GT-I9000_SBL_RCVDL_FIX_REDBEND.7z (released 9/19/2010).
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.
Click to expand...
Click to collapse
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that you provide, updates both the PBL and the SBL, and sometimes fails resulting a brick.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest (so called safer) method and had to send the phone back to Samsung for flashing. I only provided a fix for those who don't want to take that risk.
Thank you for providing at some point a SBL. It helped a lot

manosv said:
Yea right...
Click to expand...
Click to collapse
Can you elaborate a bit?

RazvanG said:
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that updates both the PBL and the SBL, sometimes fails and bricks the phone.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest method and had to send the phone back to Samsung. I only provided a fix for those who don't want to take that risk.
Thank you for providing a SBL in the first place. It helped a lot
Click to expand...
Click to collapse
True, but this version of the SBL has also been producing bricks with phones with E-Fused PBL´s. I don´t know why would it be different this time.

RazvanG said:
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that you provide, updates both the PBL and the SBL, and sometimes fails resulting a brick.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest (so called safer) method and had to send the phone back to Samsung for flashing. I only provided a fix for those who don't want to take that risk.
Thank you for providing at some point a SBL. It helped a lot
Click to expand...
Click to collapse
I am one of them

Richthofen said:
True, but this version of the SBL has also been producing bricks with phones with E-Fused PBL´s. I don´t know why would it be different this time.
Click to expand...
Click to collapse
I'll reconsider this FiX after someone using an eFused phone gets a brick following my tutorial, but for now .. 110% success rate
Thank you once again

[Q] How to flash baseband modem with Odin without rooting

Can anyone tell me if it's possible to flash/change/update just the baseband modem in my AT&T Samsung Galaxy S3 SGH-I747 without rooting the phone? After installing the latest update via the Samsung KIES software my phone reception has dropped a good bit. I no longer have service where I used to. My phone calls are also very choppy in the fringe reception areas, where before they were significantly better. I live in an area where 4G/3G coverage is fairly spotty, so EDGE is my primary network.
I wish I could remember which baseband version it had before the update so I could roll back to it, but I don't, so it may take a few tries before I can find the correct baseband version. Before the update I know I had ICS v4.0.4......not sure on Baseband version. Now I have Jelly Bean v4.1.1 (which I would like to keep) with Baseband I747UCDLK3.
I've tried using Odin v3.07 and the "AT&T Models Only! (I747U)" files via the link below and inserting the correct file path into the "Phone" section without any luck. Odin detects my phone, starts the process, but fails. http://forum.xda-developers.com/showthread.php?t=1831898
I've read to only use the "PDA" section in Odin to flash, but the files via the link below dont seem to have the proper file to use with the "PDA" seciton in Odin......am I missing something critical here maybe?
I then came across the following link where other people have used Odin to flash the baseband modem and seem to have been successful. http://forum.xda-developers.com/showthread.php?t=927568
Thanks for any help because I've spent hours searching the forum and Internet trying to find an answer!

I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.

I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!

SideWinder4x4 said:
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
Click to expand...
Click to collapse
i believe HON-HLOS.bin is your modem

SideWinder4x4 said:
and when I open or extract the files using 7zip,
Click to expand...
Click to collapse
Do not actually extract the files or else you will ruin the MD5 checksum and the flashing process will fail. Simply replace the modem file with the one you want to use by taking a "peek" in the actual TAR file.

Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.

mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
I've tried this method using Ubuntu Terminal to create a new modem.tar.md5 file, but everytime I try to flash with Odin, it fails. What am I doing wrong. Thanks for any further advice, this is driving me crazy!
My steps are as follows:
1.) I'm unzipping the correct modem files (modem_CWM_I747_UCLH9.zip) from this link - http://forum.xda-developers.com/showthread.php?t=1831898
2.) I'm taking the "modem.bin" file and copying it to Ubuntu desktop folder
3.) I'm opening Terminal
4.) I change to the Desktop directory
5.) First command...without the quotes is "tar -H ustar -c modem.bin > modem.tar"
6.) Second command...without the quotes is "md5sum -t modem.tar >> modem.tar"
7.) Third command...without the quotes is "mv modem.tar modem.tar.md5"
8.) I copy that "modem.tar.md5" file back to my Windows 7 based computer
9.) I rename "modem.tar.md5" to "modem.tar"
10.) I press and hold the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted press the "Volume Up" key
11.) On the screen I see the following: ODIN MODE, PRODUCT NAME: SGH-I747, CUSTOM BINARY DOWNLOAD: No, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, QUALCOMM SECUREBOOT: ENABLE
12.) I then open Odin v3.07 using defaults
13.) Odin recognizes my phone on COM8 with a blue teal colored box
14.) I press the "Phone" button and select the "modem.tar" file
15.) I press the "Start" button and it shows "modem.bin" in the first box in white, but about 5 seconds later it turns red and says FAIL!
The Odin message box indicates the following:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> modem.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

Well, try naming it NON-HLOS.bin instead of modem.bin. Also, don't rename it after you make the tar.md5 file.

Solution Found
I finally got this figured out. Thanks for all of the help and ideas along the way!
The key tip was found in this thread - http://forum.xda-developers.com/showthread.php?t=1658809
Just to simplify things for others in the future, the steps I performed were as follows:
1.) Installed Cygwin from http://www.cygwin.com/
2.) Started Cygwin Terminal
3.) Put the SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 firmware file into the following folder I created "c:\baseband"
4.) In Cygwin, typed the following command without the quotes "cd /cygdrive/c/baseband"
5.) In Cygwin, typed the following command without the quotes "tar -xvf SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 NON-HLOS.bin"
6.) In Cygwin, typed the following command without the quotes "tar -H ustar -c NON-HLOS.bin > baseband.tar"
7.) Pressed and held the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted pressed the "Volume Up" key to enter "Download Mode"
8.) I then opened Odin v3.07 using defaults
9.) Connected my phone to my computer using the proper USB cable
10.) Odin recognizes my phone on COM8
11.) I pressed the "Phone" button and selected the "baseband.tar" file I created in step #6
12.) I pressed the "Start" button and about 30 seconds later it finishes and the box turns green and the phone rebooted.

Thanks Sidewinder. Its very informative.. I am facing a strange issue on my Galaxy R ever since I upgraded to ICS and JB (stock/ custom ROMs).
Very often I get my calls disconnected while speaking. This was not the case with Ginger bread..
Today followed your procedure to extract the modem.bin from stock GB rom and flashed to my JB custom ROM (Carbon).. Looks good so far..tried
with test calls - seems to be OK.. Will observe for some more time.

You're Welcome asbalaji. I'm glad what I posted helped you out. My phone reception issues improved a lot after downgrading to an older modem.

Anonymously_Unknown said:
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
Click to expand...
Click to collapse
I am in desperate need of a baseband to flash via ODIN for a boostmobile galaxy S3
---------- Post added at 07:00 AM ---------- Previous post was at 06:24 AM ----------
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
Basebadn boostmobile s3

[Q] Issues installing 4.2.2 Update with Odin

Hello,
I've just acquired a GT-5120 and am trying to install the 4.2.2 update using Odin.
I downloaded the update zip for my device (1.4GB), unzipped it to see a .tar.md5 file. Opened up Odin, checked PDA, selected the .tar.md5 file. Pressed start and got a failed message.
Here's the log
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I thought there was an issue with my connection / Odin, but I was able to successfully flash a custom recovery and root the device.
Any pointers to get the flashing working?
Thanks!

Somethings to check
1) What is the version of the ODIN you used? I suggest Odin3 3.07.
2) When you try to flash, did the ODIN complete md5 check of the file you added to PDA? (Because it's note in the log you provided or it's different).
3) From where did you download the .tar.md5? "www.Sammobile.com/firmwares" is the best.
4) Did you rename the .tar.md5 file, probably a silly question, but sometimes funny things happen.

AkiOrpheus said:
1) What is the version of the ODIN you used? I suggest Odin3 3.07.
2) When you try to flash, did the ODIN complete md5 check of the file you added to PDA? (Because it's note in the log you provided or it's different).
3) From where did you download the .tar.md5? "www.Sammobile.com/firmwares" is the best.
4) Did you rename the .tar.md5 file, probably a silly question, but sometimes funny things happen.
Click to expand...
Click to collapse
Thanks for the reply, Aki!
I'm using Odin 3.07
The log may have not reflected it since I've tried removing the .md5 extension and flashing with just the tar (same extension as the recovery that successfully flashed). After selecting the file, it takes a few minutes before I'm able to do anything (md5 check?).
I downloaded the file from a thread in this forum with a bunch of mirrors. I'll check out sammobile and report back after testing the file downloaded from there.
I tried leaving the .tar.md5 and renaming it to just .tar (since I successfully flashed a .tar file).
Thanks for the help!
AGH Disregard
I was trying to flash an 5120 ROM on my I467M :crying:

danada said:
Thanks for the reply, Aki!
I'm using Odin 3.07
The log may have not reflected it since I've tried removing the .md5 extension and flashing with just the tar (same extension as the recovery that successfully flashed). After selecting the file, it takes a few minutes before I'm able to do anything (md5 check?).
I downloaded the file from a thread in this forum with a bunch of mirrors. I'll check out sammobile and report back after testing the file downloaded from there.
I tried leaving the .tar.md5 and renaming it to just .tar (since I successfully flashed a .tar file).
Thanks for the help!
AGH Disregard
I was trying to flash an 5120 ROM on my I467M :crying:
Click to expand...
Click to collapse
I think u should be glad that u didn't sucsess
coz I think success will be a bricked phone

Custom Binary Blocked by FRP Lock - How I Fixed It Without Data Loss

YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.

"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.

koop1955 said:
"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.
Click to expand...
Click to collapse
He's crazy if you ask me
Sent from my SM-G920P using Tapatalk

I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it

fentezi said:
I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it
Click to expand...
Click to collapse
First off, you should probably post in the correct forum.
Secondly, did you try flashing the firmware for your phone: https://www.sammobile.com/firmwares/galaxy-j1/SM-J120F/

I fixed it
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it:laugh:

My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.

THANK YOU
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!

killroot said:
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!
Click to expand...
Click to collapse
Hey! Glad it helped. I was really active back in the HTC Hero days and around 2013 I slowed down. I like to keep my phones rooted but i getting more and more worried about manufacturer warranty being denied over being rooted... Fortunately I was able to iron this whole thing out with some meticulous research and some help from awesome people here, and it's still satisfying knowing I've helped at least one person who appreciated it enough to say thanks!
Sent from my SM-N920P using Tapatalk

finalc said:
My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.
Click to expand...
Click to collapse
Sorry, not sure what the g928p is and unfortunately I can't help with your issue. I just wrote what I did to fix this issue and if you're still having problems I recommend doing some very in depth research to make sure you didn't miss some tiny but crucial step.
Sent from my SM-N920P using Tapatalk

fentezi said:
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it[emoji23]
Click to expand...
Click to collapse
That's what the instructions said to do [emoji6]
Glad it worked.
Sent from my SM-N920P using Tapatalk

Same issue on my Samsung A%
The file is not there anymore bro. Where do i get the file for my device please(Samsung A5) ? i found a way to solve this using kies 3 and wiping the phone. But u did it without data loss? amazing ! glad if you can help. thanks!
jerry43812 said:
YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.
Click to expand...
Click to collapse

i just had the same problem on my mothers phone and your method worked perfectly thank you so much i didnt want to do a stock flash and have her loose everything so thanks for your knowledgeable and easy to follow post

Hello @jerry43812 and @koop1955 that file has been deleted from android file host, would any of you please care to upload it again? Thanks very much. I have a Samsung Galaxy Note 5 btw, I think it works right?

I dont even remember making this thread, I definitely dont have the file you're looking for. Maybe koop can help.Sorry!

@koop1955 I don't have knowledge about any of the android OS. But I have an issue and it still is an issue from 2016 to 2022. I have an android phone launched in 2016. I rooted it using SuperSU binary. By turning ON all the necessary features required for making custom recovery (TWRP) installed and installing SuperSU binary as well.
Therefore my developer options were turned ON and OEM unlocking was ON aswell. My phone name was Samsung J2 2016 (SM-J210F). I by mistake disabled OEM unlocking switch. And restarted the phone and it never
rebooted after that.
I need the data it is very precious to me. I don't need root privileges back or anything like that.
I just need the data and state of operating system the way it was before restarting.
Please help me @koop1955.
I will be very thankful to you.

I have no idea. Good luck.

[Help?] Bootloop on flash official firmware (SM-G9600)

I got my new SM-G9600/DS in the mail today and it had the G9600ZCU1ARBG firmware on it (Updato). I wanted to check out the Hong Kong firmware, so I fired up Odin 3.13, set the phone to download mode, and tried to flash it with the AP, BL, CP, and CSC (not HOME_CSC, I wanted a clean wipe) files from the G9600TGY2ARE6 firmware (Updato), but that failed; it hung on "SetupConnection..." for a few minutes and then gave a "Complete(Write) operation failed."
After that, I tried the same flash but without the CP, and it seemed to work: it rebooted a few times, then went to the welcome screen (in Chinese). However, it was very unstable, and SystemUI crashed several times while I tried to set it to English. Even after a reboot, it was still unstable like that, so I decided to reflash again (maybe the flash was slightly corrupt?). This time I enabled the "Re-Partition" option in Odin, hoping it would overwrite everything and make it clean again, but without any other changes (BL, AP, and CSC). However, this time it failed, hanging on "SetupConnection..." like the first time I tried to flash it. Since then I've tried just about every combination of firmware files (BL and AP, BL and CSC, AP and CSC, etc) but all of them fail to establish a working connection.
I'm currently downloading the G9600ZCU2ARE6 firmware (Updato) which is the most recent firmware actually for my device. I will try flashing that when it's done (hopefully in the next 30-60 mins), but if that fails I'm at a loss. What should I do?

Update: I tried entering recovery mode (holding power + volume up + bixby), but it crashed as soon as it passed the blue android screen; I think I saw a screen flash by quickly that said something like "connection failed"? When I rebooted it and failed a few more flashes, I tried to boot up normally and got most of the way to the welcome screen, but it also crashed, so I rebooted into recovery mode again, and this time it worked! I wiped the cache partition and did a factory reset, but that didn't seem to work. Now it bootloops to the beginning of the welcome screen (the white nav bar with a back arrow appears at the bottom of the screen, but the SystemUI crashes [I think; all the error messages are in Chinese]).
EDIT: I finished downloading the G9600ZCU2ARE6 (CHO with v2 bootloader) firmware and tried to flash all four (BL, AP, CP, and CSC; not HOME_CSC) files and re-partition, and the log quickly spat out the following, then stopped (because it failed).
Odin3 v3.13 said:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6643 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Thoughts? I'm currently trying it without the re-partition option enabled, but I suspect it won't work because it's been hanging on "SetupConnection..." for a long time, it usually passes that quickly if it's going to succeed. If this fails, I'll try the same two tests but omitting the CP file.
EDIT2: It didn't work when omitting the CP file. What should I do next? I'm currently downloading the original firmware that came with the device (G9600ZCU1ARBG linked in OP) and will try that when this it finishes downloading, but that may be a task for tomorrow.

Update 2: I managed to wait out all the crashes and get the phone "set up", past the welcome screen. It still bootloops, but I get about a minute or two of use before it reboots itself. I managed to get this photo of the software information screen before it crashed:
{
"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"
}
Interestingly, the "Baseband version" is only 1ARBG, while the "Build number" is 2ARE6. I suspect this is the source of the instability? In order to fix this, I tried to flash it with the original firmware (all four files of the 1ARBG stuff, the same it was supposed to come with), but I got the following failure in Odin:
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 6556 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone itself gave me this info:
That last line, where it says "Fused 2 > Binary 1" makes me think that I've upgraded enough things to v2 that it won't let me downgrade everything to the stock v1 that it came with.
What should I do now? Maybe try to get it to do a factory reset?
...Or am I missing something obvious in the flashing process that would make it work?
EDIT: I did a factory reset, not sure if it did anything useful. It still reboots itself after 1-2 minutes of usage. I managed to connect it to my wifi, but it doesn't seem to do anything when I tell it to check for a software update. I'm pretty lost. Any suggestions? Is there a way I can at least get it back to stock Samsung?

Flashing between different CSCs for the same device model usually doesn't cause problems, the problem is likely from the bootloader
You'll probably need to flash back to the entire Hong Kong firmware with the Version 2 Bootloader until your own firmware updates to version 2 also, not sure of any way to downgrade bootloaders if Odin won't do it, factory reset after flash should fix the crashing if it is just system apps crashing
You could try enabling OEM Unlock from developer options first which unlocks the bootloader (if you have that option, might have 7 days since last flash to wait for it to appear though)
Setup connection errors is an error between phone and PC, you cannot break Download mode by flashing firmwares, so that is not the problem, more likely drivers, USB cable, PC itself / Windows / PC USB port
Try another machine / port on the PC, or remove drivers from device manager while phone is connected, then disconnect and connect it again to reinstall them

*Detection* said:
Factory reset after flash should fix the crashing if it is just system apps crashing
Setup connection errors is an error between phone and PC, you cannot break Download mode by flashing firmwares, so that is not the problem, more likely drivers, USB cable, PC itself / Windows / PC USB port
Try another machine / port on the PC, or remove drivers from device manager while phone is connected, then disconnect and connect it again to reinstall them
Click to expand...
Click to collapse
I'll try the factory reset today, not sure it can complete before the device reboots though. Or should I do it from recovery mode?
I'll also try flashing it again and make sure I have the right drivers installed. Something I noticed before was that windows installed drivers for "Galaxy S9" (or maybe "Samsung S9"? don't exactly remember) when the phone was on, but "SM845" when I connect it in Download mode. Could that be the issue?
*Detection* said:
You could try enabling OEM Unlock from developer options first which unlocks the bootloader (if you have that option, might have 7 days since last flash to wait for it to appear though)
Click to expand...
Click to collapse
Will that trip Knox?

nelsyv said:
I'll try the factory reset today, not sure it can complete before the device reboots though. Or should I do it from recovery mode?
I'll also try flashing it again and make sure I have the right drivers installed. Something I noticed before was that windows installed drivers for "Galaxy S9" (or maybe "Samsung S9"? don't exactly remember) when the phone was on, but "SM845" when I connect it in Download mode. Could that be the issue?
Will that trip Knox?
Click to expand...
Click to collapse
Drivers will auto install the correct ones
Recovery factory reset yes
No it won't trip KNOX

Success! I managed to get it to flash all 4 firmware files (BL, AP, CP, and CSC) for CHO! (G9600OWO2ARE6 Updato)
The only things I did differently were: I let the phone reboot a few times to take a look at things (took about 2 minutes to get to lock screen, and about 1..5 to 3 minutes after that before it would reboot), and I ran ODIN as my normal user account on Windows (not as administrator). Maybe running it as administrator (as I did yesterday) messed up the USB drivers somehow...?
Software information after reflash, reboot, and setup:
The baseband, build number, and service provider SW all match the CHO files, so everything seems to have flashed successfully! :victory:
However, I downloaded Samsung Pay from the Play Store and when I try to open the app it gives an error popup: "Unable to connect to Samsung Pay temporarily. Try again later."
What should I do? I have yet to add a Samsung Account or insert a SIM card. Would one of those be helpful? Or should I reflash with a different CSC?

I downloaded the "Phone INFO Samsung" app and checked the CSC page. The app is listing the phone as from Trinidad/Tobago...
Honestly I have no idea how that happened lol. What's the best way to change it to something that will support Samsung Pay? Can I flash the US unlocked (U1 I think) (just the HOME_CSC, even?) without reflashing the other parts? Or should I completely reflash to factory from a different region?

That firmware has a version 2 bootloader too which will be why it flashed OK
Samsung pay probably requires a samsung account attached to the device, set it up normally as a new phone
EDIT - Was your device 2nd hand? Or originally on TTT CSC?
If the CSC you flash is Multi and includes the original CSC, it will default to the original CSC of the phone

*Detection* said:
That firmware has a version 2 bootloader too which will be why it flashed OK
Samsung pay probably requires a samsung account attached to the device, set it up normally as a new phone
EDIT - Was your device 2nd hand? Or originally on TTT CSC?
If the CSC you flash is Multi and includes the original CSC, it will default to the original CSC of the phone
Click to expand...
Click to collapse
I set up a Samsung account and it didn't help, even after restart, even after restart with USA AT&T SIM card inserted.
I'm pretty sure the device was brand new when I got it. I believe the original CSC was UNE? I'm not sure--the device was originally in Spanish (and was packaged with the Spanish quick-start guide) and I remember it being a Mexican CSC, but unfortunately it seems I forgot to write it down specifically.
I'm not sure I really understand how Multi-CSC works. Do you know of a good resource that explains it?

nelsyv said:
I set up a Samsung account and it didn't help, even after restart, even after restart with USA AT&T SIM card inserted.
I'm pretty sure the device was brand new when I got it. I believe the original CSC was UNE? I'm not sure--the device was originally in Spanish (and was packaged with the Spanish quick-start guide) and I remember it being a Mexican CSC, but unfortunately it seems I forgot to write it down specifically.
I'm not sure I really understand how Multi-CSC works. Do you know of a good resource that explains it?
Click to expand...
Click to collapse
Not sure of any CSC info resources, googling is your best bet, my best explanation:
Multi-CSC is basically just a pack of CSCs which the device can use any of the CSCs included, imagine a driver pack for windows, you tell the device that needs the driver to search the pack and choose the driver it wants to use, it picks and installs the one that best matches that device and the rest remain in the pack unused
BTU is Multi-CSC, it contains about 10 different CSCs, if your phone was originally shipped with one of the included CSCs, when you flash BTU it will not switch to BTU it will find and switch to the devices original CSC
If the devices CSC is not included, it will switch to BTU
This causes a problem when trying to switch from say XEU to BTU as XEU is included in BTU's Multi-CSC
Single CSC only contains one CSC, so the device is forced to switch to that as there are no other choices
There used to be a trick of switching to a single CSC not included in the Multi you are trying to flash, then flashing the Multi and it would change, but seems that doesn't work now
Reason I'm asking about new or 2nd hand is it is possible it was already flashed to a different CSC when you bought it, so by not knowing it was originally TTT, flashing a Multi that included TTT would revert it back to TTT

*Detection* said:
Not sure of any CSC info resources, googling is your best bet, my best explanation:
Multi-CSC is basically just a pack of CSCs which the device can use any of the CSCs included, imagine a driver pack for windows, you tell the device that needs the driver to search the pack and choose the driver it wants to use, it picks and installs the one that best matches that device and the rest remain in the pack unused
BTU is Multi-CSC, it contains about 10 different CSCs, if your phone was originally shipped with one of the included CSCs, when you flash BTU it will not switch to BTU it will find and switch to the devices original CSC
If the devices CSC is not included, it will switch to BTU
This causes a problem when trying to switch from say XEU to BTU as XEU is included in BTU's Multi-CSC
Single CSC only contains one CSC, so the device is forced to switch to that as there are no other choices
There used to be a trick of switching to a single CSC not included in the Multi you are trying to flash, then flashing the Multi and it would change, but seems that doesn't work now
Reason I'm asking about new or 2nd hand is it is possible it was already flashed to a different CSC when you bought it, so by not knowing it was originally TTT, flashing a Multi that included TTT would revert it back to TTT
Click to expand...
Click to collapse
That's a good explanation of it, thank you. :good:
Should I try to flash with the MXO (Mexico unlocked) AP/BL/CP and use the (single) CSC from the (USA unlocked) U1? Or would that brick things?
EDIT: It seems there isn't a v2 firmware for the U1 yet. Should I try using a CSC from a U variant? Which one? I don't see anything for AT&T on Updato, just "CCT", "TMK, and "USC", should I use one of those?

nelsyv said:
That's a good explanation of it, thank you. :good:
Should I try to flash with the MXO (Mexico unlocked) AP/BL/CP and use the (single) CSC from the (USA unlocked) U1? Or would that brick things?
EDIT: It seems there isn't a v2 firmware for the U1 yet. Should I try using a CSC from a U variant? Which one? I don't see anything for AT&T on Updato, just "CCT", "TMK, and "USC", should I use one of those?
Click to expand...
Click to collapse
Personally I wouldn't mix and match CSC's with the wrong firmware but it's up to you, not sure of the consequences as I've never tried it or seen anyone else do it yet

*Detection* said:
Personally I wouldn't mix and match CSC's with the wrong firmware but it's up to you, not sure of the consequences as I've never tried it or seen anyone else do it yet
Click to expand...
Click to collapse
I'm going to attempt with the XAC (unlocked Canada, correct?) firmware's CSC—the XAA firmware hasn't updated to the v2 bootloader yet. Updato is pretty slow rn so it will be a few hours before that finishes downloading. I suspect I'll have to use Raymonf's modified Odin from the guide to flashing U1 firmware to U devices, but I'll try it with stock Odin first to see what happens.
I figure that even if this bricks, I can't break Download Mode, so I can always flash back to stock G9600, correct?

I just tried flashing the XAC CSC (2ARE6) with the MXO BL/AP/CP (2ARC6).
With stock Odin, it threw an error, saying "SECURE_CHECK_FAIL : PIT" in red text on the Download Mode screen, and Odin's log:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6777 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
With Raymonf's modded Odin, the Download Mode screen gave the same redtext error, and Odin's log gave me the following:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6777 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I suspect this is because the MXO firmware is based on the 2ARC6 bootloader, while the XAC firmware is based on the (slightly newer?) 2ARE6 bootloader, so the partition tables don't quite match up. Thoughts?
Next steps: I'll try the CHO Chile (2ARE6) BL/AP/CP with XAC (2ARE6) CSC. Might get further, since it's the same 2ARE6. I might also try the TGY Hong Kong (2ARE6) BL/AP/CP in similar fashion.

nelsyv said:
[...]
I suspect this is because the MXO firmware is based on the 2ARC6 bootloader, while the XAC firmware is based on the (slightly newer?) 2ARE6 bootloader, so the partition tables don't quite match up. Thoughts?
Next steps: I'll try the CHO Chile (2ARE6) BL/AP/CP with XAC (2ARE6) CSC. Might get further, since it's the same 2ARE6. I might also try the TGY Hong Kong (2ARE6) BL/AP/CP in similar fashion.
Click to expand...
Click to collapse
None of the mixed firmware flashes (BL/AP/CP from CHO or TGY, CSC from XAC) worked, all threw the same errors in Odin (stock and modified both failed) that the MXO/XAC flashes did. It might be possible if I knew more about how the files were structured and could modify the XAC CSC so its PIT would match the others, but I'm not totally sure how these work under-the-hood; I'll leave that to the more serious developers
Now I'm flashing the TGY (Hong Kong) firmware (all four parts). I'm going to put my AT&T SIM into it, factory reset, and see if it changes the CSC. I'll also check the VoLTE menu that @sentron was asking me for in another thread.

Flashing the TGY firmware did change the CSC! Here's some screenshots from the Software Information page.
I also tried sideloading an older version of Samsung Pay, as described in the following quote (for S7 Edge, but I thought it worth a shot).
spielnicht said:
I also have XSG variant . The only way is to downgrade back down to the previous version of the Samsung Pay Framework, but that's not going to happen. Your only option is to factory reset and start from scratch, making sure that you install the previous version of both APKs. That's what I just finished doing. Samsung Pay will force you to update to the latest app before you can use the app (modal keeps popping up). I did that, but kept the older version of the Framework (2.2.03).
To Recap (what I did):
Factory Data Reset
Installed Samsung Pay version 2.0.32
Installed Samsung Pay Framework 2.2.03
Updated to Samsung Pay version 2.1.04 (forced into update via app)
Follow the above and don't update the Framework and you should be good to go.
Click to expand...
Click to collapse
Unfortunately, Samsung bundles a recent version of the Samsung Pay Framework into the HK firmware, so it won't let me install either of those old versions. However, since I'm on the TGY CSC, when I first opened up Samsung Pay (downloaded from Google Play Store, I checked the box for it when I did the first-time device setup), it gives a popup that prompts me to download "Samsung Pay (Hong Kong)", which I agreed to. This installed the Hong Kong version of Samsung Pay, which works! However, it's pretty crippled for American users: it only supports the banks/cards supported by Hong Kong Samsung Pay (honestly this really should be the same app worldwide, Samsung smh ). Here's the chart they post on their support site, listing the supported banks/cards:
Any ideas on how I can try to get either the USA Samsung Pay app, or load an American Card into the Hong Kong system? If I were to open a new account at, e.g., Citibank, would that account need to have a Hong Kong address to use it with this version of the app?

Update: I just tried to add some American credit/debit cards and... they just worked! :victory::victory::victory:
Even though they're definitely not on the Hong Kong list I posted above, it still accepted them. I'll go shopping later and see if payment actually works, but it says that they're activated and ready to go (well, one of them; the other has to be verified by the bank and they said it would happen "within 1 business day"). Maybe the app is more international than it appears... Although the ads are still in Chinese lol.

I went shopping today and paid with a US credit card (a Visa rewards card from a US airline) and it worked without a hitch.
Also, I found a little toggle in my notification tray for VoLTE, and here's what happened when I tapped it:
However, I've noticed my device getting pretty warm, even hot, during normal use while charging. Is this normal? CPU-Z says the "ac" temp is at about 44 C, "battery" temp at about 39 C.

Thanks @nelsyv for reporting back. I'm thinking about flashing the T-Mobile US CSC on top of the OWO ARE6 that I have on my G9600. I'll read up a bit first. The T-Mobile US phone is SnapDragon (Single SIM), so the CSC should be compatible, right? Though I didn't find it stated exactly, it seems like any CSC should work on firmware? Is this correct?