Develop Bugs

Systemless OTA upgrade

I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.

How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse

Help updating from Marshmallow to Nougat

Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots

The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574

Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.

Order of operations (unlock, kernel, twrp, root, suhide)?

VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?

If I stop after step 5.5 I won't have root, but will have AP working I assume? Is 5.5 necessary if I do the remaining steps?

JU57US said:
VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?
Click to expand...
Click to collapse
3 Make sure it is TWRP RC1
4 No, boot to root is dead after 7.1. Use 2.79 SR3 for all of this. And skip 4 anyway, in unneeded.
5.5 Here is where you flash 2.79 SR3. To be clear, you install it via TWRP.
6 Unneeded with the 2.79 SR3
And I doubt suhide will hide root, my understanding is that it currently does not. But I don follow it very closely.1

My understanding was that suhide works with the libandroid patches, but only with 2.79 stable, and not RC1+
Also, question... if flashing ElementalX isn't it recommended to have root before flashing, or does it not really matter?

JU57US said:
VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?
Click to expand...
Click to collapse
Make sure before you power on you take the SIM card out. Then during the setup SKIP connecting to Wi-Fi. Then once you're through the setup unlock with dePixel8.
Take OTA update
Fastboot boot twrp RC 1 IMG
Install Twrp RC 1 zip from within twrp
Boot phone up then reboot to recovery
Flash SU 2.79 SR 3
Flash kernel if you want
Reboot
Don't use any other versions of twrp or SU. Also make sure your platform tools are completely up to date. Google also just released a separate download of them so grab those and you know for sure you're up to date

JU57US said:
My understanding was that suhide works with the libandroid patches, but only with 2.79 stable, and not RC1+
Also, question... if flashing ElementalX isn't it recommended to have root before flashing, or does it not really matter?
Click to expand...
Click to collapse
I don't believe SUHide works even with the 2 libandroid replacements. That's what I have. I think I'll have better luck with RootSwitch. I'm working to come up with something similar to RootSwitch.

quangtran1 said:
I don't believe SUHide works even with the 2 libandroid replacements. That's what I have. I think I'll have better luck with RootSwitch. I'm working to come up with something similar to RootSwitch.
Click to expand...
Click to collapse
There's a report in @Fenny's thread, here, about the files working on NMF26V stock for suhide.

JU57US said:
There's a report in @Fenny's thread, here, about the files working on NMF26V stock for suhide.
Click to expand...
Click to collapse
I know, I've been following that and one off of that. I use fenny's instructions. However, those conversations gave me some ideas to attack this.

Help With Root

I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?

So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?

jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.

sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?

jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that

sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?

jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet

sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?

jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones

If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.

jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.

It worked, I'm officially rooted .Thanks for the help!

jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.

Question Updating to Android 13 while keeping bootloader unlock/TWRP/root

I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)

jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
Hi Bro.
Your ROG Phone was CN and did you flash the RAW WW firmware?.
Regards!.

jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
I think twrp will not work properly with android 13 because twrp is made for android 12

Dumper UL full upgrade and you will get Boot.img and recovery.img (keep both files at safe place).
Use magisk manager to patch the boot file.
Keep recovery.img (original A13) and TWRP.img safe in ADB root folder (dont mix them up).
1. Update FOTA to Android 13 by copy UL full upgrade into root folder of your phone. If copy from PC/laptop with cable then unplug the cable, your phone will recognize the package, (if you already change COUNTRY CODE and currently use WW 241 rom that will be success update). Otherwise, reboot your device and pop up will appear. Wait the phone is fully reboot and set up everything.
2. Reboot your phone into download mode/fastboot mode (it's better that you should enable USB debug/Developer mode before doing anything). Using CMD command to flash patched boot from Magisk Manager. And reboot, now your phone could gain back root.
3. Check again if the recovery is gone or not. If it's gone, then use termux or any terminal emulator for the "dd command".
You will gain back the TWRP, if any failed, flash back original recovery.img that you have lately in ADB folder on your PC.
PS: backup everything, since going back from Android 13 to Android 12 need to full factory reset.
Br,

ChrisFeiveel84 said:
I think twrp will not work properly with android 13 because twrp is made for android 12
Click to expand...
Click to collapse
I'm on WW-33.0610.2810.81, and TWRP seems to be working OK so far