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?
Related
Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it
nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0
Thats not greedy, your just too excited for 4.3
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate
What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.
I searched all the internet and can't find any soliution to this.
Here are some examples (didn't find any of N4, but these are the same):
Some additional information:
It happens only on 4.3 or later (including 4.4 port) ROMs or stock OS.
It started when 4.3 came, i updated it officialy (my phone wasn't rooted/unlocked yet)
There were some times on 4.3 stock when it booted after half an hour, but I couldn't boot it again after next shutdown.
I can get to the recovery mode.
I tried to wipe everything, bring it back to factory state, but this thing still, happens. The only way I can use my phone is to have 4.2.2 ROMs/stock (I use cyanogenmod).
Any ideas on how to fix it?
EDIT: Solved by:
1. Flashing stock 4.2.2
2. Trying to officially update
3. Phone doesn't install the update, but goes to recovery instead?!?
4. Flashing official 4.3 with flash-all.bat
Man, you are lucky I saw this. This just happened to me today too and I freaked out. You need to download the radio from 4.2.2. Then manually fastboot install. Once you've done that everything works again and no more bootloop. I guess I accidentally wiped the firmware when installing 4.4. Anyways look for that and I promise you'll find it. I'll look for the post I found and post the link. I promise that's the issue.
I would recommend to download the toolkit and flash stock image. Make sure to backup all your files; it will wipe out everything.
Sent from my Nexus 4 using Tapatalk
nikeman513 said:
Man, you are lucky I saw this. This just happened to me today too and I freaked out. You need to download the radio from 4.2.2. Then manually fastboot install. Once you've done that everything works again and no more bootloop. I guess I accidentally wiped the firmware when installing 4.4. Anyways look for that and I promise you'll find it. I'll look for the post I found and post the link. I promise that's the issue.
Click to expand...
Click to collapse
Nope, doesn't work
badboy47 said:
I would recommend to download the toolkit and flash stock image. Make sure to backup all your files; it will wipe out everything.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
This one doesn't work too
00Justas said:
This one doesn't work too
Click to expand...
Click to collapse
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.
Here is a photo of my Fastboot screen :crying:
https://www.dropbox.com/s/p5xdyftiv9ua0c3/IMG_20131103_223244.jpg
abaaaabbbb63 said:
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.
Click to expand...
Click to collapse
Hello,
thahts My first post/replay but i hope it will be fine.
I have the same problem for 2 day's now.
My baseband is: M9615A-CEFWMAZM-2.0.1700.84
I've flashed the stock 4.2.2 and 4.3 with Wug's toolkit http://forum.xda-developers.com/showthread.php?t=2015469&page=94 sevral time's and it did't work
Now i'm stuck on the X logo after Google boot...
Any idea's how to get Nexus back to work ???
!!!!!! I DID IT !!!!!! :victory::victory::victory:
I just got to work My Nexus after following this steps: http://forum.xda-developers.com/showthread.php?t=2010312
IMPORTENT - please follow the instructions writen in RED color as a NOTE after flashing stock. It starts like that: "Note that some users indicate that they can't get past the X on boot...."
PS
Now back to customizing My Nexus
barteekn said:
Here is a photo of my Fastboot screen :crying:
https://www.dropbox.com/s/p5xdyftiv9ua0c3/IMG_20131103_223244.jpg
Hello,
thahts My first post/replay but i hope it will be fine.
I have the same problem for 2 day's now.
My baseband is: M9615A-CEFWMAZM-2.0.1700.84
I've flashed the stock 4.2.2 and 4.3 with Wug's toolkit http://forum.xda-developers.com/showthread.php?t=2015469&page=94 sevral time's and it did't work
Now i'm stuck on the X logo after Google boot...
Any idea's how to get Nexus back to work ???
Click to expand...
Click to collapse
use the guide "ubrick your nexus 4 as long you can get in the bootloader" it reformats everything in download mode or something like dat.
abaaaabbbb63 said:
Does your baseband show "Unknown" in the phone settings?
I had the same problem some weeks ago. Fixed it by flashing the stock 4.3 image again and again. The 3rd time it worked.
Click to expand...
Click to collapse
No, it shows the one I flash. Did you flash using flash-all.bat or in recovery or using adb, and which one jwr666y or jwr66v?
00Justas said:
Did you flash using flash-all.bat or in recovery or using adb?
Click to expand...
Click to collapse
Flash-all.bat. The other way is through Fastboot. You can't install images through adb or recovery directly.
opssemnik said:
use the guide "ubrick your nexus 4 as long you can get in the bootloader" it reformats everything in download mode or something like dat.
Click to expand...
Click to collapse
If you are talking about this, tried, didn't work.
abaaaabbbb63 said:
Flash-all.bat. The other way is through Fastboot. You can't install images through adb or recovery directly.
Click to expand...
Click to collapse
After many re-installs still not working...
EDIT: Working
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
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.