Related
Hi,
I want to flash XXLA4 ROM with OLBKL2 CSC and CF-Root LA4 using CWM Manager in one go.
I have these files:
N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5
N7000DXLA1_N7000OLBKL2_N7000DXKL2_HOME.tar.md5
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Inside the ROM package there are:
factoryfs.img -> this is System files (PDA), I will use XXLA4
modem.bin -> this is Phone modem, I will use XXLA4
zImage -> this is Kernel, I will use CF-Root XXLA4
cache.img -> this is CSC files, I will use OLBKL2
hidden.img -> what is this? should I use the file from DXLA1 or XXLA4?
I searched but found conflicting answers. Some said that it's related to CSC, so I should use the file from DXLA1. But, leaked samsung rom only have cache.img inside MULTI-CSC tar file (for example GT-N7000-MULTI-CSC-OXALA3.tar).
I also noticed that some of the ROM package that I extracted have the same modified date for factoryfs.img and hidden.img, while different modified date for cache.img; meaning it's related to System files (factoryfs.img).
So, to know from which file should I use hidden.img from (DXLA1 or XXLA4), I want to know what is inside hidden.img.
Thank you so much in advance~!
V-Lix said:
Hi,
I want to flash XXLA4 ROM with OLBKL2 CSC and CF-Root LA4 using CWM Manager in one go.
I have these files:
N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5
N7000DXLA1_N7000OLBKL2_N7000DXKL2_HOME.tar.md5
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Inside the ROM package there are:
factoryfs.img -> this is System files (PDA), I will use XXLA4
modem.bin -> this is Phone modem, I will use XXLA4
zImage -> this is Kernel, I will use CF-Root XXLA4
cache.img -> this is CSC files, I will use OLBKL2
hidden.img -> what is this? should I use the file from DXLA1 or XXLA4?
I searched but found conflicting answers. Some said that it's related to CSC, so I should use the file from DXLA1. But, leaked samsung rom only have cache.img inside MULTI-CSC tar file (for example GT-N7000-MULTI-CSC-OXALA3.tar).
I also noticed that some of the ROM package that I extracted have the same modified date for factoryfs.img and hidden.img, while different modified date for cache.img; meaning it's related to System files (factoryfs.img).
So, to know from which file should I use hidden.img from (DXLA1 or XXLA4), I want to know what is inside hidden.img.
Thank you so much in advance~!
Click to expand...
Click to collapse
cache is CSC
if you want to use another CSC file, just select cache in Mobile Odin OR in case of CWM, when it ask you to select file for Cache, you have to point to CSC file(OBL KL2 CSC e.g.)
I said you earlier too, that will wipe your data, as i remember you have not concern about losing data i think.
dr.ketan said:
cache is CSC
if you want to use another CSC file, just select cache in Mobile Odin OR in case of CWM, when it ask you to select file for Cache, you have to point to CSC file(OBL KL2 CSC e.g.)
I said you earlier too, that will wipe your data, as i remember you have not concern about losing data i think.
Click to expand...
Click to collapse
Yes, I know about cache.img is the CSC files, and I know how to use it with Mobile Odin or CWM Manager.
You are right, I don't mind factory wipe, infact I always full wipe before any firmware update.
What I want to know is about hidden.img...
Yes, I'm curious, I want to know and learn what is this image file contain.
Oh, and yes, I have flashed to XXLA4 using hidden.img from XXLA4...
It works.. But I'm still curious and want to know what is it..
Thanks again~
Bump. Any more info on what's inside the hidden.img file?
Shammyh said:
Bump. Any more info on what's inside the hidden.img file?
Click to expand...
Click to collapse
Use magic iso to mount that image file and see whats inside it
Well on my Motorola, it contains boot animation, wallpapers, carrier related settings (subsidy lock), and nvitems.
Hope that helps
It has binary counter trigger!! X10 lol
SHOT from my LOADED GT-N7000!!
Hidden.img is exclusive to carrier branded Stock ROM's.
In case of such ROM's cache.img + hidden.img together constitute the CSC. So my guess is hidden.img has some of the carrier specific bloat!
EDIT: Just saw that the hidden.img from the xwla4 ROM contains files related to the Samsung Gamehub (ngmoco)!
Thnx!
Delete hidden.img
The-Droidster said:
Hidden.img is exclusive to carrier branded Stock ROM's.
In case of such ROM's cache.img + hidden.img together constitute the CSC. So my guess is hidden.img has some of the carrier specific bloat!
EDIT: Just saw that the hidden.img from the xwla4 ROM contains files related to the Samsung Gamehub (ngmoco)!
Thnx!
Click to expand...
Click to collapse
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?
sherbie said:
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?
Click to expand...
Click to collapse
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit
mojo_jodroid said:
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit
Click to expand...
Click to collapse
Hello, I compressed them together and installed Unified Android Toolkit what I need to do on Unified Android Toolkit? what's the next step, please help
sherbie said:
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?
Click to expand...
Click to collapse
Open the zip with Total Commander, delete hidden.img and rename the file without the .md5 extension.
Only leave .tar at the end of the file name.
vijai2011 said:
Use magic iso to mount that image file and see whats inside it
Click to expand...
Click to collapse
pure BS. MagicISO or Daemon tools cannot open this file.
vratnik said:
pure BS. MagicISO or Daemon tools cannot open this file.
Click to expand...
Click to collapse
Ignorance is a bliss. Go google yourself on simg2img instead of following a 4 year old tip
mojo_jodroid said:
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit
Click to expand...
Click to collapse
Here's a detailed tutorial: http://www.droidviews.com/fixing-odin-firmware-installation-failed-at-hidden-img-issue-on-samsung/
hi, please i need help about unpack and repack galaxy mini stock roms (.tar.md5) cause i wanna remove bootloader (arm11boot) to avoid physical domage to my mini;
i didn't find the rom what im searching for in this thread: http://forum.xda-developers.com/showthread.php?t=1551586
i need this middle east rom: http://www.hotfile.com/dl/155191960/b13d98c/S5570JPKT2_S5570OJPKT2_EGY.zip.html but without bootloader;
thankx
Send a pm to annson08.. Include the link and he may do it for you..
kitrax59 said:
Send a pm to annson08.. Include the link and he may do it for you..
Click to expand...
Click to collapse
Don’t give me a fish, teach me how to fish.
I would like to help you fishing but I'M NOT RESPOSIBLE IF YOU ENDED BY CACHING A SHARK
I had downloaded a rom with removed bootloader from annson08 thread, by opening the .tar archive i noticed that he did just removed the arm11boot file from the package nothing else.
so maybe removing this file from your ROM and flashing it like usual will do the trick
Do It At Your Own Risk
Unpack rom..search bootanimation.zip.....replace with any other of ur choice
....repack
Sent from my GT-S5570 using xda premium
bilel2301 said:
hi, please i need help about unpack and repack galaxy mini stock roms (.tar.md5) cause i wanna remove bootloader (arm11boot) to avoid physical domage to my mini;
i didn't find the rom what im searching for in this thread: http://forum.xda-developers.com/showthre...?t=1551586
i need this middle east rom: http://www.hotfile.com/dl/155191960/b13d...Y.zip.html but without bootloader;
thankx
Click to expand...
Click to collapse
unpack rom and its contents
open boot.image
in that remove arm11 boot
pack your rom !
flash it via odin
abdovar said:
I would like to help you fishing but I'M NOT RESPOSIBLE IF YOU ENDED BY CACHING A SHARK
I had downloaded a rom with removed bootloader from annson08 thread, by opening the .tar archive i noticed that he did just removed the arm11boot file from the package nothing else.
so maybe removing this file from your ROM and flashing it like usual will do the trick
Do It At Your Own Risk
Click to expand...
Click to collapse
i know that he just removed arm11boot but when i did that with many method i didn't succed to add it to "odin multi downloader" it crashs every time when i add the new file without bootloader i think that is not just unpack,remove and repack there is something special to make odin fish a fish not a shark
bilel2301 said:
i know that he just removed arm11boot but when i did that with many method i didn't succed to add it to "odin multi downloader" it crashs every time when i add the new file without bootloader i think that is not just unpack,remove and repack there is something special to make odin fish a fish not a shark
Click to expand...
Click to collapse
He wrote it in his thread...
I believe the method requires linux (/cygwin)...
Edit: no, I couldn't find it... :sad:
Typed on a small touchscreen
a.cid said:
He wrote it in his thread...
I believe the method requires linux (/cygwin)...
Edit: no, I couldn't find it... :sad:
Typed on a small touchscreen
Click to expand...
Click to collapse
yeah i used cygwin too but i failed to make the output file work on odin!!!
i used this method from yagya:
Code:
cd firmware_directory
// Goes inside firmware directory
tar -cf firmware_name.tar amss mibib oemsbl qcsbl boot.img recovery.img system.rfs csc.rfs
// This will create a tar_file named firmware_name.tar containing all the files mentioned afterwards. You'll need to check if all files except arm11boot are included or not and add (or remove) to or from above list.
md5sum firmware_name.tar >> firmware_name.tar
// Checks md5sum of the tar file.
mv firmware_name.tar >> firmware_name.tar.md5
// Renames the firmware file. The outcome of this is your flashable zip file.
[optional] gzip firmware_name.tar.md5
//zips the firmware_name.tar.md5 file as gz format. It is easier while sharing the file since it reduces the file size by almost 50 %.
you did everything correct but the problem of Odin crashing is its a md5 file then you remove the arm11boot md5 of file changes which makes the Odin crash
steps to correct it:-
1. extract everything from package
2. delete arm11boot
3. then download a software which can create a tar package
4. with that software create an empty tar package
5. put all the files in that tar package
then then you are ready to flash
dhlalit11 said:
you did everything correct but the problem of Odin crashing is its a md5 file then you remove the arm11boot md5 of file changes which makes the Odin crash
steps to correct it:-
1. extract everything from package
2. delete arm11boot
3. then download a software which can create a tar package
4. with that software create an empty tar package
5. put all the files in that tar package
then then you are ready to flash
Click to expand...
Click to collapse
it doesn't work also!!!! i flash it with (.tar) odin freeze in "download amss" and with (.tar.md5) odin crash also like using cygwin!!! i think that i really need help from annson08, i pm him but he didn't answer :/ :/
bilel2301 said:
it doesn't work also!!!! i flash it with (.tar) odin freeze in "download amss" and with (.tar.md5) odin crash also like using cygwin!!! i think that i really need help from annson08, i pm him but he didn't answer :/ :/
Click to expand...
Click to collapse
hey sorry for the late reply, really busy at the moment. I believe yagya made a tutorial about this...wait....hmmmm....ahh here it is,
http://handyinformation.freevar.com/showthread.php?tid=8&pid=12#pid12
that's not how I do things but that link also works.
annson08 said:
hey sorry for the late reply, really busy at the moment. I believe yagya made a tutorial about this...wait....hmmmm....ahh here it is,
http://handyinformation.freevar.com/showthread.php?tid=8&pid=12#pid12
that's not how I do things but that link also works.
Click to expand...
Click to collapse
the link that you send to me is the link of my thread in yagya's forum
i try yagya's method but it doesn't work for me :/ :/
please when you have time pm how to do it thankx
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!
Hey there,
I've tried searching about the forum and haven't been able to find the specifics about this:
I've got my un-encrypted .tar.md5 files from the last initialization, but there are 3 files and I'm wondering how I go about converting them into one image or what's actually necessary so that I can have the added convenience/stop burdening sammys server.
AP_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: system.img, recovery.img and boot.img.
BL_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: sboot.bin and param.bin
CSC_XAR_T710XAR2BOL3_CL6649608_QB7749942_REV03_user_low_ship.tar.md5 contains: hidden.img, GTS28WIFI_EUR_OPEN.pit and cache.img.
Let me know, thanks. :good:
wirelesskebab said:
Hey there,
I've tried searching about the forum and haven't been able to find the specifics about this:
I've got my un-encrypted .tar.md5 files from the last initialization, but there are 3 files and I'm wondering how I go about converting them into one image or what's actually necessary so that I can have the added convenience/stop burdening sammys server.
AP_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: system.img, recovery.img and boot.img.
BL_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: sboot.bin and param.bin
CSC_XAR_T710XAR2BOL3_CL6649608_QB7749942_REV03_user_low_ship.tar.md5 contains: hidden.img, GTS28WIFI_EUR_OPEN.pit and cache.img.
Let me know, thanks. :good:
Click to expand...
Click to collapse
Old post i was just looking fo the answer myself for my Tab S4. Your post showed up in my Google search.. You don't need them in one image, as odin has AP BL and CSC.. So all you need to do is drop them in the right tabs and hit flash job done! Well i am just guessing will try and let you know!
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.