Database Users

[MMB29P] January Android 6.0.1 Security Patch Factory Images Available

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

March Security update

Is up on Google developer website. MMB29V
https://dl.google.com/dl/android/aosp/shamu-mmb29v-factory-0b4a53f0.tgz
Edit: No change in bootloader or radio.

Thank you for upload. my work blocks google dl but not drive for some reason XD

Has anyone been able to get the checksum to verify? the MD5 for me doesn't match from the link provided or the Google image page.

just tried as well off the Google image page..MD5 does not match :|

I just downloaded from the stock images page also and the MD5 matches for me.

They just changed the MD5 code to match the factory image I downloaded. The new one matches my image.

How does one go about flashing this?
Flash all files through fastboot, except userdata.img?

murtaza02 said:
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
Click to expand...
Click to collapse
What build are you on now?

holeindalip said:
What build are you on now?
Click to expand...
Click to collapse
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6

murtaza02 said:
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
Click to expand...
Click to collapse
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)

cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
Will do and report back.
Stupid question, but does Google post changelogs?
Other than the security patch, could anything else have changed?
Sent from my Nexus 6

@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html

cam30era said:
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
That's some pretty detailed stuff!
Thanks man.
The factory image just finished downloading, I will report back in about 10 minutes.
Sent from my Nexus 6
---------- Post added at 07:17 PM ---------- Previous post was at 07:02 PM ----------
@cam30era
Thanks so much!
It worked. I flashed it and wiped cache in stock recovery. It's Optimizing apps now, and should be done soon!

cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
That's what I was getting too just wanted to make sure he was at least on 6.0

@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016

murtaza02 said:
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
Click to expand...
Click to collapse
Kernel is included in boot.IMG with other files.

I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?

wrydgj said:
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
Click to expand...
Click to collapse
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.

harpin14789 said:
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
Click to expand...
Click to collapse
I asked about recovery.img, I know that boot.img has to be flashed. Nevermind, I flashed both of them, just in case, and twrp after all flashes[emoji6]
Sent from my shamu using Tapatalk

What I find funny is that some of the patches are not even included in the update but in the updated binaries.
Also there were changes to the kernel. A few of the issues were kernel issues.

[updated 8-27-16] [Decrypted] [Modified Boot.img's for N][MM Boot.img_SystemRoot]

I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
MM modified DM removed removed force/encryption and custom sepolicy to allow system root.
DOWNLOADS FOR 7.0 OFFICIAL
NRD90M(Decrypted)(System_root hopefully coming soon)
https://drive.google.com/file/d/0B4yuQy7Zn1WSYm5sTXNhZmsxcVk/view?usp=sharing
DOWNLOADS FOR MM
MTC20F(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSeVc1bjdDOGFETDA/view?usp=drivesdk
MTC19V(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSY3FZaVNXMjhEN2c/view?usp=drivesdk
MTC19T(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSWXMyRHF1bGQ2YUU/view?usp=sharing
MCH19q
https://drive.google.com/file/d/0B4yuQy7Zn1WSclZ6dGhCNXNUUEk/view?usp=drivesdk
DOWNLOADS FOR ANDROID N Preview builds
NPD90G
https://www.androidfilehost.com/?fid=24572369242689017
NPD56N
https://drive.google.com/file/d/0B4yuQy7Zn1WSM3FORTl4ejlUV2M/view?usp=sharing
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSTklfZW1McXZxQUk/view?usp=drivesdk
NPC91k
https://drive.google.com/file/d/0B4yuQy7Zn1WSSG5WTGNBMHVvZXc/view?usp=sharing
DIRECTIONS
fastboot flash boot boot.img

Good to see your work here as well. :good:
Would love to see more.
F.A.Q - Frequent Answers and Questions

Bringing the love to 5x!!!
To users:
Don't question just follow his directions and profit
Sent from my Nexus 5x using XDA-Developers mobile app

Tigerstown said:
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
So this is a decrypted and DM checks have been removed. flastboot this boot.img when flashing N preview factory imgs. Also i will be posting a MM modified boot.img the has DM removed removed force/encryption and custom sepolicy to allow system root. but for now here is the N boot.img
DIRECTIONS
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys

m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
To my knowledge you need to decrypt phone then flash N and before boot flash decrypt boot img then boot twrp then flash super su 2.71. To be decrypted rooted N.
Now to begin that process you need a decrypted phone which is why i am waiting for m decrypt boot begore i proceed.
Tigerstown can correct me if i am wrong.
Sent from my Nexus 5X using XDA-Developers mobile app

m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache

DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution

m.daziale said:
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
Click to expand...
Click to collapse
No bootloop guarantee, until you do something different than this. :victory:

DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This is exactly what I was just going to reply. If your on N flash boot.IMG and decrypt using fastboot like said above.

Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?

zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
Yes, perfectly alright. Avoid the recovery image, in case you have TWRP installed.

zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
that is How I do it on my 6P. After flashing I boot to twrp and do factory reset myself. You don't need to flash the N recovery.
Sent from my Huawei Nexus 6P using XDA Labs

Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.

exploreresp said:
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
Click to expand...
Click to collapse
Hey no problem just glad to be helping out.
Sent from my Huawei Nexus 6P using XDA Labs

Op has been updated added MM MCH19q support. Still have to work on sepolicy for system root on 5x like I have it for 6P. Once I get it right I'll update with that.
Sent from my Huawei Nexus 6P using XDA Labs

aaaaand thanks again for the MM boot.img ! Glad to have both actually

Thanks for this, waiting for rootable version.

Hey thanks you for this
But if i flash only the modified boot on android n and i don't make a userdata wipe ?
What happen ?

khanjui said:
Thanks for this, waiting for rootable version.
Click to expand...
Click to collapse
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs

Tigerstown said:
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I can test it.

supersu - maybe these make bootloop?

Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks

I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk

so...i'm in 8.1 and these is the conclusion in that state after few tests.

I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk

What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk

stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.

the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..

Update — February 2019

- 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.