M 146.1: Cold Boot (5 pts)
This action is often needed after changing HTTP proxy settings.In Android Studio, in Device Manager, on the line showing your device, at the right side, click the down-arrow, and click "Cold Boot Now", as shown below.
When the boot process begins, you will see the message shown below.
The flag is covered by a green box in the image below. .
M 146.2: Disabling Mobile Data (5 pts)
This action may be needed to get Web traffic to go through the Burp proxy.In the emulated device, open Settings.
Open "Network & Internet".
You should see a wireless connection named "AndroidWiFi" and also an emulated cellular network connection.
In the image below, the emulated connection is "T-Mobile".
Click the cellular network options until you find the setting to disable "Mobile data", as shown below.
The flag is covered by a green box in the image below.
M 146.3: Disabling Play Protect (5 pts)
This action may be needed to install the insecure applications used in other projects.In the emulated device, open "Google Play". Sign in if necessary.
At the top right, tap the circular icon, outlined in red in the image below.
In the next screen, tap "Play Protect".
In the Play Protect screen, at the top right, tap the gear icon.
Disable "Scan apps with Play Protect", as shown below.
In the confirmation box, tap "Turn off".
The flag is covered by a green box in the image below.
M 146.4: ADB over TCP (15 pts)
In some configurations, you need to connect ADB to an emulator running on a different host machine.First, you need to find your host machine's IP address. (If you are using my Proxmox private cloud, use the Android emulator's IP address instead, which you can find by tapping "Network & Internet", Internet, AndroidWifi.)
On your host machine, in a Terminal, execute one of these commands:
Find your host system's IP address, as shown below.
- For MacOS: ifconfig
- For Linux: ip a
- For Windows: ipconfig
Installing Socat
The procedure depends on your OS. Follow the appropriate instructions below.
- MacOS: First, install Homebrew. Then execute this command:
- Windows: Get socatx6.exe4 from this Github.
- Debian Linux: Execute these commands:
Finding the TCP Port to Connect to
On a MacOS or Linux host, execute the command below.On a Windows system, replace "grep" with "findstr".
Find listening ports beginning with 55.In the image below, ports 5554 and 5555 are listening.
Try connecting to each port in turn, with commands like these:
Find out which port number works to make a connection.In the image below, port 5555 worked.
Forwarding a Local Port to a Public Port
The Android emulator listens on the localhost adapter. We need to forward that to a public address on port 5566. <.> On the system hosting your Android emulator, in a Terminal, execute this command, replacing 5555 with the port that worked for connections in the previous step.The program has no output, it just hangs. Leave this window open, as shown below.
On your remote computer, install Android Studio and launch it.
In Android Studio, click Tools, "AVD Manager."
Find the Android SDK Location, outlined in green in the image below.
On your remote computer, open a Terminal and navigate to that location.
First ping the host device for your Android emulator, using its IP address you found above.
You should see replies.
Then connect using a command like this, replacing the IP address with the correct IP address of your host system:
Look at your Android emulator.It should show a connection attempt, as shown below.
Check the box and tap Allow.
As shown below, the first connection attempt shows "failed to authenticate".
Execute the "adb connect" command again.
Your remote system should now connect, as shown below.
Network Status on the Android Device
On your remote computer, execute these commands:In the next screen, tap "Play Protect".The flag is covered by a green box in the image below.
