Hi guys, I would like to extract boot.img from a Stock ROM without the need of installing it on my (Galaxy Note 2 T-mobile). All I found on the internet is how to extract it from an installed ROM.
So I would like to:
1. Extract the boot.img
2. Then flash it through ODIN to my custom ROM (Jedi Master 14)
Thanks in advance and please help me :crying:
Why would you do that?
Hastily spouted for your befuddlement
I don't know how you going to use boot.img to fix your problem. But the .md5 rom files are just zipped files. unzip and you will find the boot.img file. Are you sure that this will fix your problem?
Are you trying to change your boot image?
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Thanks a lot. Thats exactly what I am looking for.
Sent from my SGH-T889 using xda app-developers app
Darkshado said:
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Click to expand...
Click to collapse
and how do we do?
i flash the file without pepacking it so i can t bot, kernel error!
I'm really annoyed if you can explained to me how do we do it
thx
Related
Hello Community,
I tried to install custom recovery using this manual "wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx" (<- cannot use the link function, because it's my first post). I followed every step. At point 9 I have to make commands using the cmd. Unfortunately the result is an Error:
Failed to access device. libusb error: -12
I had two insecurities while following the manual:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
To point 5: I deinstalled Kies and the device driver in the Windows operating system. Since I've done this, there are appearing two devices in the zadig.exe when I connect my S4. I installed the zadig driver for both of them.
Im using Windows 7 x64
I hope someone can help me, for this moment I don't know what to do further...
greets
Dr. Bob! said:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
Click to expand...
Click to collapse
I don't know about the libUSB error, and I haven't modded a Galaxy S4 mini, but I have installed CM on Galaxy Player. The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
I flashed the Galaxy Player with Odin 3 v. 3.04, after having installed Kies to have the drivers installed. The Player showed in Odin with something like "ID:0 COM"; I then clicked on the "PDA" button, then pointed to the tar.md5, and clicked flashed, and it worked.
Here are my 2 cents :^)
Is your phone rooted? If rooted already it easy! For the most noob method, install ROM Manager from https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager and ROM manager will install the CWM for you. From there, its pretty simple.
If it not rooted, that the first thing you'll have to do.
fdelente said:
[...] The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
Click to expand...
Click to collapse
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
TNCS said:
If it not rooted, that the first thing you'll have to do.
Click to expand...
Click to collapse
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Dr. Bob! said:
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Click to expand...
Click to collapse
No, custom recovery is not rooting. Not my favourite method but it easy enough, try this: http://www.kingoapp.com/
It a universal root for JB and it will prompt you to install CWM afterwards.
After installing the CWM I rooted the device. I succesfully installed Canogenmod 10.2.1. The Tutorial says explicit, that it only helps for 10.2.x but I want to install the Nightly version which is running at CM version 11. If I could, I would ask this questions in the threat but I'm not allowed yet to post in the developers section. "forum.xda-developers.com/showthread.php?t=2474054"
Can I use this tutorial for flashing CM version 11?
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Yes!! I have asked countless people and put a thread up but nobody answered. Thank you very much for this tool! I used to use EXT2EXPLORE on KitKat with my S4 Mini, now I can use it on my S6. Thank you!!
citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?
thismonk said:
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?
Click to expand...
Click to collapse
You need someone that can dump the partitions of their phone and flash that partitions to your phone, you need to understand a bit the procedure before flashing with ODIN
citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
How can we use it;;it gives wrong parameter if executed.needs editing;;the newimgext2 ??
citytrader said:
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
Click to expand...
Click to collapse
Works fine ! I tried a lot of methods to do the same thing, of firmware Lollipop Samsung Galaxy S6 and S5 neo. This method is the only one which works. Thanks !
Very good love it, works even on Nougat (S7).
Hello all, I need some help finding the .tar or the .md5 file from the stock ROM zip file (Tab Pro 8.4).
I am trying to flash / revert back to stock ROM and recovery, since I am giving this tablet to my nephew. I've downloaded the official firmware directly from Samsung, I've downloaded Odin V3.07 and the samsung drivers are installed on my laptop. I've used Odin before, to flash files (months ago), but where I'm getting stuck is on Odin when I go to select the .tar or the .md5 file form the zip, I can't locate the files. I've extracted them several times using different methods, but not a single time have I been able to extract a .tar or .md5 file, all I get is: META-INF folder, system folder and boot disk image, no .tar or .md5 file anywhere in the folders either.
Am I an idiot here or what am I doing wrong that I don't get the .tar or .md5 file?
Any help is appreciated, thanks!
i am not sure where you downloaded it from. i took it from sammobile and the name of the zip is: T320XXU1BNI1_T320DBT1BNJ1_DBT.zip inside it being a file named: T320XXU1BNI1_T320DBT1BNJ1_HOME.tar.md5
PS: i have a german device thats why the DBT code...please download yours...
mospantagruel said:
i am not sure where you downloaded it from. i took it from sammobile and the name of the zip is: T320XXU1BNI1_T320DBT1BNJ1_DBT.zip inside it being a file named: T320XXU1BNI1_T320DBT1BNJ1_HOME.tar.md5
PS: i have a german device thats why the DBT code...please download yours...
Click to expand...
Click to collapse
I am downloading it one more time from sam mobile just to make sure. How did you extract the zip (what program)? 7zip, winrar, etc?
i think i know whats going on. i use winrar for windows you probably use something else. inside .zip there is a .md5 file but inside .md5 file there are meta folders etc. some software consider it being an archive inside an archive and it doesn't even bother to tell you that probably it's extracting folders directly...
mospantagruel said:
i think i know whats going on. i use winrar for windows you probably use something else. inside .zip there is a .md5 file but inside .md5 file there are meta folders etc. some software consider it being an archive inside an archive and it doesn't even bother to tell you that probably it's extracting folders directly...
Click to expand...
Click to collapse
use 7 zip, there should be a .tar.md5 in the .zip only extract the .tar.md5. dont extract anything from the tar.md5. just select the tar.md5 in odin after you put your device in download mode
As the title asks, where can I find the stock ROM for the N7100XXUFND3?
I've tried various sites, but it is hard to find anything that can actually be downloaded. I did find this https://www.sammobile.com/firmwares/galaxy-note-/GT-N7100/XEF/download/N7100XXUFND3/28780/ but it cannot be installed, with the error "Could not find 'META-INF/com/google/android/update-binary' in the zip file.".
Did you follow the instructions on the site how to install the firmware? You have to flash it through Odin (which will wipe your device) not a custom recovery like TWRP.
Sent from my SM-G935U using Tapatalk
xBkKx said:
Did you follow the instructions on the site how to install the firmware? You have to flash it through Odin (which will wipe your device) not a custom recovery like TWRP.
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
Thanks for that, don't know how I missed it.
However, when I try to use Heimdall I get: "heimdall packages shouldn't contain links or directories".
However, there are no "links or directories" in the archive.
I extracted the archive manually and attempted to create one which only contains the .img files, tar -cvzf stock_rom.tar.gz *.img.
This gives me that "firmware.xml is missing from the package".
diracdeltafunct said:
Thanks for that, don't know how I missed it.
However, when I try to use Heimdall I get: "heimdall packages shouldn't contain links or directories".
However, there are no "links or directories" in the archive.
I extracted the archive manually and attempted to create one which only contains the .img files, tar -cvzf stock_rom.tar.gz *.img.
This gives me that "firmware.xml is missing from the package".
Click to expand...
Click to collapse
Why so much effort?
use Odin to flash it directly...
so i had an issue installing supersu on my sm-a520 and after searching everywhere for the proper firmware file i could only find firmware files in .lz4 format which odin3 would not flash to the device properly i then found a program that is free called classykitchen which allowed me to decompress the .lz4 files then create a system.new.dat file to flash via recovery so if you have run into this issue i recommend finding classykitchen and installing twrp via odin3 then download the firmware file from updato.com unzip that file then when your starting a new project in classykitchen make sure you put bl ap cp and home_csc all in the new project by highlighting all the files and make sure when its done extracting the lz4 files you select create system.new.dat once thats complete put that file to the sdcard wipe the device for a clean install and flash the file youve just created and bingo your phone will be back to stock other then the twrp recovery which i will say is the best recovery ive used in my mind there is no better.. now that ive explained that i'm gonna try installing supersu again and keep on keepin on have a good one
dirtdirte said:
so i had an issue installing supersu on my sm-a520 and after searching everywhere for the proper firmware file i could only find firmware files in .lz4 format which odin3 would not flash to the device properly i then found a program that is free called classykitchen which allowed me to decompress the .lz4 files then create a system.new.dat file to flash via recovery so if you have run into this issue i recommend finding classykitchen and installing twrp via odin3 then download the firmware file from updato.com unzip that file then when your starting a new project in classykitchen make sure you put bl ap cp and home_csc all in the new project by highlighting all the files and make sure when its done extracting the lz4 files you select create system.new.dat once thats complete put that file to the sdcard wipe the device for a clean install and flash the file youve just created and bingo your phone will be back to stock other then the twrp recovery which i will say is the best recovery ive used in my mind there is no better.. now that ive explained that i'm gonna try installing supersu again and keep on keepin on have a good one
Click to expand...
Click to collapse
You shouldn't be installing SuperSU on newer versions of Android. Use magisk instead. Then you shouldn't have problems.