CANNOT get RSDLite to recognize atrix, help needed.. - Atrix 4G Q&A, Help & Troubleshooting

I've been looking around the net for about an hour and have not gotten any answers.
The info:
-Running GingerBlur 4.5
-NOT Unlocked
-Using Windows 7 64bit
-Have used multiple versions of RSD Lite
-Moto drivers installed.
Whats the problem? RSD Lite 5.3 will NOT recognize my atrix when its plugged in. I have tried everything i know of (reboot device, PC, change USB ports, install and reinstall all drivers and RSD) and nothing.
It simply will not recognize my device, even though my computer does and says all drivers installed.
Im trying to unlock and flash a new ROM. Can Gingerblur possibly be causing the issue? Ive read that Win7 64bit may be the problem? Any and all help would be appreciated

i beleve its been updated to 5.5 and also install your drivers and use the usb plug in the back of your pc
EDIT ;;;;;;!Ican confirm its been updated to 5.5. when i googled rsd lite 5.5 it
was the first topic /download on xda
Sent from my MB860 using xda premium

I heard also that WIN7 64bit has some problems RSD.
Try using a different comp with lower WIN version (I know for sure that Vista 32bit works great).
I don't think that the GingerBlur can have any effect, its just a mod, something a little more complex then a theme. besides I unlocked my BL when I was running GladiAtrix, which is another mod, and it went without problems...
Good luck

ltdanno360 said:
i beleve its been updated to 5.5 and also install your drivers and use the usb plug in the back of your pc
EDIT ;;;;;;!Ican confirm its been updated to 5.5. when i googled rsd lite 5.5 it
was the first topic /download on xda
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I have version 5.6 on my home computer. It is probably higher than that now as I have had it for a while.
I use Windows 7 64 bit without any problems.
You should definitely try a different USB port. There is a common issue of one USB port not seeing devices, whuile the port next to it does.
Uninstall the drivers and Motohelper if you have it, then reinstall Motohelper. I have found that installing Motohelper is better for driver install. You do not need to install the drivers seperately if you install Motohelper, as they are installed with Motohelper.
Boot into fastboot, connect your phone to your PC, bring up a command prompt and, in my case, I do 'cd C:\moto-fastboot' which is the location I have moto-fastboot at. (Obviously you need moto-fastboot on your PC). Then type in 'moto-fastboot devices'. If your computer sees your phone it will be listed and you should be good to go. The just 'moto-fastboot reboot' to reboot your phone.

Thanks for the replies, however i did use an older computer, Vista to be exact. It recognized my phone instantly, i flashed the SBF...
Failed to boot 2... FML
I've been looking all around and am currently going to flash the pudding 2.3.4 SBF. Is that a good call?

CaelanT said:
I have version 5.6 on my home computer. It is probably higher than that now as I have had it for a while.
I use Windows 7 64 bit without any problems.
You should definitely try a different USB port. There is a common issue of one USB port not seeing devices, whuile the port next to it does.
Uninstall the drivers and Motohelper if you have it, then reinstall Motohelper. I have found that installing Motohelper is better for driver install. You do not need to install the drivers seperately if you install Motohelper, as they are installed with Motohelper.
Boot into fastboot, connect your phone to your PC, bring up a command prompt and, in my case, I do 'cd C:\moto-fastboot' which is the location I have moto-fastboot at. (Obviously you need moto-fastboot on your PC). Then type in 'moto-fastboot devices'. If your computer sees your phone it will be listed and you should be good to go. The just 'moto-fastboot reboot' to reboot your phone.
Click to expand...
Click to collapse
I probably should have just tried that before flashing the pudding SBF. Hmm, its currently executing the file, so im kinda SOL at this point.
I upgraded to 5.5 RSD and it still wouldnt pick up my phone? Tried multiple USB ports. Its not my computer not recognizing it, because it chimes and picks up my phone just fine...its RSD.

Well, after flashing the pudding 2.3.4, its stops loading at the white ATT screen, phone will not continue booting. Suggestions?

How long on that screen?
It can take 10-15 minutes to boot up after flashing.

erick161 said:
I've been looking around the net for about an hour and have not gotten any answers.
The info:
-Running GingerBlur 4.5
-NOT Unlocked
-Using Windows 7 64bit
-Have used multiple versions of RSD Lite
-Moto drivers installed.
Whats the problem? RSD Lite 5.3 will NOT recognize my atrix when its plugged in. I have tried everything i know of (reboot device, PC, change USB ports, install and reinstall all drivers and RSD) and nothing.
It simply will not recognize my device, even though my computer does and says all drivers installed.
Im trying to unlock and flash a new ROM. Can Gingerblur possibly be causing the issue? Ive read that Win7 64bit may be the problem? Any and all help would be appreciated
Click to expand...
Click to collapse
I tried also to use Rsdlite on my Win 7 64bit laptop without any luck. My other laptop with same software installed normally works but not the one I had with me at the time. I ended up using a very old XP laptop with shattered screen and no battery and worked like a charm.
I had exactly the same problem with Motorola software update as well. On Some machines they simply refuse to work.

