I am struggling to make my USB debugging works for Momo7 dual core with RK3066 chip. This is what I found to make it works at least for my Windows 7 64bit. This should be the same with other RK3066 devices also.
1. Install ADB driver
After connect to USB (make sure USB debugging enabled and don't mount the mass storage device) You will find that MOMO7 is not recognized in the Device Manager. The simple way is to install Moborobo, it will find and install a driver for you.
If you dont want to install Moborobo, you can use standard adb driver comes from SDK but you need to edit the android_winusb.inf file to add
in both Google.NTx86 and Google.NTamd64 area.
For other model and manufacturer, just change the VID and PID which you can get from Device Manager > Properties > Details > Hardware Ids.
2. Use suitable ADB
Using adb from Android SDK is not working for some/almost RK3066 device (I think). I tried a few adb embedded from the other application like SuperOneClick but not working. No device found if you run "adb devices". I almost giveup but suddenly adb from ROOT.bat here contain is the only adb that can see my device.
Credit goes to bindassdost to point to the adb in the first link here
and yuvarajv to mentioned the adb embedded in root script contain ROOT.bat here
1. Install ADB driver
After connect to USB (make sure USB debugging enabled and don't mount the mass storage device) You will find that MOMO7 is not recognized in the Device Manager. The simple way is to install Moborobo, it will find and install a driver for you.
If you dont want to install Moborobo, you can use standard adb driver comes from SDK but you need to edit the android_winusb.inf file to add
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
in both Google.NTx86 and Google.NTamd64 area.
For other model and manufacturer, just change the VID and PID which you can get from Device Manager > Properties > Details > Hardware Ids.
2. Use suitable ADB
Using adb from Android SDK is not working for some/almost RK3066 device (I think). I tried a few adb embedded from the other application like SuperOneClick but not working. No device found if you run "adb devices". I almost giveup but suddenly adb from ROOT.bat here contain is the only adb that can see my device.
Credit goes to bindassdost to point to the adb in the first link here
and yuvarajv to mentioned the adb embedded in root script contain ROOT.bat here
Last edited: