Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo
No OTA here in Germany so far
Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk
Neither in France
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk
Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.
upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk
Got the OTA from pie right now 1188.8mb
I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?
yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.
germany here, installing the update now, takes quite some time for being only 41mb, hope it works
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^
sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?
After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).
Related
Purpose of this thread:
This thread is about changes within factory images of newly released Android updates in comparison with the previously released Android update.
Latest Android version 8.1.0 (Oreo): OPM7.181205.001
This December update is most likely gonna be the last official security update from Google for the Nexus 5X (source: https://support.google.com/nexus/answer/4457705?hl=en)
Download-Link: https://dl.google.com/dl/android/aosp/bullhead-opm7.181205.001-factory-5f189d84.zip MD5: 05DEE954B6FD17B6B301A4D1C90B1B5EChangelog: https://source.android.com/security/bulletin/pixel/2018-12-01 Unchanged:
bootloader bhz32c
radio 2.6.42.5.03
Changed: (md5sum in brackets)
boot (438936FDD50D2C8D3FA8D7586624D670)
recovery (E55D287CBCF78DACEC618E538CE74014)
system (9DD438116FB86EDBF89876A728CC0AA8)
vendor (97C79E83F00AD006D77DA9C570A71BD7)
How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.
AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.
Click to expand...
Click to collapse
That has worked before. Still should work, I have not tried it though.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 02:40 AM ---------- Previous post was at 02:39 AM ----------
Any idea what changes to the system?
Sent from my Nexus 5X using Tapatalk
Smoosh1 said:
userdata.img is the same (MD5: 808444c5b0a4cbfa1f2cbf38b6629b67)
cache.img is the same (MD5: 9aedd15ebf6bc07a38de5bcd705f516a)
Click to expand...
Click to collapse
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.
AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Click to expand...
Click to collapse
I would recommend you follow Heisenberg's guide, section 9 "How To Update To A New Build Of The Stock ROM"
sfhub said:
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.
Click to expand...
Click to collapse
You are right, they most likely won't change throughout the lifecycle of nougat. I just mentioned them for the sake of completeness.
Comparison of Android Updates
Do It A Your Own Risk. I am not responsible if you make a mistake.
I found this method on the Internet and I applied it to my phone right now:
(WITH THIS METHOD YOU WILL NOT LOSE ROOT, CUSTOM RECOVERY)
1.Download the ZIP.
2.Download FlashFire.
3.Open flashfire and accept for root access etc etc...
4.click "+" button and click to "flash firmware package" and find the ZIP.
5.Wait for a couple o seconds or 2mins, and then uncheck the "Recovery" (if you don't want to lose the custom recovery) and "Data" (maybe on your device will be already unchecked so keep it unchecked if you don't want to lose your data) and then I clicked the "ν" button.
6.Click "Flash". Your screen will be black for a minute and then you will see a progress bar at the bottom of your screen and log of FlashFire what installs on your device.
7.When it finish flashing, your device will be automatically reboot.
8.Wait a couple of minutes (approximately 3-6 mins).
9.Your device is running the latest Android Version with the latest Security patches and you have also root back....
Sent from my iPad using Tapatalk
AFK269 said:
I found this method on the Internet and I applied it to my phone right now
Click to expand...
Click to collapse
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.
krelvinaz said:
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.
Click to expand...
Click to collapse
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Sent from my iPad using Tapatalk
AFK69 shared the typical img flashing instructions for FlashFire. I've been using it on my rooted devices for months. No issues.
Sent from my Nexus 9 using Tapatalk
Android November update NRD91N released
New Android security update NRD91N got released today.
What has changed? -> See updated OP
I'm sorry, but HERE the last one is still NPF10C, it's a different branch or I'm missing something?
EDIT: nevermind i'm dumb, the post is about the official factory image, mine is about devoloepr preview
AFK269 said:
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Click to expand...
Click to collapse
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Sent from my Nexus 5X using XDA Labs
SM210 said:
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Click to expand...
Click to collapse
Me too!! (Curious)
Sent from my Nexus 5X using XDA Labs
My build number changed to N5D91L after the November update, not NRD91N. How come?
In the past there were some different builds for different countries with a different radio.img. So where do you come from?
I live in the UK.
Edit: And my radio is still 2.6.33.2.14.
Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.
N5D91L is 7.0.0_r21 while NRD91N is 7.0.0_r15. Probably a quick hotfix on the unfixed dirtycow exploit + other fixes . Too lazy to check the real changes on git.
Since some of us is still waiting for the ota by phases and by the time we are getting it, google already roll out N5D91L. Thus the mysterious build update emerged. The others on NRD91N will get it or probably not, until December.
ThorSchwar said:
Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.
Click to expand...
Click to collapse
Nevermind, apparently it's a regular build - see: http://forum.xda-developers.com/nexus-5x/help/n5d91l-strange-android-build-t3500378
November OTA patch has new tag:
Just captured this from my 5X.
Source: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Target: google/bullhead/bullhead:7.0/N5D91L/3425233:user/release-keys
https://android.googleapis.com/packa...a1f18978ec.zip
So looks like the new build is not NRD91N but N5D91L.
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Also, it seems they have added an automatic video creation "Highlights" feature to the Gallery app, utilizing Quik video editor. Not sure if this was already included in previous versions.
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Gr8 and battery life?
I guess they mentioned it in updates?
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Can u share a screenshot of ur about page after the update please?
Sent from my Honor 8 using XDA Labs
ayush rao said:
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
Can u share a screenshot of ur about page after the update please?
Click to expand...
Click to collapse
Here you go.
peterchen1999 said:
Here you go.
Click to expand...
Click to collapse
Awesome. I can't wait for the update to reach my device!!!!
Sent from my Honor 8 using XDA Labs
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
cant wait!!!
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
You need to be on stock and unrooted for the official update process to work.
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
unroot then do update
PS: My L04 still not get this update
blackbuffalo said:
unroot then do update
PS: My L04 still not get this update
Click to expand...
Click to collapse
Mine too. Might take another 1-2 weeks probably for every device to receive the OTA.
Sent from my Honor 8 using XDA Labs
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Even me, an FRD-L04 user, didn't receive it. Once we receive the update u can expect it on ur phone within a week or two. That's what happened in the case of the B385 update.
Sent from my Honor 8 using XDA Labs
Got it last night. Currently using phone on first day of the update.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Got it last night on my L14.
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Thanks! Hopefully I get it soon. Any major changes? Heard there were some apps that were added.
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
nestojean said:
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
Click to expand...
Click to collapse
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Sent from my Honor 8 using XDA Labs
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Well I got the phone about a week ago and just activated my new tmo sim card last night to get cell service on it so I'm probably not the best judge of whether any performance changes occurred. Based on the change log I wasn't expecting much though.
FYI I'm still completely stock, locked bootloader for now if that made any difference in the delivery of the update.
ayush rao said:
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Click to expand...
Click to collapse
Thanks for the explanation. This is the route I had to take. I have FRD-L04. I was on B385 with TWRP and Magisk 14.0. Unrooting and flashing boot.img and recovery.img from 385 did not help to install the new update. I keep getting the same error of Package failed. No matter what I seemed to try nothing worked.
So, this sucks, but, I factory reset. Then RE-locked bootloader. Then, I had to download *latest full package* otherwise I still received same error. But, now I am on B388 and i'm going to try flashing TWRP and installing Magisk now.
Live photos seems interesting. Pretty excited about that.
Question to anyone who got the update, any changes in battery life?
https://www.theverge.com/2017/12/5/16737066/google-burger-beer-emoji-android-8-1-fix-release-date
Your thoughts.
Edit:
Seems it is out??
https://www.phonearena.com/news/And...leased-here-are-all-the-new-features_id100421
NoobInToto said:
https://www.theverge.com/2017/12/5/16737066/google-burger-beer-emoji-android-8-1-fix-release-date
Your thoughts.
Click to expand...
Click to collapse
I think it's too soon after DP2. I think it'll be later this month or even January.
roirraW "edor" ehT said:
I think it's too soon after DP2. I think it'll be later this month or even January.
Click to expand...
Click to collapse
The verge and 9to5 Google are saying that it will be today/tomorrow (based on time zone).
NoobInToto said:
The verge and 9to5 Google are saying that it will be today/tomorrow (based on time zone).
Click to expand...
Click to collapse
It's certainly possible. Just my opinion. I don't know why they'd release a DP2 and only wait a week to release the final, but they could and then they'll likely release 8.1.1 next month.
Even if it comes out today I might wait and see what everyone else is saying about it and any bugs before I upgrade. I don't have time to tinker with my phones as much as I used to. We'll see if I can resist, though, but minimally I'll use Titanium Backup to back up all my user app data and sync to Google Drive, backup things I mean to keep from my internal storage and make sure all my photos/videos are synced, then the final nandroid - then I'll have to make the decision as to whether I flash 8.1 clean or use FlashFire to upgrade.
When the user experience may have changed some in a version of Android, sometimes I like to start fresh, besides minimizing any problems that might be due solely to updating while keeping system data.
I was happily surprised I was able to do everything from FlashFire successfully for the November update including re-flashing the Ex Kernel.
https://www.neowin.net/news/android-81-oreo-rollout-for-pixel-and-nexus-devices-will-begin-today
---------- Post added at 01:15 PM ---------- Previous post was at 01:14 PM ----------
Maybe AT&T will release for S8 and S8+ by Spring......
Hello there. I'm on DP2 now, should i unenroll from beta to get the stable release? Thanks
Nicolae-Daniel said:
Hello there. I'm on DP2 now, should i unenroll from beta to get the stable release? Thanks
Click to expand...
Click to collapse
No, unrolling right now from beta will give you update for 8.0 stable
Dont bother sideloading from dp2 either, it will fail.
For now we will have to just wait for the smaller ota which takes us from dp2 to 8.1 stable.
Nicolae-Daniel said:
Hello there. I'm on DP2 now, should i unenroll from beta to get the stable release? Thanks
Click to expand...
Click to collapse
NoobInToto said:
No, unrolling right now from beta will give you update for 8.0 stable
Dont bother sideloading from dp2 either, it will fail.
For now we will have to just wait for the smaller ota which takes us from dp2 to 8.1 stable.
Click to expand...
Click to collapse
You can flash the full image, after removing the -w from the flash all bat file to save data. Then unenroll. Worked fine here.
TonikJDK said:
You can flash the full image, after removing the -w from the flash all bat file to save data. Then unenroll. Worked fine here.
Click to expand...
Click to collapse
I haven't unlocked the BL ever since I got nexii/pixels. Never felt the need to ( except when n6p died and needed a workaround).
It's here for me.
Ota is live Pixel Verizon on beta DP2.
OTA Pixel dp2 to final 39,90mb released
Got it today.
So far so good, but I'd really like to find a way to remove the search bar. It's pretty terribly placed.
(stock, no root)
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
scrin378 said:
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
Click to expand...
Click to collapse
No, ADB sideload will fail. 8.1 DP2 is on a newer branch than December 8.1 stable. You could install via fastboot or wait until Google pushes the OTA for preview users.
Sent from my Nexus 5X using Tapatalk
Opt out beta tester
mr.joshuanice said:
Opt out beta tester
Click to expand...
Click to collapse
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
luk.giak said:
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
Click to expand...
Click to collapse
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
scrin378 said:
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
Click to expand...
Click to collapse
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
No, i opt out from beta program, and then i get official version..i lose my data, but nothing special, most of pics, docs, etc...is on the cloud storage ..so no big deal for me.. good luck with patience
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
luk.giak said:
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
Click to expand...
Click to collapse
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
whpsnp said:
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
Click to expand...
Click to collapse
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
luk.giak said:
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
Click to expand...
Click to collapse
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
whpsnp said:
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
Click to expand...
Click to collapse
:good:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Sent from my Nexus 6P using Tapatalk
OT
As a side note for all people who do not want to unlock the bootloader. Please consider at least to:
* activate developer options (tapping 7 times on the build number under phone information)
* enter developer options and activate 1) Debug USB and 2) Enable OEM Unlock
As you probably know, the nexus 6p is subject to the bootloop of death. It is hardware based and, when it happens, the only way to give a second life to the Nexus 6p is to flash a special boot.img (or kernel) that enable only 4 cores (over 8). You can perform this procedure only if you can unlock the bootloader. Hence, only if you have previously enabled the two options above (debug USB and Enable OEM Unlock).
---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ----------
Ulver said:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Click to expand...
Click to collapse
Google is really messing up with OTAs. You should consider to manually flash a factory image or to adb sideload a full OTA (available on the official website).
Same situation for me, i get ota 8.1 ~ 10 December then 8.1 dp2 ota. And for now no ota I am still on security update from November...
One question, if im rooted, can i flash full OTA with flashfire??
sideload the DP2 to Final ota (Dec patch).
Then unenroll your device from beta, you will get an update (Jan patch)
https://android.googleapis.com/pack.../105818de493dde2bb290a13474a367f78ac6122f.zip
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss
SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now
What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)
anyone know how to root on beta5??
jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below
Where is everyone getting beta 5? I only have beta 4 available.
stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here
Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:
Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?
xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.