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

[GUIDE]: How to flash CRB7 using Odin - S8+

Search This thread

MeltdownSpectre

Retired Forum Moderator
Jan 12, 2013
2,950
2,544
Sony Xperia 1
Samsung Galaxy Note 10+
UPDATE (27TH FEB 2018): We now have Odin v3.13.1 which is compatible with the new .lz4 compressed files referred to below in the tutorial. All the steps below are only required now if you are using a version of Odin older than 3.13.1. It is recommended that you use this new version to save yourself the hassle.

Odin v3.13.1 - XDA Link

S8+ G955F / G955FD (F ROMs work on the FD variants, there are no FD specific ROMs):

Mirror Link 1 (Google Drive) - Thanks @cretu01
Mirror Link 2 (Android File Host) - Thanks @panchuckles
Mirror Link 3
(OneDrive) - Thanks @Brotuck

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

Let me start of by saying, Samsung changed some things around with Oreo. I downloaded 'XXU1CRAP' using SamFirm today, tried with both TUR and DBT CSCs, to make sure it wasn't a bad download or anything, but Odin just wouldn't accept the file. It froze on the first step, sboot.bin.lz4.

I had never seen the .lz4 extension before, so I asked a couple of helpful lads in the Samsung Oreo Telegram group who were very helpful throughout this process.
For those of you who want to join:
http://t.me/sammyoreoclub

Samsung is using a new compression method for the Oreo ROMs, so all files within BL, AP, CP and CSC have the .lz4 extension which Odin has trouble reading, and so the flash will never go past the first step.

Note: THIS DOESN'T TRIP KNOX.

Pre-requisites:
-SamFirm to get the CRAP ROM - https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
-Windows PC
-This modded version of 7Zip which can open .lz4 files. Link - Github
-The ability to read the instructions below.
-Prince Comsy's modified Odin - Google Drive Link
-A Galaxy S8/S8+ (G950F / G950FD / G955F / G955FD) - I tested this on my own G955FD and it worked just fine.
-The XXU1CRB7 Oreo ROM for your device
-A decent amount of storage space on your PC
-Preferably some experience with flashing using Odin

DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
IF YOUR INTERNAL STORAGE SHOWS AS '16 GB' AFTER FLASHING, DO A FACTORY RESET AND IT'LL RETURN TO NORMAL.


Steps below:

1. Extract the zip file for the 3.7 GB firmware file you just downloaded. Should contain 5 files, AP, BL, CP, CSC_OXM and HOME_CSC_OXM.
In the tutorial below, I will be using CSC_OXM, however that does wipe internal storage.
If you are coming from ZRA5 or just don't want to wipe your data, use HOME_CSC_OXM instead.

2. All the files will have ".tar.md5" extensions. Remove the .md5 part so they can be opened in either WinRAR or 7Zip.
AP will contain a folder called 'meta-data', userdata.img.lz4, system.img.lz4, recovery.img, boot.img.lz4
Extract all these files from AP into a new folder. Right click on each one, select the '7Zip Standard' menu and hit 'Extract Here'.
This will extract all the files within, without .lz4 extensions. So you'll have userdata, system, recovery and boot as plain IMG files.
Note: Repeat this for CP, BL and CSC_OXM.


3. Grab the original file names for the files you extracted earlier, copy paste them into notepad.
They should be in this format, make sure .md5 isn't added at the end of any filenames. Do keep in mind that the filenames for the S8 (G950F) will obviously be slightly different.

Code:
AP_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship_meta.tar
BL_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
CP_G955FXXU1CRAP_CP8821296_CL12993656_QB16754780_REV00_user_low_ship.tar
CSC_OXM_G955FOXM1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar

4. Select all the files you extracted for AP (including the meta-data folder), right click, scroll down to the '7Zip Standard' menu again and this time hit 'Add to Archive'. Copy-paste the filename for whichever file you're creating an archive for, AP, BL, CP or CSC, make sure archive format is set to .tar and leave everything else default and hit 'OK' at the bottom of the window.
Note: This too will be have to be done for CP, CSC and BL as well.

5. Once this is done, you should have 4 .tar files ready to be flashed. Open up Prince Comsy's Odin, add each file to it's respective field in Odin.

6. Connect your device in Download Mode, press Start, and wait for the flash to be completed and for Odin to show 'PASS' at the top of the window.
Your device will reboot automatically.

ALTERNATIVELY, you can watch this very crappy screen recording I made for a better idea on how to do it.

YouTube link: https://youtu.be/eyIh3_p8WBQ


Credits go to:

@FatalONEM8 and @me2151 for helping out.
Tino Reichardt (mcmilk) for the modified 7Zip
Prince Comsy for the modified Odin.
Samsung for making flashing more and more difficult every year.

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

For Linux/Ubuntu, @kernel.killer has created a script to unpack the .lz4 compressed firmwares without having to do all of the above manually.
See this post - Link
 
Last edited:

jidamo

Senior Member
Oct 21, 2013
152
38
Safi
Very useful, thank you. I still hesitated to flash, but now I'm going to start.
Thanks again.
 

