Hey guy,
I have been searching and trying to fix this since yesterday and i did not find the solution,
I need adb to s-off my htc one, and the problem is whenever I plug my mobile into computer in normal mode or in bootloader mode and also in fastboot mode, adb is not finding my mobile, like when I type adb devices, it came with adb attached devices only, and not showing my mobile.
and by the way, fastboot is working perfectly, its only the adb !!
I installed the drivers many times and in many ways like pdanet and manually, and also htc sync.
I installed Android SDK and updated the platform-tools to last one.
anybody has a solution for me?
thanks you,
MohammadZkert said:
Hey guy,
I have been searching and trying to fix this since yesterday and i did not find the solution,
I need adb to s-off my htc one, and the problem is whenever I plug my mobile into computer in normal mode or in bootloader mode and also in fastboot mode, adb is not finding my mobile, like when I type adb devices, it came with adb attached devices only, and not showing my mobile.
and by the way, fastboot is working perfectly, its only the adb !!
I installed the drivers many times and in many ways like pdanet and manually, and also htc sync.
I installed Android SDK and updated the platform-tools to last one.
anybody has a solution for me?
thanks you,
Click to expand...
Click to collapse
lol, do you have usb debugging turned on in developer settings? and what version is your bootloader? if its 1.54 youre SoL. No soff yet for that one. only 1.44. (but if you soff 1.44 then upgrade to 1.54 it WILL survive.)
Related
I currently have hboot 1.13
When i type "Fastboot devices" It comes up with my phone connected, just revolutionary won't pick it up.
Help please?
Thanks
Here's a good place to start.
You probably have HTC Sync installed. Uninstall it and instal only drivers from Revolutionary documentation page.
You really think I haven't googled it before making a thread?
Also I don't have htc sync installed.
Uninstall all which is connected to HTC and their drivers, reboot your PC, install drivers pack, try different USB hub. If all that doesn't work definitely try with another PC.
Unhide said:
You really think I haven't googled it before making a thread?
Also I don't have htc sync installed.
Click to expand...
Click to collapse
You'd be surprised how many people don't google before asking. My bad.
It's been a while since I used revolutionary, but I don't think you need to be in fastboot mode. Boot the phone normally and check USB debugging. This may have not turned up in a google search, but I'm pretty sure its mentioned in the..... Instructions.... On their website...
Edit: btw the first hit in the link ZaySk provided pretty much covers every issue you could have while using revolutionary.
Nonverbose said:
It's been a while since I used revolutionary, but I don't think you need to be in fastboot mode. Boot the phone normally and check USB debugging. This may have not turned up in a google search, but I'm pretty sure its mentioned in the..... Instructions.... On their website...
Edit: btw the first hit in the link ZaySk provided pretty much covers every issue you could have while using revolutionary.
Click to expand...
Click to collapse
I think that revolutionary needs a working rom and a phone booted. For fasboot are only drivers needed, but I recommend to connect phone in fastboot mode just to install drivers, not causing a PC reboot requirement. After the drivers are installed just boot up the phone, connect to PC and run revolutionary.
Unhide said:
I currently have hboot 1.13
When i type "Fastboot devices" It comes up with my phone connected, just revolutionary won't pick it up.
Help please?
Thanks
Click to expand...
Click to collapse
Make sure your device is not in fastboot mode... It should be booted up.. when on the main screen connect to system and try revolutionary.
Sent from my HTC Incredible S using xda app-developers app
Hi all
At the moment I am trying to update my HTC One's recovery so I can install Android 4.4 ROM's, although it seems that this won't happen that easy for me.
As usual I wanted to flash the recovery.img in fastboot over adb, unfortunately, my PC doesn't seem to recognize the device when it's in fastboot mode, while it did worked before.
I've been looking around on the internet and the XDA forums for a possible solution, because it seems to be a common problem.
Unfortunarely, none of the possible solutions seem to work! Installing drivers, tried USBDeview, removing drivers, trying USB3.0 port, and I even tried a Mac system, with the same results.
adb works just fine when the device is booted in Android, but in fastboot mode, it's not recognizing the device anymore, this happens on my Windows 8.1 PC, and also on my Mac.
It worked before on Windows 8, but it seems it stopped working between the time when I upgraded to 8.1, but as I said, it doesn't work on Mac either, and I also tried a few possible solutions for this issue on Windows 8.1 (which is common), but it all didn't made any sense.
Right now, I have no idea what could solve this issue.
I hope anyone could help me.
windows 8.1 does break fastboot it will work on windows 8 but not 8.1!
the newer hboots, 1.55+ or the 1.54 that was included with the 4.4 GPE update do work on windows 8.1. but of course to update hboot you have to have working fastboot access.
you may have missed something when setting up fastboot on your mac. I haven't worked with adb or fastboot on mac so I can't offer much help there.
best bet is if you can get access to someone's windows 7 machine or just spin up a VM
joshoon said:
Hi all
At the moment I am trying to update my HTC One's recovery so I can install Android 4.4 ROM's, although it seems that this won't happen that easy for me.
As usual I wanted to flash the recovery.img in fastboot over adb, unfortunately, my PC doesn't seem to recognize the device when it's in fastboot mode, while it did worked before.
I've been looking around on the internet and the XDA forums for a possible solution, because it seems to be a common problem.
Unfortunarely, none of the possible solutions seem to work! Installing drivers, tried USBDeview, removing drivers, trying USB3.0 port, and I even tried a Mac system, with the same results.
adb works just fine when the device is booted in Android, but in fastboot mode, it's not recognizing the device anymore, this happens on my Windows 8.1 PC, and also on my Mac.
It worked before on Windows 8, but it seems it stopped working between the time when I upgraded to 8.1, but as I said, it doesn't work on Mac either, and I also tried a few possible solutions for this issue on Windows 8.1 (which is common), but it all didn't made any sense.
Right now, I have no idea what could solve this issue.
I hope anyone could help me.
Click to expand...
Click to collapse
ipfreelytech said:
windows 8.1 does break fastboot it will work on windows 8 but not 8.1!
the newer hboots, 1.55+ or the 1.54 that was included with the 4.4 GPE update do work on windows 8.1. but of course to update hboot you have to have working fastboot access.
you may have missed something when setting up fastboot on your mac. I haven't worked with adb or fastboot on mac so I can't offer much help there.
best bet is if you can get access to someone's windows 7 machine or just spin up a VM
Click to expand...
Click to collapse
Thank you for your reply.
So you are telling me it should work on Windows 8 but not on 8.1?
Because on my Macbook I also have Windows 8 running in a VM, and that doesn't work either.
why not try windows 7?
SaHiLzZ said:
why not try windows 7?
Click to expand...
Click to collapse
Well, I think I will be left with the same result, since it worked fine on Windows 8 before... And it should work on Mac too, right?
Isn't there any other way to flash the new recovery without going into fastboot?
I've been able to flash the recovery via TWRP Manager from the Playstore
The fastboot issue isn't fixed yet, but I can atleast enjoy Kitkat
I've been looking for a while for a forum with someone who has my problem hoping to solve it on my own but i haven't found one so if this is a duplicate please post a link so i can do it! thank you!
As far as i know, this m7 has never had s-off because as long as i've had it i haven't been able to access fastboot. i bought it from swappa and it already had root and a custom rom. However a few months later i thought i was going to sell it so i flashed an RUU onto it and declined root. the sale fell through and i'm trying to put a custom rom on it again but i don't have a recovery anymore. it must have gotten wiped when i flashed the RUU? i declined root when i flashed it (because of the sale) and not having root OR a recovery OR access to fastboot i'm not sure what to do from here.
ADB works just fine, as far as i know. i DO have the fast boot option turned off within the os (which is the only thing that boots) i have Hboot 1.44 which should apparently be a BREEZE to get s-off and root with except neither I, or any of the apps, programs, one click root's i've tried have been able to access fastboot.
i HAVE tried multiple machines with multiple OS. (windows 8.1 and Ubuntu 14) i've tried multiple cables. i've tried usb 3.0 and usb 2.0. i've installed htc sync drivers on the windows machine. i've tried the 'naked' unsigned drivers that a few people have said made fastboot work for them but they never worked. although what confuses me most is i've never had a problem with ADB. adb reboot bootloader works for me no issue but as soon as i get into fastboot this device has never been recognized.
at this point i'm rrreeeaaalllyyy tempted to just trash it but i was hoping this phone would last me until the rest of the year so i could save up for the m9.
Thank you so much for your help!! I was as thorough as I could be with the details.. I hope it's enough.
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
shinji257 said:
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
Click to expand...
Click to collapse
i haven't had the option yet to try with windows 7 but i had hoped that Ubuntu would recognize it because all the problems i've heard from windows 8+ were with the usb drivers.. i will see if i can get my hands on a win 7 machine though.
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?
OK guys, I'm getting desperate here...
My problem is, I can't flash RUU on my M7 UL unlocked european. All adb and fastboot commands work fine, but when I boot to RUU mode and issue "fastboot flash zip RUU.zip" my laptop restarts... I had some good help from @alray, but it didn't work so any help is apreciated.
My laptop info
HP 4730s with Windows 10 professionall
Minimal fastboot and adb 1.31 with htc fasboot.exe patched
Any insight will be highly appreciated
donkeykong1 said:
OK guys, I'm getting desperate here...
My problem is, I can't flash RUU on my M7 UL unlocked european. All adb and fastboot commands work fine, but when I boot to RUU mode and issue "fastboot flash zip RUU.zip" my laptop restarts... I had some good help from @alray, but it didn't work so any help is apreciated.
My laptop info
HP 4730s with Windows 10 professionall
Minimal fastboot and adb 1.31 with htc fasboot.exe patched
Any insight will be highly appreciated
Click to expand...
Click to collapse
Were you able to try with another computer? I'm curious to know if it's only with your laptop...
Might want to try fastboot on the same laptop with a Ubuntu live usb.... I wouldn't be surprised that Win10 is causing all this, I have a lot of problems with others things that worked fine before the update,
alray said:
Were you able to try with another computer? I'm curious to know if it's only with your laptop...
Might want to try fastboot on the same laptop with a Ubuntu live usb.... I wouldn't be surprised that Win10 is causing all this, I have a lot of problems with others things that worked fine before the update,
Click to expand...
Click to collapse
I'm waiting for a friend to bring me his W7 laptop to try. I have a W7 computer, but I was never able to get fastboot running on it. It showa something like "daemon out of time" or something. I tried few fixes for that, but it didn't work
..the thread seems to be abandoned, but i stambled on to it
..and thought: for the sake of the ones that look for answers..
in Windows 10, we have been introduced to a new feature:
,by default- it refuses to load unknown or unsigned drivers,
in many cases that is why- we all - have to struggle to set up and reliably
run fastboot on win 10
Digital signature verification can be disabled:
-temporarily - through windows settings
-permanently- via terminal ( it'd be worth searching for a bit )
Edit: this way,or another, this:
https://answers.microsoft.com/en-us...n/a53ec7ca-bdd3-4f39-a3af-3bd92336d248?auth=1
may be a part of the story- as we know it...
,and one day it surely will be compromised but
till then..
I have two driives on my pc, still keep my Win 7 on one of them
..Regards
asgardr said:
..the thread seems to be abandoned, but i stambled on to it
..and thought: for the sake of the ones that look for answers..
in Windows 10, we have been introduced to a new feature:
,by default- it refuses to load unknown or unsigned drivers,
in many cases that is why- we all - have to struggle to set up and reliably
run fastboot on win 10
Digital signature verification can be disabled:
-temporarily - through windows settings
-permanently- via terminal
Click to expand...
Click to collapse
Well, I have official HTC drivers, but I'm gonna try this. Thank you very much for the tip mate!
You mind if i ask why arent you running the exe RUU?
Luis_D1 said:
You mind if i ask why arent you running the exe RUU?
Click to expand...
Click to collapse
I don't mind at all. I never even looked at exe RUUs, I'm used to zip files, and I need fastboot to work because I want to unlock my HTC 10's bootloader [emoji6]