Frida shelling environment startup code set

This article is used to save the configuration code of my article
, so that I can quickly start the Frida shelling environment
and some updated experimental research

run Night Simulator.exe
run cmd

d:
cd D:\Program Files\Nox\bin
adb connect 127.0.0.1:62001
adb devices
adb start-server
adb devices
adb shell 

su
/data/local/tmp/frida-server-15.2.2-android-x86 

d:
cd D:\11279\Project\crackTL
python hook.py

frida -U -l hook.js -f com.package.name

open another cmd

python D:\Desktop\unpack.py 包名

real machine

adb start-server

adb shell

su

/data/local/tmp/frida-server-15.2

com.taolu.smer

1

Execute adb connect 127.0.0.1:62001 directly without opening the Yeshen simulator, and
the following prompt will appear

2

Why is it 127.0.0.1:62001, why is it the port 62001

tasklist
Nox.exe                      15752 Console                    2    219,448 K
netstat -ano
 TCP    127.0.0.1:2906         127.0.0.1:62001        ESTABLISHED     17212
 netstat   -ab
  [Nox.exe]
  TCP    127.0.0.1:2875         egg2001:61001          ESTABLISHED
 [Nox.exe]
  TCP    127.0.0.1:2893         egg2001:2894           ESTABLISHED
 [nox_adb.exe]
  TCP    127.0.0.1:2894         egg2001:2893           ESTABLISHED
 [nox_adb.exe]
  TCP    127.0.0.1:2906         egg2001:62001          ESTABLISHED

3

Enter nox and enter the directory and enter adb. Why is the adb.exe in the directory first started instead of adb.exe in the environment variable? What is the difference between the two? There is also nox_adb.exe in the same directory, what is the difference between these three?

4

Research on adb and nox_adb under the environment variables adb and nox directories

#不开启夜神模拟器，不管用环境变量的adb还是nox根目录下的adb和nox_adb都无法建立链接，且找不到设备
C:\WINDOWS\system32>adb device\
adb.exe: unknown command device\

C:\WINDOWS\system32>adb devices
adb server version (36) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached

C:\WINDOWS\system32>adb connect 127.0.0.1:62001
cannot connect to 127.0.0.1:62001: 由于目标计算机积极拒绝，无法连接。 (10061)

C:\WINDOWS\system32>d:

D:\>cd D:\Program Files\Nox\bin

D:\Program Files\Nox\bin>nox_adb.exe devices
List of devices attached
adb server version (41) doesn't match this client (36); killing...
* daemon started successfully *

D:\Program Files\Nox\bin>nox_adb.exe connect 127.0.0.1:62001
unable to connect to 127.0.0.1:62001: cannot connect to 127.0.0.1:62001: 由于目标计算机积极拒绝，无法连接。 (10061)

#打开夜神模拟器,不执行connect指令
D:\Program Files\Nox\bin>nox_adb.exe devices
List of devices attached
127.0.0.1:62001 device

D:\Program Files\Nox\bin>adb.exe devices
List of devices attached
127.0.0.1:62001 device

C:\Windows\System32>adb devices
adb server version (36) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
#发现nox目录下的adb和nox_adb执行devices都能查到设备，而环境变量的adb则查不到

5

Following the content of #4, if you can use the adb in the nox directory to connect to the device without connecting, can you directly use the adb of nox to operate?

D:\Program Files\Nox\bin>adb start-server
adb server version (41) doesn't match this client (36); killing...
* daemon started successfully *

Is this a success or a failure? I checked online and it seems that it failed. I

didn’t understand the answer, but I found out that it seems to change the adb version of nox. Let’s change it. Adopt the method of https://pcedu.pconline.com.cn/1515/15154706.html.
Then execute adb start-server again

and there will be no prompt this time, it should be successful!