renton82

Senior Member
Jan 6, 2011
459
46
When i tried to update with the 4 file, Odin read them without any problem, but when i press start, phone just reboot. Maybe it is just because i was trying to flash the same version of firmware (CRAP over CRAP)? Maybe i'll have the error reported if just started to flash... but my question is: is it possible to overwrite the firmware with the same version using Odin?
 

MeltdownSpectre

Retired Forum Moderator
Jan 12, 2013
2,950
2,544
Sony Xperia 1
Samsung Galaxy Note 10+
When i tried to update with the 4 file, Odin read them without any problem, but when i press start, phone just reboot. Maybe it is just because i was trying to flash the same version of firmware (CRAP over CRAP)? Maybe i'll have the error reported if just started to flash... but my question is: is it possible to overwrite the firmware with the same version using Odin?

Yeah that did happen with me.

If you use HOME_CSC and flash CRAP over CRAP, nothing happens.

You can overwrite if you use CSC_OXM.

Sent from my ONEPLUS A5000
 

MohamedYousri

Senior Member
Apr 6, 2006
866
163
Cairo
Worked like a charm , Much appreciated

<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cm.bin
<ID:0/004> param.bin
<ID:0/004> sboot.bin
<ID:0/004> up_param.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> userdata.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem_debug.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> omr.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

1.png
 
  • Like
Reactions: jidamo

nelfurdui85

New member
Sep 9, 2016
4
0
London
Done everything.

I got this on odin:

<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..


