[Arm-netbook] How to make A2000 adb work?

[Adam Jiang]

2012/6/6 Tom Cubie <mr.hipboi at gmail.com>:
>
>
> On Tue, Jun 5, 2012 at 11:16 PM, Adam Jiang <jiang.adam at gmail.com> wrote:
>>
>> 2012/6/4 Henrik Nordström <henrik at henriknordstrom.net>:
>> > mån 2012-06-04 klockan 10:44 +0900 skrev Adam Jiang:
>> >
>> >> I think ADB driver itself is provided by Google. It is only necessary
>> >> to provide VendorID/ProductID in ~/.android/adb.ini to get it work.
>> >> However, for A2000 board with the default firmware, I cannot get even
>> >> the devices shows up in 'lsusb'. No VID/PID could be found there for
>> >> Mele A2000.
>> >
>> > Mine shows up, even with "USB Debugging" disabled. It also provides
>> > normal USB disk access to sd-card and more?
>> >
>> > With "USB Debugging" enabled it also chats a bit about adb on the
>> > console, and there is an adbd process running.
>>
>> Now, I got the device by 'lsusb'
>>
>> Bus 002 Device 005: ID 18d1:0001 Google Inc.
>>
>> However, 'adb devices' could not find adbd on the target. How could
>> you check if there are 'adbd' process running?
>>
> try sudo adb devices

Sure. It doesn't work. Also, I have tried add vendorID=0x18d1 into
51-android.rule, it doesn't work either. I guess there are something
wrong with the stock firmware...or I am just unlucky.

Is there are guide for how to update the firmware for A2000? I'd like
to give a shot on the new version.

Best regards,
/Adam