i have a system.img file
file system.img command shows
system.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
so when i tried to convert it to ext4 using simg2img,following error comes
simg2img system.img sys.ext4.img
Invalid sparse file format at header magi
Failed to read sparse file
please help me to convert it to ext4
joel george alex said:
i have a system.img file
file system.img command shows
system.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
so when i tried to convert it to ext4 using simg2img,following error comes
simg2img system.img sys.ext4.img
Invalid sparse file format at header magi
Failed to read sparse file
please help me to convert it to ext4
Click to expand...
Click to collapse
ok solved ,just mounted it in ubuntu:cyclops::cyclops::cyclops:
Related
What is the boot process used on the Minix Neo x5/x7? And what are the formats/contents of each NAND (aka ROM) partitions?
Code:
misc /dev/block/mtdblock0 4194304
kernel /dev/block/mtdblock1 8388608
boot /dev/block/mtdblock2 16777216
recovery /dev/block/mtdblock3 16777216
backup /dev/block/mtdblock4 402653184
cache /dev/block/mtdblock5 134217728 - /cache 126M ext4
userdata /dev/block/mtdblock6 4294967296 - /data 3.9G ext4
kpanic /dev/block/mtdblock7 4194304
system /dev/block/mtdblock8 536870912 - /system 511M ext4
user /dev/block/mtdblock9 11010048000- /mnt/sdcard 10.2G
What is the boot process for the Minix Android sticks and boxes? I want to know so I can understand/manipulate the configuration. I know that people to make up new 'rom's for the systems know how to produce these '.img's, but I haven't seen it documented for those who want to get in on the act. I know how this is done on some other Linux installations, but want to know how Minix does it for their Android system.
I can see that the 'system', 'cache', 'userdata' and 'user' are normal linux filesystems that can been seen by mounting them. I assume 'boot' is some compressed bootloader code -- perhaps not the usual Android bootloader. 'kernel' is the, perhaps compressed, binary executable for the kernel that must be loaded and executed? 'recovery' seems to be uncompressed (ie you can see meaningful strings in it) -- I thought it might be a duplicate (backup) of 'boot', but its not. 'backup' seems to be uncompressed as well. No clue what 'misc' has.
I assume that on power up, some real ROM (R/O memory) loads (and decompresses?) some code from the 'boot' partition and that code loads the kernel and some root filesystem and starts things up. I know what the /init program in Android does (reading the /init.rc and other files) and mounting other file systems etc.
Can anyone share a link to the source code, or a replacement build for the NAND partition images (ie ROM .img) so I can see what it does?
System is the ROM. Misc stores all kinds of settings. As for the code.... Visit source.android.com
Sent from my Nexus 4 using Tapatalk
Hi,
I would like to know the android boot process too.
I need to replace the splash boot logo but i am not sure where to find it in the boot process
Hello
I have mounted system.img with linux the format i think it ext4 but the file is not sparse so i was successful using the following command.
sudo mount -t ext4 system.img ~/firmware2 -o loop
When the system image is mounted i have made some edits to the live image then i have unmounted the image and transferd the image back to my windows computer and ran the system.img through ext4 unpacker and extunpacker shows that my changes havent been made and and the file is the same as before however when i remount the system.img on my linux pc it shows the changes.
Im really stuck here and if anyone could help that would be great.
I am only new here but when i possible i will contribute and repay favours.
ps with the unmount i use visual unmount but have also tried unmounting with commands i used are umount /firmware2
re
I have sorted this issue now and managed to fix.
I have Zenfone 5 phone, and i want to flashable system.img for the fastboot.
I tried dump system.img with help of this topic: http://forum.xda-developers.com/showthread.php?t=2450045
I used this code for the know what devblock is system for the zenfone:
Code:
adb shell
ls -al /dev/block/platform/intel/by-label/
And the mmcblk0p9 showed as system. Than I dumped system image with this command:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img
After dump of system.img, I tried flash it via fastboot with this command:
Code:
fastboot flash system system.img
But the flashing process is aborted with this error:
Code:
invalid sparse file format at header magi [I]-> This error appeared in Windows CMD, others in the below, appeared in the fastboot screen[/I]
e:unknowing chunk type
failed: bad file number
In summary; I dumped system.img and flashed it via fastboot and, it wasn't flashed, and give error.
I tried to convert system.img to system.raw via Ubuntu with simg2img file, I took this error:
Code:
invalid sparse file format at header magi
How to solve this "invalid sparse file format error"? Please help me? I'm making a rom, but this error blocked me
I have TWRP installation file in img format ready to be loaded with
Code:
fastboot boot twrp-unofficial.img
.
I don't have the source and want to have a look at what is packaged with it.
Is it possible to mount this img file on linux or extract the contents somehow?
Code:
file twrp-unofficial.img
twrp-unofficial.img: Android bootimg, kernel, ramdisk, page size: 2048, cmdline (console=null androidboot.console=ttyHSL0 androidboot.hardware=q)
I tried with simg2img but failed
Code:
simg2img twrp-unofficial.img twrp.raw
Invalid sparse file format at header magi
Failed to read sparse file
Furius ISO mount creates a mount point but it is an empty directory.
Hello,
I am trying to investigate the contents of the stock rom. I have downloaded the zip and extracted it, and also converted the sparse image files to nonsparse ones with simg2img. Unfortunately, I am still unable to mount the images. No matter whether I try to mount the converted image as ext2, ext4 or f2fs, I am getting the error:
mount: /mnt/temp: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
Click to expand...
Click to collapse
Does anybody know if/how can the oreo stock images for griffin be mounted? The issue seems to be specific to motorola or oreo as I was able to mount files from nexus 5x oreo stock images without issues. Thank you for the advice.
It turns out motorola images have 128kb header which needs to be removed before they can be mounted. Assuming dd's default block size of 512 bytes this gives the following:
Code:
$ dd if=system.raw.img of=system.raw.img.fixed skip=256
After that the images can be mounted.