I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Factory reset will most likely resolve your problem.
therock3181 said:
Factory reset will most likely resolve your problem.
Click to expand...
Click to collapse
Thanks.
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Click to expand...
Click to collapse
No reboots at all, but I would try wiping the cache partition from recovery first before resetting. If you have TWRP installed wipe the dalvik cache too. This will often clear up minor glitches and problems. The first boot will take longer than normal while it rebuilds. If that doesn't work, a factory reset may be in order, but I would strongly recommend unlocking your bootloader at the same time. If you haven't done so already, it will factory reset the device upon unlocking. You can get more information and a how-to in the tutorial..
If you're rooted, you could look in /proc/last_kmsg to get some context on the fault.
v12xke said:
No reboots at all, but I would try wiping the cache partition from recovery first before resetting. If you have TWRP installed wipe the dalvik cache too. This will often clear up minor glitches and problems. The first boot will take longer than normal while it rebuilds. If that doesn't work, a factory reset may be in order, but I would strongly recommend unlocking your bootloader at the same time. If you haven't done so already, it will factory reset the device upon unlocking. You can get more information and a how-to in the tutorial..
Click to expand...
Click to collapse
Thanks, I'm unlocked, just not rooted. I'll try wiping cache.
Sent from my Nexus 6P using Tapatalk
rchtk said:
If you're rooted, you could look in /proc/last_kmsg to get some context on the fault.
Click to expand...
Click to collapse
Not rooted but thanks for the help.
Sent from my Nexus 6P using Tapatalk
That's where root helps. To have a chance to know what's going on. The log is there, you just don't have the permission to open it.
rchtk said:
That's where root helps. To have a chance to know what's going on. The log is there, you just don't have the permission to open it.
Click to expand...
Click to collapse
I've had developer edition phones for the past 10 years... bootloader unlocked, rooted, custom Roman etc. I decide to go pure Android, no root and see if the Android experience is the same. I do like taking updates over the air w/o the hassle of having to go back to stock though. Thanks for the help.
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've had developer edition phones for the past 10 years... bootloader unlocked, rooted, custom Roman etc. I decide to go pure Android, no root and see if the Android experience is the same. I do like taking updates over the air w/o the hassle of having to go back to stock though. Thanks for the help.
Click to expand...
Click to collapse
Yeah same here. Been doing the same for too long. Now on Nexus I'm happy with stock. There's just root that I keep exactly for this reason. But yeah I do have to take the laptop to do updates (FlashFire has failed a few times).
Understood. Hope you solve your issue with factory reset or maybe flashing a previous radio.
BTW today I reverted from 7.1.2b to 7.1.1 and began having radio problems (which I didn't have before on 7.1.1) and strangely factory reset did solve the problem.
rchtk said:
Yeah same here. Been doing the same for too long. Now on Nexus I'm happy with stock. There's just root that I keep exactly for this reason. But yeah I do have to take the laptop to do updates (FlashFire has failed a few times).
Understood. Hope you solve your issue with factory reset or maybe flashing a previous radio.
BTW today I reverted from 7.1.2b to 7.1.1 and began having radio problems (which I didn't have before on 7.1.1) and strangely factory reset did solve the problem.
Click to expand...
Click to collapse
I guess I'll do a factory reset ?
Sent from my Nexus 6P using Tapatalk
Related
As I mentioned, When I OTA 4.2.1 from 4.2, N10 got failled with android robot with word no command.
syjyj said:
As I mentioned, When I OTA 4.2.1 from 4.2, N10 got failled with android robot with word no command.
Click to expand...
Click to collapse
Welcome to the club my friend, a lot of us are in the same situation. If you visit the general forum there are a couple of ways you can get updated by rooting and using custom recovery, but no official solution just yet.
failing for me too. restore stock image from google and tried ota 4.2.1 but same failure. tried sideload and also failed. flashed factory image again and still fails for me.
HeavenDivine said:
failing for me too. restore stock image from google and tried ota 4.2.1 but same failure. tried sideload and also failed. flashed factory image again and still fails for me.
Click to expand...
Click to collapse
Did you flash the factory images before the update? Ever? The only thing I can think of is that the factory images have some sort of bug or incompatability.
Has anyone not ever done anything to their tablet and the update still failed?
alias_neo said:
Did you flash the factory images before the update? Ever? The only thing I can think of is that the factory images have some sort of bug or incompatability.
Has anyone not ever done anything to their tablet and the update still failed?
Click to expand...
Click to collapse
Yes, I had flashed the factory images before since mine was not able to reboot after unlocking.
And I want to know how long does it take from RMA(ie. I just fill the form today)?
syjyj said:
Yes, I had flashed the factory images before since mine was not able to reboot after unlocking.
And I want to know how long does it take from RMA(ie. I just fill the form today)?
Click to expand...
Click to collapse
Yeh, I think the issue is that the factory images don't upgrade gracefully.
As for RMA, im not going to send mine back over it, Im sure itll get fixed soon enough.
Sent from my GT-I9300 using Tapatalk 2
alias_neo said:
Yeh, I think the issue is that the factory images don't upgrade gracefully.
As for RMA, im not going to send mine back over it, Im sure itll get fixed soon enough.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Do you think they will replace for me if OTA fail?
Are you stuck on "no command"? If so, at that prompt, just hit the power button and volume up button simultaneously. It should open the recovery console where you can hit reboot system.
The update sets a boot flag to boot into recovery and then fails. Since it never finishes, that flag is never cleared. Mine cleared by simply doing the above.
syjyj said:
Do you think they will replace for me if OTA fail?
Click to expand...
Click to collapse
I don't know, if you can argue that your tablet is broken because of it, they probably will.
Sent from my Nexus 10 using Tapatalk 2
Confirmation of the issue and a fix
JBQ has confirmed the issue, and the issue has been fixed: groups dot google dot com /d/msg/android-building/s-qNo2fxeHY/hmtXkyexOMgJ
In short, you need to re-download the rebuilt JOP40C factory image and flash the new 4.2 system.img. You will then be able to apply the OTA properly.
chiccitstix said:
Are you stuck on "no command"? If so, at that prompt, just hit the power button and volume up button simultaneously. It should open the recovery console where you can hit reboot system.
The update sets a boot flag to boot into recovery and then fails. Since it never finishes, that flag is never cleared. Mine cleared by simply doing the above.
Click to expand...
Click to collapse
That doesn't seem to work - although I already flashed it with the updated factory image.
How do I clear the reboot mode flag using fastboot?
So I've been looking and I haven't found an answer to this problem
I have a 16 gig nexus 7 and I like to tinker with it. I rooted it quite quickly just after getting it, and I have loaded custom roms, ect. The problem arose when I saw Ubuntu for the Nexus 7! I just HAD to try it out! So I did, and it wasn't so great :/ I went back to Android and a couple days later I realized that somehow my Nexus 7 thinks it's 6 gigs instead of 16. I was wondering if it was something that went wrong with the partitions when I installed Ubuntu on it, and if there was any way I could possibly fix it.
Thanks for all the help
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I believe I have. A little unsure though. I downloaded the stock 4.2 and flashed that onto it. Was that right or do I have to find the stock image that came with it out of the box (so 4.1.2 or close)?
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
RimSide said:
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
Click to expand...
Click to collapse
What i believe has happened is that your partition module has become corrupted.
So, you tried flashing stock, and tried factory reset?
Does it show up on your computer as 6 GB when you connect it?
I had the same thing happen. I just used wugs toolkit to flash back to stock, then rerooted from there. That is the easiest way I know of to fix. Becides download times it only takes like 15 minutes to flash to stock, then unlock and root and you are back on your way.
Hi guys,
I've a major problem. Today I received a notification from google to update my N4 to 4.3 version (OTA). My phone isn't rooted, not bootloaded or anything, it's just the same as I bought it. Since the installation was finished, my device is restarting itself every 0.5-1 minute. of course I can't use it anymore. I tried to make factory reset, but it didn't help. In addition, I noticed that when I charge it or connect the device to my computer, it doesn't restart itself.
Any ideas?
Thanks,
Yaniv
Cache and Dalvik cache wipe?
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Cache and Dalvik cache wipe?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I did it. nothing has changed.
What should I do?
Try downloading the factory image and flashing it
http://forum.xda-developers.com/showthread.php?t=2010312
yanivriv said:
Yes, I did it. nothing has changed.
What should I do?
Click to expand...
Click to collapse
Oops, accidental thanks.
Ok so you will have to unlock the bootloader first and then flash this: https://developers.google.com/android/nexus/images#occamjwr66v
Go to bootloader mode and run the batch file.
Sent from my Nexus 4 using Tapatalk 4 Beta
There's no need to unlock bootloader for flashing factory images afaik.
--
Nevermind, bootloader needs to be unlocked.
Remind that unlocking the bootloader WILL wipe data!
If you have no experience in using ADB/Fastboot. I recommend using "Wugfresh Toolkit" version 1.6.4 worked on 4.3 for me (I messed up my stock ROM after OEM unlock).
Send from my Nexus 4
As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Ajxx16 said:
As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Ajxx16 said:
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Click to expand...
Click to collapse
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Ajxx16 said:
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Yep!
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
After today's update I can no longer Access the pull down menu. All I see is a message saying "No Notifications". The pull down menu isn't there and the home button and the recent button both don't work. Has anybody any idea how this can be remedied?
Have you tried the following:
- reboot the 6P
- clear the cached data in Storage and USB
- boot into recovery and clear the cache partition
Sorry, no change
Hmm and I was just going to ask if the March update was safe to load.
Sent from my Nexus 6P using Tapatalk
How did you install the update? Are you rooted and/or any mods?
Heisenberg said:
How did you install the update? Are you rooted and/or any mods?
Click to expand...
Click to collapse
I'm having the same issue. Was on MMB29Q, stock, rooted (latest 2.68 systemless), no mods. Used Fastboot to flash the MHC19I factory images. I've tried re-downloading and re-flashing the factory image with no luck. Backing up user data now to do a factory reset.
try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507
Will test and report back. Thank you.
My guess is that data needs to be wiped prior to flashing the images, dirty flash is causing problems.
Did you install it via OTA?
Sent from my Nexus 6P using Tapatalk
Momotani-Hitoshi said:
try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507
Click to expand...
Click to collapse
This worked for me, whew!
I'm not exactly sure how this occurred. I unrooted my phone with the Nexus Root Toolkit in order to catch the OTA update. After the update was installed, I had These Problems but all is good now. Thank you.
Mister-B said:
This worked for me, whew!
I'm not exactly sure how this occurred. I unrooted my phone with the Nexus Root Toolkit in order to catch the OTA update. After the update was installed, I had These Problems but all is good now. Thank you.
Click to expand...
Click to collapse
As I said, most likely due to not wiping properly.
Momotani-Hitoshi said:
try this.
http://forum.xda-developers.com/nexus-4/general/fix-errors-dirty-flashing-t2940507
Click to expand...
Click to collapse
Thank you so much for replying in this thread. Your solution also helped me.
Is any one else still waiting for the march update ota?
Mister-B said:
After today's update I can no longer Access the pull down menu. All I see is a message saying "No Notifications". The pull down menu isn't there and the home button and the recent button both don't work. Has anybody any idea how this can be remedied?
Click to expand...
Click to collapse
Installed the update OTA with no such issues.
Hope you find a solution.
I'm still waiting for the March ota. I'm not rooted and don't want to be at this point. I use mero pcs but I don't think carrier has anything to.do with the update.
mojorisin7178 said:
I'm still waiting for the March ota. I'm not rooted and don't want to be at this point. I use mero pcs but I don't think carrier has anything to.do with the update.
Click to expand...
Click to collapse
I'd recommend you sideload it from recovery then. It would be the same as getting it from the system update app.
Sent from my Nexus 6P using Tapatalk
My notification pull down isn't working on home screen. However it works on lock screen.
I've recently got my Nexus 6P, and after setting up for first time, it received Jan update. Yesterday, I did the Feb and March OTA via adb sideload. I'm completely stock. I've reseted my device twice now, once I did restore, and 2nd time I set up device as new device. Yet my notification pull down won't work on home screen.
I haven't tried flashing factory image yet.
Any suggestions?
EDIT: I've now tried flashing 2 different builds of factory image (MMB29P and MHC19I). I still have the issue.
mumbhai55 said:
My notification pull down isn't working on home screen. However it works on lock screen.
I've recently got my Nexus 6P, and after setting up for first time, it received Jan update. Yesterday, I did the Feb and March OTA via adb sideload. I'm completely stock. I've reseted my device twice now, once I did restore, and 2nd time I set up device as new device. Yet my notification pull down won't work on home screen.
I haven't tried flashing factory image yet.
Any suggestions?
EDIT: I've now tried flashing 2 different builds of factory image (MMB29P and MHC19I). I still have the issue.
Click to expand...
Click to collapse
Are you wiping userdata when flashing? As I pointed out earlier in this thread it's most likely caused to due a mismatch in data.
Heisenberg said:
Are you wiping userdata when flashing? As I pointed out earlier in this thread it's most likely caused to due a mismatch in data.
Click to expand...
Click to collapse
yes I was wiping userdata when flashing.
I turn on debugging mode and enabled show touch, that top part (only size of status bar) wouldn't show any touch, so seemed like hardware issue.
Phone is already its way for RMA now.