hi guys, ive got a quick question for you.
When you put the device in to flashing mode (the black screen with the wee USB cable plugging in to the PC)
what driver is installed? when in that mode you should see a different USB device im guessing something like HD7 or perhaps its code name.
anyhow, if someone tell me that i would be very aprechiative, also if you can tell me which driver set its installed from, for instance, OEM11.inf or perhaps a zune driver set.
use device manager, it could be under portable devices or USB devices or windows phone devices, right click on it and go to properties, then details , im looking for the matching device ID, inf name, inf section, included infs
thanks for your time folks!
I don't have all the driver info, but I know it lists the device as "HTC Shubert."
jelliottz said:
I don't have all the driver info, but I know it lists the device as "HTC Shubert."
Click to expand...
Click to collapse
well thats a start, cheers mate! amazing how 60 odd folk looked at this an didnt want to help, your an example to them all!
thanks again
Perhaps i can find the rest of the info trawling through google using that as a start, but if anyone can provide the INF details and device ID it would make my life that much easier!
was that definitely the name for the device as listed in device manager when the device was in update mode? Im finding info for that as the overall device name but not the friendly name, the friendly name is HD7 which is what would be listed in device manager and is listed when the device is connected to the computer in normal mode.
Basically what im looking in to is what exactly is happening when the HD2 is updated, it obviously doesnt work, im looking to find out exactly why that is.
when the HD2 is made to look like an HD7 it works fine and is listed as an HD7 in device manager, but the moment it goes in to update mode it changes back to a LEO device
Obviously this might not be the whole reason it doesnt work but if i can find out what driver is installed for the update mode with the HD7 i can fiddle with the device IDs in the driver inf file and force that to be used instead of the leo drivers. Now that wont work by its self i dont think but its one less thing that might be behind it not updating.
if that doesnt work than the next step is to compare the registery for both devices, but one thing at a time, and the driver issue is possibly the easiest to fix.
Bit weird here !
Hi
I've been having problems with the 801812c error.
After reading about updating the drivers using device manager, and doing so, (my device was listed as HD7) i found nothing changed and I still couldn't update, so I deleted the drivers, and then re downloaded them.
Suddenly I had loads more drivers, and my device is now listed as Windows Phone 7.
Still won't update though !
Sorry, just my tuppence worth.
Garrickus
sorry, say that again, your HD2 which is normally listed as HD7 or whatever you called it in zune, which in flashing mode is listed as a LEO?
so you updated the LEO driver and got it to use a HD7 driver?
so now in flashing mode its listed in device manager as a HD7 and it doesnt update still?
so putting all that aside you uninstalled the HD7 driver? then when you installed it again windows installed it as a windows phone?
again, this is all in the updating mode? in normal operations you will see a windows phone device and the HD7 device.
or are you using a native HD7? and i got that all wrong?
if you do have an HD7, put it in to flashing mode without the cable attached, turn off the device, then hold down the power button and the camera button, when the device turns on let go of the power button and keep holding the camera button, that should put it in to flash mode.
then in device manager check out what device is listed when you connect it to a USB cable, if you plug it in after you load device manager you iwll see which one pops up. then if you wouldnt mind going to properties and look for the info i asked above?
if you do have a HD7 and are having issues updating try this out
Windows phone support tool
and
ChevronWP7.Updater
install the first one which gives you a guide to updating and the second one does all the updating out of zune by its self.,
comes in two flavours, 32bit and 64,
My phone is updateing now, Here ya go!
i564.photobucket.com/albums/ss85/gloves085/Capture1.png
i564.photobucket.com/albums/ss85/gloves085/Capture2.png
i564.photobucket.com/albums/ss85/gloves085/Capture3.png
Apparently I'm a noob and can't post img links yet, so you can go look yourself, just add the http header to each of the above to make them into links.
cheers, so thats using the zune drive pack, now if anyone has the device ID from the details tab?
i think im running in to a rock on this, bloody LEO keeps getting installed no matter what i do, im starting to think that the update mode must have its own registery or at least a protected section thats identifying it, because no matter what i do i cant keep LEO away, which is intresting because its not apart of the zune driver, its a windows mobile driver.... so where it keeps coming from i dont know
When i put my device into bootloader mode and connect it to the pc, Qualcomm Technologies MSM Windows driver was the one that got downloaded. Also, what OS are you running? you need to download windows mobile device center if you're on vista.Windows 7 should install that driver by default. Anyways, my hardware id listed when connected to zune is :
USB\VID_045E&PID_04EC&REV_0000&MI_00
USB\VID_045E&PID_04EC&MI_00
Also, if you're on xp, get the driver from here http://forum.xda-developers.com/showthread.php?t=408105 , its in the 10th post..
cheers for that, i shall check that out tonight, i had a small amount of progress last night, i have been able to perminantely change the driver installed to a windows phone driver, although its still called LEO for some odd reason, but anyway, so instead of a invaid registry error i now get a timed out error.
So im assuming the driver ive chosen wasnt correct, with out a hardware ID of a HD7 in update mode it gets quite difficult, however ill have a look through that driver you poster a link too, im on win 7 but even if i can locate the ID from that file i may be able to find a working complete driver set i can use.
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.....
Hello,
I have searched thoroughly on this site and I cannot find any help. I used to have vista ultimate and I down loaded the usb modem drivers and it worked like a charm. I had to re image my pc and now I have vista business. However now when I try to load the drivers they do now show up on the device list and it does not successfully install the modem. Am I missing something? is there an updated driver? Can anyone please help or point me to where I can get some help. I really need to get back on line. Thanks XDA
I have a suggestion which might work.
Look at your device manager and see if there is anything on there thats coming up as unidentified... if there is, and with the phone connected to activesync so the PC knows the phone is there (assuming activesync is working), delete those entries one by one and when you delete one you need to click *scan for hardware changes under the *actions menu.
If you didnt start from scratch with the PC - IE format the hard drive and rebuild the system - that may mean there is a corrupt version of the driver still floating about and causing problems. This is why in the places I have worked we always backed machines up - did a full format - and then either imaged or rebuilt the box manually.
Another option is to go online to the manufacturers support site for updated drivers and install them from a location you have saved them too to your hard drive..
From my experience dealing with recalcitrant USB devices I would think that the first issue is more likely.
However there is another possibility that may be the root of the problem. I know that different versions of Vista support different connectivity options and setups - aka Vista Basic doesnt do Active Directory or Domains (im dredging this up from memory so its a little hazy). There is the remote possibility that the Business version doesnt support phones as USB modems, although I would be very surprised if that was the case.
It does strike me as a little odd that you have gone from one version of the same OS to a different version of the same OS and have had this sort of problem... but then Microsoft are known for compatibility gremlins - two words - Windows ME
Hope that helped.
I know, it is very surprising to me that now it does not work on Vista Business. You would think that it is basically the same OS but with less features. It is the 32 bit version. Its driving me crazy because I depend on it to do my work from my laptop and it just does not populate the device name when browsing and selecting the drivers. It sees the device it just does not pupulate. When I try to do the right click and install it does install it but it still does not show up under modems. If any one else has more suggestions I will greatly appreciate it.
No need to panic fello xda members and friends. It is all good now...i am typing thins theteering from my laptop through my tilt. Thanks xda you are the best. The speed trough my tilt is faster than my 2wire at home....ftw.:d
Alright so I was trying to update the rom on my phone to no avail, always the damn program (custom ruu.exe) came up on the last screen displaying error 262 (update error) which is VERY common.
So I find in multiple forums of people recommending a certain update of the diamond phone series, I dont know why the f^*( I tried it, halfway in the update the phone went dark, and now wont turn on AT ALL.
I try the soft reset, battery out for a while, reinstall active sync, try in different pc's (win7 64bit, xp 32bit) no hope so far.... Well the ONLY sign of life is when I plug the phone via usb cable to either PC there is a hardware detected under "Qualcomm CDMA technologies MSM"
I believe its some sort of diagnostic mode to access the phone, but I cannot find drivers ANYWHERE! Please folks help me out is this thing done? is there hope?
PS i tried to update the drive on the Qualcomm device to wince usb (HTC USB SYNC) and it will install, however since IM NOT ABLE to go in the bootloader what else can i try?
i cannot access the bootloader & phone would not turn on.
mrjacob212 said:
Alright so I was trying to update the rom on my phone to no avail, always the damn program (custom ruu.exe) came up on the last screen displaying error 262 (update error) which is VERY common.
So I find in multiple forums of people recommending a certain update of the diamond phone series, I dont know why the f^*( I tried it, halfway in the update the phone went dark, and now wont turn on AT ALL.
I try the soft reset, battery out for a while, reinstall active sync, try in different pc's (win7 64bit, xp 32bit) no hope so far.... Well the ONLY sign of life is when I plug the phone via usb cable to either PC there is a hardware detected under "Qualcomm CDMA technologies MSM"
I believe its some sort of diagnostic mode to access the phone, but I cannot find drivers ANYWHERE! Please folks help me out is this thing done? is there hope?
PS i tried to update the drive on the Qualcomm device to wince usb (HTC USB SYNC) and it will install, however since IM NOT ABLE to go in the bootloader what else can i try?
i cannot access the bootloader & phone would not turn on.
Click to expand...
Click to collapse
I hate to be the one to tell you this, but sounds like your only hope lies in using jtag (which is not easy or cheap, could try a warrenty exchange.)
zelendel said:
I hate to be the one to tell you this, but sounds like your only hope lies in using jtag (which is not easy or cheap, could try a warrenty exchange.)
Click to expand...
Click to collapse
You could also put it in a microwave, or hook it up to a car battery, say it fried it self, then get a new on warranty
so you guys are telling me theres 100% nothing i can do?
not even with the qualcomm usb situation?
mrjacob212 said:
so you guys are telling me theres 100% nothing i can do?
not even with the qualcomm usb situation?
Click to expand...
Click to collapse
so you flash a diamond gsm rom on cdma rhodium your device is one expensife brick its not easy to unbrick it best you can do is say you charge it all night and found not working in the morning send it in for repair and hope you get new one
a good advice read read read before even trying it always be shore
threads like this should get pinned for eternity.
hah i was thinking something like that, except that i just noticed battery low before sleeping, seemed drained in morning, wont turn on now, tried a friends battery and same problem.
PS: the main reason this happened and propably similar threads, is because there are notices to UPDATE YOUR TP2 with a DIAMOND UNLOCKER which misleads us novice users! its a shame for this to happen to such an expensive phone, and i wont usually do what ill attempt, but cant repay this company $600 for a simple fix for them.
mrjacob212 said:
Alright so I was trying to update the rom on my phone to no avail, always the damn program (custom ruu.exe) came up on the last screen displaying error 262 (update error) which is VERY common.
So I find in multiple forums of people recommending a certain update of the diamond phone series, I dont know why the f^*( I tried it, halfway in the update the phone went dark, and now wont turn on AT ALL.
I try the soft reset, battery out for a while, reinstall active sync, try in different pc's (win7 64bit, xp 32bit) no hope so far.... Well the ONLY sign of life is when I plug the phone via usb cable to either PC there is a hardware detected under "Qualcomm CDMA technologies MSM"
I believe its some sort of diagnostic mode to access the phone, but I cannot find drivers ANYWHERE! Please folks help me out is this thing done? is there hope?
PS i tried to update the drive on the Qualcomm device to wince usb (HTC USB SYNC) and it will install, however since IM NOT ABLE to go in the bootloader what else can i try?
i cannot access the bootloader & phone would not turn on.
Click to expand...
Click to collapse
you could try getting insurance for the phone trough a bank etc register it wait for a month with them and say u lost it or something
[frustrating] HELP HD7 seen as "generic device" not as WP, drivers fail to install
So i got my wp7 today...i download zune on my windows7 pc, install, connect the phone....ERROR installing drivers, the phone is seen not as a mobile device, but as a generic usb composite device...in the device management window i have two "unknow device" icon...tried EVERY POSSIBLE SOLUTION i found on the internet...worked for others, not for me...
...then i think maybe it's my pc, so i try my xp netbook...SAME HAPPENS...
previous owner says he connected the phone to zune flawlessly on three different PCs...
i also did a full reset from the settings
HELP I'M DESPERATE
anyone?
It seems that your device is in diagnostic mode (the 2 unknown devices are typical for this...)
for now there is no way back, but if this is without you hacking something or so you could let it repair by warranty...
is it a complete new device?
thank you very much for the answer...
this is getting intresting
my situation is similar to his one
http://forum.xda-developers.com/showthread.php?t=937235
but that image isn't showing up on my hd7 and my two devices are "unknown devices" no shubert, just unknown device.
(EDITrobably because he has his pc set up to receive the phone in diagnostic mode, but my pc isn't)
Now what i think is that the previous owner did some tethering (he told me that), but didn't put it back into zune mode...then he did a hard reset before giving the phone to me...but i'm pretty sure the reset doesn't FLASH the plain rom, but only wipes data because it's too fast
so i'm stuck here with a half usable wp7...nice
elmerendeiro said:
thank you very much for the answer...
this is getting intresting
my situation is similar to his one
http://forum.xda-developers.com/showthread.php?t=937235
but that image isn't showing up on my hd7 and my two devices are "unknown devices" no shubert, just unknown device.
(EDITrobably because he has his pc set up to receive the phone in diagnostic mode, but my pc isn't)
Now what i think is that the previous owner did some tethering (he told me that), but didn't put it back into zune mode...then he did a hard reset before giving the phone to me...but i'm pretty sure the reset doesn't FLASH the plain rom, but only wipes data because it's too fast
so i'm stuck here with a half usable wp7...nice
Click to expand...
Click to collapse
Did you try right clicking the device in device manager and selecting update driver software, then click Search automatically for updated driver software?
Mine kind of did the same thing until I allowed it to connect to microsoft and got the driver from them.
Also you could also check HTC website for HTC HD7 driver software.
Yep, but it doesn't find any driver...even if i point it directly to the zune drivers folder...the only driver that seem to get installed is "windows phone USB device" or something like that..i have to install it manually, then one of the two unknown devices transforms into that wp USB..the other one remains unknown, unless i force it to install "Windows phone" from portable devices->microsoft...then it fails and give me error10, but still the icon changes to the portable device one...
From HTC i will probably get vague or dumb answers...like "try hard reset"
Tomorrow i will see the guy who sold me the hd7 and try to connect to zune on his pc...if it works i have to keep it otherwise he will refund me...he says he tried with hd2 to tether then uninstall the tether software without putting it back to zune mode and he says that it works with no issues...HELP
i maybe wrong, but maybe u can try to load one of those rom's for europe brands, it may re set all the settings on your hd7...
but the best will be for the first owner to show you the way he did it...
so when he didn't put it back into zune mode there is no way back at the moment..
i will tell you if i know more...
the diagnostic mode isn't set on your computer... it's on the Qualcomm SoC (System on a Chip)
The drivers you need are somewhere http://forum.xda-developers.com/showthread.php?t=922000 here (don't know exactly where)
but that won't help you much as you only get "HTC Diagnostic Interface" as Serial Device...
so you have to wait till there is a solution....
btw. I'm stuck in the same situation ;-) (Diagnostic Mode) xD
and there are lots of other people too, so you are not alone ^^
best regards
EDIT:
@truffle1234:
i tried flashing another rom a few weeks ago, but it didn't help...
so it's better for all to stay with the stock-rom at the moment because we cannot get back to it at the moment
it's better for warranty
So if the phone is in diagnostic mode, it shouldn't properly connect to zune on the previous owner's pc,right? Let's see
it shouldn't connect normally at any pc...
ok, did the same on his pc so i got refunded...now maybe i go omnia7...the loose volume rocker and the visible sim card through the back cover have really bugged me in just one day...in any normal company who's responsible for that crap would be insta fired...i mean, didn't they produce any test device before sending the papers to production???? meh...
wp7 was nice btw
got another hd7 (no see thru battery cover, and no loose volume rocker this time!) and connected to zune flawlessly...so definetly that one was stuck in diagnostic mode
Great news, hope you enjoy it. It's a decent device and a great OS!
jimbonics said:
Great news, hope you enjoy it. It's a decent device and a great OS!
Click to expand...
Click to collapse
well should be more than decent as it's supposed to be the top of htc wp7 line...but still...
i got a 2nd hd7 just because i hate big bezels around the screen...if omnia7 had a smaller case around that 4inch would definetly have been my choise
is there a fix for this? I feel like throwing my phone out the freaking window. ugh!!
What exactly is your problem turbo? What OS are you using, etc?
Here's what I can say about this.
Install Zune. Reboot your computer. Let your computer FULLY boot.
Plug in your phone. Seriously be patient and let your PC think for a good 3-5 minutes. The first time it goes through this it is NOT a quick process.
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.