I´ve read about extracting one package file and I noticed that when we extract that, it won´t generate the file BOOT.tar.md5
What is this file? Is the kernel?
I wouldn´t have problem if I installed a rom stock without this file, correct?
Thanks...sorry my bad english.
If someone want to know. After search, i found the file BOOT.img.tar is the kernel!
Related
Is it possible to extract an APK from a ROM File?
If i take the JM5 ROM, I can unRar it and then I can unTar the md5 file that is the ROM - but from there I just get a bunch of system files that I assume are images of partitions. The big one is the factoryfs.rfs - is there a way to pull an apk out of here, or do i have to install on a device first and save the APKs i want?
Thanks.
alphadog00 said:
Is it possible to extract an APK from a ROM File?
If i take the JM5 ROM, I can unRar it and then I can unTar the md5 file that is the ROM - but from there I just get a bunch of system files that I assume are images of partitions. The big one is the factoryfs.rfs - is there a way to pull an apk out of here, or do i have to install on a device first and save the APKs i want?
Thanks.
Click to expand...
Click to collapse
Just tell us what application your looking for(remember to follow the forum rules before replying )
Hi all, sorry for my poor english...
I need to restore original kernel from stock firmware, extracting the file zimage and therefore creating a zimage.tar. I used 7zip, but the file seems not enough good for odin .
What windows tool you recommend to me??
Thanks
http://gnuwin32.sourceforge.net/packages/gtar.htm
http://www.computerhope.com/unix/utar.htm
Hello community,
I'm currently trying to modify the stock rom for my GT-I8200n. I didn't find cwm for the S III mini VE, and the version of twrp I found was very buggy. So I need an odin-compatible flash file for my rom. I tried to modify the stock rom by downloading the .tar.md5 from sammobile, unpacked it with winrar and copied the system.img into an ubuntu-VM. After that I created a sys.img (or sys.raw, same problem) out of system.img using the simg2img-file I found somewhere here on xda, mounted sys.img (or sys.raw) and modified it. Then I unmounted it and used img2simg to create my system_new.img. Copied it to my windows system, into the unpacked stock rom folder, renamed it to system.img, overwriting the old system.img and packed everything into a .tar file using ZArc. Now while flashing my ROM, odin works on the system.img for some minutes and then shows a fail.
Does anyone know what I'm doing wrong?
P.S.: I tried simply using simg2img on my stock system.img and then - without mounting and modifying - used img2simg kn the sys.img file. Same problem with odin and I noticed that my new system.img is approximately 50 mb smaller than the stock img, although I didn't modify it.
I hope I described my problem well (I'm not an english native speaker, but did my best to make this text understandable )
Any ideas or hints that could maybe solve this problem are welcome.
Thank you,
Chris
I have the same problem
any solution ?
So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!
.tar.md5 is a text file which contains hash of the original file. It is used to check the integrity of files.
Compare the sizes of .tar and .tar.md5 files.
Sorry @Shished that has really not helped me at all, I'm just as confused as ever. Thank you for trying though. What is "the original file"? What am I comparing, should I have some other kind of file here? Can I get the original file out of my .tar.md5? I have one file that I believe is a factory boot image and it's a .tar.md5. Believe me when I say I am a complete noob on this and I need the basics of the basics.
Edit: The file originally came as a zip, is THAT the original file?
screenshot of files: https ibb.co/fas1o7
Questioneer said:
So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!
Click to expand...
Click to collapse
.tar is the compression used for Samsung. If you extract the .tar, you will find an .img in it. A .tar.md5 is just the .tar with the hash file appended.
madbat99 said:
.tar is the compression used for Samsung. If you extract the .tar, you will a .img in it.
Click to expand...
Click to collapse
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?
A S Ovin said:
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?
Click to expand...
Click to collapse
There will likely be several .img files inside of it.
I need a tar file because ODIN doesn't accept img files. Magisk used to be able to give a tar file, what happened?
As long as I'm unable to figure out how to make this work, rooting my device will be impossible. I don't want to give up now, not after getting through so many headaches...
Did you feed it a tar file? If you do it should give a tar file as output.
Didgeridoohan said:
Did you feed it a tar file? If you do it should give a tar file as output.
Click to expand...
Click to collapse
That's the problem, I only have a .img file, and have no idea how to turn it into a .tar file, or how to get one from my firmware. There are plenty of guides around on how to convert .img into .tar, but I don't know whether they work for this purpose. I would appreciate some guidance here.