Correct Way Of Rooting A Moto Z Play As Of Feb/ 17 - Moto Z Play Guides, News, & Discussion

Ok folks you're here because you have the need to root​MM 6 or Nougat 7.0 Only
As of February 2017 you need 3 things
Unlocked Bootloader
Motorola Device Manger (drivers):Download
1) TWRP ( Recovery)
2) Modified kernel (F2FS fixes)
3) SuperSu 2.79 R3 systemless root
TWRP can be found Here: TWRP
Modified Kernel can be found here:TWRP & Modified kernel
Download both the modified kernel, either the MM one Or Nougat 7.0, depending on which OS you are using and download the modified kernel to your internal sd card ( Our external sdcard can't be read by TWRP, so all flashable zips must be in your internal sdcard)
Flash recovery through fastboot Code: fastboot flash recovery (name of recovery).img
Do not reboot but use the volume buttons on the phone to select recovery from the menu on the fastboot screen.
Now we can flash the Modified Kernel which you have previously downloaded to your internal sd card.
Flash the Kernel.
Now download SuperSu
SuperSu:SuperSu 2.79 R3
NEW FOR NOUGAT 7.1.1 ONLY
Unlocked bootloader
Motorola device manager Download:Download["]Moto Device Manager
Twrp recovery downloaded into the same folder as fastboot
Gaining root differs from 7.0 or 6.0, you can only root with magisks 13 or above if you are running any stock based rom or custom based rom that doesn't have built in root, you no longer need to flash the F2FS fixed kernel on 7.1.1
Magisks Thread :Magisks Thread
You need to flash Magisks to disable dm-verity otherwise your phone will not boot this is because the stock kernel checks for any modifications to the system
That's it
Thanks to @Alberto97 & @tomparr

Will be useful for noobies
Enviado desde mi XT1635-02 mediante Tapatalk

Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata

Nil253259 said:
Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata
Click to expand...
Click to collapse
I'm unecrytped and see real no gain, I think it's more of a placebo effect.

is that superSU better than Magisk?

Do you still need official bootloader unlocking ? aka no more warranty ? Thanks

razorsbk said:
Do you still need official bootloader unlocking ? aka no more warranty ? Thanks
Click to expand...
Click to collapse
Yes

Thank you.
Sent from my XT1635-02 using Tapatalk

Will all this work with Windows 10?

shawnsac2000 said:
Will all this work with Windows 10?
Click to expand...
Click to collapse
It will if you have the right drivers installed

punkerEVO said:
is that superSU better than Magisk?
Click to expand...
Click to collapse
It's confirmed that you'll have root with SuperSu 2.79 R3, Magisk's may cause Issues under certain circumstances.
I'ver tried to keep as simple as possible because there's 2 other threads with root method's that are not up to date.

Thanks

dedraks said:
Thanks
Click to expand...
Click to collapse
Lol OK I can see where this could get confusing now.

Thanks flashallthetime.
I misread your instructions though and I am in trouble. I misread the bit about copying the modified kernel to internal SD card; instead I copied to external SD card (as I have always done with previous devices). I now can't flash the modified kernel because the newly flashed TWRP 3.0.2 doesn't have access to the external SD card.
The current state of the device is that it is stuck at the unlocked warning screen. It says "ID: bad key", but after flashing a recovery, it says "ID: N/A".
Is this consistent with the kernel not being flashed, or do I have another issue?
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Anyone? Thanks so much!!

You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
punkerEVO said:
Lol OK I can see where this could get confusing now.
Click to expand...
Click to collapse
How?

dedraks said:
You can use fastboot to flash boot.img.
Click to expand...
Click to collapse
Is that to me? Which boot.img, where do I find it? Thanks!

raymosaurus said:
Is that to me? Which boot.img, where do I find it? Thanks!
Click to expand...
Click to collapse
Yes.
Extract from the ROM in this post:
https://forum.xda-developers.com/moto-z-play/development/rom-stock-7-0-t3553213

raymosaurus said:
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Click to expand...
Click to collapse
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img

tag68 said:
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img
Click to expand...
Click to collapse
For God's sake people , don't use the Chinese TWRP. 2 people that I know have mistakenly wiped their IMEI with that junk.

dedraks said:
You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
How?
Click to expand...
Click to collapse
I have a flashable zip of the Nougat stock boot.img
Here https://www.androidfilehost.com/?fid=457095661767138793

Related

[Guide] How to install a custom recovery and root

OK, I see that this subject has not been properly addressed in this forum and there are a lot of users who still use tool kits,etc. for this. That's fine but you're missing out on how to more effectively manage your device. I'm writing this off the top of my head, and on my n9 which is not so easy, so I may modify it in the future.
The first thing you want to do is learn how to use fastboot. Fastboot allows you to flash image, .img, files on your device. If you've never done that start here, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Rooting is as simple as flashing a custom recovery on your device and then booting into that recovery and flashing Chainfires supersu.
So how do you flash a custom recovery? Well I strongly recommend twrp. Download the latest from here, https://dl.twrp.me/flounder/ I always find it easier to rename the file you download to simply recovery. Make sure you maintain the .img file extension. Download this onto your pc and remember what folder you downloaded it to.
Then download the supersu.zip file to your device. Download from here, https://download.chainfire.eu/696/SuperSU
Now you're ready to get started. Boot your device into the bootloader and connect it to your pc.
On your computer open the folder where you downloaded the twrp image. On an open area in that folder shift, right click on your mouse. You should see a pop up and a place to "open a command window here" In that command window type, fastboot devices. If you see your device's serial number you're good to go to flash the twrp image file.
OK, the Nexus 9 is not as easy to root as other Nexus devices. So start by typing, fastboot boot recovery.img. (Remember I told you to rename the twrp image file to recovery, if you didn't do that use the full name of the twrp file you downloaded for recovery.img) Once you boot into twrp go to install and find the supersu.zip you downloaded onto your device. Install it.
Then from twrp, boot back into the bootloader.
Once booted into the bootloader open a command window in the same folder as you have the twrp image downloaded. Then type fastboot flash recovery recovery.img
You're now rooted and have twrp installed.
Having major problems trying to do this on Marshmallow, lol.
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
so mounting the usb stick to the pc, it will be recognized by twrp?
tykalx said:
so mounting the usb stick to the pc, it will be recognized by twrp?
Click to expand...
Click to collapse
If you don't have USB stick, adb sideload worked for me to flash supersu beta 2.5.1
And I'm using stock modified kernel chainfire posted to keep selinux enforcing.
tykalx said:
so mounting the usb stick to the pc, it will be recognized by twrp?
Click to expand...
Click to collapse
No, you need a usb stick and adapter to the device. But what mrRobinson said should work too. You can do that from your pc.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, that worked.
I went and installed Busybox, not sure if I needed to?
I really want to get this thing decrypted now but am happy to wait for a Marshmallow solution rather than go back. I suppose I could flash a ROM without forced encryption from the flash drive too? As long as I do a full wipe?
I only got my N9 a week ago and haven't had time to play with it so all this encryption stuff is new to me.
---------- Post added at 09:08 PM ---------- Previous post was at 09:04 PM ----------
I am rooted but can;t copy hosts file over, system is read-only, is this an encryption thing or has something gone wrong please?
---------- Post added at 09:28 PM ---------- Previous post was at 09:08 PM ----------
One more question..
If I was to factory reset and then flash the kernel and supersu would I get an unencrypted device? Or if I hit the "decrypt data" button in the "wipe" menu in TWRP? I am scared to press it, lol.
Excuse me but this only adds confusion in case of 6.0. So far the most comprehensive guide I found here is this one (see also an answer there).
That solution involves wiping data, so you need your stuff backed up somewhere. In my case I restored playstore apps from google account and just reinstalled the rest from apks.
I answered my own questions here http://forum.xda-developers.com/nexus-9/help/decrypt-marshmallow-question-t3222592. Thanks again for the help jd1639.
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
worked like a charm :good:
Any difference when already running 7.0?
I keep getting stuck in a bootloop after flashing SuperSu. Any thoughts on this? I've tried wiping caches/dalvik. Running latest stock version of 6, latest version of TWRP, installed proper ElementalX for Android version, boots fine after the kernel install.
sjrixon said:
Any difference when already running 7.0?
Click to expand...
Click to collapse
For N (and MM in some cases), you need systemless support - which the current version of SuperSU has. (Magisk 12.0 has it as well.)
Where Magisk (vice SuperSU) has advantages is being able to hide that you're rooted (Android/Samsung Pay, Visa Checkout, SafetyNet, etc.) - which is, in fact, why I am evaluating Magisk.
So far, I have seen next to no disadvantages to N - even on "moldy" SoCs (such as the TI OMAP in my Galaxy Nexus - the oldest hardware I've heard of - let alone seen - running N on a daily basis; I run N as a daily driver). I even prefer N to MM, let alone anything older, on the selfsame GNex (which utterly flies in the face of "common wisdom"; it makes me wonder, in fact, if "common wisdom" is a coverup for "fear of change", since said "common wisdom" predates Android by several years).
Hi,
Isn't is required to unlock bootloader first ?
Where this unlocking is done in this procedure ?
Thanks,
ranran
ranchu-panchu said:
Hi,
Isn't is required to unlock bootloader first ?
Where this unlocking is done in this procedure ?
Thanks,
ranran
Click to expand...
Click to collapse
That is always the first step and doesn't change. This thread covers the changing root methods on different Android versions.
madbat99 said:
That is always the first step and doesn't change. This thread covers the changing root methods on different Android versions.
Click to expand...
Click to collapse
Thanks,
Yet, I noticed in many threads of rooting in mediatek devices, that just flashing recovery.img and boot.img is the 1st procedure to make the device root.
Does it mean that mediatek device does not require unlocking the bootloader ?
Thx

[ROOT] Root for Stock MRA58N (System/Systemless) (Wi-Fi/LTE)

The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good

[OBSOLETE] Root Android 7.0 Nougat after clean Install - Just use TWRP 3.0.2.1

Edit: Obsolete now. Twrp 3.0.2.1 is Out.
For now TWRP cant decrypt Android Ns vendor images so you cant flash SuperSU. So why not flash back old vendor to root the device and reflashing the NRD90M Vendor?
It works great. I root my clean install from factory image Android 7.0 NRD90M:
1. Flash the just released NRD90M via Fastboot
2. Reboot and set up your device.
3. Reboot to fastboot and flash vendor_mob30w.img by entering: fastboot flash vendor vendor_mob30w.img
4. Boot TWRP 3.0.2.0 temporary by entering: fastboot boot twrp-3.0.2-0-flounder.img
5. In TWRP copy UPDATE-SuperSU-v2.76-20160630161323.zip to your device and install it.
5.1 If you want to use adaway flash also AdAway_systemless_hosts_v2.zip.
6. Go back - back - back and reboot your device to fastboot.
7. Reflash the original vendor vendor_nrd90m.img by entering: fastboot flash vendor vendor_nrd90m.img
8. Reboot your device. Its rooted!
Extract the vendor files from the factory images or take these just extracted files from my google drive:
Download vendor_mob30w
Download vendor_nrd90m
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
Is that one system less?
edit: nevermind this
osnapitsjoey said:
Is that one system less?
Click to expand...
Click to collapse
Yes CFAR is systemless.
If you were not a very smart man and encrypted your device during the install will this method work? Does it allow you to take monthly security updates still?
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
GialanG said:
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
Click to expand...
Click to collapse
It will bootloop and eventually load. At least that is what it did on the previews. Haven't tested on final release.
You still can not modify/read encrypted data partition, hence OTG or sideloading of zips.
Edit:- Just tested and it eventually loads.
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
corkiejp said:
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
Click to expand...
Click to collapse
Cool, thanks ! Is there also a way to decrypt the tablet ?
TheLonelyCyborg said:
Cool, thanks ! Is there also a way to decrypt the tablet ?
Click to expand...
Click to collapse
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
corkiejp said:
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
Click to expand...
Click to collapse
Thanks @corkiejp it worked like a charm !
Can you please update this guide?
Sent from my Nexus 9 using Tapatalk
Twrp bootloop
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
lawlor059 said:
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
Click to expand...
Click to collapse
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
corkiejp said:
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
Click to expand...
Click to collapse
3.0.2-1 works perfectly fine for marshmallow.
dictionary said:
3.0.2-1 works perfectly fine for marshmallow.
Click to expand...
Click to collapse
Thanks @corkiejp. @dictionary I couldn't get into the recovery with 3.0.2.1. Entering the decrypt code would just cause it to loop again. Ignoring the decrypt code I could get into the recovery but with nothing mounted it's useless. It will install successfully but nothing can be done with it.

Oxygen OS 3.1.0 Root?

Hey all!
First post on this site! Ok, so quick question, won't make this too long.
I updated my phone to os 3.1.0 which is awesome, however I want to root it now and I cannot find any recoveries for the new update? Anyone got any ideas or whether or not the old recovery would be compatible with this new update?
Thank you advance guys!
itshaassann said:
Hey all!
First post on this site! Ok, so quick question, won't make this too long.
I updated my phone to os 3.1.0 which is awesome, however I want to root it now and I cannot find any recoveries for the new update? Anyone got any ideas or whether or not the old recovery would be compatible with this new update?
Thank you advance guys!
Click to expand...
Click to collapse
In order to flash custom recovery you will need to unlock bootloader :
1. Instal adb\fastboot on PC then on your opt In developer options enable oem unlock.
2. Reboot phone to fastboot (power off, volume up+power)
3. From cmd type 'fastboot oem unlock'
Then go https://dl.twrp.me/oneplus2/ (download the latest version it will work on oxygen 3.1.0). Then flash supersu (attached)...and you got root
hi.. i flashed supersu 2.78 after updating to oos3.1.0 and i allways get stuck on bootlogo.. is your supersu file different from 2.78?
ty
DACATA said:
hi.. i flashed supersu 2.78 after updating to oos3.1.0 and i allways get stuck on bootlogo.. is your supersu file different from 2.78?
ty
Click to expand...
Click to collapse
Yes, the supersu I attached is modified, so it will work on oxygen 3.1.0.
Aca902 said:
Yes, the supersu I attached is modified, so it will work on oxygen 3.1.0.
Click to expand...
Click to collapse
yes.. got it ty still works
twrp not installing on my oxygenos 3.1.0
help me :'(
alansalim said:
twrp not installing on my oxygenos 3.1.0
help me :'(
Click to expand...
Click to collapse
I can think of two reasons: 1. Your bootloader is not unlocked
2. Your are not using the latest TWPR
It works for me.
@alansalim if you explain us the steps you took, then maybe we can help you
Aca902 said:
I can think of two reasons: 1. Your bootloader is not unlocked
2. Your are not using the latest TWPR
Click to expand...
Click to collapse
after flashing TWRP, when i boot into recovery....there is no TWRP, its stock recovery
alansalim -> step 3..... From cmd type 'fastboot oem unlock'
Aca902 -> twrp installs fine on my phone. but not your supersu ? is i because i'm not having a SD card and try to flash from phone memory ?
InzaneD said:
alansalim -> step 3..... From cmd type 'fastboot oem unlock'
Aca902 -> twrp installs fine on my phone. but not your supersu ? is i because i'm not having a SD card and try to flash from phone memory ?
Click to expand...
Click to collapse
What do you mean by SD card? OPT doesn't have a microsd slot.
I'm not sure, it should work... I have tested it on stock 3.1.0 with latest TWPR...and it worked fine (did it a few times when I was trying custom roms and going back to stock).
EDIT: Try downloading supersu again (maybe corrupted download?) and wipe cache after flashing supersu.
Aca902 said:
What do you mean by SD card? OPT doesn't have a microsd slot.
I'm not sure, it should work... I have tested it on stock 3.1.0 with latest TWPR...and it worked fine (did it a few times when I was trying custom roms and going back to stock).
EDIT: Try downloading supersu again (maybe corrupted download?) and wipe cache after flashing supersu.
Click to expand...
Click to collapse
HAHA I forgot it hasn't a microsd.. DOUGH.
well I have tried to download supersu again but same result. It fails then I try to flash and there's no error description
---------- Post added at 04:18 PM ---------- Previous post was at 03:47 PM ----------
InzaneD said:
HAHA I forgot it hasn't a microsd.. DOUGH.
well I have tried to download supersu again but same result. It fails then I try to flash and there's no error description
Click to expand...
Click to collapse
hmm got it working. just downloaded supersu again and now it works.. Thanks
the command in 3 line must be: fastboot oem unlock
and not fastboot oem ulock

Android Nougat nbd90z (flashable & image, no encryption, no dm verification)

** DISCLAIMER: APPLY AT YOUR OWN RISK **​** The following are instructions for installing Android Nougat released by Google on 10/4/2016. **​Always backup your data before flashing stuff you download from the internet!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 or higher installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to Nougat. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and flashes TWRP 3.0.2-0)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to Nougat with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.78 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703.
Some of your apps may be too old to work properly under 7.0 so if they act up you may need to uninstall them and install the newer versions. If some of your old settings like wifi calling don't work properly, especially if you upgrade from a custom ROM, it is not because of this flashable zip, the reason is that Nougat is having trouble converting your settings and a factory reset will solve all of your problems.
was waiting for this to drop, awesome, downloading now
Sent from my Nexus 6 using Tapatalk
Thanks!
so i can just flash this if im on franco kernel r19 runing andro 5.1.1?
---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------
how do i flash twrp3.02? can i just use flashify app?
Works great and as advertised. Thanks!
flash-all.bat contains a typo.
fastboot flash boot shamu-npd90g-boot-NoEncNoVerify.img
should be
fastboot flash boot shamu-nbd90z-boot-NoEncNoVerify.img
So can we still flash this over yesterday's nougat update or have to go back to M?
This is what I have been waiting for, najoor I have been using your NDP5 since July, thank you for your work downloading now.
yudumcan said:
So can we still flash this over yesterday's nougat update or have to go back to M?
Click to expand...
Click to collapse
Yes, no need to go back to M.
najoor said:
Yes, no need to go back to M.
Click to expand...
Click to collapse
Thanks mate. So what's the difference than this release http://forum.xda-developers.com/nex...ightromstock-lmy47e-03-19-2015-t3059493/page4
Edit: what if I'm encrypted?
Works great. If you are a Verizon customer with an unlimited data plan, you can use root explorer to add net.tethering.noprovisioning=true to your build prop to unlock tethering. (Must be rooted to use root explorer.)
Thanks op! Will this flash bootloader and radios too? I'm coming from MM custom ROM. Also, why the modified kernel and what is different from stock?
Sent from my Nexus 6 using Tapatalk
xt926 said:
Thanks op! Will this flash bootloader and radios too? I'm coming from MM custom ROM. Also, why the modified kernel and what is different from stock?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes it will flash everything. The kernel is modified so that you can change the OS through recovery without getting a bootloop. Unmodified kernels after lollipop check for system integrity at every boot up and generate a panic signal if something is changed. Also the modified kernel does not force encryption so your system remains unencrypted if it already is.
I presume this bootloader is backwards compatible with M ROMs as was the previous one?
Well I was hoping the official build would've fixed my Wifi disconnection problems but unfortunately I'm still having them. Anyone else? Mine started on P5 and I've done everything as far as turning on and off different settings on my phone, to resetting my router to see if that was the problem and it's still continuing to do the same thing.
Flashed this over najoor's NDP5 and added ElementalX 4.08 and superSu 2.78, works perfectly. No issues, all root apps still working, very smooth and stable.
Thank you najoor nice work.
Nexus 6
jk8260 said:
Flashed this over najoor's NDP5 and added ElementalX 4.08 and superSu 2.78, works perfectly. No issues, all root apps still working, very smooth and stable.
Thank you najoor nice work.
Nexus 6
Click to expand...
Click to collapse
Can u post a link for that superSU 2.78. TIA
So far so good. Tmo Nexus.
Sent from my SM-G935T using XDA-Developers mobile app
Thanks for this! How come no Nougat boot animation?
info[]box1 said:
Can u post a link for that superSU 2.78. TIA
So far so good. Tmo Nexus.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Direct URL
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
XDA page
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Nexus 6
kxs783kms said:
Well I was hoping the official build would've fixed my Wifi disconnection problems but unfortunately I'm still having them. Anyone else? Mine started on P5 and I've done everything as far as turning on and off different settings on my phone, to resetting my router to see if that was the problem and it's still continuing to do the same thing.
Click to expand...
Click to collapse
Do a clean install then. Dirty flashing over DP5 caused it to others too.
Sent from my Nexus 6 running cyosp using Tapatalk

Categories

Resources