Database Users

Rooting Moto G4 Plus

I just got my Moto G4 Plus and want to root it. Does somebody have a good guide for rooting it?
I found this guide on youtube, can I just follow this?: https://www.youtube.com/watch?v=g3bhXe3msxU&t=3s

What stock OS are you running on your device, Marshmallow or Nougat?

echo92 said:
What stock OS are you running on your device, Marshmallow or Nougat?
Click to expand...
Click to collapse
I just updated to Android 6.0.1 Marshmallow

If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.

echo92 said:
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
Click to expand...
Click to collapse
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw

skismas said:
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
Click to expand...
Click to collapse
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12

Don't FLASH TWRP, just BOOT it up, do whatever you need to do and... keep your stock bootloader. The TWRP is useful mostly for CM/Lineage ROM's, for stock it's just a headache waiting to happen.

echo92 said:
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Click to expand...
Click to collapse
I managed to root my phone without bricking it! I think......
SuperSU was not on the phone when I rebooted the phone like in the video. I had to download it through play store. But since it says its rooted on root checker, and I could grant it permission, im pretty sure I done it right.
Thanks for the help I really appreciate it

[GUIDE] Root using Magisk, keep stock recovery for OTA

This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.

Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g

kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?

This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.

Ok, but is Xposed etc. possible?

kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

It is really works! Thank you!

gonna check this cause i wanna root the phone but keep enjoying updates

I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial

I bump this because it worked. Quite easy, clean and fast. Thanx!

I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?

masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.

Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?

it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module

Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.

Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??

I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.

Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)

Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse

Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.

September Update is up now

Take a look here: https://developers.google.com/android/images
Download it now!!

Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)

ApoelEllhnwn said:
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
Click to expand...
Click to collapse
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.

wish someone would make the factory images Flashable. All this needing a computer to update is getting old!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I'm sorry I must not have been very clear. My ask was for someone to try the process detailed in the link I provided in my quote above. This is supposed to allow you to uninstall Magisk (don't reboot), take the OTA as you normally would on unrooted phone, and once it installs, apply Magisk to the new slot w/ the OTA installed, then reboot. No computer needed. As I stated above, I would do it, but have yet to get the update thru the Check System Update. I am well aware of how to install it manually, as I have done that process for every update. I just saw that the linked process was updated for Magisk 17.0+ and hoped it could be verified to work. Meaning this would simplify the monthly update process tremendously.

kolothuk said:
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
Click to expand...
Click to collapse
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.

kittygotwet said:
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
Click to expand...
Click to collapse
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.

davidisflash said:
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
Click to expand...
Click to collapse
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.

kittygotwet said:
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
Click to expand...
Click to collapse
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.

davidisflash said:
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
Click to expand...
Click to collapse
I actually figured it out. I had to use the Magisk uninstaller to remove any remaining Magisk, I guess, before I can reinstall. Now I just have another issue on the Pixel 2 9.0. Converting any user app to system app corrupts the phone.

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I will try this guide as soon as the OTA is available.

I got another update today on my Pixel 2, which said: critical bug and performance fixes... I wonder what it is? The phone isn't as smooth after this and some glitches with youtube in landscape, there white nav bar appears, but I can't click 3 dots menu to adjust quality for example. I have to turn the phone in portrait and then do it.

razorsbk said:
I will try this guide as soon as the OTA is available.
Click to expand...
Click to collapse
I'm also still waiting for the Update ...is that normal to wait that long time?

No, it's not. Other manufacturers have released their patches via OTA.
Sent from my Pixel 2 using Tapatalk

So you think we have to sideload the patch?

How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?

Ashyford said:
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Click to expand...
Click to collapse
You can't. Google is no longer releasing OTAs for 8.1. Your best bet is to use a custom kernel such as FlashKernel, as I believe it is backwards compatible, and Nathan streamlines the security patches from both Google and the Linux kernel fork into his kernel.

Did anyone else got the OTA ? I'm still wainting

Steps to install stock 4.5.5.3 rom after deleting recovery in twrp

Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.

Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.

treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?

Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm

treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.

gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.

Ahhh... so it somehow got locked back and need to redo the procedure?

treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?

treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????

updating to latest OTA 11.0.1.1.IN11AA

I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it

dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?

cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?

I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.

Yes, looks like we are in waiting mode for it to show up...

dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.

galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).

dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:

After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr

I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update

Same here global 406 mb ota. It's like not recognizing we have root...

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.

anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA