Yes guys,
The question is obvious. Normally we flash 4-file Roms with pit file.
But, what would happen if I flash 1-fle Rom (namely XXLSZ) via PC Odin with a pit file and Re-Partition TICKED?
TIA
Being a senior member you should know better. You might be new here but rules are rules. REPORTED
Guys, Sorry for opening the Thread in wrong section. I was subscribed to Android Development Thread and forgot to switch to Q&A thread.
Aaaaah I am so sorry for disturbing people.
Though, I would appreciate if someone could answer my question.
ardicli2000 said:
Yes guys,
The question is obvious. Normally we flash 4-file Roms with pit file.
But, what would happen if I flash 1-fle Rom (namely XXLSZ) via PC Odin with a pit file and Re-Partition TICKED?
TIA
Click to expand...
Click to collapse
If you select pit file (selecting pit itself will check repartition box) then it will make repartition, regardless of how many other files you have selected.
Basically when you flash single stock tar file, that already contains full package (system.img, kernel,modem, CSC )
while in case of leaked ROM it having separate files for Modem and CSC and you have to select along with PDA.
Even you select pit files without selecting other any files(for PDA/Modem/CSC), it will make repartition.
dr.ketan said:
If you select pit file (selecting pit itself will check repartition box) then it will make repartition, regardless of how many other files you have selected.
Basically when you flash single stock tar file, that already contains full package (system.img, kernel,modem, CSC )
while in case of leaked ROM it having separate files for Modem and CSC and you have to select along with PDA.
Even you select pit files without selecting other any files(for PDA/Modem/CSC), it will make repartition.
Click to expand...
Click to collapse
Will it work at the end?
I mean, if I flash a Rom along with a pit file, it won't boot if is no boatloader in it, so to speak.
So, what is the situation for XXLSZ? Would it boot?
But you basically say that if 1-file contains every necessary sub-files, then there will be no problem.
Pit will make partition, and then files will be flashed.
Basically there is no meaning to use pit file if there is no messing with partition.
I mean, if I flash a Rom along with a pit file, it won't boot if is no boatloader in it, so to speak.
So, what is the situation for XXLSZ? Would it boot?
Click to expand...
Click to collapse
Now regarding particular LSZ, as this file having bootloader, so using with pit it will boot
another situation
Your ROM file doesn't have bootloader and you are using pit
still it will boot unless you have used custom pit and that mess up with existing.
Phone only won't boot if you have used wrong pit
Pit file just define partition table, it won't format device, so if your existing partition table is same with one you are using in pit, it won't make any difference.
dr.ketan said:
Basically there is no meaning to use pit file if there is no messing with partition.
Now regarding particular LSZ, as this file having bootloader, so using with pit it will boot
another situation
Your ROM file doesn't have bootloader and you are using pit
still it will boot unless you have used custom pit and that mess up with existing.
Phone only won't boot if you have used wrong pit
Pit file just define partition table, it won't format device, so if your existing partition table is same with one you are using in pit, it won't make any difference.
Click to expand...
Click to collapse
Hmm.. I did not know that. I knew that whatever happens, if I use pit file while flashing, it will format every partition, including /sdcard nad delete even photos, etc.
I did not know that nothing will happen if I use the pit file which has the same partition table.
Thanks again doctor.
Related
Hi, I'm trying to use Odin 1.3 to flash JF7, and the SRE mod. I was running JF6 with the SRE mod. So far, I've used Odin one-click to wipe (with phone booted), reformatted internal sd (after reboot), and one-click restored to factory JF6 (from download mode). Now, my phone is booted, and not connected to USB. I have "Odin3. [Android + SLP]" open, and extracted the I897UCJH7.rar file, and also extracted the resulting I897UCJF7_homebinary.rar file.
Here's my question--how the hell do I use Odin 3?!? I've read that it can be picky, and I would rather just do it right the first time I've read all this stuff about .tar and .pit files, but cant seem to find them from any of the rars i've extracted. Odin3 is able to find I897UCJ7_homebinary.rar when opening a file in the "PDA" option of the program. When opening a file from the "Phone" option of the program, I'm able to open the aforementioned rar, and also the modem.bin file in the folder extracted from I897UCJ7_homebinary.rar.
So, do I open the file from the PDA option, or the PHONE option? Also, what's the deal with these pit and tar files? Do I need to load either to flash JF7?
I just can't seem to find a comprehensive overview of the program anywhere....
Thanks a lot!
Edit--turns out I897UCJF7_homebinary is actually a .tar file. The rest of questions still stand
Edit--It also seems that the I897UCJF7_homebinary.tar might just have to be loaded into the PDA sections of the app. Not sure about this yet.
Edit--I think the answer might be here, post #194: http://forum.xda-developers.com/showthread.php?t=780887
j1mb34m said:
Hi, I'm trying to use Odin 1.3 to flash JF7, and the SRE mod. I was running JF6 with the SRE mod. So far, I've used Odin one-click to wipe (with phone booted), reformatted internal sd (after reboot), and one-click restored to factory JF6 (from download mode). Now, my phone is booted, and not connected to USB. I have "Odin3. [Android + SLP]" open, and extracted the I897UCJH7.rar file, and also extracted the resulting I897UCJF7_homebinary.rar file.
Here's my question--how the hell do I use Odin 3?!? I've read that it can be picky, and I would rather just do it right the first time I've read all this stuff about .tar and .pit files, but cant seem to find them from any of the rars i've extracted. Odin3 is able to find I897UCJ7_homebinary.rar when opening a file in the "PDA" option of the program. When opening a file from the "Phone" option of the program, I'm able to open the aforementioned rar, and also the modem.bin file in the folder extracted from I897UCJ7_homebinary.rar.
So, do I open the file from the PDA option, or the PHONE option? Also, what's the deal with these pit and tar files? Do I need to load either to flash JF7?
I just can't seem to find a comprehensive overview of the program anywhere....
Thanks a lot!
Edit--turns out I897UCJF7_homebinary is actually a .tar file. The rest of questions still stand
Edit--It also seems that the I897UCJF7_homebinary.tar might just have to be loaded into the PDA sections of the app. Not sure about this yet.
Edit--I think the answer might be here, post #194: http://forum.xda-developers.com/showthread.php?t=780887
Click to expand...
Click to collapse
Yeah, that is pretty much all you need to do. Make sure you are using the full odin program and not the one click.
When I first flashed my GT-I9000 I didn't know about the ClockworkMod backup option, so used the Dump option in ODIN3 - thinking this would cover all bases.
Now I've got a .odin3.dump file and don't know what to do with it.
The PDA field only allows .tar .md5 and .smd files
but the PHONE field allows .bin files
Do I rename it to .bin and use it as a PHONE file?
If so - What would be the settings to flash i.e. 512.pit / Re-Partition / EFS Clear?
I've founds lots of posts asking what to do with the .odin3.dump file, but no answers - I'm sure a lot of folk would welcome an answer to this.
GalaxyS_JAB said:
When I first flashed my GT-I9000 I didn't know about the ClockworkMod backup option, so used the Dump option in ODIN3 - thinking this would cover all bases.
Now I've got a .odin3.dump file and don't know what to do with it.
The PDA field only allows .tar .md5 and .smd files
but the PHONE field allows .bin files
Do I rename it to .bin and use it as a PHONE file?
If so - What would be the settings to flash i.e. 512.pit / Re-Partition / EFS Clear?
I've founds lots of posts asking what to do with the .odin3.dump file, but no answers - I'm sure a lot of folk would welcome an answer to this.
Click to expand...
Click to collapse
I would... lol Ever find out?
Nope, still hoping someone will reply with what the dump file is for.
I have read several tutorials and some say that I should only use pit file when there are 3 files pda, modem and csc. Others I have seen isntructions to use the pit file when there is 1 pda file.
Which one is it? Are 3 files and repartition better than 1 file and no repartition?
WoodPusher said:
I have read several tutorials and some say that I should only use pit file when there are 3 files pda, modem and csc. Others I have seen isntructions to use the pit file when there is 1 pda file.
Which one is it? Are 3 files and repartition better than 1 file and no repartition?
Click to expand...
Click to collapse
You select repartition when you want to flash the stock RFS system or when you have formatted your file system to EXT2/EXT4/JFS etc using custom ROM or lag fix.
You dont need to check repartition every time you flash the phone.
One PDA file is usually a cooked file which contains MODEM as well as Multi CSC. So you have to see yourself what you are flashing. Usually, leaked firmwares have all 3 files seperate that you flash but custom ROMS combine all of them into 1 PDA file.
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/
Last night, I tried flashing the Android 11 GSI to my S9 Exynos to try out. Unfortunately, it ended in a bootloop, so I decided to return to stock.
For some reason, when I flashed stock, the OS only recognised 32GB of my 64GB of internal storage. I concluded that something went wrong when flashing the GSI and the partitions on the device had been all messed up, and that I needed to repartition. To do this, you must reflash the firmware and use the repartition function in Odin.
Boot your device into Download Mode (press on, vol down, and bixby at the same time). Go to the folder where you extracted the firmware, and rename the CSC (not HOME_CSC) file to remove the .md5 extension. Then use an archive extractor that works with .tar files, I used 7-zip. Extract the CSC into a folder and then go into it, and look for a file ending in .pit. In my case, that's STARLTE_EUR_OPEN.pit. That's the file you need to repartition. Now rename the CSC file back to .tar.md5.
Open Odin, and select all the firmware (BL, AP, etc) as you would usually. Then go to the options tab and check the re-partition box. Then go into the Pit tab. You'll get a warning saying it's only for engineers, but do not worry, anybody can use it if they know how to. Click on the PIT button, and then navigate to your CSC folder and select the .pit file.
Once everything is loaded in, click start. The firmware will now flash and the device will repartition. Once it's finished, your device should reboot. Now, wait for it to load, It'll take a few minutes.
Once loaded, set everything up and then go to Settings --> Device Care --> Storage. You'll see your device has the full 64GB/128GB/256GB it came with. You have successfully restored and repartitioned your Galaxy S9.
I hope this tutorial helped you in some way.
AndroidGuy087 said:
Last night, I tried flashing the Android 11 GSI to my S9 Exynos to try out. Unfortunately, it ended in a bootloop, so I decided to return to stock.
For some reason, when I flashed stock, the OS only recognised 32GB of my 64GB of internal storage. I concluded that something went wrong when flashing the GSI and the partitions on the device had been all messed up, and that I needed to repartition. To do this, you must reflash the firmware and use the repartition function in Odin.
Boot your device into Download Mode (press on, vol down, and bixby at the same time). Go to the folder where you extracted the firmware, and rename the CSC (not HOME_CSC) file to remove the .md5 extension. Then use an archive extractor that works with .tar files, I used 7-zip. Extract the CSC into a folder and then go into it, and look for a file ending in .pit. In my case, that's STARLTE_EUR_OPEN.pit. That's the file you need to repartition. Now rename the CSC file back to .tar.md5.
Open Odin, and select all the firmware (BL, AP, etc) as you would usually. Then go to the options tab and check the re-partition box. Then go into the Pit tab. You'll get a warning saying it's only for engineers, but do not worry, anybody can use it if they know how to. Click on the PIT button, and then navigate to your CSC folder and select the .pit file.
Once everything is loaded in, click start. The firmware will now flash and the device will repartition. Once it's finished, your device should reboot. Now, wait for it to load, It'll take a few minutes.
Once loaded, set everything up and then go to Settings --> Device Care --> Storage. You'll see your device has the full 64GB/128GB/256GB it came with. You have successfully restored and repartitioned your Galaxy S9.
I hope this tutorial helped you in some way.
Click to expand...
Click to collapse
I am new to flashing some Roms. Can you please tell me what is meant by resetting odin? How do you reset odin? I need all the help that I can get these directions are very technical. Thank You
will you lose data doing this?