Related
I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
I would go back to stock to try and fix it if I could, but I can't transfer anything to my phone.
studjuice said:
I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
Click to expand...
Click to collapse
Same here. I am still searching for a workaround. I think it is a USB brick.
Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.
asawoszc said:
Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.
Click to expand...
Click to collapse
I installed almost every ROM and kernel there is, there's no connection via USB and the battery life is just terrible (around 6 hours until it's completely empty).
Read through some of your posts Ultraschorsch and I'm definitely in the same boat. I have airdroid to transfer files, but it's slow. I'm gonna try to go to the deodexed stock rom and kernel (but still rooted), and hope I get lucky.
I've already gone into recovery and wiped and reflashed in every combination I could think of and that hasn't helped. It's very frustrating.
I seems like it heated up so much that it destroyed the usb chip on it or something, and it wiped the info of what kind of device it's supposed to be or something. It was seriously so hot that I couldn't hold it in my hand (and that's with a case on it).
This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
I use dropbox to transfer files on my N4, I think it's faster than airdroid.
Ultraschorsch said:
This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
Click to expand...
Click to collapse
Can too! read here: http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
This is what I'm going to do and try to get an RMA tomorrow.
Also, I feel like the only solution would be to open the device. It seems like something actually broke when it overheated when this happened, so it needs to be replaced. whatever IT is.
Dude! If this works I really owe you! I'm going to try this tomorrow! Thanks in advance! :good:
If it works post back here so I (and future people with this problem) know!
So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
Hello,
Thanks for this tutorial, do i have to lock the bootloader first? I was thinking it was the last thing to do...
(I have to return the phone to google, so I need to restore everything)
studjuice said:
So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
Click to expand...
Click to collapse
Hello all,
This is my first post in here and the reason why I'm here, is that I got the exact problem as mentioned in the opening post.
I've got my N4 last thursday, so 1 week ago. It worked like a charm and since I was busy finding out all the stuff and apps, I hadn't connect it to my PC before the weekend started.
Saturday in the morning I left for a trip and I navigated to the destination, using my car charger. The phone became extremely hot but it was the first time I tried the navigation, so I tought it was 'normal'.
That day and the days after (until today) my battery drained like hell, 6 hours standby with max. 45 minutes of active usage and it is empty.
So I started looking out for a custom ROM to solve it. But I never could connect it properly to my PC. Tried different PC's and different cables. Never a proper connection, only 'usb not recognized' or no connection at all!
Luckily I couldn't connect...because now it's still in the unlocked state as when I got it.
Today I'm going to call the company where I've bought it and ask for an RMA. Only problem is...they imported it from another country since the device isn't for sale in my country (Netherlands).
I'll keep you up to date.
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...
BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists
When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta
Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.
tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
danvee said:
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
Click to expand...
Click to collapse
You are correct. I did not want to overload the list.
I too have had the random freezes and occasional reboots.
I have something to add here. I keep my nexus 7.2 (2013) in a moko case and often use it with the case folded back all the way. When the freezes occur, I noticed that if I move the case cover slightly away, the freeze stops, and when I bring it back, it freezes again. So, in my opinion, the freezing is magnet related. If so, a weaker magnet or more back padding might help with that. I've had no freezing when I use the Nexus out of the case. Have not yet tried additional shielding.
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
beware of the "the problems only represent a small vocal group blah blah" posts you'll get. I ended up returning mine to best buy for good today. I couldn't find myself dealing with and trying to replace this unit x amount of times to get a properly working one. Back to the drawing board I go.
I don't think any other device in the history of Android devices I've owned has a more 'vocal' group of problems in the General/A&A forums. It's ridiculous how bad the quality control for this tablet is.
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Anderson2 said:
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Click to expand...
Click to collapse
albundy2010 said:
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
Click to expand...
Click to collapse
Used a different cable, different pc, different port. No difference.
I would use fastboot but am a newbie and it is over my head to do that. Afraid I'll really mess things up.
gogol said:
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Click to expand...
Click to collapse
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
sfhub said:
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
Click to expand...
Click to collapse
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Anderson2 said:
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Click to expand...
Click to collapse
Hmm you could download the goomanager app and then install TWRP, by then you can do a nandroid backup without any hassle.
Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
You can install the PDAnet driver from WugFresh. It's option no. 3 if I am not mistaken.
Anderson2 said:
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
Click to expand...
Click to collapse
Update : SUCCESS!!
It was the cable stupid!
I can't believe the hours I wasted because of this stupid cable. This must be the cable I had used when I finally successfully rooted the Nexus after multiple tries (including different cables, etc). I own several USB cables and in my hours and days of trying to get this to work I went through them all at one time or another.
I now labeled this cable as the one to use for connecting between the Nexus and the PC. It is hard to believe that a cable could make that much difference! I was of course aware that the cable could be a problem but this much of a problem?! Unbelievable. What could be so different with this Asus cable? What could be missing in the other cables?
For the record this is the cable that came with the original Nexus 7 charger. Now I have it labeled to avoid going through all this again.
I'm one happy camper! You guys have no idea how frustrating it is to follow every ones advice and still have no success. You start to feel really stupid.
Thank you all for your wonderful and patient support. You guys (and gals) are great. Sorry to have wasted your time too.
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
burnoutslo said:
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
Click to expand...
Click to collapse
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
xzces said:
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
Click to expand...
Click to collapse
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
afarnedi said:
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
Click to expand...
Click to collapse
sushant6786 said:
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
Click to expand...
Click to collapse
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
I had once this issue on cm12.1 oneplus 2 . What I did to solve this problem successfully.
1. I removed case from my phone . This causes grounding issues sometimes.
2. Reflashed OxygenOS.
3. Then I flashed cm on top of it. Wiped data, cache, dalvik only. didn't wiped system partition.
4. That's it. I'm. I'm typing right now while charging. Totally perfect.
I noticed it more with my cheaper USB C cables.
I bought a half dozen and some are better than others.
the boxed cable that was stock is the best by far.
Yesterday i aux in my phone to a audio player and observed the same problem again with touchscreen. Feeling very annoyed because of this and other bugs.
My phone used to lock up completely for up to 30 seconds after plugging in the charger. After move to cyanogenmod 13 this does not happen anymore, so obviously a bug in OxygenOS.
Skickat från min ONE A2003 via Tapatalk
Hmm, this is generally not a problem with your phone or your software, but relates to the power supply. Noise in the power or grounding issues specifically cause the 'ghost touches' and erratic behaviour you describe. If you are lucky, your charger and cable are also fine and the issue is with the power socket, in which case you need an electrician to come and take a look. If its the charger/cable, then simply get a new one and you are good to go.
To figure out where the issue is, start by using the same charger + cable in a different location (completely different physical location). If the problem persists, then try changing the cable in that same location. If it still persists, try a different charger.
If the problem is NOT there at the alternate location, then chances are its your wiring and you need an electrician to sort this out for you.
So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?
topaz330 said:
So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?
Click to expand...
Click to collapse
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.
Outbreak444 said:
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.
Click to expand...
Click to collapse
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk
amorrn said:
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Nope not rooted.
topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
topaz330 said:
Nope not rooted.
Click to expand...
Click to collapse
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.
Outbreak444 said:
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.
Click to expand...
Click to collapse
yep, its the stock cable. I plugged in my wifes s6 on it and it worked perfectly.
Anyway to flash stock rom without the use of odin or usb?
Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.
Action123 said:
Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.
Click to expand...
Click to collapse
so verizon exchanged it via warranty no issues. They just checked to see if it was rooted whichi it wasn't and confirmed that the usb port was defective. All is well in the world again!
I was having this problem about 4 weeks ago. I tried everything but nothing worked. Rebooting would help for a bit then it would slow down to a crawl when I tried to wireless charge. Then I recalled I had taken an update recently and hadn't done a factory reset. I had traditionally always done one because in the past android was always buggy if you didn't. I thought android was supposed to have gotten better about taking updates without needing a FR so I had decided to do one without and had no problems for a while so forgot about it. When I realised that was the issue I saved as much as I could with Helium (normally I would use Titanium but I don't like the root method so for now have remained stock) and performed a FR. Since then I have had no issues and wireless charging works as expected.
TLDR: Backup everything and perform a factory reset.
Sent from my SM-P600 using XDA-Developers mobile app