Any guide on how to install OTA updates after root? Thank you!
The comments after the title of each category i.e. #8 and before 'a' are notes. The main points are a, b, c, etc.Just a nitpick as this is a great guide. For sub points would it help to use something like a,b,c or I, ii, iii for clarity and less confusion? Leave main points as 1,2,3? Thoughts?
Ok!Thanks, but I think you misunderstood me. I meant how #3 in #8 was achieved (3. Install BusyBox to /sbin/supersu/xbin.), but I will give root with SuperSU a new try.
Settings/Security & location/Screen lockSettings/Security & location/Screen lock
Set to "None" or "Swipe"
And as of now, TWRP can't decrypt data, we'll have to wait for an update from Team Win...
I'd like to know the status on this, too. Anybody?Any guide on how to install OTA updates after root? Thank you!
The reason, I think, your phone bootlooped is you did not flash the boot.img or the factory image after you factory wiped the phone. Magisk #9 or # 10 work if you follow the instructions.So, I just got a new Pixel XL and decided to go ahead and update and root. I was already updated to 8.1. So, I unlocked and installed TWRP and Magisk. I decided to factory wipe so I could just set the phone up fresh again, but after the wipe I got into a bootloop, where it kept rebooting into TWRP. I read that somebody else had this problem after installing Magisk.
So, I installed the factory image, which fixed the bootloop problem then re-installed TWRP. This time, I installed SuperSU with the Hide root option. No problems this time. I don't know if Magisk caused the problem, but just in case anybody else has a simliar problem, SuperSU seems more reliable for this purpose.
---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------
I'd like to know the status on this, too. Anybody?
#7 has instructions for sideloading the OTA.zipAny guide on how to install OTA updates after root? Thank you!
The only time I took an OTA was when I first got the phone, before I unlocked or rooted. After I unlocked, I didn't connect to the internet until after I successfully rooted the phone.The reason, I think, your phone bootlooped is you did not flash the boot.img or the factory image after you factory wiped the phone. Magisk #9 or # 10 work if you follow the instructions.
That's probably right. I didn't realize that a factory wipe required the factory image to be installed again.
#7 has instructions for sideloading the OTA.zip
I don't think you can install an OTA on a rooted Pixel or Pixel XL.
SuperSU v2.82 SR5, YesDo SuperSU work with Android 8.1 and TWRP 3.2.1.0?
if you have an verizon pixel XL that has a locked bootloader and is currently on 8.1 you're out of luck getting root or unlocking the bootloader.So, ive been out of the loop for a bit. I have an untoched verizon Pixel XL on 8.1. I just wanted to confirm if this guide will work. Im a little confused seeing as how i thought the OEM Unlocking toggle used to be switched off and unable to be switched on. If anyone could clarify that would be great thanks.![]()
XDA forums for Pixel 2/Pixel 2 XLDo SuperSU work with Android 8.1 and TWRP 3.2.1.0?
What if it is on 8.0? am i still out of luck?if you have an verizon pixel XL that has a locked bootloader and is currently on 8.1 you're out of luck getting root or unlocking the bootloader.
You are out of luck. Absolutely nothing you can do.What if it is on 8.0? am i still out of luck?
the Verizon could unlock bootloader only on 7.1.0 and earlier.What if it is on 8.0? am i still out of luck?
What #step did you follow 'PRECISELY" that caused the "There is an internal problem" error? Maybe, I can help you fix it.So why make it part of the guide when talking about using TWRP 3.2.1????? What to use with TWRP 3.2.1 if SuperSU SR5 is out-dated???
---------- Post added at 11:58 AM ---------- Previous post was at 11:28 AM ----------
"There is an internal problem" error when following this guide PRECISELY. I absolutely loathe how these guides are written... No offense, but it's a huge mess. Please re-write or just delete.
He got that by using Magisk. It patches the dtbo.img which causes that error on reboot. It can be ignored, or 14.6 allows you to not patch dtbo.What #step did you follow 'PRECISELY" that caused the "There is an internal problem" error? Maybe, I can help you fix it.
No offense, but there is another option to re-writing or deleting guides that you "loathe" how they are written. You could stop reading them.