Hi at all,
I own this device for two months now and I have read a lot about rooting and flashing. It seems to be quite difficult compared to my former Samsung and Xiaomi devices...
To avoid any kind of bricking my phone I wanted to ask if there's a way to root it. I (still) have a locked bootloader and I installed the latest update to 7.1.1 with 1st July security patch.
Is there any safe way to root and install TWRP (and afterwards some ROMs of course)?
Thank you. :fingers-crossed:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
jst98 said:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
Click to expand...
Click to collapse
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
f_ries said:
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
Click to expand...
Click to collapse
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Martin-cai said:
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Click to expand...
Click to collapse
If you are in 7.1.1, unlock your bootloader, download TWRP of @Alberto97 version 3.1.1-0(https://dc4.androidfilehost.com/dl/...673368273298955814/twrp-3.1.1-0-addison.img), flash it, download this kernel( https://drive.google.com/file/d/1i8PfTQ1e-WQkZ5-zD52HzWO3LZ5luaq_/view?usp=drivesdk) and the attached Magisk.zip.
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
xdaVTU said:
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
Click to expand...
Click to collapse
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Martin-cai said:
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Click to expand...
Click to collapse
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
xdaVTU said:
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
Click to expand...
Click to collapse
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Martin-cai said:
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Click to expand...
Click to collapse
I think creating a new post won't be necessary because kernel is already in @tomparr post, but in the last page of it, the twrp you cam download from Alberto's post, and magisk from the official thread(it's actually one of the most famous threads for now hahaha), but maybe if someone else have any issue with 7.1.1 i can create the post!
Edit. If i plan to try xposed again I tell you!
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
logotoy73 said:
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
Click to expand...
Click to collapse
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Bug camera help me
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
xdaVTU said:
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Click to expand...
Click to collapse
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
Gean Teixeira said:
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
Click to expand...
Click to collapse
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Artim_96 said:
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Click to expand...
Click to collapse
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Gean Teixeira said:
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Click to expand...
Click to collapse
Well then go back to stock first
Artim_96 said:
Well then go back to stock first
Click to expand...
Click to collapse
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Artim_96 said:
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Click to expand...
Click to collapse
I'm enganed...ZIP is rooted with magisk ,flashed , It,s ok...no insue
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
sergiomc22 said:
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
Stock post shamu17...dez patch, root magisk
Related
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Do you have a link to their research or are their findings private?
Regards,
Mr_Bartek said:
Do you have a link to their research or are their findings private?
Regards,
Click to expand...
Click to collapse
saurik - his analysis of the "second master key vuln"
giantpune for his symlnink attack vuln in property space:
Code:
/system/bin/mv /data/property /data/backupprop
/system/bin/mkdir /data/property
/system/bin/ln -s /sys/kernel/uevent_helper /data/property/.temp
/system/bin/setprop persist.sys.fail /data/pwn.sh
jcase said:
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
coolrevi said:
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
Click to expand...
Click to collapse
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
jcase said:
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
Click to expand...
Click to collapse
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
ricky310711 said:
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
Click to expand...
Click to collapse
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
pulser_g2 said:
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
Click to expand...
Click to collapse
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
ricky310711 said:
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
Click to expand...
Click to collapse
It depends on if OEMs backported it, depends on which build OEMs used and depends on the bug. Four or five different zip parser bugs with similar results. This one I used was patched in 4.3, but other exist.
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
trickraca said:
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
Click to expand...
Click to collapse
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
jcase said:
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
Click to expand...
Click to collapse
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
It should not come rooted, if it comes rooted then no way did it pass CTS. I'm guessing unlocking the bootloader and flashing a recovery? I don't know, I dont have one
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
noobish doubts..
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Please i ne ed a walthrough..
1) download twrp
2) put it in root of the telephone robot
3) flash it in recovery?
4) reboot recovery wipe cache and dalvik flash omnirom..
Please correct me..
Thank you
giuliano rigon said:
1) download twrp Yes
2) put it in root of the telephone Yes
Make sure to copy Omnirom to your phone at some point
3) flash it in recovery? No - Flash TWRP in Fastboot if you haven't flashed the recovery already. Use the official Teamwin site for guidance
4) reboot recovery wipe cache and dalvik flash omnirom.. Wipe Cache, Dalvik, System, and Data
Click to expand...
Click to collapse
Updates in Red
This is off-topic for this thread though. Questions/Info for flashing Omnirom should be addressed in the Omnirom thread.
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
not rooted.. confirm i can flash
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
I nave tried my damnedest to root .. Fastboot flashing supersu flashing from recovery Direct install from google play complete unroots and reflash letting recovery do it .. No way..
So now i need a last confirmation.. Can i flash omnirom after wipes even if i am unrooted.. And has anyone rooted omnirom or does it come unrooted.. Thanks for the info .. Another idea.. Flashing color OS footing and then flashing omni.. Or is this a late night bad Dream..
---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------
Harfainx said:
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
Click to expand...
Click to collapse
Sorry now i got it.. It was in the forums.. Just unchecking the respect cyanogen settings in the super su menu got me roooted and happy.. Sorry for your time.. I flashed super su zip from recovery rebooted and unchecked .. Now i am set..
I were rooted myN1 in yesterday, its really good . thankss
Sent from my N1 using XDA Premium 4 mobile app
After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?
aalemann said:
After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?
Click to expand...
Click to collapse
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46
levone1 said:
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46
Click to expand...
Click to collapse
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works
aalemann said:
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/
levone1 said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
this is exactly the version I flashed onto my CM12.1, worked flawlessly
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
xxBrun0xx said:
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
Click to expand...
Click to collapse
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
prins29 said:
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
Click to expand...
Click to collapse
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
lpchaim said:
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
Click to expand...
Click to collapse
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
prins29 said:
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
Click to expand...
Click to collapse
I've just tried again with the new TWRP and redownloaded files on my phone to be doubly sure, result is the same error others are reporting. Mind detailing how you managed to get Magisk running exactly? I've been looking around for a few days and never found consistent reports of it working on Nougat specifically, so it'd come in pretty handy.
Bump. Anybody succeed yet?
Try the Magisk 12 Snapshot. For me it works.
-=MoRpH=- said:
Try the Magisk 12 Snapshot. For me it works.
Click to expand...
Click to collapse
Can you write a guide please?
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
-=MoRpH=- said:
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
Click to expand...
Click to collapse
V12 definitely doesn't have an error when flashing like v11.1 did, but still doesn't pass safety check even after clean flashing flashallthetime's retbr build. Anyone get this to work with any other roms? One thing I noticed that was odd after clean flashing was viper and Dolby were installed but Dolby crashed and viper said drivers weren't installed. Weird.
Edit: Reflashed several different roms without zip. Tried using unSU zip + epsilon. No way to safetynet to pass, I give up. No androidpay/pokemongo is a small price to pay for working notification sounds, adblock, and greenify.
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
iron maiden said:
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
xxBrun0xx said:
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
Click to expand...
Click to collapse
yep, but i delete de supersu zip from the rom
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
-=MoRpH=- said:
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
Click to expand...
Click to collapse
How do you pass safetynet with SuperSU? Magisk v11.1 and up has SuperSU built in, why flash it?
Not trying to give you a hard time, just trying to understand. Really appreciate the help!
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
-=MoRpH=- said:
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
Click to expand...
Click to collapse
Did you take a nougat OTA? I didn't, so I wonder if my problem is that I'm still on the marshmallow bootloader/modem?
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
-=MoRpH=- said:
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
Click to expand...
Click to collapse
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.[/QUOTE
I'll pm you with the right one
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=529152257862701536
Click to expand...
Click to collapse
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.
Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.