so.. i was going through some folders i have saved on my HDD.
i browse through my android stuffs folder and i have a folder called "stock FW" which contains:
flash_image
recovery-dump-t.img
V10L_00.kdz
i have awful memory and don't remember what these came from/what they are
can anybody help?
Recovery dump is probably a dump of the stock recovery.
And this
ah i see so i have a copy of stock 2.2 rom? haha saves me the trouble of looking for it.
flash_image is the binary used for flashing custom recovery through the shell.
Sent from my LG-P500 using XDA App
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 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?
Does anybody know of a tool that will install roms using a computer? I just want to be able to use a computer program to install roms without messing around with the phone.
I haven't had much luck with "adb shell recovery --update_package=/sdcard/rom.zip".
Or does anybody know of a way to convert the updater-script files in flashable zips into Windows batch files?
To convert zips into a flashable zip.. You will have to make some edit in "Meta-inf" folder
Brady_4love said:
To convert zips into a flashable zip.. You will have to make some edit in "Meta-inf" folder
Click to expand...
Click to collapse
I'm not looking for flashable zips though. I want to be able to install roms without scrolling around with the volume buttons in recovery. Such as a tool that could take a flashable zip, look at the update-script and then push all the files directly to /system and the other correct partitions via adb.
Well That Would Be Great But Recovery Flashing Isn't Hard And Why Can't You Flash A ROM Using Recovery?
Sent from my SAMSUNG-SGH-T769 using xda premium
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.
I am having issues with TWRP and partition on the device. I downloaded a new rom, which is in /SDCARD/Download directory. I can see it just fine using Root Explorer.
When I boot recovery, my /SDCARD/Download shows files that didn't exist before. Not only is the newly downloaded rom file (with .zip extension) not there, an OLD rom file is, one that existed before I wiped it and started over from a TWRP backup.
Its almost like there are 2 entire partition living on the device. Oh and one other thing: I just started from scratch again (not a recovery) and already have 8GB of space taken. Its under the "OTHER" tab in Phone Storage.
Is there anyway I can just delete everything and start from scratch? Will installing a stock T Mobile RUU do this? If I go that route, do I need to unlock the bootloader again / root again?
Have you flashed to and from 4.2 roms? You can find the other files in twrp by going up to the root folder and then data/media. You could ruu to get rid of it but it'll pop up again if you flash from 4.1.2 to 4.2.2 and back.
Sent from my HTC One using Tapatalk 4
Had this happen to me when I tried a 4.3 Rom and went back to stock T-mo Rom. Used a file explorer to find file O(I think) and transferred all my files back to original sdcard folder.
Sent from my HTC One using XDA Premium 4 mobile app
Well I think I found the problem. I was browsing my sd card using root browser looking for a Rom file (trickdroid.zip). I saw it before in the sdcard/download folder when using the file browser in twrp. But now it's not there.
So I start to pry through other folders and I notice a new folder: "0" zero. A folder called 0 with and entire sdcard folder structure within it. I look in the new download folder and there is.my missing file.
I'm curious how this new zero folder came to be. I have a theory, I did reinstall a Rom without wiping and I think that did it. I usually always wipe but specifically didn't this time because I have a twrp backup that I need to save.
I.take it the OS is now using the regular sdcard path? How can I tell twrp to look in that path for the backup (if I move it there)? When you hit restore in twrp I don't think it lets you browse for the backup. It assumes it's in the "default" spot...
Sent from my HTC One using xda app-developers app