Have you tried booting in RSD Support mode?
Turn the phone off.
Push Volume + rocker and keep it pressed while turning the phone on.
That will boot up the phone in RSD mode and I've always had success with that method.
Hope that helps.

CaelanT said:
How long on that screen?
It can take 10-15 minutes to boot up after flashing.
Click to expand...
Click to collapse
Yeah...I reflashed it when i thought it wasnt working, left it alone and it booted up just fine. Running pudding 2.3.4 GingerBread...
CSharpHeaven said:
I tried also to use Rsdlite on my Win 7 64bit laptop without any luck. My other laptop with same software installed normally works but not the one I had with me at the time. I ended up using a very old XP laptop with shattered screen and no battery and worked like a charm.
I had exactly the same problem with Motorola software update as well. On Some machines they simply refuse to work.
Click to expand...
Click to collapse
yup, my computer still will not recognize it! Only my old netbook w/ XP.
noobsquared said:
Have you tried booting in RSD Support mode?
Turn the phone off.
Push Volume + rocker and keep it pressed while turning the phone on.
That will boot up the phone in RSD mode and I've always had success with that method.
Hope that helps.
Click to expand...
Click to collapse
RSD mode isnt the problem, getting RSD Lite on the computer to recognize the device is the problem.

In my experience, MotoHelper is the culprit. Find the drivers itself without motohelper and try. I figured this out putting a Photon in diag mode, it wont let me read, said the port was already opened. Well was the motohelper service.
Uninstall all drivers and install just Motorola Drivers:
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-32-bit-38123.shtml
or the 64 bit version.
Hope it helps

pmcnano said:
In my experience, MotoHelper is the culprit. Find the drivers itself without motohelper and try. I figured this out putting a Photon in diag mode, it wont let me read, said the port was already opened. Well was the motohelper service.
Uninstall all drivers and install just Motorola Drivers:
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-32-bit-38123.shtml
or the 64 bit version.
Hope it helps
Click to expand...
Click to collapse
There are so many contradicting things w/ RSD lite and Win7 64bit. I ended up just manually installing the drivers, still wouldnt work on my PC, had to us XP on my netbook.
I flashed pudding 2.3.4 last night and tried messing with Rom Manager, but it says my phone no longer has root priviledges (had root previously, was running gingerblur 4.5). Superuser is installed on my phone however. Rom Manager states...
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone."
How should i reattain root? The SBF was supposed have root preinstalled i thought. Can i flash the BL unlock, use Rom Racer and flash Darkside or something? Or will i not have root still?
I havent quite kept up w/ the Atrix development since the BL was unlocked, and there seems to be many methods and multiple uncleaned threads.
Now this thread is no longer about RSD...but basically restoring root without flashing the wrong thing and bricking my device.

yea when I went from gingerblur gingerbread. I had to re root I just used gingerbreak again and it worked
Sent from my MB860 using xda premium

Change to USB 2.0
Change to USB 2.0

Related

T-mobile uk Hero goldcard but can't run RUU, USB error - help!

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.

Windows 8 + DNA in Fastboot = Nope

I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).

USB debugging mode.......

Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).

Can't find correct Windows 8 64-bit drivers.

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.

[Q] Stuck on fastboot not recognizing my device

hello.
i think i have already tried everything to get fastboot on my pc find my device, but no luck.
I've got an old laptop with usb 2.0 + windows 8.1 x64 Pro and the same OS on my PC with usb 3.0 (according to some of threads, my CPU is i7 4770k and my MOBO is MSI Z87-G45).
I use my HTC Desire X every day and it is simply slow. I cannot try every ROM cause of need to flash boot.img. And i Dont have any idea how to get the fastboot recognize my device....
Maybe someone have some time to help mi wlak through this 'issue' idiot friendly? I'm really confused and i dont have any idea what to do.
my hboot is 1.25.** JB. S-ON. I have installed TWRP recovery.
:crying: halp
EDIT:
SOLVED. Windows 7 FTW.
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Will_Xda said:
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Click to expand...
Click to collapse
So,what did you do ?:d
evnee said:
So,what did you do ?:d
Click to expand...
Click to collapse
Installed a HTC sync like program named PDAnet, and updated the drivers from that program, once in fastboot mode device is recognized in pdanet and in a command prompt (adb). this only worked on a usb2.0 port though.
(didn't bother replacing usb3.0 drivers as suggested elsewhere as this has caused big issues for me before.)

Categories

Resources