Pipo M9 Pro RileyROM 2.1

[Starcopy]

For the sake of non-duplication of efforts, I think I'll let Finless carry the baton for the M9 Pro ROM's. He's doing some great work, and it gives me a chance to learn some more from him. But in interest of the Pipo brand, I'll continue to hang around and watch the M9 Pro threads closely. That's why there isn't a RileyROM with this latest firmware.

If Bob gets busy, I may step back in...that's always an option.

Bob has stopped building, so will there be another Rileyrom for the M9pro? I must say that I can hardly wait for it. Finless was nice, but I like your roms more.

[rrileypm]

I've skipped this last firmware update because Bob already has the ROM for it. I will start back on the next update whenever that will be.

[Starcopy]

I've skipped this last firmware update because Bob already has the ROM for it. I will start back on the next update whenever that will be.

Lets hope for the 4.4 version.

[rrileypm]

I'm looking for a savvy tester to plunge into my new KitKat ROM. Here's the link:

http://www.freaktab.com/showthread.php?9432-Pipo-M9-Pro-RileyROM-2-5-1-Test-ROM&p=128277#post128277

Please read the thread and understand that this ROM is untested.

[LarsR]

Program development on M9Pro - what drivers are needed?

Hi all,
I'm playing around with some Android programming and I'd like to test my app on the M9Pro. I've got the Eclipse dev environment set up and my app and debugging on Galaxy S3 hardware works fine.

I've also flashed my M9Pro with RileyROM 2.0 a while ago so I have all USB drivers needed for flashing installed and working on my W7x64 laptop.

When I connect the tablet to the laptop it displays the "USB connected" screen, and "USB debugging connected" is shown in the event list. But on my laptop drivers for "M9pro" is missing and I cannot get Eclipse to detect the tablet, even though the Finless ROM flash tool still can.

Does somebody know what's missing?

Cheers,
Lars

[BillinCA]

The M9Pro presents one USB Device ID for "Mass Storage" (technically, two if you have an external SD plugged in), a different Device ID while in Bootloader (flash mode), and a Device ID that would come and go with the toggle of USB Debug in Dev options. Each of those three Device groups needs its own driver - and are authored by different companies. The ADB device (M9Pro if that's what appears in boot.prop) is authored by Google and is called Android Composite ADB Interface for me. That driver is included with the Android SDK, but the .INF file that comes with it doesn't include the Device ID presented by the M9Pro. It is possible to modify the .INF file in the SDK to also include the Device IDs for the M9Pro, but you could also probably locate it already modified. In Device Mgr, properties for the M9Pro item that is "unidentified", select the Details tab and change the Property drop down to Hardware ID and you should see
USB\VID_2207&PID_0010&REV_0222&MI_01
USB\VID_2207&PID_0010&MI_01
Those are the ID's you'd need to add to the .INF for the ADB driver. You could probably use the same thing you use for your S3 if you modify its .INF to include the Device IDs. There is also a post here on Freaktab for the ADB driver for "any RK3188" device, but I don't have any URL handy for it (or for other places you could find the needed ADB driver with the .INF already modified).

Bottom line is you need an ADB driver and that is totally independent of the driver needed to flash or to access the SD card(s) on the M9Pro.

[BillinCA]

This isn't what I used, but you should be able to use the ADB driver linked to in this thread:

http://www.freaktab.com/showthread.php?8817-RK3188-ROOT-Guide-for-all-Boxes-or-Sticks-with-RK3188&highlight=ADB+RK3188

Although you don't need to root it, getting ADB working is the easiest way to do the root. All you'd need is to Update Driver for the M9Pro device my browsing to the .INF in the root kit.

EDIT:
The download link in the above URL runs some other .EXE to do the actual download and I'm not terribly comfortable with that. You don't need/want to actually run its Root script (might replace SU, ...). That post credits another Freaktab post
How To easily root CX-919 (should work for all rk3188 devices) full rooting package

and that 10MB download uses a Captcha and you have to know to wait out 30 seconds, etc so here's the 10MB download directly:

https://drive.google.com/file/d/0Bxc1H2J2CX_XT3ZkeVpsaFU0RVE/edit?usp=sharing

If you unzip it, don't do anything with it other than Update Driver and browse to RK3188_Root\USB_Driver
It will find the 64 bit version from the android_winusb.inf in USB_Driver. If you check Subfolders, you only need to point it toward where you unzip RK3188_Root.

[sharonx]

crush

https://dl.dropboxusercontent.com/u/...r800_Turbo.img

with this kernel I got 5 times crashes and restarts in Antutu, so I dialed down to
kernel_cpu1608_gpu600_ddr720

https://dl.dropboxusercontent.com/u/12508344/Pipo%20M9%20Pro/kernel_cpu1608_gpu600_ddr720.img

[LarsR]

Program development on M9Pro - working!

The M9Pro presents one USB Device ID for "Mass Storage" (technically, two if you have an external SD plugged in), a different Device ID while in Bootloader (flash mode), and a Device ID that would come and go with the toggle of USB Debug in Dev options. Each of those three Device groups needs its own driver - and are authored by different companies. The ADB device (M9Pro if that's what appears in boot.prop) is authored by Google and is called Android Composite ADB Interface for me. That driver is included with the Android SDK, but the .INF file that comes with it doesn't include the Device ID presented by the M9Pro. It is possible to modify the .INF file in the SDK to also include the Device IDs for the M9Pro, but you could also probably locate it already modified. In Device Mgr, properties for the M9Pro item that is "unidentified", select the Details tab and change the Property drop down to Hardware ID and you should see
USB\VID_2207&PID_0010&REV_0222&MI_01
USB\VID_2207&PID_0010&MI_01
Those are the ID's you'd need to add to the .INF for the ADB driver. You could probably use the same thing you use for your S3 if you modify its .INF to include the Device IDs. There is also a post here on Freaktab for the ADB driver for "any RK3188" device, but I don't have any URL handy for it (or for other places you could find the needed ADB driver with the .INF already modified).

Bottom line is you need an ADB driver and that is totally independent of the driver needed to flash or to access the SD card(s) on the M9Pro.

YESSS!! Thank you BillinCA, you set me in the right direction

After some research I ended up doing the following steps and got it all to work:

1. Edited the android_winusb.ini file in the "usb_driver" folder included in the Eclipse for Android development package and added the following in sections [Google.NTx86] and [Google.NTamd64]:

;Pipo M9Pro
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01

2. Connected the tablet (with USB debugging set active) to my PC and went into the Windows Device Manager. Selected the unconfigured "M9Pro" device and pointed it to update driver from local disk, from the "usb_driver" folder. The driver installed as "Android Composite ADB Interface" (and for some reason sorted itself under "SAMSUNG Android Phone" in the device tree, but this doesn't seem to matter).

3. Went into the C:\Users\<my user>\.android folder and added the file adb_usb.ini, containing the single line:

0x2207

4. Restarted the adb service to load the ini file and detect the new device. This can be done in Window Services or by opening a command prompt and going to the "platform-tools" folder in the Eclipse dev. env and typing:

adb kill-server
adb start-server

After all this, the tablet showed up as "rockchip-m9pro-<my S/N>" in the Android Device Chooser inside of Eclipse, and I could start my tests!

Cheers,
Lars

[syazh]

stuck at android recovery mode

Hi, I tried to flash this rom a couple of time. the funny thing is that everything went smoothly until it reboot.. what went wrong? it reboot to recovery mode.. huhuhuhu help!!