Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
Hi guys, I've had a fair read through the forum already but can't find a solution to my problem.
I have a HTC Magic which I have rooted and am running cyanogen 6.0 RC.
My problem is with my girlfriend's Tmobile HTC G2 (Hero).
I initially tried running the 2 part update from Tmobile but receive the yellow triangle error so am told to downgrade my rom from the HTC site.
I cannot for the life of me get this to work, HTC sync works fine. I run the uud.exe file update and the phone boots to UUD usb mode,xp informs me of "android 1.0" being connected and the installer gives me error [171] USB connection error.
The program then terminates, the same thing happens following the guide: http :// forum .xda-developers. com/showthread.php?t=645253&page=3 (cant add the link)
I'm stuck for ideas. Booting into hboot (power on and vol down) gives me my spl:1.76.007 which know for the magic was the perfect spl. The radio is 6.35.07.08.
Any help would be appreciated, all I want is this retched device to be upgraded from android 1.5!!!
Thanks in advance.
Nath
As noted in my FaQ please follow my guide on Correct drivers and check the bootloader drivers section. This should fix your issue.
Not development related, reported to be moved to Q&A.
buddn, I have the same phone all stats identical and got the same error too. It locked up the phone on the skate-boarding android screen and let a nervous half-hour of searching before pulling the battery and it restarted fine.
If you solve this please post back what I/we are doing wrong.
btdag, can you be any more specific? Do I have to use your drivers? I have used ones from the latest HTC Sync and the latest Android-SDK, I'm running Windows 7.
Currently setting up the XP mode in Win7 as plenty of people seem to recommend flashing from XP instead. But progress is slow as the hours I have to play are limited!
Thanks both,
Craig
What ROM version are you running currently and what are you trying to downgrade to?
I had SPL 1.76.0007 originally, I ended up using the engineering SPL (2007) but that was for other reasons.
But btdag's guides are really well laid out, sometimes you do have to uninstall all your drivers and just follow his steps, I know I have in the past and that normally solves everything! He provides links to ADB and HTC Sync drivers, but personally I use the ones from the ADK and the latest HTC Sync I could find... but then I'm a bleeding edge kind of guy
Can you both try the "GoldCard" Test Procedure for me in my guide here
This has been done today and there may be some edits necessary to get it completely working, it's also designed for Windows 7 rather than XP or Vista and should work on both x86 (32-bit) and x64 (64-bit) systems. Having said that it should also work on XP and Vista in a similar way.
dancollins said:
But btdag's guides are really well laid out, sometimes you do have to uninstall all your drivers and just follow his steps, I know I have in the past and that normally solves everything! He provides links to ADB and HTC Sync drivers, but personally I use the ones from the ADK and the latest HTC Sync I could find... but then I'm a bleeding edge kind of guy
Click to expand...
Click to collapse
I have updated my guide to use the latest HTC Sync drivers as they appear to support adb correctly. I'll be editing my driver guide soon and possibly removing it altogether. I'm also a bleeding edge kind of guy but i've only recently found the latest version of the drivers to work. I had no idea about the implications, until now.
hey.
i have a tmobile g2 and i used btdag's guide for rooting it. seeing i tried to simple procedure and failed, i resorted to the goldcard method. it took me only 3 hours xD.
the reason it took me so long was the wrong drivers. when i reviewed the guide i tried the drivers mentioned there and it work. oddly enough, stock drivers that came with the g2 were said to be for g1 magic. the gold card method works flawlessly and now i have a rooted hero with amon_ra's recovery and custom rom.
btdag, mate, thanks for the guide. helped a lot.
oh and yeah...the "downgrade" was actually an upgrade seeing i had an even older rom on my hero (bought 6 weeks ago). stock rom was android 1.5 (ancient )
Thanks btdag, that revised goldcard tutorial worked a treat! I now have 2.73.4705.5 installed and can play properly!
The problem I had was the fastboot driver not being installed hence not connecting to the exe file upon the reboot. After installing the correct driver for that the process worked a treat.
As a side note, I couldn't connect to htc sync after changing the driver but it wasn't needed.
Thanks for all your help. Got a "buy me a beer" link?
Nath
Glad to have two positive responses to the revised guide.
@buddin - i also can't connect to htc sync at the moment, i'm wondering whether its because of my rom but maybe it is the software/driver, i'll look into it further.
I don't have a "buy me a beer" link cause I have only re-written other peoples work. Thanks for the praise though
i had the same problem about the htc syncr for weeks, it doesn't syncronise , i found that if uncheck USB debugging, and pull down the notification bar check the syncro and then open HTC syncro then it syncronises.
i think it something to do with, when ADB is setup and working somehow it cancels the HTC syncro, but who needs HTC syncro when you got ADB
i find HTC syncro useless comparing it to ADB. except from sync contacts and calendar ,that about it, nothing more. thanks to Btdag with his so made easy to follow guides and the all the devs for doing what HTC could not do.
try it guys, i may be wrong !!.
cheers
I have a brand new bone stock dinc 4g lte.
I have activated sim and all features of phone work except when trying to connect via DIAG (##3424#).
Phone enters diag mode just fine.
USB debugging is enabled; Charge only is the PC connection.
My laptop is windows xp 32-bit.
I have installed the HTC Drivers: HTCDriver3.0.0.007
However, whenever I plug the phone in it recognizes new hardware: "Android Phone" and "HTC DIAG"
But after clicking "Install software automatically" it searches and then fails (even though I know the drivers are there).
When not in diag mode I can see my memory card and transfer files back and forth so I know part of the drivers are working.
What am I doing wrong?
*I found my own solution so I thought I'd post it just in case anyone else had my same problem.
1) I followed all the steps in the procedures listed in this thread, but needed to "disconnect my phone" before clicking "have disk".
This allowed me to successfully install drivers and connect to QPST. However.........
2) When I was connected QPST showed a question mark in front of my ESN. So I read and found that for this phone we need v2.7 build 3.74.
This did the trick!
3) I can verify that the "open sesame door" procedure works on this phone! Now can anyone confirm that it works for the Verizon HTC One also?
Read here
Thanks for replying so quickly! I'm glad to see you still use this phone.
I actually looked at that very thread before I started this one. QPST does not see the phone, so there aren't any phones listed when I try to add the port. So I can't click the "read phone" step in your directions because it's grayed out..
I've tried a different cable and different xp computer, and still can't load drivers!
Any other suggestions?
You should notice the diag drivers are not the same as the 3.0.0.007 drivers. Check that post I linked again.
Sent from my Incredible 4G LTE using Tapatalk 2
Are you talking about this link?
>When you have QPST installed Proceed to get your HTC Diagnostic Drivers, you can get them HERE
If so, that is what I've tried and hasn't worked.
Are there other driver download links in that thread I am missing?
I also tried all of the drivers you had stickied, but none worked.
This is very frustrating. Any other ideas?
supermaxkato said:
Are you talking about this link?
>When you have QPST installed Proceed to get your HTC Diagnostic Drivers, you can get them HERE
If so, that is what I've tried and hasn't worked.
Are there other driver download links in that thread I am missing?
Click to expand...
Click to collapse
Strange, I remembered the drivers posted to that thread being correct. In any case, a simple google search for "htc diag drivers" brings this up as the first result: http://forum.xda-developers.com/showthread.php?t=697487
If there is a thread with diag drivers then I've looked at it. So yes I looked at that post already. But maybe there is another way to connect to qpst without diag drivers? Or is it possble that I don't have something enabled correctly on this brand new phone?
Is there another way to create a virtual com port besides using dm router?
instead of automatic install have you tried doing it manually.
choose drivers, navigate to file, update driver?
synisterwolf said:
instead of automatic install have you tried doing it manually.
choose drivers, navigate to file, update driver?
Click to expand...
Click to collapse
Yes; I've followed this exact same process many times.
I just did it again (re-downloaded the files from the link you posted).
HIs instructions show windows 7 and I have xp, but it shouldn't matter.
When I choose his x86 drivers it always gives me this error:
HTC DIAG
When it finds new hardware "HTC DIAG" pops up in all caps.
Are drivers case sensitive?
Because all of the drivers I am manually choosing are lower case.
Could it be that is why they don't "contain information about my hardware?"
BTW, I have installed HTC diag drivers on this laptop (and my desktop) for my incredible 2 and have no problems connecting. So I'm struggling to understand why this one is so difficult!
Mine was for the evo LTE not the incredible LTE
Going home in a few, I'll see if I can get it to work and I'll report back.
Sent from my iPhone 5 using Tapatalk 4 beta
Thanks so much for your help!
Do you have a windows XP you can test it on?
I've tried 2 XP machines (both with SP3) and 2 different cables, but no luck.
I'm so glad people actually try to help on this forum (unlike some other forums).
It's been a few days; anyone able to help this phone work with windows xp? My incredible 2 was a breeze compared to this one.
Thanks to anyone who might be able to help!
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hi guys. I downloaded an update for Windows 8.1 on my laptop and ever since, some of my drivers have gone to crap. Anyways, I would like to root my old HTC EVO 3D (HTC EVO V 4G for Virgin Mobile), but I can't. First, I tried all of the "on device" root methods like Poot, Framaroot, z4root, etc. but none of them work. So then I finally tried rooting from the laptop but NO drivers I can find will work for this old device on a newer laptop. If there are any WINDOWS 8.1 (not 8) drivers out there for the HTC EVO V 4G model PG86100 that you can link in the comments or something, that would be spectacular. Also when I attempted rooting it a while back on command prompt I got the message "waiting for device" and it would never give me new information. If you paste in youtube: How To Root HTC EVO 3D [CDMA/GSM - Sprint and Virgin Mobile, Android ICS 4.0.3, HBOOT 1.58] you can see where I got stuck after typing in "fastboot oem get_identifier_token" Finally I tried Kingo Android Root, but it doesn't see the device, so I assume the driver still doesn't work.
PS: I was successful in rooting my LG G2 so I'm not entirely a noob.
Thanks for whoever can help.
DevStep said:
Hi guys. I downloaded an update for Windows 8.1 on my laptop and ever since, some of my drivers have gone to crap. Anyways, I would like to root my old HTC EVO 3D (HTC EVO V 4G for Virgin Mobile), but I can't. First, I tried all of the "on device" root methods like Poot, Framaroot, z4root, etc. but none of them work. So then I finally tried rooting from the laptop but NO drivers I can find will work for this old device on a newer laptop. If there are any WINDOWS 8.1 (not 8) drivers out there for the HTC EVO V 4G model PG86100 that you can link in the comments or something, that would be spectacular. Also when I attempted rooting it a while back on command prompt I got the message "waiting for device" and it would never give me new information. If you paste in youtube: How To Root HTC EVO 3D [CDMA/GSM - Sprint and Virgin Mobile, Android ICS 4.0.3, HBOOT 1.58] you can see where I got stuck after typing in "fastboot oem get_identifier_token" Finally I tried Kingo Android Root, but it doesn't see the device, so I assume the driver still doesn't work.
PS: I was successful in rooting my LG G2 so I'm not entirely a noob.
Thanks for whoever can help.
Click to expand...
Click to collapse
I never had luck with older HTC fastboot drivers once I updated either. I actually do this stuff as a hobby and a job so work on LOTS of different phones and this is the most frustrating to me because of this. I keep a backup Win 7 PC just to do HTC stuff. I have tried tons of drivers, guides, rebooting, manual and auto driver installs and nothing helps. Most of the stuff I see says the issue is just for USB 3,0 ports, but I can't get the 2.0 ports to work either. I have no issues with the driver installs for adb and for MTP or USB mass storage, just fastboot refuses to work meaning you can't do half the stuff needed to start rooting them like unlocking the bootloader.
Only thing to really try is to just uninstall all HTC drivers from your PC, then reboot, then install HTC Sync, let it install the drivers, uninstall Sync (optional) and leave the drivers, and reboot. This probably won't help, but at that point, don't get too upset and just find a friend with a Win 7 PC. lol Good luck.