Step 6 Problem

[3BBUAE]

Hey I need help with step 6

I used the following:
C:\Users\Ali Al-Zaabi>docker run --volume=Y:\benign\apks:/apks alexmyg/andropytool -s /apks -all -vt key

[phamhduy]

I have try AndroPyTool Docker on Ubuntu 18 running in VMware and I have the same problem. So I change to run from the source but the problem is unchanged.

I try to create another AVD and replace img files in Droidbox folder by those from Android SDK folder (default imgs) and AndroPyTool works.
Anyway, I download DroidBox from google-drive not from git-hub.

[3BBUAE]

I have try AndroPyTool Docker on Ubuntu 18 running in VMware and I have the same problem. So I change to run from the source but the problem is unchanged.

I try to create another AVD and replace img files in Droidbox folder by those from Android SDK folder (default imgs) and AndroPyTool works.
Anyway, I download DroidBox from google-drive not from git-hub.

I have clean install of ubuntu no vmware, I managed to get it to step 6, but now i get to a different problem.

Im not sure what it means exactly when it says no such file or directory.

[3BBUAE]

I have try AndroPyTool Docker on Ubuntu 18 running in VMware and I have the same problem. So I change to run from the source but the problem is unchanged.

I try to create another AVD and replace img files in Droidbox folder by those from Android SDK folder (default imgs) and AndroPyTool works.
Anyway, I download DroidBox from google-drive not from git-hub

I manage to fix my previous problem, but now I am back to the same problem in the first post. I tried to replace the images just as you said and created new AVD, but i still cant get it to work. I would really appreciate it if you show more detailed steps thank you in advance.

[phamhduy]

I follow the installation guide except the openJDK 8 (for quick test). In my installation, the images for AndroPyTool AVD are in ~/AndroPyTool/DroidBox_AndroPyTool/images. Since startemu.sh and startemunogui.sh are refered to imgs in this folder, so I take my chance by copying imgs (ramdisk and system) from ~/android-sdk-linux/system-images to replace two origin files.
Also, I use Android SDK manager to create an AVD with same name "droidbox-emulator" and CPU (armeabi) as in createDroidBoxDevice.sh and successfully start it via this android tool. It seems that any device type would be OK.
Now, I can load "droidbox-emulator" AVD by running startemu.sh.

Also, I register with virustotal.com to get a free api key to run VirusTotal step, then put this key after the argument -vt my_api_key.

Finally, I can run the AndroPyTool from python for all analysis steps.

I'm still wondering what are in Droidbox images but I may happy with static analysis.

[phamhduy]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

[3BBUAE]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

Thank you for your help it is working with me now.

[nhatminh199989]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

Thầy ơi em vẫn chưa sửa được ạ, e chạy bằng docker ạ

[tconqueror]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

Thầy ơi em vẫn chưa sửa được ạ, e chạy bằng docker ạ

English please

[nhatminh199989]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

Thầy ơi em vẫn chưa sửa được ạ, e chạy bằng docker ạ

English please

I've the same problem but i still can't fix it. I'm using VMWare and running on docker, can u help me.

[and85620]

I'm using andropytool on docker in ubuntu 18.04, but I still have the problem in DroidBox - Boot not completed, please help me, thanks!

[alexMyG]

I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.
So, converting file system of system.img makes the tool working.

Please could you send me these images?

[phamhduy]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} -->You can download from the link below:https://drive.google.com/file/d/13fquYXcR3spc_6TVL5lUSEq8S6lo6TRy/view?usp=sharingBe aware that the file name needs to change to ‘system.img’ I cannot find a tool that directly converts yaffs2 to ext4, so I copy all files from droidbox to the default image that comes with Android SDK. This approach is problematic because I’m not sure packages in the droidbox  is fully compatible with the default image. But the modified image works. https://drive.google.com/drive/folders/1MoL4-D0eMjxg-6eGlEcQlgx0gLZNKH5b?usp=sharing The above folder contains all the files I work with. Regards,Duy Sent from Mail for Windows 10 From: Alejandro Martín GarcíaSent: Friday, July 3, 2020 12:03 AMTo: alexMyG/AndroPyToolCc: phamhduy; CommentSubject: Re: [alexMyG/AndroPyTool] Step 6 Problem (#19) I work a bit more with the system.img from Droidbox and it turns out that the file system of this file is yaffs2. By some chance, Android emulator prefers ext4 over yaffs2. It gives an error when loading from android AVD manager.So, converting file system of system.img makes the tool working.Please could you send me these images?—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe. 

[alexMyG]

Thanks a lot @phamhduy It works! I've update the repo and the Dockerhub image.