Hi, I have a Nexus 4 and Nexus 7 (2013 edition) on Stock Android 4.4 Kit Kat and I've had a problem for a while now. The problem is that my phone and tablet reboot themselves and then works normally for 10 seconds to a minute when it boots up and it crashes and reboots itself, and it keeps doing that, over and over. It's a loop. It starts when my phone reboots on itself and on my Nexus 7 it will disconnect from my home Wifi and if you reboot the tablet, it does the same thing. This is my 5th time with this problem and I can't find out why it happens. This has happened to me since I've had Android 4.3. I have always fixed this by leaving both devices off a day or two and then It would work like normal. Then the problem would disappear for a few weeks and then the problem would repeat itself. This has happened to me on Paranoid Android on 4.3 but never on stock until now. I thought it was a problem on Paranoid Android but now I see it's a problem of my devices. I'm actually on Android 4.4 when I got this problem again. I actually left both devices off for 2 days and it still has the same problem. I don't think it's because of any apps because it actually crashed on me right after I did a factory reset to my phone on the setup screen. Can someone please help me?
Capture a logcat or kmsg
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Capture a logcat or kmsg
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the adb it says my device is offline. I have usb debugging on and allowed it the RSA key fingerprint. What should I do?
Do you have drivers installed (windows) or rules (Linux)? Has it ever worked before?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Do you have drivers installed (windows) or rules (Linux)? Has it ever worked before?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the drivers installed. I actually always used the WugFresh Nexus Root Toolkit but it always worked
Try another computer or USB cable, also try to uninstall and reinstall drivers. Also best to stay away from toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try another computer or USB cable, also try to uninstall and reinstall drivers. Also best to stay away from toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It actually just died on me. Both devices where having problems with Wifi and then my Nexus 4 reboots itself so I turned off both devices. What should I do!? I'm desperate right now! :crying:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I finally could get the logcat out of the Nexus 4 and 7 (2013)!
demkantor said:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can a bug report help? Now what happens is that when I try to connect my phone to my WIFI it will actually reboot and then it works normal.
There is lots to dig through in those logcats but the main errors are with your facebook app, these shouldnt cause a reboot
on wifi to the best of my knowledge but consider uninstalling that buggy poorly made app anyway
can you get me an output when it powers off, it sounds like you can replicate easy so do this:
cat /proc/last_kmsg
right after it auto reboots, the kernel log will be more helpful
and if you want to do another logcat
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
will make things much easier to read
Ill dig some more when i get home, but for now try to at least get this kernel log immediately after reboot
demkantor said:
There is lots to dig through in those logcats but the main errors are with your facebook app, these shouldnt cause a reboot
on wifi to the best of my knowledge but consider uninstalling that buggy poorly made app anyway
can you get me an output when it powers off, it sounds like you can replicate easy so do this:
cat /proc/last_kmsg
right after it auto reboots, the kernel log will be more helpful
and if you want to do another logcat
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
will make things much easier to read
Ill dig some more when i get home, but for now try to at least get this kernel log immediately after reboot
Click to expand...
Click to collapse
Well after that happened, I actually installed the factory image of KRT16S on both my devices and now they both of them work, except for this one time where I had to reboot my phone so it could connect with my home WIFI. The problem is that I know that this problem will happen in the future and I want to stop it. Could flashing it with JTAG solve this problem?
Without the logs I can't say that it will happen again or what the cause is, but I will say it shouldn't happen. I have a n4 and n7 as well and neither do this, nor any other android I've ever owned unless I'm running an unstable build or have malicious apps.
JTAG will be more than overkill, anything you could do with JTAG can be done through bootloader as of now. If you want I'll walk you through a complete wipe and restore of all firmware software
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Without the logs I can't say that it will happen again or what the cause is, but I will say it shouldn't happen. I have a n4 and n7 as well and neither do this, nor any other android I've ever owned unless I'm running an unstable build or have malicious apps.
JTAG will be more than overkill, anything you could do with JTAG can be done through bootloader as of now. If you want I'll walk you through a complete wipe and restore of all firmware software
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
As I said, my phone and tablet are working normal right now and I really don't want to mess with them but it would be of great help if I could contact you in the future when this problem repeats itself so I could get those logs and install everything correctly.
And when you say firmware software, you mean the factory image?
Not inherently, by firmware I mean mostly the bootloader and radio and by software the os, be it custom or otherwise
Yes if you run into issues down the road feel free to find me
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Not inherently, by firmware I mean mostly the bootloader and radio and by software the os, be it custom or otherwise
Yes if you run into issues down the road feel free to find me
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
And how would you wipe and restore of all firmware software?
wipe/format through fastboot and flash in fastboot
Related
Hey guys,
Not that it is a real problem, but I was wondering why my device manager shows 5 USB devices for my Nexus 4, 3 times ADB and 2 times bootloader. Any idea why?
Thanks in advance
It this really that strange that no one knows why it's caused ?
Sent from my Nexus 4 using xda app-developers app
Remcotjuuh said:
It this really that strange that no one knows why it's caused ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've never seen that before. Uninstall all your drivers and start over?
Maybe because I installed it using a toolkit? Anyhow, I'll try installing them again
Sent from my Nexus 4 using xda app-developers app
Well, I investigated the issue a little and found out there where even six devices: 2 bootloader and 2 ADB devices which were always visible but "couldn't be started" and one bootloader and one ADB device, from which one is active when the mode is activated. I deleted the 4 devices and everything still functions well.
Do you have a Linux box anywhere near you? If you do, type "lsusb" into terminal with the phone plugged in. Windows is retarded.
I do have a dual boot with Ubuntu 12.04, but what will that command actually do?
Sent from my Nexus 4 using xda app-developers app
So I've been having some SERIOUS issues with my battery and have requested an RMA. Last night after a ton of issues (and at one where I soft-bricked pretty badly) I managed to unroot + load stock 4.2.2. It was late at night, so I decided I would re-lock the bootloader later.
Fastforward to today, I enable usb-debugging mode, plug in the phone and Windows 7 gives me an error. It says there's an issue. I go to device manager and it shows up with the yellow logo. I figure it's a driver issue so I uninstall drivers, and re-install naked drivers .72. Restart, plug it in and the same issue.
I go to a different computer and try it, same pop (this is Windows XP) saying device not recognized.
I also noticed my device no longer charges from the computer, when I plug it in it charges for a second, then stops.
How do I lock the bootloader if I cannot connect my Nexus 4 to the computer?? I tried going to bootloader and connecting the device, but nothing happens at all there. SOMEONE HELP!
EDIT: Here's the error message in Windows under the device manager: "windows has stopped this device because it has reported problems. (code 43)". Getting panicked now.
Search for BootUnlocker in the play store. Never tried it myself but by the reviews it seems to work. Good luck.
Edit: just saw that you have to be rooted. Sorry.
Sent from my Nexus 4 using xda premium
defnow said:
Search for BootUnlocker in the play store. Never tried it myself but by the reviews it seems to work. Good luck.
Edit: just saw that you have to be rooted. Sorry.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yep saw that one too.
I'm pretty much stuck. There's literally nothing I can do except hope it somehow magically works later on...
Would Google accept the phone as under warranty if the bootloader is unlocked? The battery is SHOT, like it drains 1% every min while under use + like forever to charge. My hope is that the thing never boots when they get it so they can't actually see that it's unlocked.
Try using a different usb cord and I'm not sure if Google will accept it.
Sent from my Nexus 4 using xda premium
defnow said:
Try using a different usb cord and I'm not sure if Google will accept it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Have already tried using 2 different cords. I'm going to try out another computer tomorrow that's brand new and see if it works there. Will also try charging fully but I don't see how that would affect it.
Still leaning towards them not being able to turn it on as a pass. That's the best possible case scenario for me.
I had same issue but try to update drivers of or PC
And install an app on or n4 called sdscan it will fix this issue
Sent from my Nexus 4 using xda app-developers app
illumanati22 said:
I had same issue but try to update drivers of or PC
And install an app on or n4 called sdscan it will fix this issue
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Tried it, doesn't work. Also, the issue isn't with the SD card since it mounts just fine on the phone itself. Issue comes up only when connected to a PC.
It doesn't even charge from the PC USB port.
Hey, so my nexus died while it was connected to a PC. I was sending a movie to nexus but the transfer was frozen so I decided to pull out the cable/don't judge me/. After that I realised that its off and doesn't react at all.
If I connect it to PC it tries to install apx driver without success.
It doesn't boot/adb won't find device.
Any chance to wake it up? Guess I should use warranty.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Have you tried holding the power button for 20-30 seconds?
Sent from my Nexus 7(2012) that has zero issues.
Of course that was first thing I did also with hard reset.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
margaretiak said:
Hey, so my nexus died while it was connected to a PC. I was sending a movie to nexus but the transfer was frozen so I decided to pull out the cable/don't judge me/. After that I realised that its off and doesn't react at all.
If I connect it to PC it tries to install apx driver without success.
It doesn't boot/adb won't find device.
Any chance to wake it up? Guess I should use warranty.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, margaretiak...
Some questions....
What do you see when you plug the Nexus 7 into the charger?
Do you see the WHITE-ON-BLACK battery charging animation?
Do you see anything on the screen at all? Any hint of illumination?
Sorry for all the the questions.... just trying to better understand your situation.
Have you tried these various button combinations?
http://forum.xda-developers.com/showthread.php?t=2133986
-----------
If you're PC is trying to install APX drivers, that, unfortunately, is not a good sign, as it's suggestive of a dead bootloader. APX drivers are typically used for nvFlashing, amongst other things, bootloaders. Unfortunately, nvFlash in APX mode, for the Nexus 7, is a mystery that thus far, nobody yet has been able to crack.
If you do have a dead bootloader, there's really not much that can be done, other than an RMA under warranty.
Very unusual, though, for a file transfer to cause this kind of problem...
Rgrds,
Ged.
Yep,it's totally dead. Display is off. Well I havnt lost anything important guess/got tib in PC/ so I'll get new one nexus. Hope they can't find out that it's rooted/modified.
And few days ago I had also problem with nexus. Guess also while I was transfering files..but via USB otg. I lost connection to HDD and then nexus has turned off. When I tried to turn it on, nexus was blinking/flashing. After some time I managed to boot into recovery so I deleted caches and it worked.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
The HDD removal crash is a bug in the kernel. But it shouldn't kill your device completely like that.
Shouldn't but it did. Running slim ROM 4.2 without any kernel based modification.
Well I'm not desperate since it has the screen lifting from the begin. I just hope I'll get new one or repaired..at least I can add screen lifting to issues.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Just to know..they replaced motherboard but in service they made few scratches on my n7 so I returned it with this and also screen lifting (that i forgot to add before)
Hi,
Ive just bought a brand new Nexus 10 and its doing really wierd things.
After updating to Android 4.4.4 i kept getting kicked off and the device would go to the lock screen. Additionally the screen would do strange things when running Chrome like going totally black with a white ring in the center of the screen.
Also text doesnt seem to display properly at times; i have now downgraded back to version 4.2 which seems to have got some stability back howver text is still broken on occassion.... See attached.
Its really odd as i have a Nexus 7 mkII which ultra stable.
Could this be hw related or simply is the rom simply this buggy?
Thanks for any ideas.
Sent from my Nexus 10 using XDA Free mobile app
Ok so I updated to 4.3 and the machine seems to be stable minus the occasional logout when opening Chrome.... However text still has problems displaying; also as with Android 4.2 it seems the wifi kept disconnecting every few minutes. Since the AP being used was the spare wifi card in my Linux HTPC it migt have something to do with the Intel Centrino card at the other end. I have a spare 3com AP which I will try and if not I also have a spare Cisco wireless router which I can also hookup.....
Other then that I dont know???
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Ok so I updated to 4.3 and the machine seems to be stable minus the occasional logout when opening Chrome.... However text still has problems displaying; also as with Android 4.2 it seems the wifi kept disconnecting every few minutes. Since the AP being used was the spare wifi card in my Linux HTPC it migt have something to do with the Intel Centrino card at the other end. I have a spare 3com AP which I will try and if not I also have a spare Cisco wireless router which I can also hookup.....
Other then that I dont know???
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried a complete wipe (flashing the factory image and doing a data wipe/factory reset afterwards)? Not sure if that's what you did when you downgraded. I would think a 100% fresh start would help.
Yep I did... Sorry if wasnt clear. I even reformatted the partitions.....
I think what bothers me the most is the incomplete text...... When downgrading I got the stock rom from Google directly.
Also something funky is the screen seems to slightly flicker when running the Plex app. This could just be an app thing though as everything else is fine.
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Yep I did... Sorry if wasnt clear. I even reformatted the partitions.....
I think what bothers me the most is the incomplete text...... When downgrading I got the stock rom from Google directly.
Also something funky is the screen seems to slightly flicker when running the Plex app. This could just be an app thing though as everything else is fine.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Boy. This is a real head scratcher. I've never heard of this before. It would be one thing if the screen was static, which would usually indicate a loose ribbon connection. Since you've already successfully flashed the factory image, I don't think it would be software related. But I can't think of any hardware issue that would cause this either.
Sent from my Nexus 10 using Tapatalk
Ok good news.... Using my spare Cisco wireless router I got stability on the wifi
I'm just thinking that maybe the issue could be something to do with the graphics chip??
Of course if I dont need to i really dont want to but if it isnt a software bug and the issue is hw related perhaps I should just contact the place where I bought it and get it replaced???
Sent from my Nexus 10 using XDA Free mobile app
JohnnySSH said:
Ok good news.... Using my spare Cisco wireless router I got stability on the wifi
I'm just thinking that maybe the issue could be something to do with the graphics chip??
Of course if I dont need to i really dont want to but if it isnt a software bug and the issue is hw related perhaps I should just contact the place where I bought it and get it replaced???
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
It is really bugging me, quite a weird issue. I believe it can be surely a defective unit, after all you flashed a stock ROM wiping completely and problems still persists.
I recommend you contacting the place you bought it. Hope you can get a replacement .
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Yeah I guess replacement is only way forward at this time
Sent from my Nexus 10 using XDA Free mobile app
An about a month ago switched to 7.1.2 from 6.0.1.
Stock rooted version. The phone is one and a half years old.
Since then I'm having random freezes that only pressing the power button and reboot will help.
I can't figure out what causes these freezes.
Anybody else having this ?
Sent from my Nexus 6P using xda premium
How did you update to 7.1.2 was it stock image ?
Yes. Stock image
Sent from my Nexus 6P using xda premium
Try a factory reset see if that helps really hard to say. Are you using substratum try removing overlays. If using custom kernel resore to stock. If it was me I would completely wipe my phone including internal. Then flash a fresh factory image to rule out any software related issues. Just make sure you back up all your pics etc.
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
There apps that you can get that will show you logs of what's going on in the background. Catlog or syslog are ones that I know of. They can be hard to understand but might give you some clues to what's going on. After the phone does it thing quickly check the log and see if any errors from apps and such that stand out.