Related
My cwm got broken (though my phone is working ok , but I am not able to flash anything cmw does not detect sdcard),
Now I have extracted boot.img from the kernel.
I want to flash it with the odin.
When I convert the boot.img using Caboomi's_Recovery_img2tar_odin_maker, it just makes a 11kb file. and the terminal shows the following information,(in the image).
I have two Queries:
1) How shall I convert boot.img to boot.tar.md5
2) In the Odin , Where shall I pick the boot.tar.md5 file . (in bootloader, in pda, in phone, or in CSC?)
Regards,
Shikhar
PS: Its Galaxy Y Pro Dous 5512
Hello every one today I am posting a script which you
Can create tar to md5 odin flash.
You can easly make TAR from your iMG by using 7ZIP.
When you make TAR then you can make it to MD5 ODIN FLASH
By my script
Download tar-tool-odin .zip by ihsas and extrat it on your pc.
Copy your tar file into the tar tool folder and double click on
Tar to md5 scrip and after complete the process you have
A odin flash MD5 tar.
Say thanks and from me thnx to all... cheeer.
Download link below
https://mega.nz/#!mENEyLYA!wMeReYTked_mjtCF1GuY9FALwmBFxoTeQjwX3vFdnok
Thanks man this really worked out for me.
decompile and recompile stock rom and make odin tar md5 recovery
ihsas said:
Hello every one today I am posting a script which you
Can create tar to md5 odin flash.
You can easly make TAR from your iMG by using 7ZIP.
When you make TAR then you can make it to MD5 ODIN FLASH
By my script
Download tar-tool-odin .zip by ihsas and extrat it on your pc.
Copy your tar file into the tar tool folder and double click on
Tar to md5 scrip and after complete the process you have
A odin flash MD5 tar.
Say thanks and from me thnx to all... cheeer.
Download link below
https://mega.nz/#!mENEyLYA!wMeReYTked_mjtCF1GuY9FALwmBFxoTeQjwX3vFdnok
Click to expand...
Click to collapse
You can also extract stock rom and after making changes get back tar.md5 odin flash rom by this script tool
Its to use.
Sorry for bad english
Hit thnx.......
Tar to md5 scrip ... where? is it the ImgToTar.MD5?
Also any of the batch files when clicked dont do anything nothing shows up?
using : win7 x64
EwOkie said:
Tar to md5 scrip ... where? is it the ImgToTar.MD5?
Also any of the batch files when clicked dont do anything nothing shows up?
using : win7 x64
Click to expand...
Click to collapse
This script is for just make tar to md5 you can easly make img to tar by using 7zip.
I have another script which make img to tar.md5 but with that script you can only make 1 img file not sevral file like stock rom
Stock rom have many img file when you make several img file to tar by using 7zip then you can easly make that tar to md5.tar and then flash by odin
Such as I have update my galaxy s3 to kitkat 4.4.4 and then I have download jb 4.3 when I flash it then I have found error with sboot then I make this tool to delete the sboot and flash again and its work for me.
Thank you
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
hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide
@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/
SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Feox said:
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Click to expand...
Click to collapse
Feox said:
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
Click to expand...
Click to collapse
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
ethical_haquer said:
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
Click to expand...
Click to collapse
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Feox said:
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Click to expand...
Click to collapse
So you are following the official installation instructions? I'm pretty sure you don't have to:
Feox said:
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
Click to expand...
Click to collapse
as the official installation instructions for a Samsung device running A9 or higher say:
"
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
"
It doesn't sound like you have to isolate the boot.img.
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Feox said:
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Click to expand...
Click to collapse
Just read the official installation instructions I linked to. I only copied part of it and pasted it here so you could see it.