Kukai TV ADB

One 、 About ADB 1、adb Concept ： adb The full name is Android Debug Bridge, Is to play the role of debugging bridge . adopt adb We can do it in Eclipse It's convenient to pass through DDMS To debug Android Program , To put it bluntly debug Tools .adb I work in a special way , Use monitoring Socket TCP 5554 The way of waiting for ports makes IDE and Qemu Communications , By default adb Meeting daemon Associated network port , So when we run Eclipse when adb The process will run automatically . 2、adb purpose ： adb yes android sdk A tool in the library , With this tool, you can directly operate and manage android Simulator or real android equipment ( Such as G1 mobile phone ). 　 Its main functions are : * Operating equipment shell( Command line ) * Manage port mapping for emulators or devices * Upload between computer and device / Download the file * Will local apk Software Install to simulator or android equipment ADB It's a client - Server side Program , The client is the computer you use to operate , The server side is android equipment . Two 、 wireless ADB Usually , our Android mobile phone , Pass on the computer USB Data cable to PC , Then install mobile assistant software on the computer , It can realize the daily management of mobile phones , This is it. USB Implementation of debugging . In contrast to this method , If adb Use , Not through USB Data cable connection , But through the network （TCP/IP） To achieve , So let's call that “ wireless ADB”. stay Android On the cell phone , If you want to use USB ADB debugging , Usually in Android System settings , open “ Developer options ”, And tick on “USB debugging ” Just switch it on and off . But if you want to achieve wireless ADB, Sometimes , You need to install WirelessAdb Small application of , You can easily turn on the wireless ADB The function of . such , You don't have to USB cable , adopt WIFI Go straight ahead adb Debug . 3、 ... and 、42K1 Kukai 5.0 The internal test system is wireless ADB Function of open 42K1 We can't go through USB Data line adb, So consider passing WIFI To achieve wireless ADB. 1、 Press Kukai 5.0 Internal test development guidelines , From the home page , Into the TV “ Set up ” Interface ：

3、 Use the remote control , Input instruction “ Up, down, left and right ”, open “ Factory menu ”：

3、 Get into “ Advanced settings ”：

5、 Move to “ADB switch ” Options , You can see that the default state is “ Turn off ”：

6、 Adjust this item to “ open ”, So we can open it easily 42K1 Kukai 5.0 Wireless adb The function of .

Four 、42K1 Kukai 5.0 The internal test system is wireless ADB Function trial evaluation

1、42K1 TV IP Address the query ： In front of “ About the machine ” You can see .


2、 The computer IP Address the query ：

3、TCP Network connectivity detection ：

D:adb>ping 192.168.0.100
is Ping 192.168.0.100 have 32 Bytes of data :
come from 192.168.0.100 Reply to : byte =32 Time =3ms TTL=64
come from 192.168.0.100 Reply to : byte =32 Time =2ms TTL=64
come from 192.168.0.100 Reply to : byte =32 Time =2ms TTL=64
come from 192.168.0.100 Reply to : byte =32 Time =3ms TTL=64
192.168.0.100 Of Ping Statistics :
Data packets : Has been sent = 4, Received = 4, The loss of = 0 (0% The loss of ),
Estimated time of round trip ( In Milliseconds ):
The shortest = 2ms, The longest = 3ms, Average = 2ms
detection result ： Network communication is normal .
4、 wireless ADB Connection detection ：

D:adb>adb connect 192.168.0.100

• daemon not running. starting it now on port 5037 *
  
• daemon started successfully *
  
  connected to 192.168.0.100:5555
  
  detection result ： wireless ADB Connection established successfully , Use default port ：5555;ADB Service usage port 5037.
  
  5、ADB Device view ：
  
  

D:adb>adb devices

List of devices attached

192.168.0.100:5555      device

result ： Display wireless correctly adb Connected equipment .

6、adb shell Sign in ：

D:adb>adb shell

[email protected]:/ #

result ：adb shell Successfully logged in .

7、root relevant ：

Warning ：root There are risks , Do not try the following easily ！

Get into adb shell, We just found out ,adb shell By default, there are root jurisdiction （shell The command prompt for is “#”）. Let's test it root Availability of permissions .

With root privilege use adb :

D:adb>adb root

adbd is already running as root

result ： System prompt adb Have already used root Permission mode works ;

With root Permission to re mount the system ：

D:adb>adb remount

remount succeeded

result ：system Read / write mount succeeded .

In this sense , To be cool 5.0 The system goes on root, No need to rely on any complex tool software , Direct use adb It can be easily realized .

At the beginning root Before , Let's take a look at the current root state . open Sofa housekeeper ,“ hold-all ”“ Equipment information ”：

You can see "root state "： close .
Let's first put su file ：

160550pzbjntdrjnbbrqgd.jpg.thumb.jpg(28.83 KB, amount of downloads : 39)

D:adb>adb push su /system/xbin/su

505 KB/s (159472 bytes in 0.307s)

Then we put... Into the system application root Rights management ：

D:adb>adb push Superuser.apk /system/app

375 KB/s (5249707 bytes in 13.650s)

Relevant authority modification ：su And authorization management 、 establish system/bin Under the su link

<ignore_js_op>

Is it easy ？ Now on TV “ My application ” Is there one more in the “ Authorization management ” Application ：

<ignore_js_op>

Yes , One more is called "Kingroot" Application .
Finally, install another Dangbei market Check it out , See if you can get ROOT Yes ！