> adb_usb.ini needed oXXXX as device ID . Where XXXX is the ID that shows up on Device manager. This is detailed here
after that there will be 2 yellow marks for the rest of the unknowns in device manager. for this you have to modify the .inf file to include the entire h/w ID strings. I guess that makes just about any driver get along with anyone unknown - so here I am not sure if showing them as the such h/w by changing the driver files - gives them the actual intended functionality or all it does it just makes the device manager look clean without yellow marks. Maybe someone could help expand the talk here
android_winusb.inf %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01 %CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_01 /*ADDED*/ %CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_02 %CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_03
So with that - I get 1 ADB interface and 3 devices show up under "com and LPT" - alright that completes the drivers
I found this Chinese rooting program Vroot . I still have'nt figured out what exactly it means but it looks like it DID root that sucker after all. I tested with one app - root checker - got an dialogue in Chinese , asking me whether to give or not and I think I said Y but that app still does not say I have root. Its probably the apps thats at fault because I can get Linked2SD do ALL the stuff it would be doing running as root - .e.g force move programs to SD to free up space etc.
If someone out there can make English out of that and tell me if its mine to keep or leased out ( trial ) - that'd be damn nice !!!
- WIP- when I get some more time