- There are no Pixel security patches in the February 2019 Pixel Update Bulletin.
-Functional patches
All Pixel devices running Android 9 will receive an Android 9 update as part of the February OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and
supported Pixel devices.
Now it is installing. I still don't know what is changed. The Update is 111.6MB.
https://source.android.com/security/bulletin/pixel/2019-02-01.html
Security patch levels of 2019-02-05 or later address all issues associated with the 2019-02-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Pixel update schedule.
Has anyone had issues updating to FEB then applying Magisk?
Thanks
I'm having issues flashing the factory image without "-w," gives me the "Your device is corrupt and cannot be trusted" screen. Anyone else?
EDIT: flashing the Jan update fixes this and allows my device to boot again
So, I found this little egg by tapping, then pressing on device number. Is this new?
Paint.apk ?
N3V3RS3TTL3 said:
So, I found this little egg by tapping, then pressing on device number. Is this new?
Click to expand...
Click to collapse
Nope, it's been there before.
The only visual change I have noticed on my Pixel 2 XL so far is a slightly different color on the About Phone section in Settings.
N3V3RS3TTL3 said:
Paint.apk ?
Click to expand...
Click to collapse
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk
vagkoun83 said:
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's the Easter egg:
"The new Easter Egg can be found by going to ‘System’ > ‘About phone’ > ‘Android version’ > and tapping the nine multiple times, then the old P Easter egg will appear on a Pixel 3. If you keep taping the ‘P’ a few more times, the drawing UI appears."
The about phone option is no more in the system section.
docluv01 said:
Has anyone had issues updating to FEB then applying Magisk?
Thanks
Click to expand...
Click to collapse
I had issues with the update in general, but it was my fault. Everything worked out in the end. I think more than a little of it was because of the changes under the hood that Google applied.
Updated perfectly. Downloaded OTA, flashed in TWRP with TWRP zip, reboot to recovery to flash kernel then magisk. No issues whatsoever.
February feels much better, although could just be a placebo ?
I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.
mookiexl said:
I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.
Click to expand...
Click to collapse
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
I'm not sure what state your device is in so I'd flash the feb factory image using the flash all batch file with the -w removed. That'll return your device to stock without wiping it. Then fastboot twrp, then install twrp, if you want it, then install magisk.
mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
USB cables, ports, and platform-tools up to date?
Badger50 said:
USB cables, ports, and platform-tools up to date?
Click to expand...
Click to collapse
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.
mookiexl said:
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.
Click to expand...
Click to collapse
Meh...I've had the same twrp file for months, and it's worked with all the updates. But hey, this is the P2XL...so anything's possible :good:
jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
Not sure if I'd consider Deuces flash script a toolkit per se...
New Rising said:
Not sure if I'd consider Deuces flash script a toolkit per se...
Click to expand...
Click to collapse
It's a toolkit. Toolkits generally simplify processes and hide output that advanced users can use to achieve the same results without the toolkit.
Related
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016
Anyone flashed it?
OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app
We probably need to wait a little bit for OTA zip.
following for ota link
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.
mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk
Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.
waiting for ota zip :good:
I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Just installed! You have any advice about a compatible kernel?
Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.
65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.
OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124
Hi there XDA, I've recently been having issues with custom roms and random reboots, so I decided to go back to stock. Going back to stock I used fastboot to flash the system and boot images. After some setup I wanted to get root. Instead of there being twrp I ended up with the stock recovery somehow. TWRP 3.1.1 seemed to stick, then I decided to upgrade to the most recent version. And it no longer sticks(TWRP recovery).
I just don't know what to do or what the cause for this to happen may be. My only thought is that I'll have to fastboot flash recovery every time I want to modify something.
Any way you guys would be willing to shed some light on what's going on for me???
Sent from my SM-N7507 using Tapatalk
probably since you are not rooted
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
wizardwiz said:
probably since you are not rooted
Click to expand...
Click to collapse
Nah, I'm rooted through magisk
Exodusche said:
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
Click to expand...
Click to collapse
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
double post
dirtyreturn said:
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
Click to expand...
Click to collapse
So your flashing twrp after first boot, rooting and still won't stick?
Exodusche said:
So your flashing twrp after first boot, rooting and still won't stick?
Click to expand...
Click to collapse
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
Who knows maybe google changed something. Do it my way and you will be fine.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
When you flash system and boot images, root is removed. On Oreo, TWRP does not persist without root being maintained. I believe on Nougat or Marshmallow, this was not the case. When you booted into the stock rom, this restored the stock recovery.
Flash TWRP then boot directly into TWRP and flash Magisk. When installing new security patches, boot directly into TWRP and reinstall root.
Sent from my Nexus 5X using Tapatalk
any help ?
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work
Hey, after yesterday's security update, the phone is stuck on powered by android screen. The only thing I can do is go into fastboot. It does not boot into recovery (gets stuck on powered by android screen once again). I don't have an unlocked bootloader, so I cannot really flash directly from fastboot. Any ideas what could be done?
Hi,
I had the same Problem.
When my phone has booted, I could choose between "Start", "Fastboot" and "Recovery". I choose recovery, but everytime it booted to where I can choose between the options. After a few times (5 or so) it booted to TWRP. Then I Flashed Back to the January Update (OTA ZIP-File downloaden from the Essential Website). Then my phone booted normaly to Android.
Maybe if you Don't have TWRP, you can follow the instructions on the Website from Essential.
No issues here but I'm stock and unrooted
I had issues as well. The problem is anytime i try to boot into TWRP when i apply it to the current kernel. Magisk is fine, but TWRP, when applied to the current kernel doesn't seem to load.
1. After feb install, i put TWRP (with jan kernel) in slot B and i was not able to boot to it (it came right back to the fastboot screen). I could boot into A which was the new stock kernal but B was a no-go.
2. I then put the december kernel with twrp into slot b and that did the same thing! i was not able to boot into slot b.
3. Then i put the original TWRP mata file into B and then was now able to boot into twrp.
4. now in TWRP, in slot b, i ran the TWRP installer and it patched slot A and B. Upon reboot, slot a just bootlooped!
4. i then just copied the feb kernel with magisk into A and the phone boots.
5. i now have feb w/magisk on slot a and mata TWRP in slot b. I have not found a way to have twrp working in slot A!
JD
Well, in my case, the phone is fully stock. At this point, I think I am limited to fastboot as it's not booting in recovery. Is there anything that can be done within fastboot without unlocked bootloader?
update on "no booting with feb": i cannot get into twrp at all now. It doesn't matter if i use the original mata twrp kernel or any new or old kernels with TWRP; they all fail and boot to fastboot.
I reflashed jan and now twrp works just fine. Can someone confirm if feb does indeed work with twrp?
Thanks,
JD
Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out
RoyalOrigin said:
Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out
Click to expand...
Click to collapse
do you have a link for this twrp compatible with this months ota? i am not able to find it here on xda.
Thanks,
JD
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
RimvydasT said:
Is there anything that can be done within fastboot without unlocked bootloader?
Click to expand...
Click to collapse
Don't think so... You definitely can't flash anything with a locked BL.
RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
https://drive.google.com/file/d/11YtZTqgbDRgws10RpMwIGTSy_X_2A9re/view?usp=drivesdk
I will try that.
Thank you very much.
kt-Froggy said:
Don't think so... You definitely can't flash anything with a locked BL.
Click to expand...
Click to collapse
yeah.. it doesn't look good. I wonder what Essential reps will have to say about their update bricking the phone, but as it's out of warranty, I doubt there will be any positive outcome here.
RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Very nice find! Thank you for posting this information.
JD