|
For Windows it's an exe file (almost 100 MB in size) plus a folder with the Android platform files (adb.exe, adwinapi.dll and adbwinusbapi.dll). When the tool is active and you've unlock the Reader with "adb enable device" you can also use adb in Windows command prompt, but that's really the same as using the Viwoods tool. You always hav to enable the device first. The firmware my Reader came with was much better regarding adb commands. But they fixed some other stuff like enabling fingerprint without the need to be connected to the internet, and I haven't really read the info about the first update.
The Tool for Linux has almost the same size as the Windows exe file plus there's a file named "adb" without file extension. I really have no clue about Linux. It looks like there are no file extensions for Linux.
I could upload the tools somewhere or you could just email Viwoods after you got the Reader. They certainly send you a download link. Firmware v1.3.8 is a beta version, though, and you need to contact Viwoods with the serial number of the device to take part in the beta program.
It's not that I use adb every other day but it's very useful to disable/deinstall apps that can't be disabled/deinstalled in the settings. And some apps require additional adb commands to be useful. So it's essential to have to personalize an Android device.
|