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.
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?
I wonder... Has anyone already got an OTA update to 5.0.2? Google released the factory image on its website recently so we can do it manually, but I personally don't want to, and waiting for the OTA)... If anyone got it, you can share here p.s. already got mine and updated
Nexus 7 2nd WiFi Android 5.0.2
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
yosmokinman said:
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
Click to expand...
Click to collapse
Thanks, but I'm lazy)))
Nexus 7 2nd WiFi version Android 5.0.1
yosmokinman said:
You could be waiting weeks. Just fastboot flash that **** it takes two minutes and you don't have to wipe your data.
Click to expand...
Click to collapse
Unless I'm missing some step.. I thought flashing factory image wipes all data .
vkk178 said:
Unless I'm missing some step.. I thought flashing factory image wipes all data .
Click to expand...
Click to collapse
If you remove the “-w” flag from the flash-all.bat file in the factory images zip it will prevent wiping data.
kilroystyx said:
If you remove the “-w” flag from the flash-all.bat file in the factory images zip it will prevent wiping data.
Click to expand...
Click to collapse
What about a locked device?
mutantlx said:
What about a locked device?
Click to expand...
Click to collapse
you need to unlock it, that makes it full wipe by default , so you can flash a factory image.
idCyber said:
you need to unlock it, that makes it full wipe by default , so you can flash a factory image.
Click to expand...
Click to collapse
That's what I thought, thanks [emoji4]
Cool..just received the ota update. i guess the updates are being rolled out as we speak
Got the 5.0.2 OTA this morning pst.
now we need someone to capture it
mutantlx said:
now we need someone to capture it
Click to expand...
Click to collapse
A member has already captured it in another thread. Here's a link to his post. Credit naturally to him:
http://forum.xda-developers.com/showpost.php?p=58285301&postcount=448
[emoji98]
My N7 Flo received her OTA notification just now too. I wish the OTAs would flash with TWRP
mutantlx said:
What about a locked device?
Click to expand...
Click to collapse
Read this guide and maybe you find a way to don't lose your data or let say recover your data after wiping in the first time that you unlock the bootloader.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Failed
Just got mine and it failed to go on to stock rooted 5.0.1. Recovery reported an error; not sure why?
I just got the OTA update but am not clear on what this release contains. I haven't been able to get my hands on any release notes? Is there anything big in this update?
Thanks,
Rick
C5Longhorn said:
I just got the OTA update but am not clear on what this release contains. I haven't been able to get my hands on any release notes? Is there anything big in this update?
Thanks,
Rick
Click to expand...
Click to collapse
Noting big, no major fixes it should just be more responsive and feel a bit faster. Fact that I can confirm.
Sent from my Nexus 7
I just got the OTA update. Installing now.
I've had a LOT of wifi issues on L, wifi is always disconnected with "Authentication Problem" shown, if i reconnect it's fine. I haven't seen it again since moving to 5.0.2, but then again, it's only been 24h.
My Nexus 7 2012 can download the update, but when it restarts and start the install i get an "error". I have already try hard reset and get the same result.
Any ideas?
You may be luckier than you know... The damn thing is LAGGY as hell! This may be googles Vista...
? Take me to your Leader ?
Thisisshaggy said:
My Nexus 7 2012 can download the update, but when it restarts and start the install i get an "error". I have already try hard reset and get the same result.
Any ideas?
Click to expand...
Click to collapse
Sorry that I can't help with the error and for dragging this topic just a bit off the main course, but I'm curious: Are you saying that you're receiving this as an automatic, OTA, update?
Have others been receiving this OTA too?
thanks,
john
Thisisshaggy said:
My Nexus 7 2012 can download the update, but when it restarts and start the install i get an "error". I have already try hard reset and get the same result.
Any ideas?
Click to expand...
Click to collapse
is your tab rooted?
Thisisshaggy said:
My Nexus 7 2012 can download the update, but when it restarts and start the install i get an "error". I have already try hard reset and get the same result.
Any ideas?
Click to expand...
Click to collapse
I have an unlocked bootloader and d/l the factory image for 5.1. I extracted the .img files and flashed them with fastboot. Also flashed twrp 2.8.5.1 and supersu 2.46.zip to get root. Everything is working very well and is much snappier than 5.02. You probably have changed something in the /system folder. Flashing the system.img will overwrite whatever is messing up the update.
phrozenstare said:
is your tab rooted?
Click to expand...
Click to collapse
It was rooted. I unrooted with the option in supersu, then i did a hard reset.
Groid said:
I have an unlocked bootloader and d/l the factory image for 5.1. I extracted the .img files and flashed them with fastboot. Also flashed twrp 2.8.5.1 and supersu 2.46.zip to get root. Everything is working very well and is much snappier than 5.02. You probably have changed something in the /system folder. Flashing the system.img will overwrite whatever is messing up the update.
Click to expand...
Click to collapse
Ah ok. Thanks for the info
jrredho said:
Sorry that I can't help with the error and for dragging this topic just a bit off the main course, but I'm curious: Are you saying that you're receiving this as an automatic, OTA, update?
Have others been receiving this OTA too?
thanks,
john
Click to expand...
Click to collapse
Since 2 days my grouper wlan is showing the notification that the system update android 5.1 is available.
I never did a ota update. I always used a flashable zip via custom recovery. The groupers bootloader is unlocked, rooted, a custom kernel and custom recovery installed. Can I do the update or must I undo all?
Sent from my Nexus 7 using XDA Free mobile app
Thanks for the info on the new OTA.
My N7, grouper, has always been stock, except for being unlocked/rooted. I've always taken the OTAs in the past just fine. Clearly I don't know about this one.
Based on that history, my guess is that, at the very least, you're going to need to flash the stock kernel and recovery to take this one. Time will tell...
cheers,
john
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Download the Google factory image for the 6p. Use fastboot to manually flash the system.img, boot.IMG, and recovery.IMG. take the ota then reroot.
Sent from my Nexus 6P using Tapatalk
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Go to guide, instructions there:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
raul4916 said:
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
Click to expand...
Click to collapse
Yes you can.
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
airmark said:
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
Click to expand...
Click to collapse
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
What did you do?
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Heisenberg said:
What did you do?
Click to expand...
Click to collapse
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Any ideas? Do I need to wipe data?
airmark said:
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Click to expand...
Click to collapse
airmark said:
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Click to expand...
Click to collapse
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Heisenberg said:
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Click to expand...
Click to collapse
I had a screen lock pattern, I entered the numbers that correspond to it (from what I read somewhere else, like a num keypad), no joy.
But then again, shouldn't actual booting into the system work as well? Why give this error msg?
I'm going to format then...
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
TheAtheistOtaku said:
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
Click to expand...
Click to collapse
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Heisenberg said:
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
Click to expand...
Click to collapse
i meant a TWRP zip. unless im misunderstanding something, you can just flash those over your current rooted stock and be on your way
---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------
airmark said:
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Click to expand...
Click to collapse
known problem, read this
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
airmark said:
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
TheAtheistOtaku said:
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
Click to expand...
Click to collapse
Thanks, I've just overcome the trauma and gathered the courage needed to give it another go today
So, do I have this right? If I download and flash build MDA89D ROM will it upgrade in place over my currently installed build MDB08K without losing my data? (I asked in that thread as well)
Sent from my Nexus 6P using XDA Free mobile app
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