Database Info

Moto Z "hacking" experiences...

EDIT: this is for Marshmallow only. For Nougat some adjustments are required and this way *does not work*!
It's only some days that I have finally my Moto Z on hands and have to say it's really a great piece of hardware for... geeks!
At first it seems nothing particular because of its really-close-to stock Android (it isn't for unexperienced users in my opinion... they haven't added neither a reboot option to Vanilla Android! :cyclops, but more I use it, more I go with modifications, more I like it: it's really well developed to be modified and customized and in this is great!
It's very hard to brick in my opinion, I really love the simple (to access...) and well working system for fastboot/recovery/bootloader etc... and in this it is even better than I expected...
Now I want to share some of my experiences of these days to (eventually) help new users...
My idea was to unlock it installing recovery, root, Xposed support, etc. leaving firmware as stock as possible (for now... ) and in the most "systemless" mode possible... Let's start!
First step was to unlock bootloader. No particular issues here (but Motorola web site that was down for a while when I need it for unlock code...! ). Only thing to note, command adb reboot fastboot often reboot to system instead. No problem, since access to fastboot by keys is very simple on Z.
Unlocking bootloader made a factory reset too, but this is common...
Flash TWRP: no problem at all. Only thing, if you are going to make the first backup without letting TWRP patching your system partition to have a full stock backup, prepare to flash it twice, since if you don't find the required setting after, at first system boot, the stock recovery will be rewritten (a common behaviour anyway...). This TWRP (3.0.2.0) is complete and well working in my opinion. Nothing to be surprised, since it's an official version...
Second step has been to disable encryption. Encryption introduces a bit "slowerness" that I didn't want and could be an issue in case of problems to be resolved... more, I don't need it.
Stock kernel doesn't permit to disable it and phone arrives already encrypted (all data and internal storage too).
So I flashed in TWRP the patch to disable forced encryption that you could find here in another thread and it works fine.
Please note that to decrypt phone you have to not only wipe data, BUT to format it, deleting ALL the contents of internal storage too. So... save them before!
Wanting (if possible...) a systemless modified system (ehm....), next step was to flash Magisk v.9 in TWRP and install Magisk Manager apk. All fine, no problem at all.
Then I tried to root using phh's SuperUser as hinted as best method to use with Magisk. I tried flashing both v.266 & v.266-2 (latest...), no errors during flashing, BUT no one has been able to get root...
So I went with SuperSU v.2.78 (not a particular one... the stock one! ) and it flashed with no issues and obtained root in perfect way (I'm not sure if in system or systemless way...)
Xposed: I installed "Material version installer" apk, since it's able to install both system and systemless versions of Xposed.
I tried both the available systemless versions (v.86), that this apk download and make them installed by TWRP automatically, but none apparently work. So I uninstalled them and I went with stock (system) one, that installs and works fine at first attempt. Modules as GravityBox works perfectly as expected.
I hope these experienced could be usefull for others. I'm here for eventual opinions/suggestions/Q&A... :fingers-crossed:
EDIT: please note that "unencrypt" and "Magisk" steps *are mandatory* to have SuperSU installed with no issues. At 99% in systemless mode.
EDIT: root this way is obtained in system mode.

almost identical to what i did
tried the prerooted rom but got some chinese headers so decided to drop it.
went back to stock and rooted and exposed it the same u did.
added the turbo z kernel though which gave me better battery life.

reiteravi said:
almost identical to what i did
tried the prerooted rom but got some chinese headers so decided to drop it.
went back to stock and rooted and exposed it the same u did.
added the turbo z kernel though which gave me better battery life.
Click to expand...
Click to collapse
This will be my next step I think... I want to test it a bit with stock kernel to have a starting point to compare with...

@mods: Probably this should be put as sticky, since of the lot of requests about root issues...

Can you share the link to disable encryption patch file.. the link in the other thread isn't working.

Manish54 said:
Can you share the link to disable encryption patch file.. the link in the other thread isn't working.
Click to expand...
Click to collapse
Here you are...

enetec said:
Here you are...
Click to expand...
Click to collapse
Thanks

Just to be clear... I've not tested first hand yet (I'm happily sticky with MM for now...), BUT it's my opinion that all above should work fine on Nougat too...

Updated OP to clarify that root has been obtained in system mode this way... (su located in /system/xbin...)

superuser doesn't work
enetec said:
It's only some days that I have finally my Moto Z on hands and have to say it's really a great piece of hardware for... geeks!
At first it seems nothing particular because of its really-close-to stock Android (it isn't for unexperienced users in my opinion... they haven't added neither a reboot option to Vanilla Android! :cyclops, but more I use it, more I go with modifications, more I like it: it's really well developed to be modified and customized and in this is great!
It's very hard to brick in my opinion, I really love the simple (to access...) and well working system for fastboot/recovery/bootloader etc... and in this it is even better than I expected...
Now I want to share some of my experiences of these days to (eventually) help new users...
My idea was to unlock it installing recovery, root, Xposed support, etc. leaving firmware as stock as possible (for now... ) and in the most "systemless" mode possible... Let's start!
First step was to unlock bootloader. No particular issues here (but Motorola web site that was down for a while when I need it for unlock code...! ). Only thing to note, command adb reboot fastboot often reboot to system instead. No problem, since access to fastboot by keys is very simple on Z.
Unlocking bootloader made a factory reset too, but this is common...
Flash TWRP: no problem at all. Only thing, if you are going to make the first backup without letting TWRP patching your system partition to have a full stock backup, prepare to flash it twice, since if you don't find the required setting after, at first system boot, the stock recovery will be rewritten (a common behaviour anyway...). This TWRP (3.0.2.0) is complete and well working in my opinion. Nothing to be surprised, since it's an official version...
Second step has been to disable encryption. Encryption introduces a bit "slowerness" that I didn't want and could be an issue in case of problems to be resolved... more, I don't need it.
Stock kernel doesn't permit to disable it and phone arrives already encrypted (all data and internal storage too).
So I flashed in TWRP the patch to disable forced encryption that you could find here in another thread and it works fine.
Please note that to decrypt phone you have to not only wipe data, BUT to format it, deleting ALL the contents of internal storage too. So... save them before!
Wanting (if possible...) a systemless modified system (ehm....), next step was to flash Magisk v.9 in TWRP and install Magisk Manager apk. All fine, no problem at all.
Then I tried to root using phh's SuperUser as hinted as best method to use with Magisk. I tried flashing both v.266 & v.266-2 (latest...), no errors during flashing, BUT no one has been able to get root...
So I went with SuperSU v.2.78 (not a particular one... the stock one! ) and it flashed with no issues and obtained root in perfect way (I'm not sure if in system or systemless way...)
Xposed: I installed "Material version installer" apk, since it's able to install both system and systemless versions of Xposed.
I tried both the available systemless versions (v.86), that this apk download and make them installed by TWRP automatically, but none apparently work. So I uninstalled them and I went with stock (system) one, that installs and works fine at first attempt. Modules as GravityBox works perfectly as expected.
I hope these experienced could be usefull for others. I'm here for eventual opinions/suggestions/Q&A... :fingers-crossed:
EDIT: please note that "unencrypt" and "Magisk" steps *are mandatory* to have SuperSU installed with no issues. At 99% in systemless mode.
EDIT: root this way is obtained in system mode.
Click to expand...
Click to collapse
thanks for sharing.
for me superuser doesn't work; the phone doen't boot.

[email protected] said:
thanks for sharing.
for me superuser doesn't work; the phone doen't boot.
Click to expand...
Click to collapse
There could be only some reasons:
- you are ready on Nougat (this is tested with MM)
or
- you have missed one of the mandatory steps (read Magisk installation...)
or
- you haven't used the right SuperSU version. v. 2.78 SuperSU-v2.78-201609011115.zip is the tested one.
Please doublecheck.

enetec said:
There could be only some reasons:
- you are ready on Nougat (this is tested with MM)
or
- you have missed one of the mandatory steps (read Magisk installation...)
or
- you haven't used the right SuperSU version. v. 2.78 SuperSU-v2.78-201609011115.zip is the tested one.
Please doublecheck.
Click to expand...
Click to collapse
i'm on Nougat already.

[email protected] said:
i'm on Nougat already.
Click to expand...
Click to collapse
In this case, try to install phh's SuperUser v.259 instead of SuperSU v.2.78 and then install phh's SuperUser manager from Play Store.
I've not tested first hand but many are reporting this should work (and, it seems, not newer version too... only v.259 )
Please remember that this is going to patch your boot.img instead of system.img, so have a complete backup just in case... :fingers-crossed:

Here's a link to the Phh superuser r259 https://superuser.phh.me
Worked fine for me on Nougat :good:

enetec said:
In this case, try to install phh's SuperUser v.259 instead of SuperSU v.2.78 and then install phh's SuperUser manager from Play Store.
I've not tested first hand but many are reporting this should work (and, it seems, not newer version too... only v.259 )
Please remember that this is going to patch your boot.img instead of system.img, so have a complete backup just in case... :fingers-crossed:
Click to expand...
Click to collapse
My MOTOZ rooted now! thanks!
---------- Post added at 15:37 ---------- Previous post was at 15:36 ----------
supacrazyguy42 said:
Here's a link to the Phh superuser r259 https://superuser.phh.me
Worked fine for me on Nougat :good:
Click to expand...
Click to collapse
My MOTOZ rooted now! thanks!
i'm trying to install xposed

[email protected] said:
My MOTOZ rooted now! thanks!
---------- Post added at 15:37 ---------- Previous post was at 15:36 ----------
My MOTOZ rooted now! thanks!
i'm trying to install xposed
Click to expand...
Click to collapse
Great! There's no Xposed ready for Nougat just yet though.

Is there a method for locked bootloader?

Hey there!
I've unlocked my bootloader but couldn't find the way to install the TWRP.
How can I do that? :laugh:
Ah, I'm on 7.0 already!

mrlipz said:
Hey there!
I've unlocked my bootloader but couldn't find the way to install the TWRP.
How can I do that? :laugh:
Ah, I'm on 7.0 already!
Click to expand...
Click to collapse
You can flash it with fastboot.
fastboot flash recovery XXXXX.img
After flash, not reboot your phone first reboot to recovery

MyDarkThrone said:
You can flash it with fastboot.
fastboot flash recovery XXXXX.img
After flash, not reboot your phone first reboot to recovery
Click to expand...
Click to collapse
...*and* enable write modifications in /system.
Otherwise at first system boot TWRP will be overwritten by stock recovery again...

How to Root J7 Prime (G610F) on Nougat?!

Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.

vishnurmcf said:
Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.
Click to expand...
Click to collapse
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.

anubhab723 said:
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.
Click to expand...
Click to collapse
man i need a working root i... tried by twrp by install the root latest version so now i am flashing a stock firmware hhhhhh ....will magist work 100 percent ?? i need the full confidence answer thanks a lot

lI also just updated, I tried using CF Auto Root but that didn't work and made my phone bricked (verification failed). Will Magisk work certainly because I don't want to have to reset again.

Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app

fast69mopar said:
Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Click to expand...
Click to collapse
Will try that. Thanks!

wsty said:
Will try that. Thanks!
Click to expand...
Click to collapse
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask

fast69mopar said:
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask
Click to expand...
Click to collapse
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?

wsty said:
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?
Click to expand...
Click to collapse
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Before you flash any root zip in TWRP, make a backup of your stock boot image. That was ifsomething goes wrong you can revert back and try again with a different version if Magisk.
Make sure you read the info that @topjonwu has made available for us for Magisk. The link below is full of information pertaining to Magisk.
There is one other thing that I forgot to put here. Magisk is a pretty universal root solution that patches the boot image just like Chainfire's SuperSU. There is not a device specific Magisk zip so you can flash any version if Magisk to attempt to gain root access in your device. Like I said before, I would start with flashing V12.0 and start from there. If V12.0 works and you have root, boot to TWRP and make a backup of your boot image to save it. That was if you flash, for instance, V13.0 and it doesn't work or fails to flash then you can boot back to recovery and restore your boot image and have working root.

fast69mopar said:
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks!

wsty said:
Thanks!
Click to expand...
Click to collapse
No problem

Any working Twrp for this?

Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...

denizbay said:
Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...
Click to expand...
Click to collapse
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app

Looking this: https://forum.xda-developers.com/ga...ared-root-file-j7-prime-g610f-nougat-t3678253

inamie said:
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app

inamie said:
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
What Magisk version, Version 14 tripped the verification error on my 610M

Try Magisk v14.0
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-sys

FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.

vishnurmcf said:
FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.
Click to expand...
Click to collapse
Looking forward to your instructions. Please release soon! Thank you!

Flashed Supersu but still not rooted. On 8.0

I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3

champstar said:
I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3
Click to expand...
Click to collapse
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs

Sgace said:
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
That is exactly what I did. Still root did not work. Should I try a different supersu zip?

champstar said:
That is exactly what I did. Still root did not work. Should I try a different supersu zip?
Click to expand...
Click to collapse
Supersu zip mentioned should be the latest and working.
Maybe ask in that thread.
Sent from my Google Pixel using XDA Labs

Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.

champstar said:
Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.
Click to expand...
Click to collapse
What messages does it say in twrp, as you flash SuperSU? ... if you've already flashed SuperSU, the script could be restoring the backup boot.IMG, which could be your problem...
When I bump into that, personally; I just download the factory image, then edit the flash-all.sh script and remove the -w flag (which tells the script to not wipe the device), I save the script then execute it...
It flashes the image and I end up with an unaltered boot.IMG and system, then I flash SuperSU after....
I'm on the Sept 5 image using SuperSU sr3 ... SuperSU works like a charm.

After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.

THANKS!
champstar said:
After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.
Click to expand...
Click to collapse
Im an htc u11+ user, the device is largely underrated thus very few resources available.
However, i was having the exact same issues you were, flashing your supersu zip worked for me after various frustrating attempts using other versions of superSU
Thanks a lot

[OOS 5.1.11] Pre-Rooted Bootimage

Hi there,
OnePlus is rolling out the OxygenOS 5.1.11 update! According to this thread, I made a pre-rooted bootimage for you to flash
I used the guide on the mentioned thread and used Magisk Manager 5.8.3 (129) with Magisk 16.7
For those who'd rather like to do it on their own, I'll also attach the original bootimage of OOS 5.1.11.
Downloads:
- patched bootimage [MD5: 5EC7C328AEE0D38B43A2727BCD767378]
- original bootimage (5.1.11) [MD5: B6790A9D38F41E0EBC6830D1076FAFF0]
Video instructions:
The awesome @GizmoFreak made a nice step-by-step video for you! :good:
Special thanks for his guide at @b1czu, [MENTION=4470081 ]TopJohnWu[/MENTION] and @GizmoFreak! Please also give him a "thanks" :good:
UPDATE: Magisk 17.1 was released by @topjohnwu ! Many fixes and most important: "Install to inactive Slot (After OTA)" is back! Upgrading our ROM should now be much easier again since already rooted users don't need to use the whole fastboot thing again. However, for new 'unrooted' users, I'll still provide here the always latest patched bootimages.
Cheers,
T.Bear

thanks do we still need to do the direct install from magisk manager?

czerdrill said:
thanks do we still need to do the direct install from magisk manager?
Click to expand...
Click to collapse
Yes, if you whish to keep root. Otherwise your device would take the stock bootimage for the next boot again. This patched one is only for booting with 'temp' root privileges so that you can use magisk Manager to direct install the root stuff to the original bootimage.

does this pass the safety checks?

It's the same procedure as in the thread I mentioned! This is not a standalone 'project', just the missing bootimage for the latest OxygenOS update.
But to answer your question, yes if you follow the instructions on the mentioned thread it passes all checks.
Only if you install things like Xposed framework it won't pass.

RiTCHiE007 said:
does this pass the safety checks?
Click to expand...
Click to collapse
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
fastboot boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
EDIT 1: Added 3rd command which I used but forgot to mention it here ?. Thanks GizmoFreak !

amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
SafetyNet will show the response is invalid because Google recently updated the SafetyNet API. Now developers need to use an API key to access SafetyNet. We need to wait for Magisk to be updated.
---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------
amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
And the second command should be fastboot boot boot.img

Plz make for H2OS OB 1

Thanks

Do I need to install 5.1.11 first?

williamcll said:
Do I need to install 5.1.11 first?
Click to expand...
Click to collapse
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Created a video. I hope it will make things easy for others.

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Will I lose my data in the process?

no, all are retained

GizmoFreak said:
Created a video. I hope it will make things easy for others.
Click to expand...
Click to collapse
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Click to expand...
Click to collapse
Yes feel free to add it to OP.

ed-gonzo said:
no, all are retained
Click to expand...
Click to collapse
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)

Brother, your download link is not working?

williamcll said:
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)
Click to expand...
Click to collapse
Magisk 16.7 is up to date

What's the benefit of keeping stock recovery and not rooting via twrp?

Relock unroot pixel 2

So I unlocked my bootloader and rooted my pixel 2 successfully.
Now I get security warning on boot and can't run my mobile banking apps and a few other apps that tell me I can't use because I am unlocked rooted.. is any workaround for this?
Can I relock it and unroot somehow or is there I way to get these apps working with an unlocked rooted pixel 2 device. Thanks in advance

Would.like to keep it unlocked rooted an run these apps if at all possible but if. It possible I might have to fix this any assistance is appreciated

Hi! You could use magisk hide function, this is magisk inbuilt function for hidding root for selected apps.
And use safetynet fix too.
With this two things you should be able to use your apps.
Good luck

somin.n said:
Hi! You could use magisk hide function, this is magisk inbuilt function for hidding root for selected apps.
And use safetynet fix too.
With this two things you should be able to use your apps.
Good luck
Click to expand...
Click to collapse
Thanks I'll try those and get back with my results

somin.n said:
Hi! You could use magisk hide function, this is magisk inbuilt function for hidding root for selected apps.
And use safetynet fix too.
With this two things you should be able to use your apps.
Good luck
Click to expand...
Click to collapse
Boom dome and working now much appreciated buddy thanks again.. the hide magical worked

Yep, it should. Using safetynet fix is hightly recomanded too If you are using gpay and in future for some others google apps...

tice60 said:
Boom dome and working now much appreciated buddy thanks again.. the hide magical worked
Click to expand...
Click to collapse
Magisk
somin.n said:
Yep, it should. Using safetynet fix is hightly recomanded too If you are using gpay and in future for some others google apps...
Click to expand...
Click to collapse
Ya Google pay forgot about that one thanks have an issue though with when entering recovery twrp .. half the time asks for PW and can't get in .using any my set passwords.. other times.. I get errors flashing zips..when I remove PW and get into my twrp .. zip files just give me errors when I try and flash them.. something to do with partition issues or encryption on this device?

somin.n said:
Hi! You could use magisk hide function, this is magisk inbuilt function for hidding root for selected apps.
And use safetynet fix too.
With this two things you should be able to use your apps.
Good luck
Click to expand...
Click to collapse
hey need help please when able.no zips are flashing for me from twrp...
but i am in unlocked bootloader and newest twrp working. did factory reset, wipe etc.
Roms and zips are all is giving me Error installing zip file, Updating partition details
Failed to mount /system ( invalid arguement)
Failed to mount /vendor ( invalid arguement)
will not install , i likely have missed something obvious
please help thanks
i am unlocked booterloader

Only way how to access with TWRP is disable all password protection (disable device encryption)... However, most of todays zips are magisk modules, it means that you have to "flash" it with magisk app.

somin.n said:
Only way how to access with TWRP is disable all password protection (disable device encryption)... However, most of todays zips are magisk modules, it means that you have to "flash" it with magisk app.
Click to expand...
Click to collapse
Don't mean to be a pain and I have researched alot with no success. Yes I can get into twrp decrypted but cant flash anything in twrp. Various errors
Could you kindly refresh me on how to flash a zip out of twrp using magisk.. or even fastboot , ADB
.and also a ROM zip? I can't even wipe pre flashing a ROM zip..
I can't even wipe data cache etc ..twrp gives me errors on that too... I hope I am not asking to much I understand twrp on this device is finicky..

When your able thanks again.
I miss my 2010 HTC was so much easier that this googgleessss to do this stuff hahah..but what can I do lol

somin.n said:
Only way how to access with TWRP is disable all password protection (disable device encryption)... However, most of todays zips are magisk modules, it means that you have to "flash" it with magisk app.
Click to expand...
Click to collapse
I mean I know how to flash zips with magisk but will it flash a ROM fine and how do I wipe data cache etc before flashing a ROM via this method and out of twrp? A bit paranoid only have one phone don't wanna brick it haha have a good day

Sorry, only idea is, if you are using latest TWRP, and maybe, I am not sure, but I think, that TWRP is not supported on Android 11 ROMs... Sorry, I can't help with this, I didn't use TWRP for ages... I am really happy with stock pixel ROM and didn't own P2 anymore...