Okay, I'm not sure exactly what happened, but long story short:
I flashed a rom and instead of getting a new rom on my phone, the phone rebooted into fastboot. I tried to enter recovery... no dice. Somhow my recovery uninstalled itself. So now I'm stuck with a phone with no rom installed, and no recovery installed. Frustration.
First step would be to reinstall recovery right? But when attempting to use fastboot flash command, i get stuck at <waiting for device>. I have the htc phone driver installed, and it's recognizing the phone is plugged into the pc in device manager. The phone screen even says FASTBOOT USB. I have no idea why it's not flashing. The recovery i'm trying to flash is twrp, the latest sprint build. It's the same one I had before it somehow uninstalled itself.
Please help out guys?
Thanks.
What phone?
Sent from my SM-P600 using Tapatalk
Details
Sorry for not making this clear earlier: the phone is the HTC One, Sprint. Just the regular one.
I'm really in a bind in here. Right now I have no recovery or rom to work with, and the only rom on my phone is the one that caused all this mess. I'm going to have to sideload a rom, but right now I need to get twrp on there. For some reason, it still won't get on, i'm still stuck at <waiting for device>. The phone is coming up on device manager as "My htc", so it's definitely plugged into the computer correctly. I have no idea what's going on.
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
tdhite said:
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
Click to expand...
Click to collapse
The command doesn't return anything. I guess this means my drivers aren't working. This doesn't make any sense though (pun intended): the phone is being recognized in device manager under "Android USB Devices" as "My HTC" via HTC's drivers that come with htc sync. I already downloaded htc sync and uninstalled it, keeping the driver files. This is really wierd stuff, any idea on how to get the drivers working? I'm sure if I could just get a recovery on there, resolving the issue wouldn't be too difficult via adb. Thanks.
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
BD619 said:
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
Click to expand...
Click to collapse
I am running 8.1, but my hboot is 1.55.
There it's a specific question in this in the faq page, particularly 8.1 and usb. Did you look at that?
See this: http://forum.xda-developers.com/showthread.php?p=49038239
EXDetonator said:
I am running 8.1, but my hboot is 1.55.
Click to expand...
Click to collapse
Did you install HTC sync? You need it for the proper drivers
Fixed! ...halfway
Alright guys, I flashed a recovery.
I actually started off with HTC's drivers, but they were causing the issue.
Thankfully the information the thread tdhite posted had a link to a working driver.
Thanks everyone! Now I need to sideload a rom.
Related
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!
Which version of Win are you running?
And, if you open the device manager how is recognized the phone?
Fastboot usb is normal, try using win 7 instead of win 8, I had the same problem
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery
Arcellano said:
Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!
Click to expand...
Click to collapse
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
The only for sure way to get fastboot working on windows 8.1 is to update your hboot to 1.55.000 and up or the hboot 1.54.000 from the GPE from the Android 4.4 update. Once your on these hboot fastboot and adb work fine in windows 8.1 x86 or x64.
the dark bootloader files here are all updated to the newer version hboot
http://www.htc1guru.com/downloads/firmware-downloads/
You need S-off for these to work
Click to expand...
Click to collapse
Guich said:
Which version of Win are you running?
And, if you open the device manager how is recognized the phone?
Click to expand...
Click to collapse
Hi, my PC runs Windows 8.1 32bit. If my phone is normally on, my PC recognizes it as "Android Devices", My HTC or something similar. If my phone is in the bootloader my device manager recognised it as unknown USB device, with error 43.
clsA said:
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
Click to expand...
Click to collapse
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.
Arcellano said:
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.
Click to expand...
Click to collapse
you can RUU to version 3.xx.xxx.x to get the new hboot
find your phones RUU here>> http://forum.xda-developers.com/showthread.php?t=2428276
ADB Works but Fastboot does not...
So tonight I decided to venture into the idea of pushing the GPE on to my HTC One. I unlocked the bootloader and got S-Off (The 2 prerequisites for the conversion). I loaded TWRP for the recovery mod and rooted it by installing SuperUser. Then came time to push the GPE RUU over to the phone using these instructions: http://forum.xda-developers.com/showthread.php?t=2358781
Before I pushed the ROM my bootloader screen looked like this: https://www.dropbox.com/s/r7jodkxh8gq7epy/2014-04-22 21.07.51.jpg
When I was pushing it, everything stalled, and it disconnected from the computer. I now no longer have any access to the Fastboot, my computer is saying that the usb device is not recognized by my computer and my bootloader screen now looks like this: https://www.dropbox.com/s/0zap1jiykeqrd9a/2014-04-23 00.00.06.jpg
If I boot into Android, it boots up in the stock AT&T version and I still have ADB control over USB. I run the prompt [ADB reboot bootloader] and it does what it is supposed to, boots it up to the bootloader, but again it is the broken version that I have no access to fastboot with.
I can still load up TWRP and run anything in there that I need. I have tried clearing all caches and doing factory resets with no success. I am at a loss and everything I am finding online is telling me that it is a driver issue or windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Any help here would be amazing. The phone still works as a phone which is a plus, but I would really like to be able to either successfully load the Google Play Edition on it or get everything back to stock for warranty reasons. Thanks so much for your help in advance!! I look forward to trying some new solutions soon!
zpeverman said:
windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Click to expand...
Click to collapse
It's because you're original hboot was 1.55 which works with Win 8.1, but after the first flash hboot got downgraded and therefore "broke" for Win8.1.
Use a Windows 7 PC to complete the conversion, or if you don't have access to one, you can make an Ubuntu Live USB (you can check in my guide under the FAQs how to do that).
and do not ever go S-On again!!!!
@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app
zpeverman said:
@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes their are newer black GPE firmware that work look for the firmware at htc1guru in my sig.
I was also able to get fastboot working on windows 8.1 with this fix
http://forum.xda-developers.com/showthread.php?p=49131915
use the old dirty method described
Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help
abedi75 said:
Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help
Click to expand...
Click to collapse
Probably a bad usb cabpe or usb port. fastboot ac = phone only get power, no data connection.
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~
ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop
Hi guys,
I'm having a really strange issue. I wanted to update my M7 to firmware 7.15.401.1
So before rebooting into RUU mode, I always check my getvar all to ensure that everything is working. However, today, when I got into RUU mode, fastboot wasn't working. It was working in bootloader mode, but not in RUU. I got the 'Windows didn't recognize the connected device' or something like that. And, when I typed 'fastboot reboot' it was 'waiting for devices'.
My PC is on Windows 8.1 with the latest Sync Manager, my M7 is S-OFF, unlocked bootloader and TWRP 2.8.4.0. There's no issue with the working of the phone; its rocking MaximusHD perfectly. But this issue prevents me from updating my firmware or going back to stock if I need to.
Any help is greatly appreciated.
raghav kapur said:
Hi guys,
I'm having a really strange issue. I wanted to update my M7 to firmware 7.15.401.1
So before rebooting into RUU mode, I always check my getvar all to ensure that everything is working. However, today, when I got into RUU mode, fastboot wasn't working. It was working in bootloader mode, but not in RUU. I got the 'Windows didn't recognize the connected device' or something like that. And, when I typed 'fastboot reboot' it was 'waiting for devices'.
My PC is on Windows 8.1 with the latest Sync Manager, my M7 is S-OFF, unlocked bootloader and TWRP 2.8.4.0. There's no issue with the working of the phone; its rocking MaximusHD perfectly. But this issue prevents me from updating my firmware or going back to stock if I need to.
Any help is greatly appreciated.
Click to expand...
Click to collapse
The issue is the driver, I had the same problem recently, when you plug your phone into the computer and put your phone into ruu mode or recovery, have a look in Windows device manager, it will probably say "one" with a yellow exclamation mark next to it, you need to force the driver, so right click on it, select update driver, the when given 2 options, choose Browse my computer for driver, next select android devices from the list it gives you, and then choose your latest myhtc driver, should be at the top of the list of available drivers, it will give you a warning about the driver might be wrong are you sure you want to install it, just say yes, done, problem solved.
Seanie280672 said:
The issue is the driver, I had the same problem recently, when you plug your phone into the computer and put your phone into ruu mode or recovery, have a look in Windows device manager, it will probably say "one" with a yellow exclamation mark next to it, you need to force the driver, so right click on it, select update driver, the when given 2 options, choose let me pick the driver myself, next select android devices from the list it gives you, and then choose your latest myhtc driver, should be at the top of the list of available drivers, it will give you a warning about the driver might be wrong are you sure you want to install it, just say yes, done, problem solved.
Click to expand...
Click to collapse
Alright. Ill try it later. Thanks a lot mate
Help me please! I have an htc one m7 AT&T. My device is still s-on, I can access recovery (twrp), but my phone cannot be identified in adb sideload. I am on hboot 1.55.0000. My computer is also bricked so I can't do much unless I drive to my parents. When I went there to use their PC, I installed all the latest htc drivers (even tried some older ones), android sdk and Java SE. I was on a windows 7 64 bit PC. Trust me I've done a sideload before and everything was set up properly. The phone is recognized in fast boot, but not in recovery. The phone has no os on it and recovery says it is no longer rooted. What can I do from here? I am thinking perhaps mounting from usb otg. Will this work? Is there a fast boot command that could be of assistance? I am completely stuck and could really use some help. I don't care what I have to do just explain it to me and I'll love you forever. There is nothing on my internal memory anymore it was wiped somehow. If you need any other info I'll happily provide it for you. Anything involving using a PC or Mac (I have access to both platforms at my parents) will have to wait until I can get out there again. I can't afford a new phone right now and this iPhone im using sucks lol. Thanks In advance for any help.
Anyone... anyone? Please help me.
Justkevin09 said:
Anyone... anyone? Please help me.
Click to expand...
Click to collapse
Are you still needing help with this? Your problem appears to be driver related or possibly a problem with you recovery version.
Which recovery are you using (name and version please) to check if it's a driver problem boot to recovery and connect to a Windows pc. Open the device manager and check what the device is listed as. It should be "MY HTC".
Now I'm running windows 10, I have TWRP v. 2.7.1.1. Like I said previously the computer is not detecting the device at all. I literally have no idea what to do. My new PC doesn't recognize it in fastboot either :/
what is status ur bootloader?
if locked or relocked then
1. install latest htc syn manager
2. run RUU.exe