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.
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.
can anyone tell what is the difference between a .tar file and .tar.md5 file? cos i downloaded a pda file that is .tar.md5 from here:
http://hotfile.com/dl/104777809/7737...A.tar.rar.html
and normally when flashing via odin theres always the .tar file only...
so i renamed the md5 file by deleting the ending(.md5) and seems like nothing changed to the file size etc(is it still safe to use in odin?). just need to know which file should i use to flash the single pda, the .tar or .tar.md5?(which is safer?)
thanks!!!
mab71 said:
can anyone tell what is the difference between a .tar file and .tar.md5 file? cos i downloaded a pda file that is .tar.md5 from here:
http://hotfile.com/dl/104777809/7737...A.tar.rar.html
and normally when flashing via odin theres always the .tar file only...
so i renamed the md5 file by deleting the ending(.md5) and seems like nothing changed to the file size etc(is it still safe to use in odin?). just need to know which file should i use to flash the single pda, the .tar or .tar.md5?(which is safer?)
thanks!!!
Click to expand...
Click to collapse
Ahahahaha for real? Nothing changed to the file size? . You know my HDD got suddenly light as I deleted some big files
Sorry, really sorry for that . I just couldn't resist .
the file is the same, has nothing to do with the "ending"
you can flash it .the md5 just suggest it has a checksum/hash maybe there
http://goo.gl/SGj1d
Just Google MD5 .
Its a verification of the file is all ..
jje
looking for some 1 clicks for kk4. need both with and without bootloaders. that or a guide to making them and a copy of the stock kk4 with bootloaders. thanks in advance.
^ In the i897ucKF1 leaked Firmware .rar download, there is an Odin DL Creator that u can use to make One Click Downloaders. There are Manuals included in there as well, but unfortunately they got corrupted somewhere along the way and I could never find a way to open and read them. But the process to build the One Click was still easy enough to figure out.
Run the DLCreator v1.8 then choose the Downloader tab and then navigate to where this Creator file is and select the Odin3Execution v1.81 and then simply proceed down the tabs loading the files, select the Options u want (re-partition, auto reboot) and then select the File Name, then Downloader Title. After that is done select the Make Downloader tab.
Now I did encounter freezes/force closes (if u will) with the Creator, but I would just simply have to start over and then it would work. The i897ucKF1 firmware, u can get from here... http://www.sammobile.com/forum/showthread.php?t=306 (u will probably have to register and log in)
And as an alternative there is the Heimdall One-Click - ROM Packaging and Distribution System. See the link here...http://forum.xda-developers.com/showpost.php?p=19386742&postcount=1
4-2ndtwin said:
^ In the i897ucKF1 leaked Firmware .rar download, there is an Odin DL Creator that u can use to make One Click Downloaders. There are Manuals included in there as well, but unfortunately they got corrupted somewhere along the way and I could never find a way to open and read them. But the process to build the One Click was still easy enough to figure out.
Run the DLCreator v1.8 then choose the Downloader tab and then navigate to where this Creator file is and select the Odin3Execution v1.81 and then simply proceed down the tabs loading the files, select the Options u want (re-partition, auto reboot) and then select the File Name, then Downloader Title. After that is done select the Make Downloader tab.
Now I did encounter freezes/force closes (if u will) with the Creator, but I would just simply have to start over and then it would work. The i897ucKF1 firmware, u can get from here... http://www.sammobile.com/forum/showthread.php?t=306 (u will probably have to register and log in)
And as an alternative there is the Heimdall One-Click - ROM Packaging and Distribution System. See the link here...http://forum.xda-developers.com/showpost.php?p=19386742&postcount=1
Click to expand...
Click to collapse
thanks a ton. i remember seeing a guide somewhere on converting cwm zips to odin tars. i knew i kept my noobuntu install for something lol.
found the odin creator and a stock kk4 md5 ball. time to do some research on the proper way to remove the bootloaders.
EDIT: sorry for double post. please merge if possible.
Use an Archiver (IZArc, 7zip, etc.) and extract the .tar out of the .rar that u downloaded. Then click on the name of the .tar.md5 to rename it and simply delete the .md5 from the name. Select yes to make the change. Open the .tar and then u will see the files. Bootloaders are of course the boot.bin and sbl.bin files (they r in the main.tar file. Think it was named Code something blah blah). Drag them to desktop to keep in a seperate file and then just delete them out of the .tar file. The param.lfs of course contains the initial bootslash jpeg image. And etc., etc.
Also, just fyi, this was a full wipe leaked firmware. --> (Edit: the KF1 was a full wipe, all others since have only wiped /cache after the install. And the other leaks since KF1 have only been in single .tar file, where as the kf1 was in 3 different .tar files)
Sent by XDA Premium App
4-2ndtwin said:
Use an Archiver (IZArc, 7zip, etc.) and extract the .tar out of the .rar that u downloaded. Then click on the name of the .tar.md5 to rename it and simply delete the .md5 from the name. Select yes to make the change. Open the .tar and then u will see the files. Bootloaders are of course the boot.bin and sbl.bin files (they r in the main.tar file. Think it was named Code something blah blah). Drag them to desktop to keep in a seperate file and then just delete them out of the .tar file. The param.lfs of course contains the initial bootslash jpeg image. And etc., etc.
Also, just fyi, this was a full wipe leaked firmware.
Sent by XDA Premium App
Click to expand...
Click to collapse
KK4 isn't full wipe...
Sent from my SGH-I897 using xda premium
^ Yep, u r correct. My bad. I was thinking about the KF1 leak. Thanks for the correction.
4-2ndtwin said:
^ Yep, u r correct. My bad. I was thinking about the KF1 leak. Thanks for the correction.
Click to expand...
Click to collapse
Its fine, you know just don't want people going around with false info!
Sent from my SGH-I897 using xda premium
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.
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.