And nothing happens.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 54
    UPDATE (27TH FEB 2018): We now have Odin v3.13.1 which is compatible with the new .lz4 compressed files referred to below in the tutorial. All the steps below are only required now if you are using a version of Odin older than 3.13.1. It is recommended that you use this new version to save yourself the hassle.

    Odin v3.13.1 - XDA Link

    S8+ G955F / G955FD (F ROMs work on the FD variants, there are no FD specific ROMs):

    Mirror Link 1 (Google Drive) - Thanks @cretu01
    Mirror Link 2 (Android File Host) - Thanks @panchuckles
    Mirror Link 3
    (OneDrive) - Thanks @Brotuck

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

    Let me start of by saying, Samsung changed some things around with Oreo. I downloaded 'XXU1CRAP' using SamFirm today, tried with both TUR and DBT CSCs, to make sure it wasn't a bad download or anything, but Odin just wouldn't accept the file. It froze on the first step, sboot.bin.lz4.

    I had never seen the .lz4 extension before, so I asked a couple of helpful lads in the Samsung Oreo Telegram group who were very helpful throughout this process.
    For those of you who want to join:
    http://t.me/sammyoreoclub

    Samsung is using a new compression method for the Oreo ROMs, so all files within BL, AP, CP and CSC have the .lz4 extension which Odin has trouble reading, and so the flash will never go past the first step.

    Note: THIS DOESN'T TRIP KNOX.

    Pre-requisites:
    -SamFirm to get the CRAP ROM - https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
    -Windows PC
    -This modded version of 7Zip which can open .lz4 files. Link - Github
    -The ability to read the instructions below.
    -Prince Comsy's modified Odin - Google Drive Link
    -A Galaxy S8/S8+ (G950F / G950FD / G955F / G955FD) - I tested this on my own G955FD and it worked just fine.
    -The XXU1CRB7 Oreo ROM for your device
    -A decent amount of storage space on your PC
    -Preferably some experience with flashing using Odin

    DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
    INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
    IF YOUR INTERNAL STORAGE SHOWS AS '16 GB' AFTER FLASHING, DO A FACTORY RESET AND IT'LL RETURN TO NORMAL.


    Steps below:

    1. Extract the zip file for the 3.7 GB firmware file you just downloaded. Should contain 5 files, AP, BL, CP, CSC_OXM and HOME_CSC_OXM.
    In the tutorial below, I will be using CSC_OXM, however that does wipe internal storage.
    If you are coming from ZRA5 or just don't want to wipe your data, use HOME_CSC_OXM instead.

    2. All the files will have ".tar.md5" extensions. Remove the .md5 part so they can be opened in either WinRAR or 7Zip.
    AP will contain a folder called 'meta-data', userdata.img.lz4, system.img.lz4, recovery.img, boot.img.lz4
    Extract all these files from AP into a new folder. Right click on each one, select the '7Zip Standard' menu and hit 'Extract Here'.
    This will extract all the files within, without .lz4 extensions. So you'll have userdata, system, recovery and boot as plain IMG files.
    Note: Repeat this for CP, BL and CSC_OXM.


    3. Grab the original file names for the files you extracted earlier, copy paste them into notepad.
    They should be in this format, make sure .md5 isn't added at the end of any filenames. Do keep in mind that the filenames for the S8 (G950F) will obviously be slightly different.

    Code:
    AP_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship_meta.tar
    BL_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
    CP_G955FXXU1CRAP_CP8821296_CL12993656_QB16754780_REV00_user_low_ship.tar
    CSC_OXM_G955FOXM1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar

    4. Select all the files you extracted for AP (including the meta-data folder), right click, scroll down to the '7Zip Standard' menu again and this time hit 'Add to Archive'. Copy-paste the filename for whichever file you're creating an archive for, AP, BL, CP or CSC, make sure archive format is set to .tar and leave everything else default and hit 'OK' at the bottom of the window.
    Note: This too will be have to be done for CP, CSC and BL as well.

    5. Once this is done, you should have 4 .tar files ready to be flashed. Open up Prince Comsy's Odin, add each file to it's respective field in Odin.

    6. Connect your device in Download Mode, press Start, and wait for the flash to be completed and for Odin to show 'PASS' at the top of the window.
    Your device will reboot automatically.

    ALTERNATIVELY, you can watch this very crappy screen recording I made for a better idea on how to do it.

    YouTube link: https://youtu.be/eyIh3_p8WBQ


    Credits go to:

    @FatalONEM8 and @me2151 for helping out.
    Tino Reichardt (mcmilk) for the modified 7Zip
    Prince Comsy for the modified Odin.
    Samsung for making flashing more and more difficult every year.

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

    For Linux/Ubuntu, @kernel.killer has created a script to unpack the .lz4 compressed firmwares without having to do all of the above manually.
    See this post - Link
    7
    Bash script to repack newer firmwares

    Hey,

    I have created a small bash script to automate the tasks involved in transforming the new Odin archives into ones' flash-able using official/unmodified Odin <= 3.12.10

    GitHub repository: https://github.com/kernel-killer/sam-fw-tool

    This tool is meant for Linux, however, it works without any issues on Ubuntu on Windows 10 (Windows Subsystem for Linux).
    To use this script, first you must fetch some prerequisites (for Ubuntu or any other Debian-based distro):
    Code:
    sudo apt-get install tar unzip liblz4-tool coreutils
    All you need to do is put the script to folder with *.tar.md5 firmware files, open (bash) console and cd to location of the firmware:
    Code:
    cd /mnt/c/Users/username/Documents/android/SM-G955F_1_20180201101301_ww6yh32b3f_fac
    ./repack.sh
    The script handles the extraction of firmware tar archives, decompression of lz4-compressed images and repacking of tar archives, then it appends md5 checksum at the end of each archive, to prevent flashing of corrupted images.

    The resulting archives can be flashed using (older) Odin (<= 3.12.10). The results are stored in current_directory/firmware by default. I will soon update the script to move the results into a single folder and to verify md5 checksums of original images before unpacking them (Done!).
    5
    @murtaza02, I think you should add these to the first post.
    These are modified firmware files, packaged to work with Odin. You would need prince comsy Odin BTW.
    I have tested one of these (S8, Single SIM, Turkey) on my Galaxy S8, and it worked alright.
    These have been packaged with HOME_CSC file, so that your region doesn't change from the current one, and the factory reset should not happen too -- but I cannot guarantee things, as is the case always.

    Galaxy S8 - SM-G950F - Single SIM - Turkey
    http://downloadmirror.co/Wo0/Galaxy...ompatible_G950FXXU1CRAP_G950FOXM1CRAP_TUR.zip
    Galaxy S8 - SM-G950FD - Dual SIM - India
    http://downloadmirror.co/Wo3/Galaxy...e-working-G950FXXU1CRAP_G950FOXM1CRAP_INS.zip

    Galaxy S8 Plus - SM-G955F - Single SIM - Turkey
    http://downloadmirror.co/Wo2/Galaxy...-modified-G955FXXU1CRAP_G955FOXM1CRAP_TUR.zip
    Galaxy S8 Plus - SM-G955FD - Dual SIM - India
    http://downloadmirror.co/1MpN/Galax...ompatible_G955FXXU1CRAP_G955FOXM1CRAP_INS.zip
    4
    RMM State FIX

    I may get this slightly wrong but this is what I learned regarding the issue with not being able to flash TWRP.

    It is caused by something referred to as RMM State - some new security thing Samsung Started. There are two states your phone can be in:
    Pre-Normal or Normal
    if you are PRE-NORMAL - you won't be able to flash anything for 7 days - you are locked out. If you are normal - you can flash.

    You will see this if you go into Download mode and look for the thing that says RMM State or something like that.

    There is a fix - BUT only after you hit the 7 days - after you get OEM unloock again, flash twrp and then flash the file I linked to below - that will fix the phone and lock it to Normal State. (but anytime you flash a custom rom you will have to flash that file again.)

    Oh, one more thing - you need to keep your phone running that entire time during the 7 day period. From what I have been told, you can't reboot the phone or it will start the clock over and you will need to wait another FULL 7 days from that point.

    Read more and get the file to fix this here: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22

    From What I understand, this will work on any device that is in the Pre-Normal State - S8, S8 Plus, Note 8 and so on.
    4
    Samsung reveals why it stopped the Galaxy S8 Android Oreo release https://www.sammobile.com/news/samsung-reveals-why-it-stopped-the-galaxy-s8-android-oreo-release/

    Enviado desde mi S8+ mediante Tapatalk