i was on android m latest build and then i decided to try the new android n dp3 beta so i enrolled my 6p and updated through the ota update but after the update my 6p never started it stucks at the boot animation forever i tried wiping cache and also did a full wipe but its still the same. the oem unlock option is also disabled so i cannot flash factory images. i came to know that when we want to roll back to android m from the current beta we just have to unenroll our device from the beta and google sends an ota update of the current marshmallow build to roll back to it. now want i want to try is sideload that update package through adb an see if i can go back to android marshmallow. Please any of you who are trying out the latest android n beta provide me the zip file for the ota which google sends when we unenroll our device?
actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try
Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
murphyjasonc said:
Try to adb side load dp3. I think it can be installed on stock recovery and a fresh install might help. Wipe cache and factory reset afterwards and hope for the best. This won't make your problem any worse but has a chance at helping.
Click to expand...
Click to collapse
spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?
Ame123 said:
no its not happening. if anyone of you are using nexus 6p and are on the android n beta then please can you follow what i have posted in the first comment?
Click to expand...
Click to collapse
I second this. Would be very helpful if someone could post the official roll-back marshmallow .zip for the 6p.
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!
AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Click to expand...
Click to collapse
Correct.
AlfexOmega said:
My phone is in the same position as OP. Do I just sideload this ZIP using adb?
Update: Sideload completed, first boot froze and phone restarted then second boot has booted to welcome screen!! Dude I cannot thank you enough I tried literally everything and nothing worked and I lost hope until I saw this!
Click to expand...
Click to collapse
Good stuff! Glad to help I thought this would work!
matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?
matt1515 said:
Good stuff! Glad to help I thought this would work!
Click to expand...
Click to collapse
Yep--can confirm this worked for me as well. Thank you so much for posting the .zip, matt1515.
AlfexOmega said:
So this was the OTA that you get when you unenroll your Nexus from the Beta Programme?
Click to expand...
Click to collapse
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
Ame123 said:
actually there is a simple step. anybody using the nexus 6p and running the latest android n beta just unenroll your device and when you get a notification for the ota update just enable usb debugging adn connect to computer and type command adb logcat and in the logcat file there will be a url for the ota just give me that url i will download it and try
Click to expand...
Click to collapse
https://android.googleapis.com/packa...cd4f52b800.zip
matt1515 said:
Yes sir I unenrolled from the beta I got the link from adb logcat
---------- Post added at 01:22 PM ---------- Previous post was at 12:48 PM ----------
https://android.googleapis.com/packa...cd4f52b800.zip
Click to expand...
Click to collapse
Nice! Thanks so much again
matt1515 said:
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Good luck! Hope this helps people
Dev preview 3 downgrade to MM
Click to expand...
Click to collapse
it worked. thank you very much for helping:good::good::good::good:
Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks
kick069 said:
Same thing happened to me, luckily it decided itself to boot fully after an hour. However I did notice that USB debugging was not enabled after all this mess. Does that mean if it didn't resolve then I would have had a nice brick without the option of side loading from a PC? Also does the unlock bootloader in dev options need to be checked off for any reason other than flashing custom roms? Can I still install official images and still have the bootloader locked?
Now I'm just looking for ways to be prepared in the future in case it happens again, thanks
Click to expand...
Click to collapse
Leave USB debugging and OEM Unlock enabled. This will help you so much more in the event of any issues during updates.
If OEM Unlock is turned off then you cannot flash factory images. You CAN leave this off and still ADB Sideload OTAs. However, if the ADB Sideload update is corrupt or flashes and you are stuck in a bootloop, there is very little that can be done to resolve it.
Sent from my Nexus 5X using Tapatalk
Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?
freezerbite said:
Has anyone here who flashed back to MM tried to do the OTA N update again? How did it go?
Click to expand...
Click to collapse
Yes. I tried but again got stucked in bootloop. So i am not touching any beta
It's so weird that some people get stuck with this boot loop issue and some just don't. I know things can happen, but I feel there's a enough users in the same boat that there's has to be a common denominator.
Sent from my Nexus 6P using Tapatalk
Related
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
kujhawk1977 said:
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
Click to expand...
Click to collapse
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
playya said:
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
Click to expand...
Click to collapse
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
kujhawk1977 said:
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
Click to expand...
Click to collapse
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
CWM will not be able to flash OTA successfully. You need to sideload it through stock recovery or TWRP.
playya said:
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
Click to expand...
Click to collapse
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
kujhawk1977 said:
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
Click to expand...
Click to collapse
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
playya said:
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
Click to expand...
Click to collapse
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
kujhawk1977 said:
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
Click to expand...
Click to collapse
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
I what to do whatever I have to do to fix my problem and I am not sure what that is.
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
Click to expand...
Click to collapse
OK I have adb platform tools. And I have the krt16s.zip Where can I find instructions on how to push the rom over to my phone and flash?
kujhawk1977 said:
I what to do whatever I have to do to fix my problem and I am not sure what that is.
Click to expand...
Click to collapse
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
playya said:
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
Click to expand...
Click to collapse
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
kujhawk1977 said:
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
Click to expand...
Click to collapse
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
playya said:
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
!!!!!!!!!!
So I still have the problem and cannot find a fix. Anyone here up for the challenge?
I was stuck in a bootloop and a failed OTA 4.4 update.
My nexus 4 is rooted and has CWM so yes I know i should have updated manually in the first place, but I didn't. After the update failed, it was stuck in a bootloop.
The next step I did was to side load the update. It ran through the install and at the end when 100% is says Installation Aborted. When my device is rebooted it is now stuck on the screen Google in white font.
Some other notes that MIGHT be related: USB Debugging is NOT enabled, as I can not boot into my device.
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
---------- Post added at 07:37 PM ---------- Previous post was at 07:31 PM ----------
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
No one has answered your question yet. I will.
Edited to say I did find a way to bridge (adb) files over without having USB Debugging selected on the phone.
Updated drivers and used ADB / SDK to move new Recovery and ROM over to my phone using CWM. Never trusting TWRP again
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
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
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.
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Sent from my A0001 using Tapatalk
trsargent said:
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Click to expand...
Click to collapse
do you have an adb option in your recovery ?
nicoconepala said:
do you have an adb option in your recovery ?
Click to expand...
Click to collapse
Yes, I can get to an adb option in recovery
Sent from my A0001 using Tapatalk
trsargent said:
Yes, I can get to an adb option in recovery
Click to expand...
Click to collapse
ok then you should try to flash stock rom from essential
nicoconepala said:
ok then you should try to flash stock rom from essential
Click to expand...
Click to collapse
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Sent from my A0001 using Tapatalk
trsargent said:
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Click to expand...
Click to collapse
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Wrong section.
NaterTots said:
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Click to expand...
Click to collapse
Gave it a try, but it didn't resolve the issue. Got the your device is corrupt message. Any other ideas? Thanks!
Sent from my A0001 using Tapatalk
I'm searching for answers too! My essential is doing the dotted box to the dotted circle spin back & forth over & over ! I saw the dead robot with exclamation mark . The only thing on the essential website is to wipe phone ! Help. If the person that made this phone do this to people dies please let me know, so I can smile during this stressful time . If they r still alive I hope they are in agony over something thx!