04-02-14 01:38 AM
116 ... 345
tools
  1. kaymre's Avatar
    Finally, I fixed it!

    The reason it does not work may be different for you - your pb may have been recognized but disabled, or have the tcp properties disabled, or have wifi enabled, or you may just have a broken pb

    In my case Windows (7, 64 bit) couldn't find a driver for the PB usb network interface. Blackberry Desktop Manager was installed, I even installed the USB driver package from their website but to no avail.

    Then here's what I did:

    1) removed BB desktop manager and BB drivers, unplugged the PB and rebooted

    2) copied the following files to a temporary folder from another computer where the PB works fine (see below for a zip archive): netrndis.inf, oem21.inf, netrndis.pnf, RimSerial_AMD64.sys, RimUsb_AMD64.sys, RNDISMP.sys, rndismpx.sys, usb8023.sys, usb8023x.sys (these are from c:\windows\system32 and i'm pretty sure only some of them are actually needed...)

    3) plugged in my PB and went to Windows' device manager: an unrecognized device appeared (usb) with an yellow esclamation mark. I chose update driver, did a manual (not automatic) search and chose oem21.inf (from the temporary folder, step #2)

    4) Windows recognized the driver as "Research In Motion Network Device" (finally!) but complained it didn't like it... I said install it anyway

    5) made sure smb sharing was enabled, by running the following commands (one by line):
    sc config LanmanServer start= auto
    net start LanmanServer
    sc config lmhosts start= auto
    net start lmhosts
    net start Browser

    6) opened \\name_or_address_of_your_playbook\media\

    I can now do whatever I want with my files and folders, install .bars with DDPB, etc. and best of all, I don't have the horrible Desktop Manager installed... the drivers alone are less than 300 kb in size :-)

    Hope it works for you too... and sorry for my english!

    EDIT: I have uploaded my usb drivers here: http://www.mediafire.com/?dk2mla12a74efdn
    Keep in mind that these are only for Windows 7 64-bit, as I don't have access to other Windows versions!
    Last edited by kaymre; 05-06-12 at 12:06 PM. Reason: Added link to usb drivers
    sputneek likes this.
    05-06-12 12:59 AM
  2. Saidz's Avatar
    I tried all of the solutions suggested in this thread to no avail. Eventually, I realized that although Desktop Manager does not allow me to access the files on my PB, it did allow me to perform a full backup, so I made a backup and did a security wipe. When I tried to restore the data on my PlayBook Desktop Manager told me the restore file 'may be corrupted'. In short, I've lost all my PB data so please do not try this at home!
    Last edited by Saidz; 05-08-12 at 07:07 PM.
    05-08-12 12:47 PM
  3. bengaliweb's Avatar
    sorry not to read all the topic, but similar problem with XP after a reinstall no device recognised with my PB was solved with this

    http://btsc.webapps.blackberry.com/btsc/KB29216

    I found it with keyword browse on the error E:0x35

    hope this helps !!

    Philippe
    Last edited by bengaliweb; 06-06-12 at 02:47 PM.
    06-06-12 02:45 PM
  4. FF22's Avatar
    Thanks for sharing.
    06-06-12 04:20 PM
  5. arhcangel's Avatar
    I had been wrestling with the USB connectivity with BlackBerry Desktop since it was released. I could generally connect with the "unbrick" process (even when it wasn't bricked) but this process would erase all data & media from the Playbook. Restoring consumes hours. However, I was almost always frustrated when attempting a simple media sync.

    Recently, while at work, I was able to connect and sync without issue. Surprised, I discovered that I could consistently plug and unplug with the desired connection behavior with BB Desktop.

    The difference, the only difference, is that at work my notebook is docked while at home it is powered by a Dell AC power adapter. The adapter powering the docking station is 130W, the home power brick is 90W. Plugging a 130W power adapter into the notebook at home resulted in the same positive and consistent results as work.

    I believe that the power/current delivered to the USB ports of my notebook directly affects the connectivity with the Playbook over USB. For the record, file sharing via WiFi has never been a problem, regardless of where the notebook was powered, or if running via battery. But, if I need the BB Desktop synch capability, I must ensure full power to the USB ports.
    Even though I am connecting my PlayBook to a desktop I thought you might be on to something. The PlayBook is notoriously finicky when it comes to its power needs. In my system the Network adapter showed up in Device Manager but quickly errored with "This device cannot start. (Code 10)". Despite the error BB Device Manager still showed it connected with an IP address but the adapter did not show up in Network Sharing Center. I decided to try another USB port. A USB/eSATA hybrid port and viola! no more error.
    07-26-12 09:56 PM
  6. kdkd008's Avatar
    When I went to Network Connections, I found that my RIM network was disabled. I enabled it and it mapped Z drive only for a few minutes and then told me something was wrong with my password? I uninstalled Desktop Manager and went to Network Connections again and disabled and enabled RIM connection and now it's working fine. RIM should really fix this as it keeps happening with new updates from the Playbook and from Desktop Manager.



    THANK YOU THANK YOU THANK YOU!

    Step 5 was what fixed it for me.
    On windows 7 Pro version the steps are a little different so here is what I did.
    -go to control panel>network and sharing center then on the left side you should have an option for "change adapter settings"- click on it
    You should then see your network connections, with any luck one will say "local area connection 2, unidentified network, Research In Motion Network device" right click on it and go to properties.
    then like step 5 above put a check on
    "client for Microsoft networks"
    "File and printer sharing for microsoft networks"
    "internet protocol Version 4 (tcp/ipv4)
    Hit ok, wait 2min and see if anything starts installing if it doesnt disconnect your playbook wait a few and then plug it back in. you should now see that its installing more stuff and adds a Z drive under my computer, network.

    For those that dont have the "Research in motion network device" in device manager under network adapters. The drivers on my system show that they are located in C:\windows\system32\DRIVERS\mdismpx.sys and
    C:\windows\system32\DRIVERS\usb8023x.sys

    My data transfer from PC to playbook went from 142kb to 5-6mb
    08-16-12 05:34 AM
  7. danzainvisible's Avatar
    at last! a big thank you to (avaio) for his fix on page 2 of this thread i had tried everything to get my computer to recognize my playbook with no luck.then tried avaio fix ie type mscofig etc. ty tony
    08-18-12 09:57 AM
  8. RohrohrohURboat's Avatar
    The thing that worked for me was just to turn off wi-fi and bluetooth before plugging the PB into the PC on USB. Prior to that it just wouldn't play ball, but once wi-fi and bluetooth were switched off the drivers installed and it was recognised as a network drive and recognised by Desktop Manager with no problem...

    Bill
    I've been banging my head against my desktop trying to find out why my play book took forever to connect to the DM and then failed!?!

    Tried almost everything posted here but the issues were WIFI and Bluetooth. With them off, USB connection to DM works like a treat

    Now I can backup and get a bit of 2.1 action
    otaku2 likes this.
    10-03-12 08:32 AM
  9. otaku2's Avatar
    @RohrohrohURboat

    You sir, are a genius.

    Many many many thanks.
    10-14-12 01:47 PM
  10. bitek's Avatar
    for me rolling back drivers option in device manager worked on windows 8.I have tried to turn off wifi,bluetooth but this did not help. i went to device manager and clicked on "research in motion network device" and under driver "roll back driver". this worked and the driver did install properly.
    thatplaybookguy likes this.
    01-10-13 08:41 PM
  11. thatplaybookguy's Avatar
    your trick did the trick for me, started at this at 10 am my time, now almost 2am. i am so glad I found this thread thanks bitek. saved me from turning my laptop into a frisbe. but windows 8 sucks. deleted everything I had, even my backups.
    bitek likes this.
    01-16-13 11:10 PM
  12. krayZpaving's Avatar
    Turning off WiFi works for me. As long as WiFi is off when the PlayBook is plugged into the computer, the drive connects beautifully as a mounted volume. If WiFi is on, then only mounting as a network drive works. This is a new behaviour in the last few weeks - perhaps a Windows Update has changed something?
    05-20-13 11:03 PM
  13. seaswho's Avatar
    The thing that worked for me was just to turn off wi-fi and bluetooth before plugging the PB into the PC on USB. Prior to that it just wouldn't play ball, but once wi-fi and bluetooth were switched off the drivers installed and it was recognised as a network drive and recognised by Desktop Manager with no problem...

    Bill
    This is what worked for me ! After 3 hours of trying everything else.
    FF22 likes this.
    05-24-13 01:54 AM
  14. LuanNguyen69's Avatar
    Just turn on the developement mode. Remember the developement address, windows + r ,\\thefaddress and paste your porny horny movies. cheer up !
    04-01-14 09:47 AM
  15. LuanNguyen69's Avatar
    For those who is still has this problems. I 've just found an easy way to make the Blackberry Desktop Software connects your playbook.
    My way is open the Services . find the service named Blackberry Device Manager and turn it on.
    Gook luck !!
    04-02-14 01:37 AM
  16. LuanNguyen69's Avatar
    For those who is still has this problems. I 've just found an easy way to make the Blackberry Desktop Software connects your playbook.
    My way is open the Services . find the service named Blackberry Device Manager and turn it on.
    Gook luck !!
    04-02-14 01:38 AM
116 ... 345
LINK TO POST COPIED TO CLIPBOARD