Related
I have been running Windows Vista x64 Ultimate for some time now. I have been able to sync fine for some time now but all of sudden I am unable to now. I have tried flashing back the original AT&T ROM and still haven't had any sucess syncing it to Vista. I was doing some reading on Microsoft's website and found this solution to the exact problem that I am having.
I have re-installed WMDC 3 times already, so I don't think that's the problem either. I can't do a system restore because my restore only goes back that far. My phone is able to sync fine with Windows XP Professional so I pretty sure it has something to do with Vista, not working correctly.
Here is the error that I get and Microsoft's solution to the problem:
Windows Mobile Device Center fails to connect due to the Windows Portable Device driver failing to load. In some cases, you may be unable to connect and only a red X error icon is displayed in Windows Mobile Device Center. This can be caused by Windows Portable Device driver failing to load. Connect your device
Go to Manager (Computer > Properties)
Find the Portable Devices node
Locate the Windows Mobile device entry
Choose to uninstall the driver
Reconnect your device
I tried following the directions but I am not sure where to go. What is Microsoft talking about when it says go to Manager? I have no idea where that is. Any help would be greatly appreciated. I am been fighting with this for some time now, about a week in all, and I still haven't been able to figure it out.
Oh this ActiveSync issue was thought to be resolved by WMDC but not yet completely. Anyway, you might try the above as Microsoft says. Manager is the Device Manager. You shall find it by right-click on My Computer icon, select Properties and in the Window that opens, a link to Device Manager is at the left top corner. Is that the one you were looking for?
Regards,
Carty..
Carty said:
Oh this ActiveSync issue was thought to be resolved by WMDC but not yet completely. Anyway, you might try the above as Microsoft says. Manager is the Device Manager. You shall find it by right-click on My Computer icon, select Properties and in the Window that opens, a link to Device Manager is at the left top corner. Is that the one you were looking for?
Regards,
Carty..
Click to expand...
Click to collapse
Thanks for the quick reply but I don't think that is it. I have searched through the device manager and couldn't find anything that related to what Microsoft said. I was just wondering if there was something else they were refering to but I was guessing it was Device Manager. However I thought they would just say "Device Manager" if that's what it really was.
Dude, i think you are on the right track. The "Manager" is definitely "Device Manager" although the Portable Devices item will not actually be displayed in Device Manager if the Kaiser / TyTN II is not actually connected to the PC via USB / Bluetooth.
Try connecting the phone to the PC and check Device Manager again. If the Portable Devices heading does not show up with the phone connected the steps suggested by Microsoft may not fix your problem. Let us know how you get on. I have 3 vista PC's here with me so I may be able to help you work it out if you still have no luck.
Cheers
Chris
I needed a hotfix from microsoft before i could even sync mine the first time.....
Hi
My beloved HTC HD7 on O2 (Unlocked now) advises me that their is an update.
I imagine this is the pre-update to the No-Do update
However everytime i try to install i get to stage 6 and then the error 801812C is reported.
I have searched this and found the same answer in every article regarding-
"During Step 6 (Rebooting your phone), your Windows OS detects your phone as a new device and starts searching for driver updates online. This can be seen when you click on the little indicator with a spinning green circle in the bottom-right corner of your desktop called the notification area (you might need to click on Show Hidden Icons if it's hidden)."
"You have to *immediately* click on "Skip Obtaining Device Software Online" or Zune will time-out and show error 801812C1"
However i see no option come up on XP to allow me to stop such device updates. And i definatly have no hidden icons!
Someone please help with a better solution...
Jayne (Yes i am a girl so be nice, so sartactic answers please, I am Tech savvy but this one eludes me)
From what you post, it sounds as if maybe you have to right-click the notification icon in the system tray for that option.
From what i understand from the OP's first post, she doesn't have the icon so can't right-click it.
I know it's not really a solution, but have you tried updating on a Windows 7 machine? I've always thought that windows 7 is more compatible with WP7. I know this isn't excplicitly mentioned anywhere, but why else would the Dev Tools only be available in Win7? strange....
Windows 7
Many thanks
Yes indeed no notification is showing and I have set the taskbar not to hide inactive icons so nothing can be lurking!
I will see if i can find someone with Windows 7 as i'm a XP user through and through lol
Many thanks for the ideas so far but if anyone has another brain wave please contribute, I don't want to miss out on the proper upgrade when it arrives..this week fingers crossed eh!
same error here
Hi Jayneh,
I too have an HD7 on o2 (Sim unlocked, but stock otherwise).
I am also an XP sp3 user, and I'm getting the same error as you, 801812c1.
The update fails at step six. The phone will reboot and then show a picture on the screen suggesting I connect my phone to the pc, despite the fact it is connected already. I've tried three times with no joy so far.
I've done some searching and as you say, the current theory is that after rebooting the phone, the pc doesn't recognise it as WP7, but Wm, and proceeds to hunt for the right drivers. This will of course fail, and the update times out.
Several users on different model of phone have reported the error and Microsoft are advising you hold off updating until the issue is investigated.
A number of users are saying they are using Windows 7, so it can't be an Xp specific problem.
Several fixes have been reported by some users which include unplugging and re connecting the phone quickly, or stopping the pc hunting for non existing drivers by clicking the update icon in the notification area. This does not seem to work for everyone.
I have tried unplugging which didn't work for me. I looked for the update icon but can't see one, but in anycase, my machine runs incredibly slowly during the whole process so doing anything at all is frustrating.
One thing I haven't seen anyone reporting is whether they use the same machine to sync a WM6.1/6.5 device or not. I do, but I'm just grasping at straws here.
I'm also slightly worried as I only have a little over 10GB left on the laptop.
Here's hoping NoDo isn't a NoGo for us.
Garrickus
Many thanks Garrickus, as long as i'm not alone with this and it is being looked at, hopefully if all else fails the fab developers on here will soon have us an update rom we can port straight to our HD7's. Fingers crossed and hope the sucking up to the developers speeds this along
One solution to the 801812C1 error code
jayneh & Garrickus,
Do you have windows automatic updates turned off?
I had automatic updates turned off (XP Home 2002) and I had the same problem when I first tried updating.
After reading something elsewhere, I turned automatic updates back on and tried updating again 24 hours later. It worked, with the update running smoothly through all 9 steps without a hitch.
I don't know if you have to wait after turning automatic updates on, I just thought it would be prudent.
I'm also using an HTC HD7 on the o2 network. I hope this information helps you like it helped me.
Ian.
Automatic updates
Hi Ian,
Thanks for your feedback regarding automatic updates.
Unfortunately, I have automatic updates turned on, and PC and Zune are fully up to date, so that's not an option for me.
Interestingly, Zune had a minor update after a couple of failed phone updates and now when the little bubble pops up it describes my device as 'Zune' not 'Windows Mobile', but still getting same error code and updates fails exactly the same.
I see their is no specific response to this error code from Microsoft as yet
Are you still experiencing problems Jayneh ?
Garrickus.
Update
I was still having problems and my PC was/is up to date and automatic updates is on.
I say was because i now have the NoDo update having followed the brilliant update method by Petbede for updating without a gold card.
It went smoothly and here i am with a speedy phone and cut and paste. My god bejewelled loads so much quicker
frustration
Im using Vista, have the same problem as Garrickus. HD7 on Vodafone network. After reboot the device pops up as Zune device and computer tries to look for Zune drivers, after some time it gives up. I have tried all ways of updating drivers, nothin works.
Hi everyone,
I experienced that problem today downgrading my HD7 with Zune installed on XP SP3, three times it didn't work...then i closed all running app like firefox & other utilities...and the downgrade process worked at least...
My advice : just be patient!
Update WP7 driver on PC before running the WP7 upgrade
The error '801812C1' appears when the phone is wrongly identified as a 'Zune' device (MS MP3 reader !) after the phone restarts at step 6 of the WP7 March 2011 upgrade.
In order to set the correct WP7 device on the PC:
1. Shut down the phone (press & hold the power button)
2. Restart the phone and press & hold the camera button
3. A black screen appears on the phone showing a device connected to a PC
4. Connect the phone to PC on USB port
5. Open Device Manager on PC and check the entry for Portable Device: 'Schubert' (= HD7) or other name (depends on your phone).
6. Shut down the phone (press & hold the power button) and restart it.
7. Connect the phone to PC and run the WP7 upgrade from Zune.
The error '801812C' no longer occurs at step 6.
Imerda said:
The error '801812C1' appears when the phone is wrongly identified as a 'Zune' device (MS MP3 reader !) after the phone restarts at step 6 of the WP7 March 2011 upgrade.
In order to set the correct WP7 device on the PC:
1. Shut down the phone (press & hold the power button)
2. Restart the phone and press & hold the camera button
3. A black screen appears on the phone showing a device connected to a PC
4. Connect the phone to PC on USB port
5. Open Device Manager on PC and check the entry for Portable Device: 'Schubert' (= HD7) or other name (depends on your phone).
6. Shut down the phone (press & hold the power button) and restart it.
7. Connect the phone to PC and run the WP7 upgrade from Zune.
The error '801812C' no longer occurs at step 6.
Click to expand...
Click to collapse
This worked perfectly!! Thank you!!
I got a error "801812C0" and it said device couldnt be updated. i took the battery out and restarted it and it was updated wtf lol
Hello everyone,
I am sure this is one of the most often asked questions around here. But I am going to ask anyway because I've not been able to use the solutions provided before and my research elsewhere has not yielded the results I expect.
So here goes. I have a T-Mobile MDA Vario III connected to a new-built Window 7 (Home Premium version) using a USB cable. On connection, Windows detects a new "Generic RNDIS" device and starts downloading the driver for it. From the message on the screen, it seems to have found the driver but fails when it tries to install.
So far I've tried the following:
The Microsoft Solution of Pausing the Windows Update Service, Clearing the %WINDIR%\SoftwareDistribution\Download and %WINDIR%\DataStore\ folders, resuming the service and then re-trying. This does not change the error.
On my mobile, go under Start > Settings > Connections > USB to PC > {Uncheck the only option} - This seems to partially work as Windows 7 now discovers a "Serial" device and promptly installs a "HTC USB Sync" driver for it. But this does not seem to be very useful because I cannot see a new drive or any other signs of a new device being attached (other than under the USB list). Turning ON the unchecked box takes me back to square one.
Uninstalled *everything* and then installed Windows Mobile Device Center v6.1 from Microsoft's site. However, that does not help with the RNDIS as it continues to find a driver, yet is unable to install it
I've tried hard AND soft resetting the device in various combinations with the above options - again, to no use.
Are there any other options that I can try? Any other suggestions are welcome.
thank you in advance..
tropicanapure said:
Hello everyone,
I am sure this is one of the most often asked questions around here. But I am going to ask anyway because I've not been able to use the solutions provided before and my research elsewhere has not yielded the results I expect.
So here goes. I have a T-Mobile MDA Vario III connected to a new-built Window 7 (Home Premium version) using a USB cable. On connection, Windows detects a new "Generic RNDIS" device and starts downloading the driver for it. From the message on the screen, it seems to have found the driver but fails when it tries to install.
So far I've tried the following:
The Microsoft Solution of Pausing the Windows Update Service, Clearing the %WINDIR%\SoftwareDistribution\Download and %WINDIR%\DataStore\ folders, resuming the service and then re-trying. This does not change the error.
On my mobile, go under Start > Settings > Connections > USB to PC > {Uncheck the only option} - This seems to partially work as Windows 7 now discovers a "Serial" device and promptly installs a "HTC USB Sync" driver for it. But this does not seem to be very useful because I cannot see a new drive or any other signs of a new device being attached (other than under the USB list). Turning ON the unchecked box takes me back to square one.
Uninstalled *everything* and then installed Windows Mobile Device Center v6.1 from Microsoft's site. However, that does not help with the RNDIS as it continues to find a driver, yet is unable to install it
I've tried hard AND soft resetting the device in various combinations with the above options - again, to no use.
Are there any other options that I can try? Any other suggestions are welcome.
thank you in advance..
Click to expand...
Click to collapse
use this Driver.... for more details about Use this method only if you have Windows Vista or Windows 7 go to --> http://forum.xda-developers.com/showpost.php?p=3932827&postcount=3
I use my Lumia 920 as my main communications device with unlimited internet/tethering from my provider. The Wifi internet sharing feature works fine but is a HUGE drain on the battery. Plus I have concerns about the safety of wifi!
Ideally I wanted to tether to my computer using USB but there doesn't seem to be a lot of information about regarding this with WP8.
Has anyone found a way to do this? Have I been missing something obvious?
I would recommend against using your phone as a router, it will simply die a lot faster due to high hardware stress.
http://microsoftarena.net/usb-tethering-in-windows-phone-7/
WP8 should be similar.
mcosmin222 said:
I would recommend against using your phone as a router, it will simply die a lot faster due to high hardware stress.
http://microsoftarena.net/usb-tethering-in-windows-phone-7/
WP8 should be similar.
Click to expand...
Click to collapse
Thanks for the link, unfortunately, this doesn't work on either the Lumia 900 or 920. Nokia don't seem to have built the option the same as Samsung.
As for the hardware stress, thankfully in the UK we get a 2 year warranty! It'll be up to Nokia to repair/replace if my phone dies using one of the built in features
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
[*[Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
this way doesn't work on Windows phone 8 s by htc =(
allesand said:
this way doesn't work on Windows phone 8 s by htc =(
Click to expand...
Click to collapse
my htc 8x dosent work with these code ##634# work but *#7284# doesnt work
these drivers don't seem to work for windows 8.1. Any idea where to get them?
No, sorry. It took me hours of searching to find them for Win7. They should, in theory, be pretty standard drivers; you could maybe find ones that work for an Android phone with the same Qualcomm USB modem and tweak the INF file to get them to install for the Windows phone. I don't have an easy solution, though.
The USB tethering code (*#7284#) doesn't work on my Sprint Atic S Neo. Is this a known issue on the Sprint version of this phone?
For some reason Windows 8 x64 doesn't like these drivers. It complains there isn't a hash for the file. I guess back to test-signing mode....
Diag codes
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
(deleted text)
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
Thanks for the drivers
I found it interesting that additional features appeared in Ativ S T899M after diags turned on (##MFG# replies with Odyssey_121205 on diagnostics page) EXCEPT the ability to gain better control of APNs.
With my Ativ S (T899M again) the #7284# does nothing when entered into the diagnostic app.
I was wondering if there is a decent listing of all (or at least some) of the diagnostic codes.
whoops!
ramjetwiebe said:
Thanks for the drivers
I found it interesting that additional features appeared in Ativ S T899M after diags turned on (##MFG# replies with Odyssey_121205 on diagnostics page) EXCEPT the ability to gain better control of APNs.
With my Ativ S (T899M again) the #7284# does nothing when entered into the diagnostic app.
I was wondering if there is a decent listing of all (or at least some) of the diagnostic codes.
Click to expand...
Click to collapse
WHOOPS!
Missed the star in front of the hash when I entered the command. Should have been *#7284# which works just fine. Should have done more than copy and paste.
also found the complete listing by W_O_L_F ( http://forum.xda-developers.com/showthread.php?t=2311626 )
!SPOOHW
ramjetwiebe said:
WHOOPS!
Missed the star in front of the hash when I entered the command. Should have been *#7284# which works just fine. Should have done more than copy and paste.
also found the complete listing by W_O_L_F ( http://forum.xda-developers.com/showthread.php?t=2311626 )
!SPOOHW
Click to expand...
Click to collapse
There's even more things hidden in there that's available by using the native toast launcher in the hacking forum.
I have a Sprint ATIV S Neo and *#7284# does nothing.
However...
##3424# takes me to the proper screen (Micro USB Test).
Still haven't found drivers for 8.1 yet though...
You'll need to use the Native toast launcher to bring it up.
Sent from my Lumia 928 (RM-860) using Tapatalk
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
Hi everyone, especially the writer of the quoted post, i know this is a old post but i just want to tell how to install the driver on Windows 8.1 64 bit in case if someone ended up here.
Windows 8.1 64 bit won't allow users to install unsigned driver like the driver he attached (Actually, the driver is signed, but i forget the reason why windows recognize it as unsigned driver. Please refer to the previous post). So, to make windows allow that, use this instruction:
http*://www*.howtogeek.*com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
nb: remove the star. i'm new here, so i can't post a link.
After you follow the instruction, then install the driver as the guy described.
I've tried this method, and it's work!
Pearlian said:
Hi everyone, especially the writer of the quoted post, i know this is a old post but i just want to tell how to install the driver on Windows 8.1 64 bit in case if someone ended up here.
Windows 8.1 64 bit won't allow users to install unsigned driver like the driver he attached (Actually, the driver is signed, but i forget the reason why windows recognize it as unsigned driver. Please refer to the previous post). So, to make windows allow that, use this instruction:
http*://www*.howtogeek.*com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
nb: remove the star. i'm new here, so i can't post a link.
After you follow the instruction, then install the driver as the guy described.
I've tried this method, and it's work!
Click to expand...
Click to collapse
Pearlian,
How did you find this driver?
I am looking for an modem driver for HTC One (M8) and would appreciated if you can point me in the right direction for my Search.
Volosat1y said:
Pearlian,
How did you find this driver?
I am looking for an modem driver for HTC One (M8) and would appreciated if you can point me in the right direction for my Search.
Click to expand...
Click to collapse
Ok, i've figured it out. Here is a link to my post.
Hello again.
Windows Phone Developer Registration tool doesn't "see" my device. I've double checked all requisites (.net framework, IpOverUsbSvc, phone listed in file explorer, screen unlocked, correct time, internet connected, etc.) The only issue I can think of is the fact that I still haven't set up a Microsoft account in the phone; but... is this reason enough for the WPDR tool to not even see the phone?
Any hint appreciated. Thanks!
That's probably the cause, yeah. You could try setting up the account to see if it works, then...
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
zogoibi said:
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
Click to expand...
Click to collapse
Well maybe the virtual Win 8 OS with WP8 SDK recognized your phone because Win 8 has the winusb drivers build in. On Windows 7, you need to install these winusb driver (you normally have a unrecognized device called Windows Phone 8 in the Device Management).
Link to the drivers : http://catalog.update.microsoft.com/v7/site/Search.aspx?q=winusb http://catalog.update.microsoft.com...updateid=90462af8-f533-4522-9ad1-dcc969d94832
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
zogoibi said:
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
Click to expand...
Click to collapse
You need to visit the website with Internet Explorer. Go to google type "winusb windows phone microsoft update catalog" and go to the site with "catalog.update.microsoft.com" in the URL. If you don't see the download link of the driver type "winusb windows phone" in search. There should be an unrecognized device called "Windows Phone 8" in the device manager (start menu -> My Computer -> right mouse click -> Manage -> Device Manager in left context menu) for this driver to be installed, if not I can't help you further.
Thanks Bruce. I've done what you said and was able to download winusb. It's a .rar package containing two files, winusbcompat.cat and winusbcompat.inf. Now, if I'm not abusing your patience... what do I do with them?
[EDIT] Ok, don't bother. I figured out how. Actually this solved my problem. After properly installing the winusb driver, the WP8 SDK lite by Arnold Vink recognized my phone.
Thanks to everybody who helped me "out".
Now I wonder how could I mark this thread as "solved"...
Hi,
My Nokia Lumia 925 won't respond to anything (NSU, NSU->”My phone does not startup or respond”, Nokia Care Suite->recover phone, volume down + power button,…).
Already leave it charging for several hours. Can’t have any reply from the phone.
Now the phone is kind of dead. Can start it and the only thing I see Is a QHSUSB_DLOAD (Nokia Emergency Connectivity) in PC.
I have tried many things according to internet but i can't get any success windows device recovery tool is also not detecting my phone and it is not listed in it. i have tried thor command also not working it says invalid hex file.
Please help me to recover my phone from QHSUSB_DLOAD mode.