I flashed a custom rom a couple of months back. That rom was android version 2.3.5.
Now when I try and connect my phone to my pc using the standard usb cable, it only charges but no connection.
I did some reading before I posted and found several methods to try out
1.Use kies, download drivers
2.Enable USB Debugging mode
3.Go to settings-wireless and network-usb utilities and connect it through there.
None of the methods mentioned above worked.
So my questions to you guys are
1. Does this problem have to do with the custom rom?
2. Can I degrade to the stock rom without the use of an USB cable?
2b Can I update to another custom rom (because the phone charges when it is connected to the pc, even though I cant see it on "my computer", it should still be considered as connected?) ?
3. Which is the best custom rom out right now (Speed and performance wise)
*Side note - I know people prefer different custom roms based on their taste, but I really want to think what you guys think about which one I should upgrade to!!! I also might want to overclock to 1.6 and root the phone in the coming week if I can solve my usb problem!
Have you tried using SwiFTP app on your phone and Filezilla on your pc, then you can transfer files wirelessly
killall said:
Have you tried using SwiFTP app on your phone and Filezilla on your pc, then you can transfer files wirelessly
Click to expand...
Click to collapse
Yes I have but it wasn't what I was looking for. My phone randomly gets usb connected and starts charging without the cable being connected???
I went to the retail store I bought it from and he said you should degrade your firmware and see if the problem goes away, if it doesnt we send it in for repair.
But how can I do that if my usb only charges when I connect to the pc?
There is a Mobile Odin apk. Perhaps you could install that then flash stock firmware with it. You would have to get the .tar onto your phone though.
Unfortunately, if I´m not wrong your trobule seems to be a hardward issue.
My cell phone began a couple of weeks ago with the same problem, and it became even rather serious. Some days ago it didn´t charged if I connected the charger when it was on. I should switch it off and then connect the charger, having done this, the cell rebooted by itsefl and then began charging.
But, just seeking and testing I bought a "charger block replacement" in ebay and replaced it by myself. It is not complex to do it on your own... today I am happyy.. cause I fixed it..
If your problem continue.. I hope you will remember my words!
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried a new "factory" cable ??
That is the next place to look..IMHO...g
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried Kies whilst your Note is in recovery and download mode?
If not...
If I recall correctly, the stock recovery has an OTA firmware install option.
If I am right, you can use a WiFi FTP connection, Dropbox, Google Drive, Skydrive, Box, etc to get the CWM/TWRP installable stock recovery package onto your phone, flash that, then restore to stock firmware via the OTA option.
I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.
bunnsguy said:
I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.
Click to expand...
Click to collapse
I've noticed this problem also after the update. C3 seems to be the culprit. Flash back to a stock rooted 4.1.1 rom and set radios back. Install Kies (again) and then you can keep or uinstall kies. This worked for me. The 4.1.2 update for some reason will not play nice with the drivers. Will only let me connect as camera on both windows and Ubuntu 13.04. Thats what led me to down grade and try again.
Also, it seemed that my phone got "stuck" in PTP for some reason after all that. Once i got it to work again. I was able to connect back to Ubuntu 13.04 in MTP mode using a new 4.1.2 rom. (this for those trying to figure out how to get MTP to work on Linux boxes after update. Use a computer to set phone back to MTP, and Linux will recognize it again.) If windows jogs the phone to PTP, for some reason it will not go back until you fix that on windows. Not a science, just what i've experienced in the last 2 weeks.
each time I connect phone to computer using odin in download I get no "ID:COM" number showing connectivity with the device
Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Sent from my SCH-I605 using xda premium
joeriv5692 said:
Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Click to expand...
Click to collapse
ive only tried this 10 times so far and no worky
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...
Issue (TL;DR):
Previously working fine. Mistakenly changed USB connection option to "charge only/always". Hassle to change it back to MTP but did. Now unstable connection when attempting file transfer via USB to Windows 7 PC. Known good cables.
Phone: LG-US998 (unlocked LC V30)
Android: 7.1.2 (stock)
Security patch: September 1, 2017 (stock)
Kernel: 4.4.63 (stock)
Build: N2G47H (stock)
Software: US99810b (stock)
Cables: AUKEY USB C Cable 3.0 (I have 3 of them).
PC's: Windows 7 and Linux Mint 18.something/cinammon. Direct USB 3.0 ports, no hubs.
Issue in detail:
1.) Everything was working fine. Good connections and successful file transfers between phone and multiple PCs and cables.
2.) Was connected via Aukey USB3.0 cable1 to Windows 10 PC. Just wanted to charge, didn't want to have file transfer active.
3.) Selected "charging only" option and "always" by mistake. This seems to be "the change" that messed everything up.
4.) Finally needed to transfer files over the weekend. Plugged Aukey cable2 into Linux Mint PC but did not get a chime or a pop-up window like normal. Looking at DISKS and phone is not visible.
5.) Remembered that I had made this change and went to go change it back. Found out that there are no options in the settings menus to do this. This seems like a bug.
6.) Tried to select a different option with the drop down after connecting. No options available even when tapping on the notification that normally brings up the USB connection options. This seems like a bug, too. Or maybe an oversight.
7.) Unlocked developer options to get to USB connection menu (this seems like overkill to change this setting back). Found "Select USB Configuration" under "Networking". Changed from "charging only" to "MTP".
8.) Disconnected USB. Reconnected USB. Didn't work. Phone still not found. Verified with Aukey cable2.
9.) Went back to developer options, turned on USB debugging. Repeated step 8, same result.
10.) Went back to developer options, revoked USB debugging authorizations. Repeated step 8, same result.
11.) Tried plugging into a different port on the PC(Linux Mint). This worked. Which seems strange. Just used next port over on motherboard.
12.) Thought strange but ok, works, don't care. Verified with Aukey cable2.
13.) Attempt file transfer on Windows 7 PC today. Kinda works, but isn't stable. Used Aukey cable 1.
14.) Plug phone in, pop up window that shows internal storage and SD card like normal. Think cool, still works. Delve into deeper subdirectories of SD card, find the one I need, start copying, phone disconnects. WTF.
15.) Try again, same thing. Never had this issue before.
16.) Works better if I go really slow (select SD, wait 10 sec, select DCIM, wait 10 sec, select Camera, wait 10 sec, select target folder, wait 10 sec, copy contents [about 500 pictures], paste to windows destination). However, the connection will still drop randomly in the middle of file transfer. Error message on PC is "The device is not connected".
17.) When this happens, the phone shows no connection, then automatically reconnects. Then get the pop up on the phone showing usb connection options like normal and windows pops up with the root file folder (internal and SD) like normal. It is behaving like I am disconnecting the USB cable.
18.) Repeat step 16, same results.
19.) Tried different USB ports. Same issue.
20.) Tried debugging on/off, oem on/off, revoke authorization yes/no, select charge only then back to MTP. Same results.
Seems like something broke when selecting USB charging only/always the first time. So I would recommend against that based on what I experience. Now, hopefully someone can help point me in a direction that helps solve this for me.
Options:
1.) Prefer not to go nuclear and factory reset. But I guess that would probably work.
2.) Is the bootloader unlocked for this phone? I would like to make an image for backup regardless, but this would make me feel a lot better about a factory reset.
3.) OTA available for US99810c. I could apply that but not sure if that would fix it as I haven't seen a good write up of all the changes from b to c. Also, would this prevent me from bootloader/root? I am not up to date on this phone but have done that kind of thing before (OG droid, galaxy S3).
4.) Don't want to unmount and remove SD card to file tranfer, that's just archaic.
Thanks in advance.
enginesong said:
Phone: LG-US998 (unlocked LC V30)
Android: 7.1.2 (stock)
Security patch: September 1, 2017 (stock)
Kernel: 4.4.63 (stock)
Build: N2G47H (stock)
Software: US99810b (stock)
Is the bootloader unlocked for this phone? I would like to make an image for backup regardless, but this would make me feel a lot better about a factory reset.
Click to expand...
Click to collapse
Yes, bootloader unlock, TWRP and root is available if you have the open market LG US998, such as those bought from B&H Photo. NOT the U.S. Cellular model US998. Both are "unlocked" (SIM card unlocked/carrier unlocked/network unlocked) -- but the open market LG US998 is the OFFICIAL carrier unlocked model and is eligible for bootloader unlock. The U.S.Cellular model US998 is not.
If you have the open market LG US998, look here:
[GUIDE][LGV30]Unlocking and Rooting - TWRP/Magisk Step-by-Step
https://forum.xda-developers.com/showthread.php?t=3745006
enginesong said:
OTA available for US99810c.
I could apply that but not sure if that would fix it as I haven't seen a good write up of all the changes from b to c.
Click to expand...
Click to collapse
Every write up of 10B to 10C should tell how much better it is. If they don't, they don't know what they're talking about.
I have 10C KDZ posted down in development section. It even works for the U.S. Cellular model US998, even though I downloaded it for the open market LG US998.
[US998][STOCK]LG V30 open market US998 US99810c_03_1216.KDZ
https://forum.xda-developers.com/showthread.php?t=3736910
enginesong said:
Also, would this prevent me from bootloader/root?
I am not up to date on this phone but have done that kind of thing before (OG droid, galaxy S3).
Click to expand...
Click to collapse
My open market LG US998 is bootloader unlocked and rooted and I was using the 10C when I did it.
Whereas, if you have the U.S. Cellular US998, no version of firmware will make your bootloader eligible to be unlocked.
Sent via open market LG US998 V30/V30+
Thanks for all the info on the bootloader! Yes, I have an official carrier unlocked unit (purchased from B&H photo). This could be a fun side project in the future.
Regarding the USB issue I posted about. I tried connecting the phone to a different laptop, this one with Windows 10. Phone connects and transfers files just fine, like it is intended. Same cable. That would point to the Windows 7 machine as buggy, broken, or possibly out of date drivers? Strange, because it used to work fine.
I can get by with the Windows 10 laptop but would love to hear if anyone else has seen this or can provide advice.
Also, it seems like the USB connection configuration option shouldn't disappear completely from the phone, just in case you hit "always" by mistake like I did. And you shouldn't have to unlock developer options to change it back. Is this normal? Anyone else want to be brave and try it out?
It's the USB3 cables
I could have sworn I already wrote a post on this (and I realize this is an ancient thread) but I've tested a variety of cables and the USB2 ones work fine for file transfer while the USB3 ones exhibit disconnection after some period of time and faster if you're trying to transfer data.
The USB cable that comes with the phone is a USB2 (4-pin on the A side) cable. I've seen the reconnection issue with Windows 10 so it may not always be a fix.
enginesong said:
Regarding the USB issue I posted about. I tried connecting the phone to a different laptop, this one with Windows 10. Phone connects and transfers files just fine, like it is intended. Same cable. That would point to the Windows 7 machine as buggy, broken, or possibly out of date drivers? Strange, because it used to work fine.
I can get by with the Windows 10 laptop but would love to hear if anyone else has seen this or can provide advice.
Click to expand...
Click to collapse
Ironically many people have used their old Win7 computer successfully when their Win10 PC fails.
I still have Win7 computer as my main home computer.