Related
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Nobody?
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!
try installing the latest CWM recovery and see if it helps.
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one
I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline
You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.
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.
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs
So, I have found a couple other posts on this issue but none of their solutions have worked for me.
Ill start with the set up I am currently on:
-Stock Official Android N (US Unlocked)
-Firmware 2.28.617.8
-T-Mobile with CID changed to run US unlocked
-S-off and unlocked
-Using windows 10 with ABD Fast boot file (not sdk)
So I have the drivers installed. Originally I was just using the HTC sync software drivers but moved to drivers I found in a forum post here, which unfortunately did not work.
USB Debug is checked.
My phone shows as connected and I can run ADB Devices and see it in the list until I ADB reboot bootloader. Once it is booted into bootloader ADB no longer sees the phone. Checking device manager shows that the phone is connected with no exclamation mark or question mark next to it.
I have restarted and reinstalled several times with no luck. I even run a usb bootable copy of Linux Mint hoping that it may just be an MS issue but I have the same problem on Linux whether I sudo or not.
Since I have had the phone ADB has worked whether in fastboot or not. It was only until I ran the official RUU and upgraded to Android N that it has stopped working. If I am not mistaken, in MM there was a popup when you had USB Debug enabled and connected to a pc that asked if you wanted to use that pc (or something like that). I am not seeing that pop in N.
Any help would be greatly appreciated as I would really like to get twrp installed and rooted.
Thanks all.
I have spent the past couple hours fiddling around with this and thought I would add and update.
I downloaded and installed Android SDK, updating everything and adding the Google USB drivers. Unfortunately this did not work. Same result.
I did however just find that if I go to the stock recovery and select the Apply update from ADB option, the device is recognized again in my cmd window.
Am I missing something. Is there a new procedure for flashing things like twrp with command lines? All the forums still show Fastboot as the method.
Anyway, that is it for my feeble brain for the night.
Sometimes it helps to use the usbdeview tool. It removes the link to drivers and gives you a clean start. Worked earlier for me. File is attached.
@Ludolf71
I gave that a try but it doesn't seem to help. Looking through the list of drivers there doesn't seem to be any driver conflicts and the only instances that show up on the list relating to my phone are the vendor drivers and the port that the phone is on.
At this point I am lost. I have spent hours reading forums and searching around for a solution. I am not sure what might have changed between running MM and updating to the current HTC RUU. Prior to installing the current RUU everything worked fine.
Looking though dev options there is an option to revoke USB debugging authorizations, is there a way to see the list of authorized devices? Also, I swear that in MM when I had debug on I had to authorize my pc when I plugged it in the first time after a fresh flash. Is that not the case anymore or is that option somewhere hidden that I am missing?
Has anyone put together an adb zip specific to the HTC 10 and the current firmware? Do to changes in the Android N firmware could this be the cause?
I tried Andoid SDK last night but I have to admit I am not very well versed in their software so I may not done it correctly. I have been modding and flashing custom rom since the poorly name MyTouch but have so far gotten by without having to use Google software suite.
Thanks all for the help.
Tried installing the HTC Sync Manager? That shall provide you with the correct drivers.
Yeah, I have installed and reinstalled the Sync manager several times. Like I said the phone is recognized using ADB devices while booted to OS but the second I adb reboot bootloader it is no longer seen.
I keep coming back to authorizations and i think this may be the issue. I see the option to revoke but I am not getting any options to authorize the PC I am using.
Solved: I was using the wrong command line as pointed out by xunholyx in another thread. Thanks @Ludolf71 for helping as well. Felling pretty dumb about this one
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
---------- Post added at 06:40 PM ---------- Previous post was at 06:40 PM ----------
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.