Ok thanks, is this the recommended one or any custom kernel will do just fine?
Would I still get future ota update or do I just sideload ota zips?
[Tut][Jan-update]Fix DTBO message "There's an internal problem with your device"
- Thread starter Shadow/Walker
- Start date
Would I still get future ota update or do I just sideload ota zips?
It's the most popular one for sure. When your rooted with custom recovery, you won't be able to install OTA's. If you've unlocked your bootloader, with BOTH unlocking commands, you'd be far better off just fastbooting the monthly security updates. Seen too many problems with side loading as of late.
How exactly to fastboot monthly security updates?
I've only done sideloading ota before this
Is it similar to this steps?
https://forum.xda-developers.com/showpost.php?p=74751590&postcount=6
Here's a great guide, written by the same guy that made the kernel I recommended. If you have a windows machine, up to date SDK, a little patience to learn, it's really easy to do ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Thanks, I take it I need to follow the steps for
Updating to a new release (factory image)
So basically just skip sideloading ota?
Yes. Sounds like you already have a good working knowledge of SDK/adb/fastboot, so you should be fine. You will need to have already ran BOTH bootloader unlocking commands. You'll need to extract the factory image with 7zip or Winzip, or a similar program. Once that's done, you simply place all the extracted files into the SDK platform- tools folder, and follow the guides instructions. There's even a way to do it that doesn't wipe your data :good:
Thanks, if I needed to sent it back for RMA
What's the proper sequence of restoring back to stock?
1) Fastboot stock firmware
2) Lock the bootloader
or vice versa?
Just fastboot back to stock. Forget about the bootloader. Unlocking the bootloader does not void your warranty. But if you want to, then do it last :good:
I just found out you don't have to remove lock screen security if you use adb sideload in TWRP.
So it'll be
adb reboot bootloader
fastboot boot [path to twrp 3.2.1.0 img]
When it asks for pattern or pic tap on CANCEL
Then tap on Keep Read Only
Advanced - ADB SIDELOAD then swipe to adb sideload
then in your command prompt or terminal
adb sideload [path to kernel zip]
in twrp tap back (or reboot to be safe [i do not install twrp app when it suggests it] and redo temp boot into twrp, advanced, adb sideload)
adb sideload [path to magisk]
reboot.
Yep, that works great, as long as your near your pc ?
Not to mention the many more steps than: change to none, do your business, change to pin or pattern and add fingerprint. Like an extra minute of time. Lol To each their own.
Looks like the latest update doesn't mess with DTBO. After the update I flashed DTBO into slots a and b and haven't been notified of it reverting.
Not to necropost, but it appears Magisk is again attempting to patch dtbo.img. Happened on the latest beta tonight, and even upon rolling back to latest stable.
I can confirm that. Magisk's stable channel, latest manager etc., while reinstalling Magisk due to July's security update [read: factory image reflashing] dtbo.img was patched and resulted in "internal problem" alert after every restart
replying again, because the solution has been found
I mean - it was always there, I just didn't read that [in the original Magisk thread].so, the steps are:
1. using Magisk Manager, uninstall Magisk by choosing "restore images".
2. restart your phone
3. open Magisk Manager, do not install Magisk - first check two options to "Preserve AVB 2.0/dm-verify" and "force encryption" [well, this isn't mentioned, but it seemed like is needed on my Pixel]
4. install Magisk as usually [patched boot etc.]
5. profit
Thanks for the steps! I actually ended up rolling back because the latest magisk screwed my go-tcha for pokemon go and kept disconnecting my bluetooth from my kia soul.replying again, because the solution has been found
so, the steps are:
1. using Magisk Manager, uninstall Magisk by choosing "restore images".
2. restart your phone
3. open Magisk Manager, do not install Magisk - first check two options to "Preserve AVB 2.0/dm-verify" and "force encryption" [well, this isn't mentioned, but it seemed like is needed on my Pixel]
4. install Magisk as usually [patched boot etc.]
5. profit
Thanks!!!replying again, because the solution has been found
so, the steps are:
1. using Magisk Manager, uninstall Magisk by choosing "restore images".
2. restart your phone
3. open Magisk Manager, do not install Magisk - first check two options to "Preserve AVB 2.0/dm-verify" and "force encryption" [well, this isn't mentioned, but it seemed like is needed on my Pixel]
4. install Magisk as usually [patched boot etc.]
5. profit
Thanks for the description. It can be done even quicker as I tested on my Oneplus 6 (without step 2):replying again, because the solution has been found
so, the steps are:
1. using Magisk Manager, uninstall Magisk by choosing "restore images".
2. restart your phone
3. open Magisk Manager, do not install Magisk - first check two options to "Preserve AVB 2.0/dm-verify" and "force encryption" [well, this isn't mentioned, but it seemed like is needed on my Pixel]
4. install Magisk as usually [patched boot etc.]
5. profit
1. using Magisk Manager, uninstall Magisk by choosing "restore images".
2. check two options to "Preserve AVB 2.0/dm-verify" and "force encryption"
3. install Magisk as usually
sure it is possible to bypass this step - altought my Pixel didn't liked this way & I had to restart inbetween changes
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone