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.
Related
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
Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016
Anyone flashed it?
OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app
We probably need to wait a little bit for OTA zip.
following for ota link
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.
mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk
Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.
waiting for ota zip :good:
I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Just installed! You have any advice about a compatible kernel?
Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.
65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.
OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124
[RECOVERY][ROOT] N910T/T3 6.0.1 PE3 - How to Root (Systemless & System Mode) / TWRP
This is really simple but I'm guessing people are still wondering.
Download TWRP
Download SuperSU 2.76 Systemless (for Stock Kernels) or Download SuperSU 2.76 SystemMode (Permissive Kernel Required)
*Optional* Download a Permissive Kernel like BeastMode (only needed for System Mode SuperSu)
Download Odin
Put the SuperSU on your SD Card / Internal Storage
*Optional* Put Custom Kernel on SD Card (Optional, Only required if using SuperSu SystemMode)
Reboot into Download Mode
Flash TWRP in Odin
Boot into TWRP
Flash SuperSU
Enjoy!
For details on how to flash with Odin, flash with TWRP please see other threads or use Google.
Additional Downloads:
-N910T PE3 Stock Recovery
Additional Info:
NetFlix:
Some users have reported that NetFlix would not connect after rooting. There is no need to do this if you do not have any problems with NetFlix.
-Delete /system/vendor/lib/liboemcrypto.so and reboot.
------------------------------------------------------
Thanks of course to Chainfire & Teamwin
Also Thanks to freeza.
Cool. Thanks. it's same for all other mm roms too.
Is this Systemless root?
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
So if we already have a rooted device with TWRP installed, and assuming we already were able to flash 6.0.1 to the device, then the only step required is:
Download SuperSU
Flash SuperSU via TWRP
Is that right?
Sent from my SM-N910T3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your prior rooted device needs to be rerooted. Download SuperSu to phone. Download TWRP to computer. Odin TWRP. Once TWRP is flashed, boot to TWRP and install Supersu [at least that's what I did.]
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Sent from my SM-N910T3 using XDA-Developers mobile app
f4phantomii said:
But since I already have TWRP installed as recovery, do I need to re-install it via Odin?
Unless flashing 6.0.1 overwrites the recovery?
Otherwise just flashing SuperSU should re-root.
Click to expand...
Click to collapse
Odin flashing MM will overwrite your recovery.
Got it. Thanks fo clarifying that.
Sent from my SM-N910T3 using XDA-Developers mobile app
Question, have rooted and jail broke many but not this 910T yet. I am on non-root 5.1.1, should I take the OTA 6.0.1 and then follow the above instructions or download 6.0.1 from samsung and install via Odin and then start following these instructions? Would perfer to take over the air so I dont have to reset up everything.
Thanks in advance and I cant fn wait to start using Adfree again!
I downloaded via Kies. Didn't have to setup a thing after.
Sent from my SM-N910T using XDA-Developers mobile app
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
Agreed.
Anybody know if editing the platform.xml still works for SD card writing? And with the update I am getting the stupid -504 error in google play store trying to install Titanium backup......I might have to reflash ugh.
Edit*****
I fixed my issue
Bubba Fett said:
I'm impressed we got this being 1.90 generations old. I usually feel forgotten and abandoned by now. Thanks T-Mo. Now please don't F us on the Note 6/7 bootloader!
Click to expand...
Click to collapse
They will.
Man I hope not. We did a lot of *****in! Looks like HTC is gonna do the next nexus and should be on par with the N7 but I really don't want to do that. There is no way any phone can compare with the same phone rooted and custom. We will see.
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Has anyone flashed the new 6.0 MM BL and CP vs Flashfire?
The G.O.A.T. said:
I'm having the same issue however I can't get into TWRP period... I pushed MM and TWRP 3.0.2 from ODIN 3.07. During reboot it rw's the MM recovery
Click to expand...
Click to collapse
richard75013 said:
Any ideas, stock non rooted 5.1 updated via OTA to 6.0.1, flashed latest TWRP 3.2.0 successfully (USB Deb enabled, R/L disabled) and still boots into stock recovery? What am I doing wrong?
SM-N910T
---------- Post added at 02:39 AM ---------- Previous post was at 01:41 AM ----------
Found a work around from another post:
'm trying to install TWRP, but it keeps getting overwritten. After installing, I can initially boot into TWRP, but after doing a system reboot, it goes back to stock recovery. What am I doing wrong?
Here's the steps I take:
Open Odin, check AP and load twrp image (3.0.0)
Connect phone and wait for Added!
Uncheck Auto Reboot
Click Start and wait to finish.
I then have to take out the battery to turn the phone off (I had to do it this way because leaving Auto Reboot checked would cause the same issue as below). I then boot directly into recovery and TWRP loads as expected. Everything looks fine, and I can do a recovery reboot back to TWRP. However, if I do a system reboot and let Android load, then shutdown and boot into recovery again, I'm back to stock.
Sprint SM-N910P
Android 5.1.1
http://androidforums.com/threads/twrp-keeps-getting-overwritten.1003988/
Click to expand...
Click to collapse
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
DeeXii said:
Perhaps try wiping everything...
System, Data, Internal Storage.
Then flash the Odin MM tar.
Then start the process in the thread.
I personally did the process after a SmartSwitch update and it worked from just doing what I listed in the OP.
Click to expand...
Click to collapse
Yeah idk... It just worked this time. IF I was to say what I did different I booted into recovery first it started with applying update or something then crashed because no update was there, then showed stock MM recovery I then. Shutdown and went into download mode and did the OP.
It work!!!
Doing a new backup now
Hi all
Ok so, I am updated to Nougat (EU) with no modifications besides an unlocked bootloader.
Since the last fastboot firmware file currently available to us is the September 2016 security patch, I'm a little hesitant to root right now. I want to be sure I'm be able to take new OTAs (if we ever get more). But I'm not sure if the September build will work now after updating to Nougat.
So what can we do in the meantime. Well that's where I may need guidance, but I think I have the idea down, so might still be useful information.
Ok, so to root, I first need to install TWRP - a custom recovery. But to accept OTAs I need to keep the stock recovery.img (which is overwritten by TWRP). Then I'd flash Magisk for root - and Magisk will modify the boot.img, so i need to keep the stock boot image (all of which we'd have if we had the actual fastboot files).
Anyways, I think it's quite easy. The only tricky part for me is the recovery. How do I get a backup of the stock one? Does TWRP make a backup during install ("fastboot flash recovery TWRP.img")? If so, where is this backup? I know I can back up the boot.img with TWRP before flashing Magisk (I believe Magisk makes a backup anyways, so if you use the Magisk uninstaller, the stock boot will be restored). But the recovery... If these two stock images can be backed up then it's easy to restore them to accept an OTA. Or is it not that simple? Can you actually flash the stock recovery from within TWRP (thereby overwriting itself)?
1. Unlock bootloader.
2. Boot only twrp 3.1.+ with:
fastboot boot NameOfTwrp.img
2a. Create your own full backup(recovery, boot, system, efs, opt. data).
3. Flash twrp for stable:
fastboot flash recovery NameOfTwrp.img
Boot into twrp from BL menu without rebooting system.
4. Magisk, read here, post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Newest version is 13.3, you need twrp for magisk updates or modules.
https://forum.xda-developers.com/apps/magisk
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
@d.casper.b
dzidexx said:
1. Unlock bootloader.
2. Boot only twrp 3.1.+ with:
fastboot boot NameOfTwrp.img
2a. Create your own full backup(recovery, boot, system, efs, opt. data).
3. Flash twrp for stable:
fastboot flash recovery NameOfTwrp.img
Boot into twrp from BL menu without rebooting system.
4. Magisk, read here, post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Newest version is 13.3, you need twrp for magisk updates or modules.
https://forum.xda-developers.com/apps/magisk
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
@d.casper.b
Click to expand...
Click to collapse
Awesome thanks, I'll try that when I get home tonight.
And one can just restore stock recovery when needed from within TWRP?
One must really prepare well for OTAs these days without the actual fastboot files readily available.
d.casper.b said:
Awesome thanks, I'll try that when I get home tonight.
And one can just restore stock recovery when needed from within TWRP?
One must really prepare well for OTAs these days without the actual fastboot files readily available.
Click to expand...
Click to collapse
All canbe restored with twrp.
Only modified logo.bin you have to flash with fastboot. It is in "stock ota nougat reteu" thread.
---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------
#163 & next few posts
https://forum.xda-developers.com/mo...7-0-nougat-t3630248/post72928449#post72928449
I've just booted TWRP and backed up all partitions...but I don't see recovery.
All that is available is: Boot, System, Data, Cache, and EFS.
It seems silly, but I know the official TWRP app from the play store has a backup recovery option but it needs root...
So my thinking is: boot into TWRP (don't flash it) then root the device with magisk. Use the TWRP app to backup recovery .............. and you just replied with my same thinking...
HAHA, I just unistalled flashfire today. I'll install it again.
d.casper.b said:
I've just booted TWRP and backed up all partitions...but I don't see recovery.
All that is available is: Boot, System, Data, Cache, and EFS.
Click to expand...
Click to collapse
Hmm...
I thought twrp 3.1.1 can backup stock recovery.
Don't flash twrp.
Boot twrp, root with magisk(same way), reboot phone.
Install flashfire app(play store) and do backup of stock recovery(option - for fastboot).
Flashfire: , backup, ..., it will reboot the phone and do backup. After it you can flash twrp with fastboot.
awesome man, I was just editing my post when the email that you replied came through
I think I'll do this tomorrow night now! I'll update if it's successful.
Thanks for assisting me to get this done!
Ok, well I decided to get it over with.
Backed up the recovery with TWRP app and just made a fastboot backup of recovery with flashfire now..
Actually, if you never flash TWRP then it would just be a matter of restoring the boot.img - but of course, then you always need to be at a PC.
Last thing, can I use the No Unlocked Bootloader warning logo and it won't break anything (like later OTAs)?
d.casper.b said:
Last thing, can I use the No Unlocked Bootloader warning logo and it won't break anything (like later OTAs)?
Click to expand...
Click to collapse
I don't know(about ota).
Original Logo bin - flashfire can backup it(normal or full section).
All done! Now hopefully prepared for whenever the time comes!
Thank you so much for helping me out on this little journey
You're welcome.
I hope it will be useful to others. Everyone should do so.
dzidexx said:
You're welcome.
I hope it will be useful to others. Everyone should do so.
Click to expand...
Click to collapse
My thoughts exactly.
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good: