Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
{
"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"
}
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
Click to expand...
Click to collapse
I tried that as the file in Odin contains a cache.img and a hidden.img but when I boot the a custom ROM and check Phone Info, the CSC didn't change. I am just wondering how some developers extracted those .img files into the files we see into say the CSC changer.
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Andrw0830 said:
Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.
Click to expand...
Click to collapse
Not quite sure what you want to do, flash a stock (any) rom with you CSC ( home _ csc ) check this
Or change the CSC of your custom rom, if so check here
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Very useful post, thanks! Works like a charm.
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Yep thanks so much. That is what I wanted to accomplish!
Andrw0830 said:
Yep thanks so much. That is what I wanted to accomplish!
Click to expand...
Click to collapse
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
What I believe is if you flash stock Samsung packages from ODIN, your Knox stays at 0x0 but once you flash modified software like TWRP Recovery, then you lose Warranty. Your phone should detect default region anyways as was the case when I went back to stock so only if you change the package integrity or flash custom recovery is when you will trip KNOX unless someone corrects me. I'll keep this thread open for the useful post about extracting .tar.md5 files in case someone has the same question I had, but I may not reply to other questions as besides flashing ROMs am not too knowledgeable in customizing ROMs.
viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
@ viewdetails, did you try modifying the zip to change the default region and flash it back? Did it work?
I've recently bought an S7 whose region code I want to change to XFA, except it is still stock and unrooted, and XFA is part of a multi CSC only.
Not wanting to void the warranty by rooting just yet, I also had the idea of modifying the CSC tar.md5 file to make it work. Thing is I have not done something like this before and I don't know if doing so will set KNOX to 0x1 anyway.
When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse
Serifbilgin20 said:
When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Click to expand...
Click to collapse
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse
You don't need to extract the PIT file, just check repartition, the CSC will do the rest as it contains the PIT anyway
I need a pit file for any device. The firmware file I downloaded for that device is csc.tar.md5 and the pit file that comes out of it is the file I am looking for ?
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''
EmperorGsi said:
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''
Click to expand...
Click to collapse
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.
kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
kykint said:
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.
Click to expand...
Click to collapse
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?
EmperorGsi said:
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?
Click to expand...
Click to collapse
If you're trying to unpack an oreo firmware, looks like imgextractor cannot handle the cache.img properly. Instead you can follow the steps below:
1. Extract lz4 image
Code:
lz4 -d cache.img.lz4
2. Convert the extracted image with simg2img (you can compile one from AOSP source or grab from here)
Code:
simg2img cache.img cache.raw.img
3. Open cache.raw.img with a proper program like 7zip explorer, and you'll find recovery/sec_omc.zip.
I used the method from here.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-extract-pixel-factory-t3563698
I changed cache.img to system.img
The program created a folder called system and copied there all the files
In system/recovery I found the file sec_csc.zip
Related
A lot of people were having issues with designgear's instructions on rooted their official roms.
Please read this guide (link below) first if you have no experience with this URDLV rooting method (a root method that avoids triggering KNOX counter).
http://www.theandroidsoul.com/universal-root-de-la-vega-script/
Here's a set of steps that worked
------------------------------------------------------------------
To URDLV your offical ROM (worked on MF4)
Some Assumptions:
1.) Snapdragon Processor
2.) Current Bootloader on your phone, MJ1 or lower. If higher, you'll likely trip KNOX
3.) Reactivation Lock = Disabled
Procedure:
Applying URDLV to Official ROM:
- Install Cygwin (64bit or 32 bit depending on your OS)
- Started the Cygwin terminal
- cd'ed to proper drive and URDLV folder
-----ie: cd urdl
- chmod +x URDLV.bat
- ./URDLV.bat full c:/URDLV/blahblah....tar.md5 (drag-n-dropped the path to the file)
-----this will take a while on regular HD
The following steps are folked into two alternate methods.
Method 1 can work for MF4, because it seems to work with the MF1 files, so not uploading the accompanying files from the official MF4 rom neglected by URDLV's process can work.
Method 2 is more complete, and includes the uploading of all files EXCEPT the bootloader, this should minimize any mismatches of files causing issues.
Method 1: Upload only System and Cache First, other files individually
-Use ODIN to send the file over to Phone (follow designgear's OP instructions)(or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-Put the root files on the phone
Extra Reading (optional):
- follow designgear's OP instructions
- PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/
-----extract root_de_la_vega_sdcard.zip
-------- root_de_la_vega.sh (file)
-------- root_files (folder)
-----put into the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
-Extract the Modem.bin and NON-HLOS.bin file from the Official ROM (optional for MF4) (some later roms REQUIRE matching NON-HLOS.bin and MODEM.bin files)
-----these files were excluded by URDLV's output ROM (for reasons unknown with other ROM version, but the NON-HLOS.bin and modem files from MF4 seem to integrate fine)
-Use ODIN to send Modem.bin and NON-HLOS.bin to the phone via CP slot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
Method 2 (which includes all files except the bootloader):
1.) Extract the System.img and Cache file FROM the URDLV tar.md5 TO [Folder]
--------You could use 7Zip
2.) Extract all files EXCEPT ABOOT and Cache file FROM the Official ROM TO [Folder]
3.) Now [Folder] should contain 10 files
4.) Tar up those files in [Folder].
----In Cygwin:
Change directory to the [Folder]
Enter the following commands to tar up your files into a TAR.MD5 file:
tar -H ustar -c *.* > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
How your TAR.MD5 should look like:
{
"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"
}
5.) Send your your_odin_package.tar.md5 package via ODIN (AP Slot) to your phone
6.) -Put the root files on the phone (follow designgear's OP instructions) (or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-----the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
------------------------------------------------------------------------------
For future rom updates (applicable to rooted users):
Reports claim that Mobile Odin works: http://forum.xda-developers.com/showthread.php?t=2522729
-------------------------------------------------------------------------------
Download Links in case if needed:
Working link:
https://mega.co.nz/#!co1jRKYY!p94iENAmHkqd9wD3c0T1qC_dz03o7n8xmmkuIiVxCLQ
OLD DELETED:
Universal RDLV script (v0.2)
https://mega.co.nz/#!ugJFUTCL!NrME135Mia6-x4e0E-21uQXmh8wMbhrksHG0HjTtg4g
Root de la Vega sdcard files
https://mega.co.nz/#!qoQnmAQD!U_dQMRsZ7UFMpEicnnGIFAtvn7V6Ti_gbyPDt9TDmmY
Odin v3.09
http://filecloud.io/cp43ua5j
Sammobile Firmwares
http://www.sammobile.com/firmwares/
Good guide m8 if I may tell you something to put in top of everything and This is that URDLV works only in mj1 bootloader and below, if with any way you have updated with OTA/KIES/SERVICECENTER or bought with mj3 and above you cannot use any of Vega ways.
Sent from my SM-N9005 using Tapatalk
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
geek78 said:
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
Click to expand...
Click to collapse
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
klau1 said:
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
Click to expand...
Click to collapse
No it won't as those are not the bootloader. I made a URDLV system image of MJ7 and added all the other files from the original rom (MINUS aboot --> bootloader) and flashed with odin. Got root and knox counter not tripped. :good:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
klau1 said:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
Click to expand...
Click to collapse
Yes you can just tar.md5 the rest and flash it. Not really sure where to place it but you can try ap or wait for others to reply.
Yes, I tar.md5 them up and ODIN them up from the AP slot.
It works
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
klau1 said:
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
Click to expand...
Click to collapse
Guides don't go in Development threads.
@klau1
Can you remove the download links please and link to the thread. I am going to be updating soon and don't want you to have dead links or links to older versions up. Thanks.
This guide will NOT work and brick your camera and wifi (did for me)
Real solution: http://forum.xda-developers.com/showthread.php?p=47390175
@klau1 u are allowed to copy my guide if you put my name on the op
My guide is 100% working for me 0x0 root camera wifi dmj7
Sent from my SM-N9005 using XDA Premium 4 mobile app
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
In the case of mj7, the other files designgears urdlv neglected to include are required.
@designgears Let me know once you've updated your guide so I can update and reflect the changes here thanks.
Hi all!
I own SGN 3 with exynos octa processor.
Versions of installed firmware:
AP: N900XXUBMJ1
CP: N900XXUMI2
CSC: N900OJVBMI5
Can I root this device with URDLV method without any problem with KNOX and warranty?
Can I update firmware in the future with KNOX trigger = 0x0 and so on?
Thanks.
No, UDRLV only works with Snap Dragon version.
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
SimerToor said:
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
Click to expand...
Click to collapse
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
If the phone is ALREADY on MJ4 it's impossible to root with the current URDLV.
This method requires you to START OFF with MJ1 ROM because once your phone already has been upgraded beyond MJ1, the newer bootloader can detect changes in the URDLV rom and trigger KNOX.
Whereas the bootloader in MJ1 can be exploited.
You can't factory reset the bootloader back to MJ1 after you've upgraded AFAIK.
efs safe?
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Masterz said:
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Click to expand...
Click to collapse
100% safe
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app
Frickin amazing. Worked perfectly on my T-Mobile Note 3. No flag tripped, have root, will party. Had to use Cygwin to do it BTW.
hello hope you are fine
i have galaxy s6 sm -g920f
it was running on 5.1..1 G920FXXU2BOGE
tried to install marshmallow XEF-G920FXXU3DPAD-20160223100452 via odin
my fone stuck and dont boot
when i tried to flash 5.1.1 again with 4 files it fail to flash bootloader
in recovery mode it was still MM recovery and written dm-verify verification failed need to check dRK first ... ?
what the problem please any solution ???
sorry for my bad english
Hmm. Let's try this.
1. Go to recovery->wipe everything.
2. Reflash stock rom through odin.
2a. If it fails at cm.bin or any other .bin file or hidden.img file just delete them from the .tar file using 7zip.
3. If it still fails. Google "G920F pit file" and flash it with that file.
3a. If that STILL fails. Remove all files from the .tar file and just leave system.img and sboot.bin(or img not sure).
4. Now reflash and enjoy! . If anything fails after all my steps. Copy and paste the odin log and I will try to figure out something else.
ProtoDeVNan0 said:
Hmm. Let's try this.
1. Go to recovery->wipe everything.
2. Reflash stock rom through odin.
2a. If it fails at cm.bin or any other .bin file or hidden.img file just delete them from the .tar file using 7zip.
3. If it still fails. Google "G920F pit file" and flash it with that file.
3a. If that STILL fails. Remove all files from the .tar file and just leave system.img and sboot.bin(or img not sure).
4. Now reflash and enjoy! . If anything fails after all my steps. Copy and paste the odin log and I will try to figure out something else.
Click to expand...
Click to collapse
thx bro i'll try and give you feed back
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 G950F / G950FD (F ROMs work on the FD variants, there are no FD specific ROMs):
Mirror Link 1 (MEGA NZ) (WIPE) - Thanks @ciccio80
Mirror Link 2 (MEGA NZ) (NO WIPE) - Thanks @ciccio80
Mirror Link 3 (Google Drive) - Uploaded by me
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
Delete this please, im a moron
also, worked like a charm for me
Odin stuck File Analysis
Worked like a charm. Thanks a lot dude
s
It works perfectly!, finally I have Oreo from a clean installation
{
"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"
}
I uploaded the files with the extraction process done (.lz4) in Google Drive but I can not publish it because I'm new, If someone wants it, you can ask for it through PM.
Works! Thank you so much!
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Currently CRAP file is one and the same for the Nordic Countries, Spain, France, Germany, Turkey, Poland found on Sammobile.com ?
Tnx.
Trimis de pe al meu SM-G950F folosind Tapatalk
Thanks!! Finally my S8 is running Android Oreo.
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Pavezi80 said:
Works! Thank you so much!
Click to expand...
Click to collapse
brenopapito said:
Thanks!! Finally my S8 is running Android Oreo.
Click to expand...
Click to collapse
Any of you guys try with Home_CSC?
Thanks!
geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?
Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
I just tried with CSC_OXM file.
tomaasz said:
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?
Click to expand...
Click to collapse
only when you dont let phone boot after flash in system and then you flash directly twrp and boot directly in twrp for mod build.prop so that vaultkeeper is set to 0 and flash magisk
Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)
It works! thanks!
Pavezi80 said:
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)
Click to expand...
Click to collapse
That's the point, I'm going to travel tomorrow and I don't want to format at this moment
Just wondering if anyone tried with home_CSC from Nougat to Oreo directly to see if they found any issue.
Thanks!
worked here with HOME_CSC... will see if i will need to do it clean or if it will be ok with nowipe. i was on zre5, unoficial betatester
geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
How to recover from this?
I made everything like in instruction but it stops at File analysis.... . What should i do ?
lumenit said:
I made everything like in instruction but it stops at File analysis.... . What should i do ?
Click to expand...
Click to collapse
Install with Prince Comsy's modified Odin
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing. I have a PDA file for my old GT-S6102 Galaxy Y,........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is also specific to your device as well.
https://forum.xda-developers.com/galaxy-y
With that guidance...
Your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2063534
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
Click to expand...
Click to collapse
It doesn't quite work like that, you can create your own Odin flashable file(.tar.md5) containing the custom ROM, but it isn't as simple as just pasting the system.img into the .tar.md5.
Here are some threads for extracting Odin files and for creating your own .tar.md5 using the custom ROM file.
This thread is for correctly extracting the existing .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=74
This thread is for creating your own Odin flashable .tar or .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=92
Sent from my LGL84VL using Tapatalk
Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
{
"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"
}
itsmirel said:
Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
View attachment 5264873
Click to expand...
Click to collapse
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Tab E said:
Download the stock recovery and any recovery from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
itsmirel said:
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Click to expand...
Click to collapse
Is fastboot available? If yes then use fastboot to flash. If no try odin
Tab E said:
Is fastboot available? If yes then use fastboot to flash. If no try odin
Click to expand...
Click to collapse
I guess so
Ok great. Then go ahead with fastboot
Tab E said:
Ok great. Then go ahead with fastboot
Click to expand...
Click to collapse
i will use odin, i dont know how to enter fastboot and couldnt find
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
ALSO, the stock rom i downloaded has only .md5 files
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
itsmirel said:
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
Click to expand...
Click to collapse
Btw, the tutorial "How To Extract Files From a TAR.MD5 Stock ROM" isn't working anymore. his MyBB forum doesnt work. (MyBB has experienced an internal error and cannot continue.)
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
benniehelder said:
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
Click to expand...
Click to collapse
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Tab E said:
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Click to expand...
Click to collapse
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
benniehelder said:
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
Click to expand...
Click to collapse
how to make from the new homemade recovery a tar, so you can flash with odin?
benniehelder said:
how to make from the new homemade recovery a tar, so you can flash with odin?
Click to expand...
Click to collapse
Convert TWRP .img to .tar (for ODIN)[Easy]
Sometimes the latest version of TWRP is in ".img", so some people use an older version instead, which is in .tar, so they can flash it with ODIN. The thing is that the ".tar" version is just the ".img" compressed XD, so I'm going to show you how...
forum.xda-developers.com
i had done this with z7 myself already, but to no avail, but: i began, in a moment of despair, with Odon to try all the .tars i had collected sofar , to flash and when i flashed PBRP (it was not the first time) it worked!!!. after a week the gizmo do have a recovery, that is not stock! Little new prob: By rebooting system he bootloops (for a change!) in bootloader mode.