This does not appear to be a hard ware issue, I've tried multiple cables including the official HTC one, cleaned the port, phone charges fine, tried multiple computers and re-installed drivers many times.
What appears to be happening is a software issue on the phone side, I would assume is from running a custom kernel, I was using Elengacia 5.3 for quite sometime. Im not even sure what kernal I was using, most likely the one that was recommended with the rom.
Everything works fine but the USB mass storage, it cant even be detected in the boot-loader, Id like to reset all to stock so I can sell my device but that does not appear to be possible at the moment, this just came out of nowhere.
If anyone has even the slightest idea of what I could do, post away.
It would be convenient if I could flash another kernal via CWM.
I can flash roms if I get them on the phone via WIFI or data.
ATT ONE X + 64 GB
nick130069 said:
this does not appear to be a hard ware issue, i've tried multiple cables including the official htc one, cleaned the port, phone charges fine, tried multiple computers and re-installed drivers many times.
What appears to be happening is a software issue on the phone side, i would assume is from running a custom kernel, i was using elengacia 5.3 for quite sometime. Im not even sure what kernal i was using, most likely the one that was recommended with the rom.
Everything works fine but the usb mass storage, it cant even be detected in the boot-loader, id like to reset all to stock so i can sell my device but that does not appear to be possible at the moment, this just came out of nowhere.
If anyone has even the slightest idea of what i could do, post away.
It would be convenient if i could flash another kernal via cwm.
I can flash roms if i get them on the phone via wifi or data.
Att one x + 64 gb
Click to expand...
Click to collapse
please help anyone!!!!
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.
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 all,
Apologies if this has been covered here before, but I've been unable to find the solution on looking.
I'm running the RN4X (SD) on the Global Beta MIUI 10. The problem I'm having is that my phone will not connect to the PC. I get USB Device not recognised in Windows, and an unable to enumerate device error in Linux, on multiple PCs with multiple different USB Cables, including the one that came with the phone.
I want to unlock the bootloader, but cannot, as it requires connection to the PC. I was hoping I could force the issue by forcing the PC to use the correct driver, but since the Xiaomi drivers require the phone to be connected to the PC to install, I'm catch-22'd out of that avenue.
I have seen mention somewhere that rolling back to either Stable or MIUI9 might fix the issue, but since I wasn't wanting to actually install a custom rom at this point, just unlock the ability to do so in the future, I'm not sure doing athe full wipe neccesary to install either will give me any benefit.
So I guess what I would like to know is one of the below:
Does anyone know how to fix the not recognised issue?
Can anyone point me at the correct drivers/how to install them without having the phone recognised by the PC?
Does anyone know if this is a known issue with MIUI10 Global Beta, and if it would be fixed by installing either 10 Stable or 9?
Thanks for any and all assistance, I've been bashing my head against this for days with no solution in sight
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Maybe your usb port is broken, but if you have root you can flash twrp using apps such as flashify. Won't be much use since usb might be broken. Try going to a service center nearby to get it fixed.
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Found any solution for this. I am facing the same issue
kiranbala003 said:
Found any solution for this. I am facing the same issue
Click to expand...
Click to collapse
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
tiennhu89 said:
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
Click to expand...
Click to collapse
Yup. Tried everything. Still not detecting
Are you using the cable that comes out of the box ?
Some third party cables don't transfer data.
(Can be the case for deteriorated cables too)
If You trying with Windows make batch file for example:
c:\usb-fix.bat
@Echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
Start cmd as Administrator and restart PC, then will work on Windows.