Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
README:
Code:
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
Disable Verity
Oreo
Flash this kernel (only compatible with latest oreo build, OPNS27.76-12-22-9) through fastboot (fastboot flash boot boot-noverity.img) or TWRP (Install -> Install image -> Select Boot -> Swipe to install)
Verity is now disabled, you can flash Magisk or anything else
Marshmallow/Nougat
If you aren't going to root your device, you can use my patcher (that disables forced encryption as well) else Magisk/SuperSU will do this for you.
In order to definitely get rid of encryption, if you wish to, you'll have to erase userdata with fastboot
Download
https://twrp.me/motorola/motorolamotozplay2016.html
AndroidFileHost (old/unofficial builds)
Credits
@squid2 for Moto msm8916 TWRP tree which I used as base and help in building binaries for my patcher
@vache for SDCard fix
arter97 for finding F2FS bug and fix that didn't allow TWRP flashing SuperSU
gladiac and Chainfire for some ideas from FED-Patcher and SuperSU
XDA:DevDB Information
TWRP for Moto Z Play, Tool/Utility for the Moto Z Play
Contributors
Alberto97
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-11-07
Last Updated 2018-12-23
Seems to work just as decribed. Thank you so much!
EDIT: SuperSU SR3 seems to have trouble with the extracting the ramdisk...
I will finally be able to get rid of that shady Chinese TWRP.
Really_Rekt said:
Seems to work just as decribed. Thank you so much!
EDIT: SuperSU SR3 seems to have trouble with the extracting the ramdisk...
Click to expand...
Click to collapse
After flashing SU i ended beeing stuck in boot.
But installing and using the Recovery worked without problems.
Pretty much what's going on here as well
I am having trouble getting the phone to start again.
Installing the stock firmware results in an error:
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '%path_to_zip'. "
Possibly a corrupt download? Looks like the updater-binary file didn't get to your hard drive in one piece...
Does it work root from the recovery itself without needing to flash the .zip?
in the chinese twrp this method works without problem
Yeah, I tried this one, seems to work just fine until you try and flash SuperSU with it. For the official releases it fails to extract ramdisk and the system-mode ones it doesn't patch dm-verity. I ended up using the Chinese one to get a rooted addison.
Really_Rekt said:
Yeah, I tried this one, seems to work just fine until you try and flash SuperSU with it. For the official releases it fails to extract ramdisk and the system-mode ones it doesn't patch dm-verity. I ended up using the Chinese one to get a rooted addison.
Click to expand...
Click to collapse
Phh superuser works with our device. Flashed that instead of using TWRP auto root.
DroneDoom said:
Phh superuser works with our device. Flashed that instead of using TWRP auto root.
Click to expand...
Click to collapse
Would you mind sharing a URL to the PHH SU you used? I'll give that one a try. Did you flash it in inside TWRP?
skalogre said:
Would you mind sharing a URL to the PHH SU you used? I'll give that one a try. Did you flash it in inside TWRP?
Click to expand...
Click to collapse
I flashed it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/details?id=me.phh.superuser
DroneDoom said:
I flashed it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/details?id=me.phh.superuser
Click to expand...
Click to collapse
YES YES YES!
Thank you! That one worked perfectly. I now have root access.
DroneDoom said:
I flashed it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/details?id=me.phh.superuser
Click to expand...
Click to collapse
wondering if this version is systemless root?
thanks
If it's the same one that you flash with magisk (which it should be???) then yes. Any ideas as to what's up with SuperSU then?
EDIT: whoops. See below
ilovemeow said:
wondering if this version is systemless root?
thanks
Click to expand...
Click to collapse
I think this is system root, I believe the phh superuser on the magisk thread hosts the systemless version.
What advantages does this recovery have in comparison to the original Chinese?
Thanks for this!
diegochiva95 said:
What advantages does this recovery have in comparison to the original Chinese?
Click to expand...
Click to collapse
From what he says in the first post this is the same thing just in English.
where is chinese recovery ...???
can anyone provide a link to Chinese TWRP recovery .... I want to flash it as this version/edition of TWRP recovery does not allow to flash supersu ( though phhs usperuser works fine but I'm not able to install Busybox and adaway with superuser )
Thanks
Can we root the device without unlocking bootloader and without flashing twrp?
Στάλθηκε από το moto z play μου
Related
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82), XT1643 (Adarsh balu), XT1644 (WTF?), XT1641 (EkisDeMX).
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Works perfect on Moto g4 (XT1622) :good:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Dex5er said:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Click to expand...
Click to collapse
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
tywinlannister7 said:
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Click to expand...
Click to collapse
Didn't find any thread which describes the method rooting with SuperSU in the first post and as its topic.
In some threads (with other topics like how to root with phh's SuperUser) there is in the discussion mentioned this method with SuperSU but nobody will ever find these posts...
disguisedview said:
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
Click to expand...
Click to collapse
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Dex5er said:
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Click to expand...
Click to collapse
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
disguisedview said:
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
Click to expand...
Click to collapse
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Dex5er said:
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Click to expand...
Click to collapse
I don't know. If you have backup of your partitions then flash your original system and boot partition and start from beginning (ElementalX and then SuperSU 2.79 SR3).
If you don't have backups then download (here on xda or somewhere else) stock firmware and flash system und boot partition.
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Is it really not working? Or it just doesn't show the popup "TurboPower connected"?
does it work on XT1643 Indian variant ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Turbo Power worked fine in my device when using the Ressuruction Rom. Probably restarting the device would solve the issue.
I checked the power input using ampere..its working fine..thnks every1
disguisedview said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82).
Click to expand...
Click to collapse
Does it work with XT1643 Indian variant ? Please do let me know .
arpith.pr said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Nobody confirmed it yet in this thread.
I could it only test with 1642.
But normally i would say it should also work on 1643 variant.
arpith.pr said:
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Yes it does work. It is the only way to root stock N on any of the models.
tywinlannister7 said:
Yes it does work. It is the only way to root stock N on any of the models.
Click to expand...
Click to collapse
Thanks
Working on XT1643....
Im making a video on how to do this to make it easier .... For others like me to understand
I can just Reboot to custom recovery, root and then still use my stock recovery?
Hi @ante0
How can i root Oreo ?
I need recovery and root files,also boot image if needed or what ever u think i need to have to root my phone.
can u upload and give me the links too please ?
thank you
ezraiil1 said:
Hi @ante0
How can i root Oreo ?
I need recovery and root files,also boot image if needed or what ever u think i need to have to root my phone.
can u upload and give me the links too please ?
thank you
Click to expand...
Click to collapse
You can use this recovery, when you're on Oreo: https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Then this SuperSU: https://androidfilehost.com/?fid=962021903579485056
There's no Magisk yet.
ante0 said:
You can use this recovery, when you're on Oreo: https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Then this SuperSU: https://androidfilehost.com/?fid=962021903579485056
There's no Magisk yet.
Click to expand...
Click to collapse
thanks,
how can i decrypt data ??
i tried to format data and install "update_all_hw" and "update_data_public" zip files but TWRP Kept restarting...
then i had to reinstall Oreo using this.(btw phone stayed unlocked)
Any solutions ?
ezraiil1 said:
thanks,
how can i decrypt data ??
i tried to format data and install "update_all_hw" and "update_data_public" zip files but TWRP Kept restarting...
then i had to reinstall Oreo using this.(btw phone stayed unlocked)
Any solutions ?
Click to expand...
Click to collapse
I've yet to try decrypting oreo, but you should be able to modify the updater-script in both public and HW zips, and remove the command mountcrypt and the last that should normally install update.app.
So unzip, edit, zip. It should work if it's just the Huawei commands that are making it reboot.
ante0 said:
I've yet to try decrypting oreo, but you should be able to modify the updater-script in both public and HW zips, and remove the command mountcrypt and the last that should normally install update.app.
So unzip, edit, zip. It should work if it's just the Huawei commands that are making it reboot.
Click to expand...
Click to collapse
Hi again @ante0
i just installed oreo again,tried to decrypt data:
1.flashed oreo
2.boot,factory reset with erasing data.
3.unlock BL
4.flashed TWRP
5.format data
6.reboot recovery,data was decrypted.
7.install SuperSu with the file u gave me in this thread.
8.flashed modified public and hw,( i had to remove verify files(verify script and verify script_data) which they contain mountencrypt ("data") command. ).(Hw ended up with error 9 but everything seems to be okay)
9.reboot
but when i boot in TWRP between first boot loop after installing SuperSu,data was encrypted.
any idea how can i decrypt data ?
ezraiil1 said:
thanks,
how can i decrypt data ??
i tried to format data and install "update_all_hw" and "update_data_public" zip files but TWRP Kept restarting...
then i had to reinstall Oreo using this.(btw phone stayed unlocked)
Any solutions ?
Click to expand...
Click to collapse
Not possible with twrp
erase require [must with fastboot only]
Code:
fastboot format userdata
XN Logos said:
Not possible with twrp
erase require [must with fastboot only]
Code:
fastboot format userdata
Click to expand...
Click to collapse
It should be possible. I don't think SuperSU changes/removes everything it needs to though, as we now seem to have 3 different fstab rather than 1. It should be possible to modify the AVB script to remove fileencryptioninline.
ante0 said:
You can use this recovery, when you're on Oreo: https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Then this SuperSU: https://androidfilehost.com/?fid=962021903579485056
There's no Magisk yet.
Click to expand...
Click to collapse
Can we use OpenGaaps with Oreo?
ante0 said:
You can use this recovery, when you're on Oreo: https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Then this SuperSU: https://androidfilehost.com/?fid=962021903579485056
There's no Magisk yet.
Click to expand...
Click to collapse
I have unlocked bootloader, installed RR rom for oreo. Flashed the above super su file but I got error. System only have partially root. Any idea?
drift08 said:
I have unlocked bootloader, installed RR rom for oreo. Flashed the above super su file but I got error. System only have partially root. Any idea?
Click to expand...
Click to collapse
Much has changed since I posted that
Use this TWRP: https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ (flash to recovery_ramdisk)
With official Magisk v16 : http://tiny.cc/latestmagisk
I don't think SuperSU will get more updates tbh, and I haven't tested it lately. I do know that Magisk works on AOSP
Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img
RootingPro-18 said:
Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img
Click to expand...
Click to collapse
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU
SkaboXD said:
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU
Click to expand...
Click to collapse
No, this is clean boot img. Magisk you have to flash by yourself
Does systemless xposed work on nougat? If so, please provide the links.
BELIEVER PK said:
Does systemless xposed work on nougat? If so, please provide the links.
Click to expand...
Click to collapse
Yes,it does,just install magisk and in downloads search for Xposed modul.Then install and reboot your phone.
Thanks bud.
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
RedSkull23 said:
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
nagrale.prem said:
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
Click to expand...
Click to collapse
Completely uninstall SuperSU, flash through TWRP the unsu.zip available here on XDA thanks to osm0sis, and then flash Magisk.
BELIEVER PK said:
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
Click to expand...
Click to collapse
Of course they works. Every module works, but not GravityBox. It can't work on an heavy Android modification like EMUI as far as I know, so unless that there's a way to make it work while on SuperSU, it isn't possible to use it on EMUI (as stated in module description on Xposed repo).
Failed while flashing magisk zip.
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-Unpacking boot image
-Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done
Need solutions for above error please...
nagrale.prem said:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Click to expand...
Click to collapse
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
nagrale.prem said:
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
Click to expand...
Click to collapse
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
RedSkull23 said:
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
Click to expand...
Click to collapse
I own honor 6x India version. I understand Uninstal process for supersu. Right now I'm using ELITE ROM V7.3 so i don't know bulid no. N all stuff sorry. I know you will help me
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
matusala said:
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
Click to expand...
Click to collapse
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Horgar said:
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Click to expand...
Click to collapse
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
matusala said:
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
Click to expand...
Click to collapse
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Horgar said:
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Click to expand...
Click to collapse
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
jackdubl said:
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
Click to expand...
Click to collapse
Magisk is systemless root maybe that's why it did that.
matusala said:
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
Click to expand...
Click to collapse
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Horgar said:
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Click to expand...
Click to collapse
Have you tried just booting twrp instead of flashing it?
jackdubl said:
Have you tried just booting twrp instead of flashing it?
Click to expand...
Click to collapse
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Horgar said:
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Click to expand...
Click to collapse
I seem to remember getting some strange messages while flashing Magisk, like it couldn't mount system or something. It was in red. It seemed bad but it also came after successfully flashing Magisk, so it said. Everything was working fine after I rebooted. All root apps working as normal.
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
jeffritz1 said:
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
Click to expand...
Click to collapse
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
junglism93 said:
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
Click to expand...
Click to collapse
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
is rooted Magisk on Android 10 or 11 with Pixel 1 possible?
jeffritz1 said:
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
Click to expand...
Click to collapse
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
YogaSlackers said:
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
Click to expand...
Click to collapse
Hey, almost a week late but hope it's still helpful. Yes I recommend the official 10 firmware with Magisk, flashed through a temporary TWRP.
I've been running this setup for months, I can use all my root apps, even Google Pay and Netflix no problem.