I have used LGUP and selected all partitions from DUMP. Is it enough if something goes wrong, do I have everything I need? It must have specific extension?
Yes you have everything you need. Partitions dont need a file extension you can add .img to the file names if you want, which will make them image files. They can all be flashed via fastboot or twrp using console commands just the way they are.
Related
I've compiled and installed a modded kernel. I'm trying to figure out how to load AOSP compiled binaries. I've tried using adb flash_image system /sdcard/system.img, but I get "failed with error: 6." Does anyone know what this means or how to load system.img on a Galaxy Tab from VZW? I'm working on reactivating the phone dialer...
the galaxy tab has nothing like fastboot, so its pretty hard to flash it! but u can try to overwrite a stock factory.rfs with the files from ur system.img and flash via odin!
That sounds like a great idea. However, I'm trying to figure out how to put the vendor specific drivers in the system.img, which is mountable and editable. If I could get my hands on an original stock system.img, that'd be awesome.
Sent from my SCH-I800 using XDA App
As far as I know, the Tab doesn't use mtd file system, so I don't think it uses .img extensions.
Not positive though. Somebody correct me if I'm wrong.
I know for a fact that img files are created as the output of an Android system build. This img can be broken apart with standard Linux tools. I've already done this. I've also mounted factoryfs.rfs to a local directory, which allows me to move apps to and from the file system.
Sent from my SCH-I800 using XDA App
If you have a md5 of it too, you should be able to flash it via an advanced restore in CWM recovery. That is if it is only the data that is flashed to /system. otherwise I would suggest converting it to a .fs or .tar and flash via heimdall or Odin (respectively).
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
Landroid said:
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
Click to expand...
Click to collapse
thanks! this was very easy to use
I am a beginner, and I have compiled a game built with C. The instructions I have say that I have to flash the final .img file to a separate partition on my SM-N900P. Now I have successfully downloaded the stockfirmware, unpacked it with mkbootimg, built my own dtb.img and flashed the phone. (Side note: I got an error about Samsung Keyboard, which if you know how I can address I would be grateful). I do not know how / where to put the .img file I compiled though. Do I pack it when I tar my files?
I've been scouring the interweb looking for a way to take a stock tar file and convert it to a zip file that will flash with twrp. I know it can be done, but thus far I'm not happy with the processes I've found... how do you guys do it?
The stock TAR files contain partitions in IMG format - an all in one file system, and in this case using EXT4 formatting.
In order to create a ZIP, you need to access the files on the partition, which means finding a way to mount those IMG partitions to copy their contents, or find a piece of software to extract from them w/o mounting. Since they are EXT4, you can probably assume a Windows solution isn't available (EXT4 is Linux). Some utilities may exist to handle EXT4 on Windows, but finding one that knows EXT4 and can extract/mount an IMG file is pretty specific.
EDIT : found a utility for you - http://forum.xda-developers.com/showthread.php?t=2285831
If you can somehow get the files out of the archive, you'll need to find a tutorial on the structure of a flashable ZIP. Generally, its just folders and files but there is also a META-INF folder, scripts to install and set permissions, etc. There are likely threads here on XDA that can detail these steps.
Spitzaf, thanks so much! I was hoping for just such a tool
Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Teracotta said:
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Click to expand...
Click to collapse
It depends on the image, boot, recovery, system etc and what you want to do with it?
ashyx said:
It depends on the image, boot, recovery, system etc and what you want to do with it?
Click to expand...
Click to collapse
I figured out the issue.
The earlier firmwares list the files as .img, but they are in fact .img.ext4 files. I renamed them, then converted them to proper .imgs and it worked.
Thanks you for giving a response.