Database Users

T-Mobile OTA URL 5.0.1 LRX22C to 5.1 LMY47M

5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing

How do i install this again what are the requirements

Looks like I'm reverting back to 5.01 to get this one.

Just installed it. Thank you!

iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.

someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???

simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?

the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.

nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol

Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!

I just finish side loading it......

mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E

jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......

Sorry too far OT delete

kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?

LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.

Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)

lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.

Android 6.0.1 and any camera (stock included) fail.

I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?

Are you using the stock kernel

I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.

SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.

fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.

aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.

fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.

I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img

aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.

fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.

Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera

edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.

I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...

Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?

captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.

this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195

[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

[OBSOLETE] Root Android 7.0 Nougat after clean Install - Just use TWRP 3.0.2.1

Edit: Obsolete now. Twrp 3.0.2.1 is Out.
For now TWRP cant decrypt Android Ns vendor images so you cant flash SuperSU. So why not flash back old vendor to root the device and reflashing the NRD90M Vendor?
It works great. I root my clean install from factory image Android 7.0 NRD90M:
1. Flash the just released NRD90M via Fastboot
2. Reboot and set up your device.
3. Reboot to fastboot and flash vendor_mob30w.img by entering: fastboot flash vendor vendor_mob30w.img
4. Boot TWRP 3.0.2.0 temporary by entering: fastboot boot twrp-3.0.2-0-flounder.img
5. In TWRP copy UPDATE-SuperSU-v2.76-20160630161323.zip to your device and install it.
5.1 If you want to use adaway flash also AdAway_systemless_hosts_v2.zip.
6. Go back - back - back and reboot your device to fastboot.
7. Reflash the original vendor vendor_nrd90m.img by entering: fastboot flash vendor vendor_nrd90m.img
8. Reboot your device. Its rooted!
Extract the vendor files from the factory images or take these just extracted files from my google drive:
Download vendor_mob30w
Download vendor_nrd90m

Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.

corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
Is that one system less?

edit: nevermind this

osnapitsjoey said:
Is that one system less?
Click to expand...
Click to collapse
Yes CFAR is systemless.

If you were not a very smart man and encrypted your device during the install will this method work? Does it allow you to take monthly security updates still?

corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.

GialanG said:
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
Click to expand...
Click to collapse
It will bootloop and eventually load. At least that is what it did on the previews. Haven't tested on final release.
You still can not modify/read encrypted data partition, hence OTG or sideloading of zips.
Edit:- Just tested and it eventually loads.

twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.

corkiejp said:
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
Click to expand...
Click to collapse
Cool, thanks ! Is there also a way to decrypt the tablet ?

TheLonelyCyborg said:
Cool, thanks ! Is there also a way to decrypt the tablet ?
Click to expand...
Click to collapse
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.

corkiejp said:
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
Click to expand...
Click to collapse
Thanks @corkiejp it worked like a charm !

Can you please update this guide?
Sent from my Nexus 9 using Tapatalk

Twrp bootloop
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?

lawlor059 said:
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
Click to expand...
Click to collapse
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.

corkiejp said:
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
Click to expand...
Click to collapse
3.0.2-1 works perfectly fine for marshmallow.

dictionary said:
3.0.2-1 works perfectly fine for marshmallow.
Click to expand...
Click to collapse
Thanks @corkiejp. @dictionary I couldn't get into the recovery with 3.0.2.1. Entering the decrypt code would just cause it to loop again. Ignoring the decrypt code I could get into the recovery but with nothing mounted it's useless. It will install successfully but nothing can be done with it.

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.