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
Related
I have a very strange issue going on with my fascinate right now. Before I go into too much description, here is my setup, to see the big picture. Rooted, stock vzw with geekniks stupidfast for DI01 (thought original kernel was original issue). I've tried to force the ota to DL09 and I get "IP_PREVIOUS_UPDATE_FAILED" as it fails to verify the dl signature.
Ok, on to my true issue. When I plug my SF into my pc, I get unrecognized usb device. I have the drivers installed properly and have previously been able to use odin via usb. My pc doesn't see the sd card mounted or anything. I'm debating unistalling the usb hub and restarting the pc so it will pick it back up as a new device. I have debug mode and unsigned checked, however, the little red triangle is no longer present like it used to be. I also every once in a while have issues with my battery level being accurate, as in it shows 100% when its really at 36% etc. It still charges, and recognizes being plugged in (haptic and audible confirmation).
Anyone have a clue or suggestion? I'm new to android, but well versed in the pc world. I just installed the android sdk in hopes of maybe doing a wireless adb push eventually. I'm A) trying to correct the issue and update my os/rom, or B) somehow get me back to stock and unrooted without being able to usb odin, so I can swap out for a new phone.
Thanks in advance for any help, whether it works or not.
Sent from my SCH-I500 using XDA App
Oh yeah, I'm running Win7 64bit.
Sent from my SCH-I500 using XDA App
so you are on stock vzw but you have used odin before. Did you use it to get clockworkmod on the phone?
did you return to stock from dj05 or dl09 OR have you always been on stock rom
I used odin to flash cwm. I'm on DI01 upadate-1. Had done the first update ota, then rooted and flashed cwm. I have been running that since until today. Thought kernel may have been issue, so flashed geekniks kernel for DI01 and have seen no change, except better performance as was expected. That is where I am now. Thinking about going back to previous kernel, but this seems better until I decide what I can do. Original nandroid and other in betweens to date still manifest the issues, which are only recent, like last few weeks.
Thanks again.
Sent from my SCH-I500 using XDA App
Does not see the Samsung SD Card
I have had similiar issues since DL09.
Try turning off your phone then reconnect USB after it reboots.
Seems to want to see it as a CD Rom.
norm883
I've rebooted my phone and pc, multiple times, no luck. Oh, one other thing, I tried popping the sd card into a card reader and I was able to see the files briefly, and upon trying to select anything, it totally disappears from view, as in pc doesn't see card anymore. Now I can't get the pc to see it at all. So I can't read/write it that way. My phone still sees it and can mount and unmount for removal on phone itself, but not with the pc.
Sent from my SCH-I500 using XDA App
I'm non-voodoo as well.
Sent from my SCH-I500 using XDA App
Try flashing a different kernel. My first fascinate was picky with which kernels wanted to work right with the.usb connection.
Sent from my SCH-I500 using XDA App
In my experience, you can still use ADB to push and pull things from your device even when your pc doesn't recognize your device. I know this doesn't help with flashing DL09, but it could help you push a different kernel to your device (or you could download one from xda forums via the xda app). A different kernel might clear up the issue for you. Good luck!
This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709
For your first issue it is because you are rooted you will not get ota updates. You should use odin and flash DJ05 imo it is much better and there are more ROMs and kernels
Sent from my SCH-I500 using XDA App
Thanks for all the help, I'm going to give it a whirl later and see if it works. I'll let you know.
Sent from my SCH-I500 using XDA App
Before I get too far deep in, could I just unroot via a terminalapp and then force the OTA to get me up to speed? Would at least like to see if I can deal with the minor malfunction while still being current.
nunyazz said:
This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709
Click to expand...
Click to collapse
This won't fix the problem because he is not on DL09. It will likely make his problem worse. You might want to read the entire post b4 you give suggestion.
To answer your question sir: if you can't get your pc to read your sd card with a card reader, the problem most likely has nothing to do with your phone. It probably is a corrupted|damaged card. It could also be a problem with your computer (this can be ruled out by successfully connecting another usb device to your computer).
Most likely, you will have to buy another micro usb card.
Sent from my Vanilla Froyo Fascinate
Ok, been trying a few things, and I'm starting to lean towards the sd card being corrupt (as one of the issues), sending my important pics and backups of my contacts, sms, etc to dropbox as we speak. I actually tried the SV kernel from adryn, and my phone has seen no ill effects (possibly no haptic, but didn't care at this point), everything seems to be working just like nothing changed. I actually briefly got the USB debug icon up for a second and it said usb connected, however I was not connected to anything, lol. It had done this on the stock kernel as well. I've booted my phone without the sd card in and it starts up normally, but the USB debug icon is still not present, even though the option is ticked on.
I can still force my phone into download mode, however my computer still doesn't recognize the COM port, so odin is out of the question right now. If I were to get my hands on the stock kernel again, could I factory reset the phone, remove root, and potentially force the OTA and then reroot? I've seen some options for terminal apps where I could ru superuser and busybox. Any thoughts on that route? I may give my roomie's pc a try, when he's out, as well to widen my test field.
Well, I got my pc reading the card via a card reader, but not while inserted in my phone. I'm going to try to uninstall the usb hub on my computer and restart my pc with no usb periphs connected. I read somewhere that someone was able to get the phone recognized again, but I have a feeling that it isn't going to work, since I never see the USB debug icon anymore.
On a side note, I get a com.android.settings force close message somewhat frequently, on stock, geeknik and adryn's kernel. I've started unloading apps left and right, but no avail. Thinking I need to get back to full stock somehow without odin. Suggestions?
I had similar issues. No usb, battery flashing to 100%. Tried everything as you have. Couldn't figure out how to get back to stock without odin. I'm running DJ05 superdark with geeknik 1.54 kernel.
This went on for a week and I was ready to give up and go buy another phone when one day the usb icon flashed momentarily when I plugged it in to charge.
In the end, it turned out to be a dirty usb connector on the phone. Cleaned it with a paper swab dampened with alcohol. I still have no idea why it was so sensitive to the small amount of dirt that came off it.
Hope this helps.
Well, I tried the alcohol swabbing, and it mildly worked. I get the usb debugging icon more often, but it also shows that the usb is connected, even though it isn't. My pc briefly recognized it once. Would I be able to disassemble it and clean or replace the usb port myself?
I've even blasted it with compressed air.
Sent from my SCH-I500 using Tapatalk
You've gone farther than I had to. I didn't need to resort to compressed air.
Do you have more than one usb cable available? I had bought an aftermarket one in addition to the one that came with the phone.
The original cable is still wonky on connection. It charges ok (no more battery jumping to 100%), but usb recognition is a fifty-fifty proposition. The aftermarket cable does charging and usb correctly.
I have had to reset my PC's usb drivers once by rebooting the phone while connected (the PC recognized it as a CD-ROM drive). This may be coincidental or an indication of a chronic connection problem.
I speculate in my case that the aftermarket cable distorted the phone connector somehow so that it doesn't like the original cable any more. Pure speculation.
Anyhow, glad to see that you're making progress. I know how frustrating it was for me. Keep us posted.
I had the same problem at one point. I found out that if your turn the phone off, plug in the usb cord from the computer, then turn the phone on while the phone is still plugged in. once the phone reboots, unplug the phone, then replug the phone in to the computer and then the computer should recognize it. This works for me every time that i have this problem
My nexus 4 has been working great for 3 or 4 weeks now. I have it unlocked and rooted and have flashed several roms over this time period without any problems. Yesterday I noticed a significant battery drain issue. On top of that that the only thing the phone will do now when I connect it to my computer is charge. I have tried changing my usb settings in android, and have enabled usb debugging as usual, and tried several different cables but nothing I have done has made the phone recognizable to my computer. After doing some research it seems a few other people are having the same issue
http://forum.xda-developers.com/showthread.php?t=2005437
I remember that in the past the htc desire had a usb brick issue that displayed the same symptoms so I have a strong feeling this may be the case here.
http://forum.xda-developers.com/showthread.php?t=1137763
With people starting to have this problem I was wondering if anyone has any information on possible fixes or the best course of action to fix this problem.
loopyoyo said:
My nexus 4 has been working great for 3 or 4 weeks now. I have it unlocked and rooted and have flashed several roms over this time period without any problems. Yesterday I noticed a significant battery drain issue. On top of that that the only thing the phone will do now when I connect it to my computer is charge. I have tried changing my usb settings in android, and have enabled usb debugging as usual, and tried several different cables but nothing I have done has made the phone recognizable to my computer. After doing some research it seems a few other people are having the same issue
http://forum.xda-developers.com/showthread.php?t=2005437
I remember that in the past the htc desire had a usb brick issue that displayed the same symptoms so I have a strong feeling this may be the case here.
http://forum.xda-developers.com/showthread.php?t=1137763
With people starting to have this problem I was wondering if anyone has any information on possible fixes or the best course of action to fix this problem.
Click to expand...
Click to collapse
I have the same issue.
1) last few weeks Ive noticed that the battery gets discharged in 6 hours! I will go from 100% to 40% in 3 hours. Doing nothing.
2) I have the franco kernel, but this doesnt fix it.
3) I cannot connect the n4 to my computer. It only shows as charging., tried disabling and reenabling usb debugging, rebooting, flashing recovery back to stock... nothing works.
4) WTF to do ?
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
return to stock as stated above but if the usb is bricked then how do you restore without fastboot?, nandroid restore stock with chainfire kernel then try connect
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 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.
(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Wingman626 said:
(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Click to expand...
Click to collapse
Just msm it and run the latest Oxygen OS. There is a MSM tool thread that will assist you and, also a Oxygen OS thread too. This will solve what you mentioned are your issues
Wingman626 said:
(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Click to expand...
Click to collapse
scorpio76r said:
Just msm it and run the latest Oxygen OS. There is a MSM tool thread that will assist you and, also a Oxygen OS thread too. This will solve what you mentioned are your issues
Click to expand...
Click to collapse
I totally agree flash the stock Rom
OOS is amazing. Rooting is easy if you decide you need it.
Sent from my ONEPLUS A6010 using Tapatalk
Does your friend have the the same phone? It is very common that custom ROM works flawlessly on one model but full of issues on the other, even they are from same manufacturer. The stability of a custom ROM depends on how many active user use the rom. Most of one plus users used oxygen. So not so many people could give you answer.
BTW, I would never advise someone to use custom ROM if they don't know how to flash by themselves.