Hi, I'm wondering how to make the system.img used by the emulator persistent across reboots. From `emulator -help-disk-images`:
It will also use the following writable image files:
userdata-qemu.img the persistent data partition image
system-qemu.img an *optional* persistent system image
cache.img an *optional* cache partition image
sdcard.img an *optional* SD Card partition image
Click to expand...
Click to collapse
I tried to copy the stock system.img as system-qemu.img to the directory of my avd but it didn't work. What am I doing wrong?
If this cannot be done, modifying the system.img and use that in the current non-persistent way would be ok too.
Thanks
Anyone? Thanks
What would the best way to pull all my system files so I can start messing with them be?
Connect to computer via disk drive and then adb pull /system?
Tar the whole partition with cvjpf to preserve permissions and put the tar on your SD.
Evostance said:
What would the best way to pull all my system files so I can start messing with them be?
Connect to computer via disk drive and then adb pull /system?
Click to expand...
Click to collapse
working on the exact same thing hahaha lol but it should be in general
sfjuocekr said:
Tar the whole partition with cvjpf to preserve permissions and put the tar on your SD.
Click to expand...
Click to collapse
thats a good way too
i've mounted the system.img
mount -o loop -t ext3 system.img /tmp and you can put /what ever directory you want instead of temp if you want.
i got the system.img from an official ruu and its rom.zip
got quiet a lot to do tonight
Moved to General
I have downloaded a nand androuid build that I am 99% happy with. I do however want to change a couple of things on the build.
I have downloaed and got ubutu up and running on a virtual box. I have then copied the system.img file on to a usb drive and copied it into ubuntu. Location of the file is in stephen which is my logon name.
I have also created a folder called mount which I want to mount the img file to.
I have done this before in ubuntu using ext2 files but I can not get the mount command to work for an img file. Is there an way to mount the img file, remove the files I do not want and then comple a newer smaller img file?
EDIT: logged on as root and moved the system.img and mount folder to main file system folder. Ran command mount -t img /system.img /mount but now getting error unknown filesystem type 'img'
Any help would be appreciated.
Hi,
when i copy bml 1,2,3 etc. I can mount most of the partitions in linux using the loop mount. I cannot do this with the efs partition. Does anyone know how to decrypt it? A work around is to copy the files themselves.
On Root Explorer or other similar file explorers, the 'boot' partition seems to be missing, hidden or not accessible. Even Mount Manager can't find it. I think it's not a partition to be accessed as it is needed for booting.
The main reason for this thread is for http://forum.xda-developers.com/showthread.php?t=1196426. When backing up boot.img, it fails. I think this isn't directly related but the problem seems to occur to both the system and the user.
jhonnyx1000 said:
On Root Explorer or other similar file explorers, the 'boot' partition seems to be missing, hidden or not accessible. Even Mount Manager can't find it. I think it's not a partition to be accessed as it is needed for booting.
The main reason for this thread is for http://forum.xda-developers.com/showthread.php?t=1196426. When backing up boot.img, it fails. I think this isn't directly related but the problem seems to occur to both the system and the user.
Click to expand...
Click to collapse
I think this is due to the boot partition being extracted, which is why there's the /sys folder with the kernel in. Not all folders are from the system.img, you find that by extracting it
Quinny899 said:
I think this is due to the boot partition being extracted, which is why there's the /sys folder with the kernel in. Not all folders are from the system.img, you find that by extracting it
Click to expand...
Click to collapse
Thanks. Forgot about the distribution of components throughout different partitions.
Boot.img is not a folder, it makes up the filesystem structure, so in the boot ramdisk, there are files such as default.prop, init.swift.rc which are in the root filesystem (in root explorer) The ramdisk inside boot.img is what mounts all the partitions and prepares the filesystem. So it is set to mount the /system, /data partitions etc. The devices 1st bootloader (Hard bootloader) reads this partition then boots from it. Then the boot partition will load the Linux kernel, and begin to boot android.