Page 4 of 4 FirstFirst ... 234
Results 61 to 71 of 71

Thread: Driver problems pipo m8 pro 3g

  1. #61
    Senior Member pr0xZen's Avatar
    Join Date
    Jun 2013
    Location
    Trondheim, Norway
    Posts
    397
    Quote Originally Posted by bokkie View Post
    It's off. Double and triple checked but still won't recognise it as mass storage device and won't have the rockchip drivers either.
    Any ideas?
    If you flashed CWM recovery - boot into recovery, connect your tablet, go to Mounts and Storage, and select "mount USB storage" and give it a few seconds. As long as you stay in this menu (says so up top), it should mount sdcard and ext_sdcard as USB mass storage. Its not the most practical method - but it could serve to indicate if its an Android issue or something else. It could ofcourse also serve as a temporary (yet not the most practical) solution.
    Support your local flasher
    Current devices : Pipo MAX M8 Pro - Samsung Galaxy S4 - Intel NUC

  2. #62
    Member
    Join Date
    Jul 2013
    Location
    u k.
    Posts
    65
    Thread Starter
    Thanks, I'll try that tomorrow. Does the "mount USB storage" come up on the tablet screen once I click Boot into recovery?
    I've never done this before so just want to make sure I get it right.

  3. #63
    Senior Member pr0xZen's Avatar
    Join Date
    Jun 2013
    Location
    Trondheim, Norway
    Posts
    397

    Re: Driver problems pipo m8 pro 3g

    No, a menu comes up. You navigate with scrolling up/down by swiping (its slow), and select option by power button. What you're looking for is within menu alternative "Mounts anf Storage" on the main menu.
    Support your local flasher
    Current devices : Pipo MAX M8 Pro - Samsung Galaxy S4 - Intel NUC

  4. #64
    Member
    Join Date
    Jul 2013
    Location
    u k.
    Posts
    65
    Thread Starter
    Thanks for the tip Mate, that did the trick.
    Although I did notice that when I plugged it in when it was in recovery it said cannot find drivers for your rk3066 device. Isn't the pipo m8 pro a rk3188 device?

  5. #65
    Senior Member pr0xZen's Avatar
    Join Date
    Jun 2013
    Location
    Trondheim, Norway
    Posts
    397
    Quote Originally Posted by bokkie View Post
    Thanks for the tip Mate, that did the trick.
    Although I did notice that when I plugged it in when it was in recovery it said cannot find drivers for your rk3066 device. Isn't the pipo m8 pro a rk3188 device?
    Yes it is. Is it windows (xp) giving off this message, or the flashing software?

    Reboot to flash mode with the Reboot app, while connected by usb. Go to device manager - and if the tablet comes up as anything, try updating with these drivers: https://dl.dropboxusercontent.com/u/...ockUSBv3_5.zip

    Note: After 2 minutes of no flashing activity, the tablet will power off. Just boot it normally, or hold esc+power to boot (USB CONNECTED) from powered off state, and keep holding for a few seconds. It should boot straight to flash mode. (loader).
    Support your local flasher
    Current devices : Pipo MAX M8 Pro - Samsung Galaxy S4 - Intel NUC

  6. #66
    Member
    Join Date
    Jul 2013
    Location
    u k.
    Posts
    65
    Thread Starter
    It's in vista that the message comes up.
    I'll give it a go tomorrow, is the reboot to flash just so that the pc sees the tablet?
    Are those drivers updated from Rileyrom 1.7 which I flashed?

  7. #67
    ROM Developers rrileypm's Avatar
    Join Date
    Mar 2012
    Location
    Springdale, AR USA
    Posts
    8,506
    I have never encountered this on my Windows 7 Started laptop, but on my Windows 7 64 desktop I have been seeing Windows trying to load drivers every time I connect a tablet, which I stop Windows from searching further for it. If I manually put the tablet in flash mode, either by external keys or by using the Reboot app, the Flash Tool recognizes the tablet in flash mode and I'm able to flash with no problem...I'm just unable to use the button on the tool to reboot to flash mode.

    It isn't really a problem, since I know it is happening...but I thought I would share this experience.
    Randy
    Freaktab Developer, Moderator and "Flashaholic".
    Read my BIO Here
    Thanks, for your continued support. Funds are low right now for new projects, so your help is greatly appreciated.
    Donate here

  8. #68
    Senior Member pr0xZen's Avatar
    Join Date
    Jun 2013
    Location
    Trondheim, Norway
    Posts
    397
    Quote Originally Posted by bokkie View Post
    It's in vista that the message comes up.
    I'll give it a go tomorrow, is the reboot to flash just so that the pc sees the tablet?
    Are those drivers updated from Rileyrom 1.7 which I flashed?
    Reboot to flash mode is for rebooting to flash mode ^^, - So that the pc will see the tablet in the mode that actually requires the rockship drivers. if the tablet is NOT in flash / loader mode - but i "ordinary" USB Mass storage mode - windows should use its own native usb drivers. There should be no need for any rockchip drivers except for in "flash mode" (loader).

    These 2 different modes will represent Windows with 2 different Hardware ID's from the tablet, but only one of them will show in each respective mode.

    A multifunction printer might have for instance printer, scanner, fax and sd card reader functionality. Each of these "functions" will have its own hardware ID for the respective drivers (for each function) to adress. And, the multifunction printer will show ALL of these hardware ID's simultaneously. This defines it as what Windows calls a "Composite Device". It has several functions, each with its own Hardware ID and each Hardware ID has its own driver - yet Windows recognizes it as a single unit.

    Now the RK3066 and RK3188 tablets (for instance your M8pro) - Only show one Hardware ID at a time - one for Flash Mode (loader), and one for USB storage. Each mode has its own driver; Flash mode uses the RockChip drivers, USB storage uses Windows own native USB drivers.

    When it is designed this way (only showing one Hardware ID at a time in different modes) - Windows will "see" your tablet as 2 separate individual devices.

    --
    The drivers with the RileyROM 1.7 (i don't know about the 3G version, just downloaded wifi-only version) - are 3.0. The drivers I linked to are 3.5. Always use the latest drivers available if you can - so please try to upgrade them as instructed earlier.

    After that, I suggest that you connect with the tablet on in "normal" (usb storage) mode, no usb debugging - and leve the flash tools closed. Go to device manager, look for device (that should now be in USB mass storage mode) - and "update" driver. Let windows search for the drivers - and install standard windows USB drivers for it. Those are the correct drivers for USB mass storage mode.
    Last edited by pr0xZen; 07-16-2013 at 02:27 AM.
    Support your local flasher
    Current devices : Pipo MAX M8 Pro - Samsung Galaxy S4 - Intel NUC

  9. #69
    Junior Member
    Join Date
    Jun 2013
    Location
    Australia
    Posts
    16

    An easy solution for those stubborn android driver problems

    Quote Originally Posted by bokkie View Post
    It's in vista that the message comes up.
    I'll give it a go tomorrow, is the reboot to flash just so that the pc sees the tablet?
    Are those drivers updated from Rileyrom 1.7 which I flashed?
    I noticed this thread too late to be of help to bokkie who had to apply a heavy solution, but I'll leave this tip here for the many who will encounter the same problem in the future:

    For those stubborn cases with Vista or Windows 7, there is an easy way to remove (or force-remove) wrong drivers that remain stuck in the Windows driver store. (The driver store was introduced with Vista and kept with later versions to enable Windows to store trusted drivers for reuse. It causes a lot of trouble)

    The following application saved me from this madness once:

    DriverStore Explorer (http://driverstoreexplorer.codeplex.com/) is more than an explorer. It allows deletion of driver packages from the store, even enables force deletion for some drivers that resist being removed the standard way.
    In my case under Windows 7, even though the correct drivers appeared to install correctly, they would let me flash the tablet, but not use ADB. It failed to see the tablet, so I could not root the tablet or do other basic jobs. I even built a special ADB driver for the M8 pro... Nothing worked, I was going crazy!

    That's when I tried DriverStore Explorer. It showed me several (5 if I remember well) old drivers that I had thought had been successfully removed a long time ago. Even some that I had used for my 3 years old tablet. They were still lurking in the store.
    I deleted all these old android drivers, had to force delete 2 or 3 of them if I remember well.

    After that I reinstalled the latest driver and everything (flashing and ADB, etc..) is now working as it should.
    Last edited by pan2fire; 07-30-2013 at 03:19 PM.

  10. #70
    Senior Member pr0xZen's Avatar
    Join Date
    Jun 2013
    Location
    Trondheim, Norway
    Posts
    397
    I would advice care when using this solution. If the "errorous" driver is one of the Windows native usb drivers - keep in mind that these are an integral part of Windows usb function - and actually deleting these (if this program can actually do so) may cause a wide array of issues.
    Support your local flasher
    Current devices : Pipo MAX M8 Pro - Samsung Galaxy S4 - Intel NUC

  11. #71
    Junior Member
    Join Date
    Jun 2013
    Location
    Australia
    Posts
    16
    Quote Originally Posted by pr0xZen View Post
    I would advice care when using this solution. If the "errorous" driver is one of the Windows native usb drivers - keep in mind that these are an integral part of Windows usb function - and actually deleting these (if this program can actually do so) may cause a wide array of issues.
    I am pretty sure that this program can remove a driver automatically installed by Windows using the "force-remove" option.
    I have never tried it however as all the Android drivers lurking in the driver store of my PC had been installed by me.
    My guess is that removing an automatically installed bad Android driver to replace it by a correct driver from the manufacturer would be no different from removing a previous manually installed Android driver to replace it by a correct manufacturer driver.
    However it is only a guess and pr0xZen is right to give this warning.

Page 4 of 4 FirstFirst ... 234

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •