cuckoo-droid
cuckoo-droid copied to clipboard
idanr1986
qemu-system-armel: -nand: invalid option
Hi,
when I try to start the emulator according to documentation, I receive this:
... > emulator @aosx -writable-system -qemu -nand -system,size=0x1f400000,file=/home/viktor/Android/Sdk/system-images/android-16/default/armeabi-v7a/system.img&
emulator: WARNING: System image is writable
statvfs('/home/viktor/.android/avd/aosx.avd/snapshots/default_boot/ram.img') failed:
No such file or directory
emulator: WARNING: encryption is off
qemu-system-armel: -nand: invalid option
Job 1, 'emulator @aosx -writable-system…' has ended
Removing -nand only makes the output the same except for this instead:
qemu-system-armel: -system,size=........: invalid option
How important are -nand and -system flags for QEMU?
Without the flags running just
...> emulator @aosx -writable-system -qemu
Makes it possible to follow rest of the steps but during analysis I only get following message repeated:
2019-05-07 11:35:20,479 [lib.cuckoo.core.guest] DEBUG: aosx_1: not ready yet
Which I suppose is because it is waiting for the agent to start inside the guest.
Cuckoo Sandbox 1.2. I strictly followed the instructions for installation at this git-repository.
I did an internship in which I used cuckoodroid extensively. Seach in the issues and you may find your answer.
Also You might find these useful: https://github.com/waqarrashid33/cuckoo-droid (A few bug fixes and updated docs) My internship report pdf
According to:
https://stackoverflow.com/questions/15417105/forcing-the-android-emulator-to-store-changes-to-system
the -nand option was removed from QEMU and the way to keep changes between boots is the -writable-system option.
This option persists your changes in a system.img.qcow2 file, instead of writing directly to system.img
According to: https://stackoverflow.com/questions/15417105/forcing-the-android-emulator-to-store-changes-to-system the
-nandoption was removed from QEMU and the way to keep changes between boots is the-writable-systemoption. This option persists your changes in a system.img.qcow2 file, instead of writing directly to system.img
Hello, How do you fix this issue finally, I meet the same issue with you. thanks
Hello, How do you fix this issue finally, I meet the same issue with you. thanks
Hi @stoude19961225, unfortunately I was not able to get it fully functional but I used this:
emulator -avd aosx -writable-system -qemu
And then merged my the repository with the changes from @waqarrashid33 above.
Those changes did get it up and running, although the only dynamic logs i received was the network traffic.
