Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
cwburns32 said:
Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
Click to expand...
Click to collapse
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Sent from my Pixel 2 XL using XDA Labs
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
jd1639 said:
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
Click to expand...
Click to collapse
MrMeeseeks said:
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Click to expand...
Click to collapse
Badger50 said:
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
Click to expand...
Click to collapse
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
cwburns32 said:
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
Click to expand...
Click to collapse
Same process, no issues.
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
What he said! :laugh:
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
Badger50 said:
What he said! :laugh:
Click to expand...
Click to collapse
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
cwburns32 said:
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
Click to expand...
Click to collapse
The 3.3 version magisk module working fine for me :good:
Badger50 said:
The 3.3 version magisk module working fine for me :good:
Click to expand...
Click to collapse
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
cwburns32 said:
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
Click to expand...
Click to collapse
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Badger50 said:
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Click to expand...
Click to collapse
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
CyberpodS2 said:
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
Click to expand...
Click to collapse
Yeah, uninstall any other sound mods you have. Then flash the Dolby.zip in twrp, then install ViPER4Android FX version 3.3 magisk module, reboot, then install the AML module. Then you should be good :good:
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
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk
Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!
DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?
DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.
DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?
DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:
I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.
The OTA fixed it for me, thank you so much!
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
thank you! worked great!
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.
spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Is something up with the OP or is it just my XDA app causing it to show like this..
aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update
https://developers.google.com/android/images
https://developers.google.com/android/ota
Has anyone flashed this factory image yet? Does it break TWRP and/or Magisk?
Sent from my Pixel 2 using Tapatalk
I haven't yet, but expect it to break things if you flash it like that. Though if you sideload and update from a factory image it'll do a full wipe unless you edit the flash script.
Tentatively the following process should work:
- Flash factory image after removing wipe flag
- Boot TWRP image
- Flash TWRP zip
- Flash kernel
- Flash Magisk
Everything should work normally at that point.
Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Sent from my Pixel 2 using Tapatalk
Hi, update received.
Diesel_Jeremiah said:
Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Click to expand...
Click to collapse
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.
Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!
guapinoy said:
Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!
Click to expand...
Click to collapse
Magisk and TWRP working correctly?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Magisk and TWRP working correctly?
Click to expand...
Click to collapse
Yup.
Would love to see if this patches the Verizon bootloader unlock.
PuffDaddy_d said:
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.
Click to expand...
Click to collapse
Here is how I updated: [DEC 2017 to JAN 2018 Update] How I updated successfully
So far only one report of receipt via OTA? I had to sideload Dec, really hoping to just get these OTA going forward.
I've found that using old ADB tools will not flash the factory image properly. I was using a tool that an XDA member provided that had adb binaries from 2015 and kept getting errors when trying to use the flash-all.bat from the factory image. If you guys get stuck with something, update your adb and fastboot tools from the latest platform tools. It will save you a headache. If you want step by step instructions of what I did, I can provide them.
Hmm, I'm failing SafetyNet now.
Lightn1ng said:
Hmm, I'm failing SafetyNet now.
Click to expand...
Click to collapse
Did you follow Diesel's method or was this after you soft bricked your phone?
PuffDaddy_d said:
Did you follow Diesel's method or was this after you soft bricked your phone?
Click to expand...
Click to collapse
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data
Lightn1ng said:
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data
Click to expand...
Click to collapse
Formatting data decrypts it, that may or may not be why it's failing.
Telperion said:
Formatting data decrypts it, that may or may not be why it's failing.
Click to expand...
Click to collapse
Ooohhhhhh. How do I get it back to encrypted?
Lightn1ng said:
Ooohhhhhh. How do I get it back to encrypted?
Click to expand...
Click to collapse
Same as before, but don't format your data partition.
no OTA for me yet. I heard sideloading results in lag but who knows.
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
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