I have been doing a lot of restoring, it would be nice to just be able to push the flash rather than geting an os installed, installing a recovery and then recovering.
I saw something for another samsung device and it involved dd'ing files and then putting them into a tar. but i suspect the /dev/xxxxxx files would be a different name on the GT10.1?
Thanks
Rob
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Right, but they are dumps of the /dev/system|recovery|... file systems from using dd to get a binary image, they are not the files like in a zip. which is why, if my reading is correct, zips actually get processed (extracted and moved) and the files in the odin.tar are binary dumps and they just get splatted back out into the file system like a Norton Gost restore. The trick is knowing which /dev/xxxx/ systems to pickup. I found a link right before leaving for work that seems to suggest if I get rooted and busybody on, I should be able to run an fdsik -l and get a list of the partitions.
I just got the stupid tablet back to stock ICS 4.04 this morning after running updates last night, so I hope to have some time play today.
Related
I have a basic question about the CWM recovery mod using fastboot. I just loaded the updated .img file with no problems. All works great! My question is do I have to delete the first .img file? Can we just keep loading updated. Img files using fastboot without ever deleting the old files? Won't it take up more space?
Sent from my MB860 using XDA App
Everytime you flash a new img file to the phone, it overwrites the "img file" on the phone. So no, you don't need to delete the older one. Hope that explains it.
I want to create a Odin or zip of the recovery that is on my phone. Right now I have two Fascinates, Froyo on one and GB on the other.
Is there any How-To or anything as far as that gos that can explain the process of pulling the recovery and creating the update file. I have searched the forum and the net but have not found anything.
Thanks
Here's what I think your looking for??
http://forum.xda-developers.com/showthread.php?t=1150016
Sent from my SCH-I500 using XDA App
efan450 said:
Here's what I think your looking for??
http://forum.xda-developers.com/showthread.php?t=1150016
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've tried using this method on both stock froyo, and gb... neither worked. I ripped all the info, including the personal stuff. The regular system files were the normal sizes.. the movinand.bin was 4GBs.
I tool all the files and made one single tar file, then did the md5sum, etc... using cygwin, filesize was approx 4.4GB. When I tried to flash it back with odin it fails at the beginning.
I've been thinking too... would it be possible to tar/md5 each of the files individually? Then using each of the odin slots accordingly.
What about flashing a complete stock odin img first.. then flash my apps/data/info seperate.. with odin.
Maniac
I have a couple questions about CWM and backups:
Is there a difference between flashing update.zip and installing a zip from the sdcard in CWM?
Also, let's say I make a change to boot.img and system.img and something goes wrong. Instead of flashing the backups of those two images from my computer to my phone using fastboot, can I just place them both in a zip file and install it from CWM? Would I need to include any other files?
How come a nandroid backup makes a system.ext4.tar and not a system.img? How do I turn that into a system.img?
How come I need unyaffs to read cache, data, and system.img files? I thought the filesystem was ext4 and not YAFFS?
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
marko! said:
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
So I found some links about the update-script and I'll be reading those shortly, but after skimming them I didn't see any mention of the binary. Is the binary an executable version of the same script or something else? Any links?
So what your saying is I could just skip the update.zip stuff, extract the images from the zip, and use advanced restore to flash each image? Obviously more work but it's good to know if these two processes are equivalent.
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
And also the last question about ext4 and YAFFS is still there. Thanks.
Most of those I'm really not sure. The update binary is the same for every zip. Just grab it from a rom or theme
I would go with the cwm zips. Way easier once you get them working.
sent from my Atrix via XDA premium
gsingh2011 said:
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
Click to expand...
Click to collapse
I was just looking at this too. My old recoveries from before atrix4.1 was released were all .img files and the post atrix4.1 backups are .ext3.tar (except for boot.img and recovery.img). I'm on a stock deodexed GB ROM, so I don't have any ext4 partitions. I think he changed this with the newest update so CWM can recognize the ext type and mount them appropriately.
This post should hopefully clarify a bit more than I can. I'm relatively new to all this so I'm still learning different aspects of modding. I'm guessing you have some ext4's because you're running one of the newer custom ROM's?
I have a Samsung Galaxy S 2,
It's been rooted and has CMW on it with superuser
I ve downloaded from this website, the ICS remix Rom v7.1
After saving it to my computer, I unzipped the .rar file and moved the folder in to:
phone/clockworkmod/backup (like the post tells me to)
I then rebooted my phone into recovery mode, Wiped everything and then went into backup and restore, restore from internal sd card and then chose the restore files i downloaded from the ICS remix Rom v7.1
However, when proceeding with the restore process I get messages such as
cache.img not found, data.img not found phone.img not found etc etc...
is it because all the files I downloaded are in .tar format???
Can anyone help me with this??
You should see .md5 and .img files in the backup folder. TAR files are for Odin flashing I believe.
Sent from my GT-I9100
Don't post almost identical thread's within an hour of eachother... The moderators and also the users do not appreciate this.
In regards to OP, I have no clue on that particular ROM.
If the files are in tar, they are supoused to flash with odin, but if you knew the files are in tar files, Then I suggest to learn about flashing roms more or you might end up to bricked phone
Sent from my GT-I9100 using XDA App
Hey guys.. Odin3 version3 and higher has gz support. I've been working with this for a bit and tonight I found that Odin will accept tar.md5.gz files. This is important for GNote2 users as the stock ROM is 1.2Gigs! You can get an extra 10-40% compression and 100% gaurantee that the files arrive to your users computer in the condition that you packaged them using this method. I have not found a guide on using the gz format so I thought I would write one up.
You will need:
A Linux computer
Your rom (we will call it MyROM)
How to package for Odin on Windows
I will cover packing into a single file, adding an MD5, and compressing the file down. For the purposes of this, we are working with "MyROM". You will want to call your ROM whatever you like. Just make sure to add version information to the file name so users don't get confused. Also note, the name MUST be consistent throughout the process. If you change the name, Odin can fail.
Another good tip is to put a model number in the name so there is no confusion as to what device your Odin package goes to. Several users, myself included, have 20+ Odin packages on their computer.
So first you want to turn the ROM into a single tar file and then make sure changes are written to the disk.
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./MyROM.tar;sync;
Next we want to add an MD5 to the file so Odin can check its consistancy.
Code:
md5sum MyROM.tar >> MyROM.tar;
Now we will change it into a tar.md5 file so Odin knows it has an MD5 attached to it.
Code:
mv MyROM.tar MyROM.tar.md5; sync;
Finally we will compress it with GZip. GZip is the only compression method supported by Odin.
Code:
gzip MyROM.tar.md5 -c -v > MyROM.tar.md5.gz;
You will now have a file called MyROM.tar.md5.gz.
Conclusion
The first time the file is flashed, Odin will uncompress it into MyROM.tar.md5, then check its consistancy, then flash the file. Using this method you will be transferring the smallest file possible and adding integrity checks.
notes
Note to Verizon GNote2 users: Stay away from using Odin after IROM unlock as flashing a package intended for another device will perma-lock your device into another carrier's bootloaders. Especially stay away from GS3 as the displays are not compatible.
good ****! this is def useful
Awesome news! Any test results with the older versions? If not one click solutions may not benefit.. but servers and users will by cutting the downloads even more!
Sent from my SPH-L900 using Tapatalk 2
Windows OS
How can I do it on a Windows computer?
MAQ7 said:
How can I do it on a Windows computer?
Click to expand...
Click to collapse
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
cygwin.
Mine all work
imnuts said:
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
Click to expand...
Click to collapse
adrynalyne said:
cygwin.
Mine all work
Click to expand...
Click to collapse
I managed to make tar on Windows using cygwin :good:.
Thank you
Interesting adam, I always compressed the whole odin package into a rar file (same effect but one step extra). Also I made an article about odin a while ago:
http://broodplank.net/?p=496
Btw, did you know that you can put cwm backups (ext4.tar) inside an odin package? It's the first odin image I ever saw, filled with a CWM backup, and yes it works XD
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Last thing, Odin packages can be a last resort fix, believe me, many users reported that flashing my rom broodROM_RC5.tar.md5 (which contains about 13 files, you can imagine how many partitions it includes) fixed their phone when nothing else worked.
So thank you Samsung for leaking your tool, A world with Samsung Kies only would be a very sad "softbricky" world
broodplank1337 said:
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Click to expand...
Click to collapse
TAR files preserve file permissions.
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
mrRobinson said:
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
Click to expand...
Click to collapse
Only on the Verizon Galaxy Note. All others are IROM locked. The IROM lock prevents flashing of an improper SBOOT. An unlocked VZWGNote 2 can flash any SBOOT.
Other than this specific case, adding third party tools other than ZIP compression means your user must download special tools.
Extra files?
If I were to pack an extra README.txt file into the tar before prepping it for Odin, would Odin then ignore it during the flash? Obviously there's no entry for what to do with an extraneous text file in the pit, so hopefully Odin would just disregard it.
I happened to find out today that heimdall has support for "Heimdall Firmware Packages." You can read and write them from the heimdall frontend (the 1.3 FE binary is forward compatible with my source built 1.4 heimdall). What's interesting, is that the format is almost identical to odin's format. It is still packaged in a tar file, and it contains the same system.img, boot.bin, recovery.bin etc. files you'd find in the Odin tar. By default it's format is Package.tar.gz. The only significant difference is the addition of a firmware.xml file that identifies the proper partition for each image file, as well as the target platform, the author, and other details like that.
So I got curious. I took a Package.tar.gz file generated by heimdall, and repackaged it as a Package.tar.MD5.gz file. Heimdall has no problem reading this! So the upshot is, Odin now handles the .gz, so as long as Odin isn't bothered by an extra firmware.xml file inside the tar, the same format would be compatible with either tool.
PS> Don't flame me about flash counters or bricked phones. I do understand that Odin/Heimdall are only particularly relevant for returning a phone to stock, but that's still a very important functionality and it would be great to have a unified format.