Hi Guys,
I used the new Nexus 4 Toolkit to unlock the bootloader.
As I unfortunately dont have 10 Posts, I cant ask in this thread, so I hope it's ok to ask here.
I installed the drivers with USB-Debugging (as before for my galaxy nexus) and unlocked the bootloader.
So far everything went normal and good!
Then I wanted to root the system. It was said that I've to enable USB-Debugging again and the system will reboot.
But then :
I tap on "Enable USB-Debugging" and I'm asked If im sure. After this, nothing happens. Usually I see a information-icon, that usb-debugging is enabled in the taskbar.
This icon is now missing. And im completly not able to connect to phone via PC and use ADB.
Im slightly desperated, as anything I could do requires ADB/USB-Debugging.
Can you guys help me?
Thanks in advance.
Does your phone show up as MTP storage OK?
I remember my One X decided to cease all USB activity except charging once, a reboot sorted it.
The USB debugging icon is a little jelly bean as per the attached screenshot.
thanks for your reply.
I dont remember If it was shown as MPT-Storage - will check this immediately after work
THe Jelly-Bean-Icon showed up before, when used the toolkit to unlock the bootloader.
I also rebooted the phone several times
Ok, now everything seems to be identified correctly, again. Very strange.
Maybe the PC needed to be restarted.
Sorry for this post. It can be closed.
Thank you!
Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.
ev!denz said:
Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.
Click to expand...
Click to collapse
I've got the same problem, except my device is not loading until 100%. It gets really hot while not doing anything and it's empty in about 3 hours.
I figured out that the Nexus is only charged via "USB" although it's plugged in the charger.
Now my device is charging up until 100% but it still gets hot, is empty in about 5 hours and if I connect it in fastboot mode my laptop says that the drivers are not installed properly even though I installed the naked drivers. Re-installing the drivers does not work either, it says that my laptop already had the right drivers installed. And when I connect my device when it's booted it is not recognized at all and does not show up in the device manager. I tried three other cables... Sounds like an USB brick, right?
Ultraschorsch said:
Sounds like an USB brick, right?
Click to expand...
Click to collapse
That's what I think, too.
ev!denz said:
That's what I think, too.
Click to expand...
Click to collapse
Having the same trouble guys. Anyone found any insight into this or possibly a fix?
loopyoyo said:
Having the same trouble guys. Anyone found any insight into this or possibly a fix?
Click to expand...
Click to collapse
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...
Ultraschorsch said:
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...
Click to expand...
Click to collapse
Tap Build Number in about phone 10 times.
zephiK said:
Tap Build Number in about phone 10 times.
Click to expand...
Click to collapse
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.
Ultraschorsch said:
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.
Click to expand...
Click to collapse
Yea...computer doesn't even recognize nexus under recovery or fastboot menus..I think it's really fooked up. Just submitted a rma request to lg so will see how this plays out.
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
I have teh same problem.
1) the battery drains like crazy, even with franco kernel lastest nightly
2) USB debugging does not work now... when plugging into the pc the phone is just not found...
3) I can reboot to recovery but that doesnt do me any good since I cant do jack from it.
anyone has any insight ? what can be going on that the phone is not showing up in windows
studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
spaceman860 said:
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
Click to expand...
Click to collapse
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes. If your on stock with a locked bootloader your warranty is still good
Sent from my Nexus 4
al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes, I called Google but they don't have any N4's in stock. so I keep rooted until I get a new device from them.
Related
So I updated some apps on my phone, handcent and flash and my phone was having a lot of FC issues. Handcent was FCing for a lot of things and I couldn't open almost any app. So I figured lets do a quick reboot....chose the reboot option and the phone turned off but never came back on.....pulled the battery and I've left it out but still no go. Even pulled the memory card and SIM card but the phone won't do anything. Won't show charging when I plug it in but my computer does make a noise when it plugs in but the device doesn't show up on the computer anywhere.
Am I toast and do I need to get a new phone or is there something that I can do?
Wow never heard of that happening.. hmm try going to the bootloader... get a new battery maybe... this beats me
mytouch 4g
S-off
gfree method
running: royal ginger 1.6
How do I get to the boot loader from hardware keys? I can't for the life of me find that.
Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.
Spectral8x said:
Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.
Click to expand...
Click to collapse
If you are certain your battery is good and your phone does not respond to anything AKA brick then I think somehow you have ended up with a corrupted bootloader if that is the case you'd need a RIFF box or call HTC. I'm in the same boat as you i won't be buying the JTAG cable for that phone only so i'll be sending mine in.
I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.
Spectral8x said:
I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.
Click to expand...
Click to collapse
is adb recognizing your device? you did mention you heard a noise on your pc. The usb drivers should be kicking then (pray its not the qualcomm modem drivers kicking in lol)
you still have hope if you can get adb up and running.
Also were you on the stock bootloader or eng bootloader?
1. What was the state of your phone before those app updates? (Rooted? Custom ROM / kernel? Engineering bootloader?)
2. Do you remember specifically which apps you updated? Anyone else who updated the same apps recently, have you noticed anything?
3. Do you have ADB set up on your computer? Have you tried using 'adb devices' to see if your device is recognized?
Happen to me once due a battery pull then reinsert the battery should be able to boot back up. When you do a battery pull wait a few minutes like 5.
Sent from my HTC Glacier using XDA Premium App
That happened to me everything got messed up except bootloader and even that was freezing so I loaded pd151img.zip and pulled battery when updating bootloader to hide s-off
Sent from my HTC Glacier using XDA Premium App
So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there.
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.
Spectral8x said:
So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.
Click to expand...
Click to collapse
Well if it wont boot it won't be recognized I don't think.. and I just corrupted the bootloader by pulling the battery so they wouldn't see I had rooted and I wouldn't have to pay the fee (bad karma and all I know) so if you don't have insurance your sol. But on some other thread a Guy had this issue and held both volume keys and power while plugging it in and his comp recognized it as qualcomm cdma device or something like that. That maybe recognizable via adb not sure though..
Sent from my HTC Glacier using XDA Premium App
Well I should be fine under warranty tho since the device won't do anything. I'm going to try to see if I can get the device to show up in adb and if not i guess i'm getting a replacement phone and starting from scratch UGH! Lol.
Hi Guys,
I have a question about the update to version 4.1.2.
When I go to Settings > About > System update, I see that the update to 4.1.2 is found but it says that it is waiting to download but it stays like that forever and nothing happens.
Has anyone else seen such behavior? Do you know why it is happening and if it is normal?
Thanks!
Maybe a stupid question but... are you connected to WiFi when you see the message?
b00mb00mchuck said:
Maybe a stupid question but... are you connected to WiFi when you see the message?
Click to expand...
Click to collapse
Yes, of course I am
I also forgot to mention that I am fully stock, unrooted and locked.
wyvorn said:
Hi Guys,
I have a question about the update to version 4.1.2.
When I go to Settings > About > System update, I see that the update to 4.1.2 is found but it says that it is waiting to download but it stays like that forever and nothing happens.
Has anyone else seen such behavior? Do you know why it is happening and if it is normal?
Thanks!
Click to expand...
Click to collapse
Make sure you have a good WiFi connection. The WiFi in my dorm shows a good connection (String signal) but the internet can sometimes timeout easily. Make sure your connection to the internet is superb.
wyvorn said:
Yes, of course I am
I also forgot to mention that I am fully stock, unrooted and locked.
Click to expand...
Click to collapse
Taking a quick look at your wifi icon its not transferring or receiving data. No black arows inside..
Sent from my Nexus 7 using Tapatalk 2
mattrmay said:
Make sure you have a good WiFi connection. The WiFi in my dorm shows a good connection (String signal) but the internet can sometimes timeout easily. Make sure your connection to the internet is superb.
Click to expand...
Click to collapse
My connection is very good. For just in case, I put the Nexus besides the wifi router and still nothing happens.
Omar04 said:
Taking a quick look at your wifi icon its not transferring or receiving data. No black arows inside..
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I know what the arrows mean but my question is why this is happening? Is there a way for me to force the download? Or maybe I just have to wait more (it's been like this since yesterday)?
Try powering off the Nexus and then starting it up again. If that doesn't work, try using the technique to trick it into updating mentioned in this thread (yes, it's for a different situation but still worth a shot)
http://forum.xda-developers.com/showthread.php?t=1930603
Sent from my MB860 using xda app-developers app
wyvorn said:
My connection is very good. For just in case, I put the Nexus besides the wifi router and still nothing happens.
Yes, I know what the arrows mean but my question is why this is happening? Is there a way for me to force the download? Or maybe I just have to wait more (it's been like this since yesterday)?
Click to expand...
Click to collapse
Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1934670
AnotherBill said:
Try powering off the Nexus and then starting it up again. If that doesn't work, try using the technique to trick it into updating mentioned in this thread (yes, it's for a different situation but still worth a shot)
http://forum.xda-developers.com/showthread.php?t=1930603
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Hey, thanks for the suggestions. I tried powering off and on and it didn't work.
Then I tried the method to force stop the Google Services Framework and when I went to the System updates screen, I had the option to check for updates. I checked and I am back to where I was before - the update shows but is only "waiting to download"
wyvorn said:
I also forgot to mention that I am fully stock, unrooted and locked.
Click to expand...
Click to collapse
Not really a solution but why are your locked?
Sent from my Nexus 7
krelvinaz said:
Not really a solution but why are your locked?
Sent from my Nexus 7
Click to expand...
Click to collapse
probably because he isnt in to rooting?? and just wants his update. not everyone on XDA unlocks and flashes im sure.
krelvinaz said:
Not really a solution but why are your locked?
Sent from my Nexus 7
Click to expand...
Click to collapse
Well, I bought the N7 recently and I want to see how it feels without rooting and custom roms. But later on, I will most probably unlock it.
Hi everyone. I have the same problem with the download. Mine N7 is also stock. Tried the method with the framework multiple times, tried to restart, tried another internet, still no luck in downloading. Any further suggestions?
svetlio89 said:
Hi everyone. I have the same problem with the download. Mine N7 is also stock. Tried the method with the framework multiple times, tried to restart, tried another internet, still no luck in downloading. Any further suggestions?
Click to expand...
Click to collapse
Same issue here! I see the update, but it's waiting to download forever. Could this be connected to the location? Same as the the other guy I'm located in Sofia, Bulgaria.
spooooky said:
Same issue here! I see the update, but it's waiting to download forever. Could this be connected to the location? Same as the the other guy I'm located in Sofia, Bulgaria.
Click to expand...
Click to collapse
Yeah, I'm starting to think the same, as I am in Sofia too.
Anyway, I could not find a solution, so I rooted and installed CM10, so no issue for me anymore.
Another one from Sofia. Waiting to download and after some time... unable to download.....
Sent from my Nexus 7 using Tapatalk 2
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
Hi,
This problem has been going months now. And it's getting worse. Before, it was just happening when I open games that use Internet connections. However, this time, even if it's just opening the lock screen the distortion problem appears. Any help, please?
Links to videos of the screen problem below:
Months before
https://www.youtube.com/watch?v=VVKhpII6MwY
Happening now
https://www.youtube.com/watch?v=XWNleEjl6-g
chubiprince said:
Hi,
This problem has been going months now. And it's getting worse. Before, it was just happening when I open games that use Internet connections. However, this time, even if it's just opening the lock screen the distortion problem appears. Any help, please?
Links to videos of the screen problem below:
Months before
https://www.youtube.com/watch?v=VVKhpII6MwY
Happening now
https://www.youtube.com/watch?v=XWNleEjl6-g
Click to expand...
Click to collapse
It could be a number of things. Have you tried flashing new firmware or a custom ROM to see if it persists? Does it jump while it is booting up? Your digitizer could be going foul whilst displaying in some spectra. I had a similar problem myself on an HTC Rezound and it turns out the presence of Nova Launcher was the problem...
Take a screenshot and put it on your computer. If it looks fine, you have bad hardware, more than likely.
kcipopnevets said:
It could be a number of things. Have you tried flashing new firmware or a custom ROM to see if it persists? Does it jump while it is booting up? Your digitizer could be going foul whilst displaying in some spectra. I had a similar problem myself on an HTC Rezound and it turns out the presence of Nova Launcher was the problem...
Take a screenshot and put it on your computer. If it looks fine, you have bad hardware, more than likely.
Click to expand...
Click to collapse
Im using stock rom. Updated my OS via OTA. Does not jump while the boot screen is loading. I'm using Nova Launcher too. I'll try to remove Nova and see what will happen.
Anyway, this are what my screen looks like after taking a screenshot. I took this after I recorded the videos.
chubiprince said:
Im using stock rom. Updated my OS via OTA. I'm using Nova Launcher too. I'll try to remove Nova and see what will happen.
Anyway, this are what my screen looks like after taking a screenshot. I took this after I recorded the videos.
Click to expand...
Click to collapse
This is really odd... Do you mind uploading a raw screenshot?
kcipopnevets said:
This is really odd... Do you mind uploading a raw screenshot?
Click to expand...
Click to collapse
I really think this has not happen to any Nexus 7 users before. Tried to look for other pictures or videos all over the web, but I couldn't find anything. Okay, I will. Wait for a sec.
EDIT: One thing I also notice is that this only happens when I'm using WIFI, Mobile Data, or when any app tries to access the web PLUS when the device is starting to heat up.
Nothing is happening right now. My device seems normal. Will upload a raw screenshot when something happens. I'll message you too. Thanks for this! Will try to remove Nova and see what will happen.
chubiprince said:
Nothing is happening right now. My device seems normal. Will upload a raw screenshot when something happens. I'll message you too. Thanks for this! Will try to remove Nova and see what will happen.
Click to expand...
Click to collapse
I have some doubt that Nova is the problem but you're welcome! Just keep me posted, I'll be glad to help.
kcipopnevets said:
I have some doubt that Nova is the problem but you're welcome! Just keep me posted, I'll be glad to help.
Click to expand...
Click to collapse
It happened again. I took a screenshot two times and all are normal. No distortions. Why is this?
chubiprince said:
It happened again. I took a screenshot two times and all are normal. No distortions. Why is this?
Click to expand...
Click to collapse
Ah, for now it seems like a hardware issue. If you don't mind, whenever you have the chance, can you try using another ROM? Graphical artifacts that don't show up in the OS are usually signs of bad hardware, though...
If that's too much of a stretch to do, can I ask a couple more questions/favors?
kcipopnevets said:
Ah, for now it seems like a hardware issue. If you don't mind, whenever you have the chance, can you try using another ROM? Graphical artifacts that don't show up in the OS are usually signs of bad hardware, though...
If that's too much of a stretch to do, can I ask a couple more questions/favors?
Click to expand...
Click to collapse
Sorry for the late reply. There was a power outage in my place, and it took hours to get the power back. Sure, I am willing to answer your questions or do any favor, as long as it will help my device.
For flashing a new ROM, well I really don't know how to flash a ROM. Plus, the instructions here are only for Windows 7. I am Windows 8 user.
chubiprince said:
Sorry for the late reply. There was a power outage in my place, and it took hours to get the power back. Sure, I am willing to answer your questions or do any favor, as long as it will help my device.
For flashing a new ROM, well I really don't know how to flash a ROM. Plus, the instructions here are only for Windows 7. I am Windows 8 user.
Click to expand...
Click to collapse
Oh man. The outage isn't your fault in the slightest so it's okay.
Earlier you specified it happens when the tablet heats up? Maybe when it acts up, try finding a way to quickly cool it off to see if the interference stops. This issue can certainly also be caused by any underlying interference. If the tablet gets hot, try holding power until the system reboots to check if the Google screen or the boot animation jump (I'm assuming they don't?) and we'll see what happens.
And in terms of bootloader unlock and all that stuff, I thought WugFresh's Nexus Root Toolkit was compatible with 8? There are definitely drivers for the N7 so if toolkit fails, I can walk you through the alternate route to unlock manually.
kcipopnevets said:
Oh man. The outage isn't your fault in the slightest so it's okay.
Earlier you specified it happens when the tablet heats up? Maybe when it acts up, try finding a way to quickly cool it off to see if the interference stops. This issue can certainly also be caused by any underlying interference. If the tablet gets hot, try holding power until the system reboots to check if the Google screen or the boot animation jump (I'm assuming they don't?) and we'll see what happens.
And in terms of bootloader unlock and all that stuff, I thought WugFresh's Nexus Root Toolkit was compatible with 8? There are definitely drivers for the N7 so if toolkit fails, I can walk you through the alternate route to unlock manually.
Click to expand...
Click to collapse
Hmmm. I'll try it by tomorrow (It's 2 AM here. Hehe). I'll try to make the device "heat up" and restart it. I haven't tried investigating if the boot animation jumps when this distortion thing happens, so, again, I'll do it tomorrow.
I tried manually updating my Gnex before thru efran's manual tutorial (on a Windows 7), so I am okay with manual unlocking the bootloader, and trying another ROM. Just tell me the steps via Windows 8, please.
chubiprince said:
Hmmm. I'll try it by tomorrow (It's 2 AM here. Hehe). I'll try to make the device "heat up" and restart it. I haven't tried investigating if the boot animation jumps when this distortion thing happens, so, again, I'll do it tomorrow.
I tried manually updating my Gnex before thru efran's manual tutorial (on a Windows 7), so I am okay with manual unlocking the bootloader, and trying another ROM. Just tell me the steps via Windows 8, please.
Click to expand...
Click to collapse
Please forgive my tardiness, I was SUPER busy this weekend, but for the most part I'm free now.
Phase them me when you're ready!
kcipopnevets said:
Please forgive my tardiness, I was SUPER busy this weekend, but for the most part I'm free now.
Phase them me when you're ready!
Click to expand...
Click to collapse
Ready!
Can I ask for the steps on how to unlock the bootloader, and then installing a new rom via Windows 8?
chubiprince said:
Ready!
Can I ask for the steps on how to unlock the bootloader, and then installing a new rom via Windows 8?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801
This procedure should be sufficient for driver setup. I used this but you'll need adb 1.0.31 to communicate with your device.
kcipopnevets said:
http://forum.xda-developers.com/showthread.php?t=1583801
This procedure should be sufficient for driver setup. I used this but you'll need adb 1.0.31 to communicate with your device.
Click to expand...
Click to collapse
Okay got it! Will provide feedback after.
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