Making emulator's system.img persistent - Android Software Development

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

Related

How to edit data.img and system.img from Nandroid backup?

I am looking at modifying the contents of the data.img and system.img files that were created by nandroid.
I've looked around, but came up empty.
How can I do this?
outsider787 said:
I am looking at modifying the contents of the data.img and system.img files that were created by nandroid.
I've looked around, but came up empty.
How can I do this?
Click to expand...
Click to collapse
I just recently learned that you have to unyaffs them. Not sure how to recomplie (is that the right word?) them after you make edits though.
I've been trying to get the system.img file mounted on the device itself (since it has yaffs2 built into the kernel), but no luck so far.
Has anyone else have had any success mounting these .img files from within the android OS?
Yaffs won't work that way since the image isn't a block device. It has to actually be on a block device to mount.
Ok.
What if I make a partition on my SDcard, somehow write the data.img file to that partition, and then mount that partition.
Would that work?
I have only one problem. I don't know how to write the .img file to a partition.
Anyone have any idea?

[Q] Boot partition access

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.

[MOD][External-SD card as Internal-SD card]

Looking through the forum I have noticed the complaints on low internal-sdcard space.
This is a workaround for this issue
What's required:
A fast SD-card with greater than 16GB will benefit you the most
Tegra device ofcourse with an unlocked bootloader!
USB cable
TWRP recovery (Can be found here >> http://forum.xda-developers.com/showthread.php?t=2586432)
Installation:
Format SD-Card into EXT4 file system (This will wipe your whole SD-card ofcourse so do backup!)
Copy downloaded zip file onto your tegranote device
Reboot into recovery
Locate and install zip file
If you cannot do the above you can also use adb sideload in terminal (Sideload with TWRP (Terminal command "adb sideload zipfile.zip"))
Issues:
Internal Userdata does not mount as external-sd when formatted to FAT so keep it as EXT4 file-system for now
Download Links:
Stock 4.2.2: http://d-h.st/N7Q
Modified 4.2.2: http://d-h.st/jbM​
can you reupload that mod please?
id like to use it since exFat is not working and fat32 is not a filesystem for me :/
Will this work on 5.1?
Shaky156 said:
Looking through the forum I have noticed the complaints on low internal-sdcard space.
This is a workaround for this issue
What's required:
A fast SD-card with greater than 16GB will benefit you the most
Tegra device ofcourse with an unlocked bootloader!
USB cable
TWRP recovery (Can be found here >> http://forum.xda-developers.com/showthread.php?t=2586432)
Installation:
Format SD-Card into EXT4 file system (This will wipe your whole SD-card ofcourse so do backup!)
Copy downloaded zip file onto your tegranote device
Reboot into recovery
Locate and install zip file
If you cannot do the above you can also use adb sideload in terminal (Sideload with TWRP (Terminal command "adb sideload zipfile.zip"))
Issues:
Internal Userdata does not mount as external-sd when formatted to FAT so keep it as EXT4 file-system for now
​
Click to expand...
Click to collapse
Did anyone test this on Android 5.1 ?

is it possible to force USERDATA readonly during FW installation?

I'm trying to recover files from my phone. coping /dev/block/sda18 using dd has not worked for me as recovery software only finds 3 files on the filesystem (it was high level formatted). There are alot of file recovery tools on android but I need to be able to boot my phone, in order to prevent any damage to the USERDATA partition (sda18), I thought of possiblly forcing it to be read only and then installing firmware, booting, installing recovery software, and using it on the read only internal memory.
is this feasible?
Thanks all
I could use an undelete apk, like this one -> fahrbot.apps.undelete. I'll try to install with /data unmounted...

Data recovery internal storage - how to create image with dd of /storage/emulate/0

Hello!
Unfortunately I have deleted internal storage in TWRP recovery.
Now I want to try to restore the files using Testdisk / Photorec.
The directory of interest is: /storage/emulated/0/DCIM
Is this directory located on a specific partition?
If yes, which partition?
And can I create an image of this partition with dd?

Categories

Resources