Related
Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hi. First of all I want to excuse me that I' m asking a common thing several times threated in other posts.
I'm working now 2 days on getting another rom on my lemax 2.
I have installed the driver for the phone on my windows 7. system manager shows a propper installation. ADB driver's have been installed. The phone is in developper mode and oem and usb debugging is turned on. I switched to MTP and to PTP to make my device visible for ADB. But when I'm trying to see if my computer shows the mobile phone in CMD with the following command "adb devices" there will never be something listed! I tried already a lot... Uninstalling drvers for ADB, tried different drivers... And so on... Does anybody have an idea to help me??
Same problem here. Phone doesn't show, ADB can't connect. I am starting to get frustrated.
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
MOB* said:
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
Click to expand...
Click to collapse
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Sörnäinen said:
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Click to expand...
Click to collapse
I have no second android phone to test. But I tried already on OS Win 7 & 10 with different drivers on Win 7 as well. On win 10 the driver was already given by Windows, no need to install. I think that the problem has something to do with the phone, but I can't find the problem. It must be something with authorisation, that Win Os will recognize the Leeco correctly to have access.
I finally found a good working driver for WIN 10. I found it from a Chinese chatting group, so use it at your own risk.
Below is the share link.
https://drive.google.com/file/d/0BxNNPNS50QQiUk50YTliT2p5Mmc/view?usp=sharing
You will need to boot your phone into bootloader, connect to computer, manually switch the diver via 'Browse my computer for driver software" -> 'Let me pick fromm a list of device drivers on my computer"-> "Have Disk".
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
valy_cta said:
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
Click to expand...
Click to collapse
Thanks a lot for sharing it !!! This helped me A LOT !! :fingers-crossed: :fingers-crossed: :fingers-crossed:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
midirt said:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
Click to expand...
Click to collapse
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Dhatchina said:
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Click to expand...
Click to collapse
if you're sure it's not a driver issue you can try the following (solved the problem for me):
on your windows machine navigate to "c:\users\<insert your user name here>\.android" and delete the file "adbkey".
either jump directly to the folder or turn on hidden/os files in explorer and navigate there.
now plug in your phone, the rsa-key dialog should pop up.
if not, that wasn't your problem.
btw. i'm using "universal adb installer".
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
It helpded me a lot. Thanx.
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
Great, man.!. It works for me
THIS Method Works For LeEco Le Max2
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This Method Works Perfectly.... After Enabling the AT port.. the drivers begin installing immediately. Have Patience. They will all install.
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
You should post a Screenshot of your devicemanager becsuse that information is not enough.
Gesendet von meinem Le X820 mit Tapatalk
Install ADB Driver installer 2.0
dhankhar13 said:
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
Click to expand...
Click to collapse
adbdriver.com/downloads/
Use this above link
1 ) Download adb driver installer software zip file
2 ) Extract the zip file
3 ) Install & Run a adb driver installer.exe file
my le2 doesn't show up in fastboot mode, but shows up once booted into system. Any idea?
Thanks!
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This worked for me too!!!:good::good::good:
Hello guys, im really in trouble. I have a general mobile e tab 5 tablet and i'm living some problems. This tablet don't have an microsd card so i can't setup anything from microsd. Don't have an os and when i connect to computer it's not being visible. I setup sdk android tools, fastboot or smth. This didn't work too. I'm updated the java things and it's still not working. I can't wiping datas, it's giving error like "failed to mount '/cache' and '/data' (invalid arguments), Unable to mount storage" and i can't doing any little thing. Im totally stucked, no way, im thinking only i can fix it from terminal but i don't know what i should to write I don't know what i should to do. Really i need help guys. Also ADB sideload not working too as i said, it's not being visible on computer. (Sorry for bad English.)
Is it detected by your computer (showes in device manager) but no storage or is it not detected at all?
You may need to install/reinstall usb drivers for ADB?
bailey239 said:
Is it detected by your computer (showes in device manager) but no storage or is it not detected at all?
You may need to install/reinstall usb drivers for ADB?
Click to expand...
Click to collapse
Nothing being detected, also i'm always keep opened the fastboot (from adb shell, sdk tools) with command "fastboot flashall"
You can check the picture. (I couldn't insert to image because i don't have 10 messages. )
i.hizliresim .com/aXk3nQ.png
I did everything, i deleted every usb drivers and setup again. At the same time i deleted from device manager every usb port and i setup again all of them. It's not detectable. In twrp MTP enabled and im opening adb sideload.
Just judging from the image you provided, it looks like your drivers are not installed properly. There are a few different drivers you can try, googles, Universal Naked Driver, Motorola, etc. I would suggest trying a different route than the one you took already. Your device is not being recognized, it must be related to the adb USB drivers.
bailey239 said:
Just judging from the image you provided, it looks like your drivers are not installed properly. There are a few different drivers you can try, googles, Universal Naked Driver, Motorola, etc. I would suggest trying a different route than the one you took already. Your device is not being recognized, it must be related to the adb USB drivers.
Click to expand...
Click to collapse
Can you help me about the links?
remove any spaces.
http ://koush.com/post/universal-adb-driver
http ://adbdriver.com/
https ://androidmtk.com/download-universal-adb-driver
http ://visualgdb.com/KB/usbdebug-manual/
I setup all of them, google usb drivers and also tablet usb drivers but nothing is working. I'm gonna cry actually.
Note: I think problem is TWRP. But another problem is computer is never seeing tablet because of TWRP. Tablet don't have a microsd card connection. No OS. Hard hard hard bricked. If i connect a USB Flash Memory to my tablet, can it work?
@AKagNA
Be specific with your device info. You still able to go in recovery, try flashing it with stock firmware, Please please please make sure you get proper firmware for your device, please read this information HERE before proceeding, it might take few minutes but this is useful,Also hit thanks button and share if you find it useful
Thanks
Salman
Salman Al-Badgail said:
@AKagNA
Be specific with your device info. You still able to go in recovery, try flashing it with stock firmware, Please please please make sure you get proper firmware for your device, please read this information HERE before proceeding, it might take few minutes but this is useful,Also hit thanks button and share if you find it useful
Thanks
Salman
Click to expand...
Click to collapse
Hello Salman, i tried to setup stock firmware with every usb driver and flash tool. I swear i tried everything and also i'm a programmer. I'm really understand the computer. But nothing is happenning. Even computer doesnt seeing the tablet.(Sorry for bad Eng..)
You could use flashfire download it from the playstore and download a new rom. Can you boot into os?
_Exeedy_ said:
You could use flashfire download it from the playstore and download a new rom. Can you boot into os?
Click to expand...
Click to collapse
There is no OS and i can't boot it.
Hello Friends!
I'm from Argentina, and recently bought an oppo find x (chinese version].
The first thing I wanted to do was install more locale 2, so that I can have most of my apps in Spanish.
Of course before I created this topic I searched if there's a solution out there, and I found this thread:
https://forum.xda-developers.com/find-X/help/install-locale-t3818383
I followed that, step by step but doesn't work.
Indeed I tried the "long" version of it here: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
But with no luck. The problem is that I never get the prompt notification on my phone allowing usb debuggin (step 11).
So I think the problem must be in the drivers, that for some reason my windows doesnt install the drivers of my phone (but I can Transfer files with no problem....that's strange).
But where can I get those drivers? They're not even in oppo page.
This problem is driven me crazy, even more cause I think I'm the only one with this issue!!!
PLEASE HELPPPP
New information: I tried with another PC (with Windows 10) and with another cellphone (vivo x21). With both devices and both PC the problem is the same: when I write the command adb devices no devices appear, despite I have the USB debugging enabled in my phone. If I write the command adb shell it says no devices/emulators attached.
I'm have no clue what to do now.
Hello everyone.
I have found a solution. I leave it here, in case someone is in this 1% like me with problems with adb:
The problem was the drivers: apparently my windows doesn't have the correct driver to support ADB android interface, and it doesn't get installed automatically with windows update.
So, what I did was download the drivers from here: http://adbdriver.com/downloads/
And ready, problem solved.
Now my google assistant doesn't work with more locale....but that's another problem...