I have a Desire 500, no brand, never touched, I would flash a rom stock more updated, I think I understood that I have to go before the release through the site HTCDev, then the flash recovery, then flash the rom. The problem is that I block in the first phase. Downloaded the sdk and fastboot from the site, I installed the drivers (HTCDriver_4.1.0.001 although the installation does not convince me, proceeds and closes by itself) then htc sync, but the phone in bootloader mode is not recognized Windows 8.1, I always error in the recognition in fact I have question mark in device manager, also trying to update the drivers from device in manual, either by downloading google android usb driveres, indicating that the folder the SDK. In fact, the command "fastboot oem get_identifier_token command" I have always "waiting for device".
Can you tell me what I can try to solve?
DRAFF said:
I have a Desire 500, no brand, never touched, I would flash a rom stock more updated, I think I understood that I have to go before the release through the site HTCDev, then the flash recovery, then flash the rom. The problem is that I block in the first phase. Downloaded the sdk and fastboot from the site, I installed the drivers (HTCDriver_4.1.0.001 although the installation does not convince me, proceeds and closes by itself) then htc sync, but the phone in bootloader mode is not recognized Windows 8.1, I always error in the recognition in fact I have question mark in device manager, also trying to update the drivers from device in manual, either by downloading google android usb driveres, indicating that the folder the SDK. In fact, the command "fastboot oem get_identifier_token command" I have always "waiting for device".
Can you tell me what I can try to solve?
Click to expand...
Click to collapse
Is not working on Win 8 or Win 8.1 try with win 7 or later version of windows.
driter said:
Is not working on Win 8 or Win 8.1 try with win 7 or later version of windows.
Click to expand...
Click to collapse
I agree an this one. It does work perfectly with Windows 7 32/64.
Related
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.
davewuvswaffles said:
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.
Click to expand...
Click to collapse
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:
Try a different USB cable, or port, or a different computer..
Your phone says Fastboot or Fastboot USB?
Remove unneeded drivers
elfrisi said:
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:
Click to expand...
Click to collapse
If Windows PC can see phone in normal working state ( like MTP device / Android ADB / USB disk ect ... ) mean - you no need to worry - HW is OK, then try to use a small free tool called DeviceRemover and just clean unneeded ( wrong / old / damaged / ect.. ) FastBoot driver(s) from your system and then try again to connect phone in fastboot mode. Hint - use last tab "Display Mode" to select "Hidden / Deattached" devices - these that not work for you.
elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
You'll have to use a different computer, one running a pre windows 8.1 os.
Windows 8.1 only recognises fastboot for 1.55 or greater bootloaders at the moment.
I had the same situation and had to re-install windows 8 which was a bit drastic but solved this problem
If you're having trouble with the connection in Windows 8.1 like that your Phone does not get recognised, easiest solution get a Linux Live ISO on a USB stick.
Get Universal USB Installer from here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Let it Download a UBUNTU Live ISO
Let the Programm install it on your USB stick and set the Persistent File Size to your liking
Boot from the stick
Open Terminal Window
Install "adb" and "fastboot" with .... sudo apt-get install android-tools-adb android-tools-fastboot
Connect the Phone and check if the Phone is recognised (fastboot devices or adb devices)
Do the update
Well, it was a driver issue. I did everything using the Mac OS X partition of my MacBook (for some odd reason I thought all this process was "exclusive" to Windows due to the exes and whatnot, but I was wrong). Now I am running the Stock Google Play Edition on my phone with no issues.
Having a strange problem with my HTC One (m7) where adb works fine and can even reboot to bootloader, but fastboot doesn't see the device.
My HTC One is S-Off and rooted and unlocked. Running Android Revolution HD 31.5 (JB 4.3) and my current recovery is TWRP.
The computer is running Windows 8.1 x64.
I've got the latest Android SDK installed, and can run both adb and fastboot from command prompt with no problem.
I've got the latest HTC Sync manager installed so the drivers should be there as well.
adb works fine, I can issue "adb devices" and it shows my device and serial number and I can do all other things with adb as well (so no issue with USB cable or port either).
I can boot to bootloader with "adb reboot bootoader" and when I'm there it shows "Fastboot USB" so that looks ok as well.
But fastboot doesn't see the device. "fastboot devices" returns nothing.
I've tried searching the forums and googling and everything, but can't find anything. I'm at my wits' end. Any help greatly appreciated.
aryonoco said:
The computer is running Windows 8.1 x64.
Click to expand...
Click to collapse
That is the problem mate
google: fastboot windows 8.1 and you will find your answer im sure.
alray said:
That is the problem mate
google: fastboot windows 8.1 and you will find your answer im sure.
Click to expand...
Click to collapse
You were indeed correct, and I was obviously googling for the wrong thing. I just didn't think the 8.1 update would have broken that...
Anyway, for the record, this guide helped me fix it by replacing Microsoft's USB drivers with Intel's. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Oh, and thanks to Microsoft for wasting hours of my time with your buggy driver Times like this I really miss my Linux box.
fastboot not returning anything
deleted
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
rocktv88 said:
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
Click to expand...
Click to collapse
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
TomFader said:
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
Click to expand...
Click to collapse
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
rocktv88 said:
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
Click to expand...
Click to collapse
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
TomFader said:
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
Click to expand...
Click to collapse
Are you on S-off?
Anyway, I would do the RUU. restore your phone and try again with a good custom ROM. Did you check MD5 with the rom you download? You still can connect your phone with ADB. That mean your phone is not brick yet. : )
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
clsA said:
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
Click to expand...
Click to collapse
You are right, i can confirm hboot 1.54.0000 - i was flashing the RUU to convert my HTC ONE toa Google Edition.
So all I need is a windows 7 or lower pc to get fastboot running again?
That's good news, I would have searched for ages.
Yeah it's frustrating I know
If you use the 1.54.000 from the 4.4 GPe update it works also
Sent from my HTC One using Tapatalk
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?
HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.
I have used adb and fastboot for a long time, and this is the first time I've had a problem. I updated to the August security update on the first with no problem, and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Windows Device Manager shows an exclamation mark for "Fastboot Shamu S". I have looked for hidden devices and uninstalled the driver. I tried to update the driver but Windows can't find one.
The adb and fastboot drivers I have been using are from December of last year, so I installed these: http://www.teamandroid.com/2016/06/15/install-fastboot-adb-google-usb-drivers-windows/ but still can't get fastboot working.
Has anyone run into this and can suggest a solution?
Same configuration here - Windows 10 Anniversary 64 bit ,shamu, old fastboot files and drivers from Google. Everything is fine.
Try to download official drivers.
JimSmith94 said:
.... and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Has anyone run into this and can suggest a solution?
Click to expand...
Click to collapse
The W10 anniversary update doesn't accept drivers that aren't certified by Microsoft.
When there are no certified fastboot drivers you may thank Microsoft.
If it's a driver issue, uninstall then follow this http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Then reinstall after disabling the driver signature verification
bultras said:
Same configuration here - Windows 10 Anniversary 64 bit ,shamu, old fastboot files and drivers from Google. Everything is fine.
Try to download official drivers.
Click to expand...
Click to collapse
Thanks to all! Installing the driver from "latest_usb_driver_windows.zip" in your link did the trick!
Works fine for me.
Sent from my DROID Turbo 2
JimSmith94 said:
I have used adb and fastboot for a long time, and this is the first time I've had a problem. I updated to the August security update on the first with no problem, and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Windows Device Manager shows an exclamation mark for "Fastboot Shamu S". I have looked for hidden devices and uninstalled the driver. I tried to update the driver but Windows can't find one.
The adb and fastboot drivers I have been using are from December of last year, so I installed these: http://www.teamandroid.com/2016/06/15/install-fastboot-adb-google-usb-drivers-windows/ but still can't get fastboot working.
Has anyone run into this and can suggest a solution?
Click to expand...
Click to collapse
Not sure if exact to your issue but I'm using a moto g play (2021) and windows 10. Now as long as I don't boot android into recovery mode, the phone is available within file explorer as well as command line. Once I boot into recovery adb commands useless. Unseen. I've reinstalled every driver... It just won't let me fastboot
Lightnin'BoWatt said:
Not sure if exact to your issue but I'm using a moto g play (2021) and windows 10. Now as long as I don't boot android into recovery mode, the phone is available within file explorer as well as command line. Once I boot into recovery adb commands useless. Unseen. I've reinstalled every driver... It just won't let me fastboot
Click to expand...
Click to collapse
Now, this thread is for the Nexus 6 phone. If your problem is specific to the Moto G Play, it is unlikely that anyone here is able to answer.
But generally, fastboot works when the phone is in bootloader mode, not in recovery. However, not all phones have a fastboot-compatible bootloader.
If you have installed an advanced recovery like TWRP, you should be able to use adb. But probably not with the default recovery.