Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.
correction, sd works, so just usb needs sorting, tried reflashing /misc but no joy
jmprince80 said:
Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.
Click to expand...
Click to collapse
No...when flashing to cm 11+ you need to update your SDK. Update the files(all the android versions). To access fastboot u have to open platform folder..then anywhere in that folder hold shift and right click..chose command here
---------- Post added at 03:20 AM ---------- Previous post was at 03:19 AM ----------
P.s.
Edit: its either platforms or platform tools folder. Sorry about that.
---------- Post added at 03:23 AM ---------- Previous post was at 03:20 AM ----------
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.
jmprince80 said:
it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.
Click to expand...
Click to collapse
No! With the android versions 4.4 and up, you need to install the SDK updated files for that android versions. Believe me,I know
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
If one cannot find the specific drivers for a device, they can use the SDK toolkit
Im happy to try installing the latest SDK.
However Im pretty sure that its not going to change anything.
Simple fact is that is a USB device is plugged in, whether or not there are drivers present, it will still show up with a LSUSB or as an unknown device in windows device manager.
I think the problem lies somewhere in one of the configuration partitions - I am able to flash different ROMS by adb pushing to /sdcard but none i have tried have yet solved the USB issue. If I flash back to stock I will lose recovery and be unable to fix problem at all.
Dude. Yes it will
in RUU are *ALL* partitions replaced back to stock? Don't fancy being stuck back on GB....
Its not a matter of "staying"on gingerbread. Its a matter of getting your device back on track. Running that ruu after locking your bootloader will sort things out. You can always unlock it again and flash a fresh custom ROM.
---------- Post added at 02:16 AM ---------- Previous post was at 02:13 AM ----------
If u are s off, then all that will be wiped pertaining to wiping is your bootloader. There u can use SDK to access your device. U don't exactly need the "USB" thing sorted. All u need is to have SDK updated with all android versions and getting access to your bootloader via platform tools in SDK. Ppl are sadly misguided by this USB situation.
Related
I am unable to get USB connection working with my phone for development purposes. I have turned on the USB debugging and connected the device with USB cable and it does detect file transfer capabilities, but I am unable to get the ADB connection working.
I am running Windows XP SP3
It says it has found a device 'Galaxy' but is unable to install drivers for it.
What I have tried:
sdk/extras/google/usb_driver directory
I tried installing PdaNetA302.exe
I tried installing Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I selected 'install from specific location' -> choose a driver -> 'Android Phone' but it had none listed and the aforementioned driver directories did not work either when I selected them as 'Have Disk' options.
I also tried uninstalling all related devices and do the whole connecting thing again, but without success.
Help please?
SOLUTION
Apparently HTC drivers got in the way. After I removed all HTC drivers from my Windows XP, restarted and connected the device, the Samsung drivers kicked in and made it work.
To remove unused drivers from Windows XP you can follow this guide.
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
PdaNet
waylo said:
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
Click to expand...
Click to collapse
I had no end of problems getting adb and fastboot working for GN due to the usb driver problems.
After much Google-ing...
I installed PdaNet on my laptop and this installed all required drivers in the process of installing, you can then un-install PdaNet and the required drivers are still on your system.
I now have adb and fastboot working for both my Nexus One and Galaxy Nexus phones on my Windows 7 x64 laptop.
Hope this helps!
Thanks to XDA member el3ctrik for this tip!
Thanks, figured it out just after you posted. The PDANet drivers were the trick, in #3 below (don't need to actually run the installation in this case).
You'd think after 1.5 years of playing/hacking/unhacking/fixing and refixing the N1 I'd know how this is supposed to work.
A couple of comments, since some tutorials are based on older installations.
1. Installing android sdk. I went through a crapload of unnecessary trouble in trying to reinstall these, thinking that the usb drivers, adb, and fastboot needed to be updated. NO.
1a. In fact, in trying to reinstall the android sdk, you have to install the Java SDK. THEN, with the latest revision, R15, FASTBOOT IS MISSING! Need to pull that from a r13 zip.
2. You need the CORRECT samsung drivers. The ones mentioned above are the correct ones. I installed some limited half-ass versions which did not do the job.
3. You need FASTBOOT drivers. These were found from this post http://forum.xda-developers.com/showpost.php?p=9919944&postcount=1
which states:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
The #2 drivers let ADB see it when ICS is running, #3 (and probably #2 too) are needed while in fastboot. To get #3 installed, I had to go to device manager in Win7, hit update driver (next to the error exclamation mark device), and direct to these files.
That is all <whew!>
Glad you got it sorted out buddy, I was in exact same boat, years of Nexus One fastboot and adb use, but still had problems!
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Windows 7N USB driver issues
First post on this forum, so please bear with me.
I struggled for a few weeks trying to connect my new Samsung Galaxy Nexus (Rogers) to a 32-bit Windows 7 Ultimate N machine. The system wouldn't accept the drivers from Samsung - failed to recognize, driver software not successfully installed, etc. Tried all variety of proposed fixes, manually selecting the driver (have disk), downloading SDKs and ADB drivers.
Finally fixed it based on a very old suggestion from several years ago from an HTC user. The USB driver wasn't recognized in the absence of Windows Media Player being installed on the machine (a quirk of Ultimate N). Found the Patch from MS for WMP for 7 Ultimate N and the system immediately recognized and installed the Samsung driver and thus the Nexus is now connected.
Download my toolkit (ROM-Less), it will assist you in that manner!
It has easy instructions, and it will do most of the work itselff!
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
AMoosa said:
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Click to expand...
Click to collapse
Check this, it has all neccesary info/drivers for your device, including fastboot drivers!
Beatsleigher root helper (My toolkit) check it out
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
SenorSmartyPants said:
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
Click to expand...
Click to collapse
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging and no check in protect usb storage
Click to expand...
Click to collapse
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Many thanks.
I think I will do a full wipe (was just doing the cache/dalvik after the first install) to make sure nothing else is screwy
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Click to expand...
Click to collapse
no prob
SenorSmartyPants said:
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Click to expand...
Click to collapse
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
SenorSmartyPants said:
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
Click to expand...
Click to collapse
i have the same issue on mine, using twa builds
also, sometimes when i plug in the usb cable it makes the kindle run extremely slow and laggish, requiring a reboot.
*Bump*
Does only detecting usb connected once per reboot only happen to the two of us in this thread? CM10 works pretty well for me, but this is a bit of an annoyance. I have a work around, reboot, but still...
I have the same issue. In fact, I can't get USB storage to work after installing CM10 8/24.
But I think the issue has to do with multiple Android USB drives being installed in Win7. I have a TF201 and Xoom and when I plug in the KF, USB reports the TF201 being connected. Of course Win7 does not show KF in Desktop Explorer. The only way I can download a new ROM to my KF is via my NAS which I connect via ES File Manager....
Can anyone confirm that having multiple Android devices causes this USB confusion?
You have to specifically enable USB storage before it will mount.
Unable to root! Stucked on TWRPP 2.2.0 Screen with several options
Hello!
I've tried to root my Kindle Fire, following the same steps that most of the users have followed (Using KFU 0.9.6).
Unfortunately, while installing the root (I guess) once it installs TWRPP, it inmediately boots up to the TWRPP screen with several options ( Install, Backup, Restore...) and the KFU software keeps a message that says Please wait.
Does anyone know how to fix this and finish the rooting of the device?
Thanks in advanced.
jjosue17
soupmagnet said:
You have to specifically enable USB storage before it will mount.
Click to expand...
Click to collapse
I have enabled but it still will not mount for some reason. I had a forced reboot issue appear as well.
try the previous build see if that doesnt solve your problem you must have usb debugging enabled and then tap on the icon in your status bar to transfer files...
I've been limping along just using the work around of rebooting while plugged in to get usb mounting to work.
But today I had KF mount to my PC, deleted the ADB drivers in windows from the device manager. Did a factory wipe on the tablet (even wiped the SD card), I'm running the latest TWA rom 8/28. I still can only get usb to detect if I reboot while connected to a pc. A couple little differences; after the wipe ADB was turned off on the ROM, I left it that way to see what happens. It does still mount (only after reboot, did I mention that ) but now it shows up under "Portable Devices" in device manager and the Device ID string is different in some apps (on PC) "Amazon Kindle Fire" instead of "Kindle Fire" which is what it was before today.
What else can I try? Do I need to do a super duper wipe? Factory, reinstall ROM, cache/dalvik? Do I need to purge even usb android driver on my system? (And how would I do that?)
Thanks for any help. I would love to get rid of this issue and just be able to plug in the KF and not worry about rebooting all the time.
Funny thing is I worked with someone the other day and when he mounted nothing would come up..... Reinstalled his adb drivers from kfu and it worked like a champ... Dont really know why... This is what I would try instead of messing with windows try creating a live usb as a formidable test to see if its simply just windows stupid drivers that are killing you... Create it with persistent and use this script to set up the drivers http://forum.xda-developers.com/showthread.php?t=1850038 very good chance it will work then you will know its a driver problem...
I'll see if I can give the Live USB thing a try if KFU driver reinstall doesn't help.
But I have a laptop that I never messed with the drivers on. With stock usb was always detected, after rooting and rom installed, had the same usb detection problems as my desktop.
Well I never did give the Live linux USB thing a try. I just keep going with my work around of rebooting with the usb connected and then doing my file transfers. I would only do this about once a week. I even noticed that with a couple of the more recent builds if I would plug KF in several times it would detect usb and I would not have to reboot.
But now with the last build (or two?) not exactly sure when it changed even that isn't working. Plugging in several times never detects usb now (95%+ detects usb charging though). And now it also won't detect usb after reboot while the cable is plugged in during the reboot. So I've had to do my file transfers in recovery mode. Recovery mode always works. What is different about what recovery mode "says" to the computer compared to what the full ROM "says"
Oh, and I only get USB 1.1 transfer speeds. But I think I read that this is a kernel driver issue that is well known, or has that been fixed somewhere?
Thanks
Kind of at my wits end here. Phone is rooted and running Slim ROM. Wanted to put it back to stock. All current recommended procedures use ODIN. I have installed the USB drivers independently and through latest version of KIES but phone is not recognized when I plug it in and no USB registration tones are heard.
If I plug into USB with device off, it registers. If I plug in with device on, it registers. If I plug in in ODIN mode - nothing!
Any idea what might be causing this? Alternatively, how to put back to stock without ODIN? Thanks in advance
kosherham51 said:
Kind of at my wits end here. Phone is rooted and running Slim ROM. Wanted to put it back to stock. All current recommended procedures use ODIN. I have installed the USB drivers independently and through latest version of KIES but phone is not recognized when I plug it in and no USB registration tones are heard.
If I plug into USB with device off, it registers. If I plug in with device on, it registers. If I plug in in ODIN mode - nothing!
Any idea what might be causing this? Alternatively, how to put back to stock without ODIN? Thanks in advance
Click to expand...
Click to collapse
You have Kies AND drivers installed? You should only install the drivers without Kies if that is the case as the driver suite and Kies will conflict.
Have you tried another pc and/or usb cable?
---------- Post added at 02:04 PM ---------- Previous post was at 01:27 PM ----------
The other choice is to use mobile odin to flash the rom from external SD if you can mount external storage and copy over the file.
Or you can flash a regular flashable zip of the rom if you can get the phone to flash to the appropriate kernel first.
Believe I only have one set of drivers installed. Was just trying alternate drivers to get it working, Yes, tried other computers/cables to no avail. Was able to flash using Mobile ODIN but still puzzled why USB/ODIN not working. Didn't think the USB port could malfunction that selectively.
tdunham said:
You have Kies AND drivers installed? You should only install the drivers without Kies if that is the case as the driver suite and Kies will conflict.
Have you tried another pc and/or usb cable?
---------- Post added at 02:04 PM ---------- Previous post was at 01:27 PM ----------
The other choice is to use mobile odin to flash the rom from external SD if you can mount external storage and copy over the file.
Or you can flash a regular flashable zip of the rom if you can get the phone to flash to the appropriate kernel first.
Click to expand...
Click to collapse
I apologize if this has been gone over already, but I searched and have not found a solution. I have a Verizon m8 and would like toy around with a custom ROM. I got weaksauce to achieve root, but cannot get s-off or TWRP because I cannot for the life of me get ADB to work, It just won't recognize my device. I have Windows 7 and I feel that it may be a driver problem. I downloaded HTC Sync manager but it won't recognize the device either. I've called HTC and they have not been much help just want me to use AirDroid. Anybody have any suggestions to what I might try? Thanks a bunch in advance, I really like the phone but would like to make a few changes if I can.
Is the USB debugging on your phone enabled ? It is needed for ADB to work.
and you need at least ADB version 1.0.31
Try to uninstall and re-install HTC Sync. Also there are some "minimal" HTC drivers around XDA which folks sometimes have better luck with. Try different USB ports, and make sure its a direct link (no USB hub, etc.). You might even have to try a different computer.
---------- Post added at 01:00 PM ---------- Previous post was at 01:00 PM ----------
ckpv5 said:
Is the USB debugging on your phone enabled ? It is needed for ADB to work.
Click to expand...
Click to collapse
This is also a good point. Seems silly and obvious. But I forgot myself, when doing root, S-off on this phone.
ckpv5 said:
Is the USB debugging on your phone enabled ? It is needed for ADB to work.
and you need at least ADB version 1.0.31
Click to expand...
Click to collapse
Oh yeah, yes USB debugging is enabled. Thanks for the reminder.
redpoint73 said:
Try to uninstall and re-install HTC Sync. Also there are some "minimal" HTC drivers around XDA which folks sometimes have better luck with. Try different USB ports, and make sure its a direct link (no USB hub, etc.). You might even have to try a different computer.
---------- Post added at 01:00 PM ---------- Previous post was at 01:00 PM ----------
This is also a good point. Seems silly and obvious. But I forgot myself, when doing root, S-off on this phone.
Click to expand...
Click to collapse
I've tried unistalling and reinstalling HTC Sync. Its plugged directly into my computer and I've tried different ports
Means that your PC device manager doesn't show Android USB devices and My HTC under it ? Any yellow unknown device there ?
Something like this
View attachment 2883823
If no, then that's driver issue
ckpv5 said:
Means that your PC device manager doesn't show Android USB devices and My HTC under it ? Any yellow unknown device there ?
Something like this
View attachment 2883823
If no, then that's driver issue
Click to expand...
Click to collapse
My device manager does not show any Android usb devices. It shows up under portable devices though
I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Here is the steps : http://forum.xda-developers.com/showpost.php?p=28963569&postcount=171
and http://forum.xda-developers.com/showpost.php?p=28965062&postcount=173
Here are the drivers
Hopefully this helps and you can manage it .. bed time for me here
ckpv5 said:
I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Click to expand...
Click to collapse
Yes, you would think such a thing would be more consistent by this point. You wouldn't expect it to be rocket science, but USB connectivity on HTC devices tends to be more problematic that you would think. For me, adb and fastboot worked perfectly out of the box, but my M8 would not mount internal storage to my Windows 7 PC. That was on my home computer. On my work laptop (also Win 7) it mounted internal storage just fine.
ckpv5 said:
I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Here is the steps : http://forum.xda-developers.com/showpost.php?p=28963569&postcount=171
and http://forum.xda-developers.com/showpost.php?p=28965062&postcount=173
Here are the drivers
Hopefully this helps and you can manage it .. bed time for me here
Click to expand...
Click to collapse
Thanks guys. Really appreciate it. Looks like I got it working, I'm able to use adb commands now. Now I'm trying to achieve s-off and can't get firewater to run. I get to the last step /data/local/tmp/firewater and nothing happens. Any ideas. Thanks again, I really appreciate the help.
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.