Hi,
Having a few issues trying to root my phone. I have tried to follow the guide posted by Vomer using a windows 7 pc. I have successfully unlocked my bootloader but when I try to flash a custom recovery I keep getting the error device offline. I have spent some time looking into this issue and potential fixes including updating adb, disabling and re-enabling USB debugging, switched of lock screen, updating HTC drivers, uninstalling HTC sync, trying different USB port and cables and trying a different computer all to no avail. I can confirm that I am getting the Allow USB debugging request on my device. If anyone can suggest anything to help I would be very grateful.
Thanks in advance
Abir
Abir85 said:
Hi,
Having a few issues trying to root my phone. I have tried to follow the guide posted by Vomer using a windows 7 pc. I have successfully unlocked my bootloader but when I try to flash a custom recovery I keep getting the error device offline. I have spent some time looking into this issue and potential fixes including updating adb, disabling and re-enabling USB debugging, switched of lock screen, updating HTC drivers, uninstalling HTC sync, trying different USB port and cables and trying a different computer all to no avail. I can confirm that I am getting the Allow USB debugging request on my device. If anyone can suggest anything to help I would be very grateful.
Thanks in advance
Abir
Click to expand...
Click to collapse
If i'm not mistaken device offline is a message given when running an adb command.
If fastboot command doesn't find your phone gives a <waiting for device> message
Can you please post a screenshot of what you are trying to do?
stathis95194 said:
If i'm not mistaken device offline is a message given when running an adb command.
If fastboot command doesn't find your phone gives a <waiting for device> message
Can you please post a screenshot of what you are trying to do?
Click to expand...
Click to collapse
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir
Abir85 said:
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir
Click to expand...
Click to collapse
Did you...
- Enable USB debugging on your phone
- Turn off all security settings from Settings -> Security.
- Disable Fast boot mode from Settings -> Power/Battery Manager.
- Plug in your device to your computer.
stathis95194 said:
Did you...
- Enable USB debugging on your phone
- Turn off all security settings from Settings -> Security.
- Disable Fast boot mode from Settings -> Power/Battery Manager.
- Plug in your device to your computer.
Click to expand...
Click to collapse
yes I can confirm I have done all of the above
Abir85 said:
yes I can confirm I have done all of the above
Click to expand...
Click to collapse
Strange...you are running the command within the OS right? Not in fastboot mode.
stathis95194 said:
Strange...you are running the command within the OS right? Not in fastboot mode.
Click to expand...
Click to collapse
Yes
Abir85 said:
Yes
Click to expand...
Click to collapse
hmmmm probably an old version adb drivers....is it an x86 or x64 win7?
Edit: i don't think it matters....try this package
and toggle USB debugging first
stathis95194 said:
hmmmm probably an old version adb drivers....is it an x86 or x64 win7?
Click to expand...
Click to collapse
Im using x64 win7
Abir85 said:
Im using x64 win7
Click to expand...
Click to collapse
i edited my post above....try the adb package i attached
stathis95194 said:
i edited my post above....try the adb package i attached
Click to expand...
Click to collapse
Same error. It detects my device serial number and says offline.
Abir85 said:
Same error. It detects my device serial number and says offline.
Click to expand...
Click to collapse
"adb devices" is working? i mean does it recognize your phone?
try also "adb kill-server" and retry.
Try also to reboot phone and PC
Abir85 said:
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir
Click to expand...
Click to collapse
I'm having the same issue. I ran RUU RUU_M8_WHL_K444_SENSE60_SPCS_MR_Sprint_WWE_3.30.651.2_R_Radio_1.08.20.0916_NV_SPCS_1.52_003_release_395172_signed_2 to get back to stock from ViperOne Rom, which was running off hboot 3.18 (s-on) and older firmware. After unrooting and relocking hboot, I ran the RUU which worked fine. Once I was back to stock, I then attempted to run adb command adb devices from Win7 with adb 1.0.3.1 installed. I followed all the standard steps (USB Debug on, fastboot off, lockscreen none, and I uninstalled previous HTC drivers and reinstalled when prompted to run htc sync install. Rebooted and tried again and it still says device offline. Anyone know a fix for this?
JTOLOGY said:
I'm having the same issue. I ran RUU RUU_M8_WHL_K444_SENSE60_SPCS_MR_Sprint_WWE_3.30.651.2_R_Radio_1.08.20.0916_NV_SPCS_1.52_003_release_395172_signed_2 to get back to stock from ViperOne Rom, which was running off hboot 3.18 (s-on) and older firmware. After unrooting and relocking hboot, I ran the RUU which worked fine. Once I was back to stock, I then attempted to run adb command adb devices from Win7 with adb 1.0.3.1 installed. I followed all the standard steps (USB Debug on, fastboot off, lockscreen none, and I uninstalled previous HTC drivers and reinstalled when prompted to run htc sync install. Rebooted and tried again and it still says device offline. Anyone know a fix for this?
Click to expand...
Click to collapse
Hey mate sorry for the late reply I have been away for a while. I fixed all my issues with the updated ABD file posted on this thread
Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....
elpicard said:
Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....
Click to expand...
Click to collapse
Is the phone in the proper mode for the command? It needs to be in bootloader-fastboot mode for fastboot commands. Needs to be booted into OS for adb commands (adb never works in bootloader, common mistake).
redpoint73 said:
Is the phone in the proper mode for the command? It needs to be in bootloader-fastboot mode for fastboot commands. Needs to be booted into OS for adb commands (adb never works in bootloader, common mistake).
Click to expand...
Click to collapse
Im not in bootloader. Im into OS. This happend since Im on 6.0. I already reinstall phones drivers and ADB
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SHxxxxxxx09 offline
elpicard said:
Im not in bootloader. Im into OS. This happend since Im on 6.0. I already reinstall phones drivers and ADB
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SHxxxxxxx09 offline
Click to expand...
Click to collapse
OS for adb
Bootloader-fastboot mode for fastboot
This thread refers to both fastboot and adb commands. Which are you using? You haven't specified.
elpicard said:
Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....
Click to expand...
Click to collapse
ARHD 50 ? Change your kernel/boot.img
Read this : http://forum.xda-developers.com/showpost.php?p=64450308&postcount=27996
Related
The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.
Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...
Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...
Is there a way for Linux?
D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.
Can you help/guide me on how to install it ?
Sorry for being a dummy.
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...
Thanks
Thats Work
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.
I need help getting out of this never ending misery. I'm stuck with my unlocked Desire HD, no ROM, and no idea how to get one working. I can't even get back to stock.
I've been looking for solutions for a week now, but it seems the combination of S-ON, no USB debugging and an unlocked bootloader makes most of them undoable.
I am able to get into boot loader, and the currently installed 4eXT recovery.
See attached file for bootloader screen.
Can anyone help me get my phone to work again? Either by a custom ROM or HTC stock; whatever.
Thanks.
What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.
bananagranola said:
What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.
Click to expand...
Click to collapse
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.
SageNTitled said:
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.
Click to expand...
Click to collapse
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.
bananagranola said:
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.
Click to expand...
Click to collapse
Yes, I did read your thread. But it doesn't work since it's not getting a connection to the device.
See attached image.
So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.
bananagranola said:
So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.
Click to expand...
Click to collapse
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.
SageNTitled said:
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.
Click to expand...
Click to collapse
No, USB debugging (aka ADB) is separate from fastboot. ADB kicks in when you boot the ROM. Fastboot is from the bootloader. Fastboot doesn't access the system's individual folders. It's used to flash entire images.
Not to worry, for I have solved the problem. I was apparently missing a driver that didn't get installed since I was missing USB debugging mode when installing adb and fastboot on my PC.
Going into Device Manager and manually looking up the HTC driver solved it.
Thanks for your time.
Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Sent from my Desire HD using Tapatalk 2
humzaahmed155 said:
Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Click to expand...
Click to collapse
No, I did not have that installed.
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
Some video tutorials to help out n00bs as well as confused members:
How to get working ADB and Fastboot, as well as drivers for Windows 8.1 64 bit:
Video embed not working? Click here for a direct link!
How to lock the bootloader and go S-ON:
Video embed not working? Click here for a direct link!
How to go S-OFF and unlock the bootloader with Firewater S-OFF:
Video embed not working? Click here for a direct link!
You are free to link to any of these tutorials or to this thread.
Enjoy these tutorials and leave a reply if you have any suggestions for future guides.
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
synisterwolf said:
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
Click to expand...
Click to collapse
Been so busy in the past few months or so that I couldn't do my helpful stuff. Now I have more free time.
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Update 4: I swear, when we get this working, I'm gonna send whoever a little kickback through Pay pal for helping out with my issues.lol. I feel that maybe it could be my laptop, I'll have to try my 10 year old toshiba.
BygSii said:
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
Uninstall the phone in device manager. Disconnect the phone. Disable windows updates to prevent it from auto installing a generic windows driver. Then plug the phone back in and try to manually install the driver from the video.
Okay. I'll try that out here in a little bit. Another thing I found to be odd, is that my OS is showing up as blank. I hope it will show the correct OS that I'm on, when I get far enough to flash an RUU.
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
BygSii said:
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
Click to expand...
Click to collapse
Glad you got it working.
Windows update is nice, but it is really annoying when you want to manually install a better driver.
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
It should work. No promises though.
Sticky?
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Vids now viewable in OP.
Link added to roll up in Development
dagrx8 said:
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Click to expand...
Click to collapse
Excellent to hear. Been waiting for this to get sorted out. Will report back when I get time to sit down and run through it all.
I can confirm it works on win 8, got my surface pro adb and fastbooting like a baws in minutes. As above poster mentioned, you either have to uninstall and prevent auto device installation, or if you find it in device manager you can force update the driver , you may have to take the extra step to "Have Disk", manually select the androidusb.inf file from unpacked drivers, then select My HTC
Sent from my HTC6500LVW using Tapatalk
Files are missing from the first video, could you reupload or post another link for the driver?
nekubg said:
Files are missing from the first video, could you reupload or post another link for the driver?
Click to expand...
Click to collapse
Updated.
Thanks for the fast reply!
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Plauges said:
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Click to expand...
Click to collapse
What version of Windows?
If it is Windows 8 you need to make sure that you installed the drivers while signature enforcement was off. I have also posted an updated video with new drivers, give it a try.
I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up
Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing
USB debugging enabled?
Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues
canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices
Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked
canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep
canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.