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
Related
There are two methods to root Android N .
Method 1
Flash the Supersu.zip from custom recovery.
RC-SuperSU-v2.69-20160313161431.zip
Method 2
This method will work without custom recovery , just download it and go the fastboot and follow the steps .
CF-Auto-Root-bullhead-bullhead-nexus5x-NPC56P.zip
Just download the file
Extract it
reboot your Nexus 5X into bootloader
Now open the root-windows(If you are using windows otherwise select the file which is for your operating system)
Now the command window will open and ask you to enter any key to continue
Then press any key from your keyboard and it will automatically done the remaining process and your phone will reboot
If you device got bootloop then poweroff the device once and power on manually
Thats it you will see the SuperSu icon .
If you like hit the thanks ......
how do you get access to the files on your phone to flash this. I have twrp flashed but it wont get access to any files that are actually on phone so I can not flash SUPSERSU?
brennerj said:
how do you get access to the files on your phone to flash this. I have twrp flashed but it wont get access to any files that are actually on phone so I can not flash SUPSERSU?
Click to expand...
Click to collapse
Then try the second method , it doesnt need the TWRP recovery.
How I root my HTC One m8
adeeta said:
How I root my HTC One m8
Click to expand...
Click to collapse
Wrong forum..
Sent from my Nexus 6 using XDA Free mobile app
karthik432 said:
There are two methods to root Android N .
Method 1
Flash the Supersu.zip from custom recovery.
RC-SuperSU-v2.69-20160313161431.zip
Method 2
This method will work without custom recovery , just download it and go the fastboot and follow the steps .
CF-Auto-Root-bullhead-bullhead-nexus5x-NPC56P.zip
If you like hit the thanks ......
Click to expand...
Click to collapse
can you explain how to do the second method. Do not have experience flashing that one. Do we use android toolkit or SDK? Please elaborate. Thanks!
brennerj said:
can you explain how to do the second method. Do not have experience flashing that one. Do we use android toolkit or SDK? Please elaborate. Thanks!
Click to expand...
Click to collapse
Just download the file
Extract it
reboot your Nexus 5X into bootloader
Now open the root-windows(If you are using windows otherwise select the file which is for your operating system)
Now the command window will open and ask you to enter any key to continue
Then press any key from your keyboard and it will automatically done the remaining process and your phone will reboot
If you device got bootloop then poweroff the device once and power on manually
Thats it you will see the SuperSu icon .
Thanks autoroot worked. Also format userdata then flash twrp then flash SuperSU works but after a reboot I'm back to stock recovery again. Do we need a modified boot.img?
Edit:: OK I managed to get twrp to stick but I need password to decrypt data. Tried formatting userdata but stock recovery is back after a reboot
how to install custom recovery on nexus 5x android n dev prev 2? i stuck on splash screen (twrp 3.0.0.2)
tomgacz said:
how to install custom recovery on nexus 5x android n dev prev 2? i stuck on splash screen (twrp 3.0.0.2)
Click to expand...
Click to collapse
that because the encrypted user data
i try this method and work for me
1. clean flash the N prev 2
2. boot into bootloader
3. flash twrp
4. flash the modifed boot.img
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
5. format the userdata
6. boot into the recovery and flash the SuperSU
before format the userdata, don't reboot the device
hope this can help
Well, I sideloaded super su latest after installing N preview. I cannot get txrp to read write system files, though. ANyone get twrp on N yet?
Xdevillived666 said:
Well, I sideloaded super su latest after installing N preview. I cannot get txrp to read write system files, though. ANyone get twrp on N yet?
Click to expand...
Click to collapse
Yes, I did. First, your phone must be decrypted. TWRP cannot be flashed on encrypted Android N.
ttakacs said:
Yes, I did. First, your phone must be decrypted. TWRP cannot be flashed on encrypted Android N.
Click to expand...
Click to collapse
How do I do this? Can I be on N or must I be on MM first?
Xdevillived666 said:
How do I do this? Can I be on N or must I be on MM first?
Click to expand...
Click to collapse
Three steps:
1. Disable forced-encryption & decrypt (fastboot)
Flash the modified boot.img
Format the data partition
See: http://www.droidorigin.com/decrypt-nexus-5x/
2. Reboot and copy SuperSU 2.74 to internal storage
3. Root
Install TWRP using fastboot
Boot into TWRP and flash SuperSU 2.74
See http://www.droidorigin.com/root-android-n-developer-preview/
ttakacs said:
Three steps:
1. Disable forced-encryption & decrypt (fastboot)
Flash the modified boot.img
Format the data partition
See: http://www.droidorigin.com/decrypt-nexus-5x/
2. Reboot and copy SuperSU 2.74 to internal storage
3. Root
Install TWRP using fastboot
Boot into TWRP and flash SuperSU 2.74
See http://www.droidorigin.com/root-andr...loper-preview/
Click to expand...
Click to collapse
Thanks man!! !The second link you sent me to no longer exists, though:-/
Ooops... Error 404
Oh! That's a 404. Please contact the website owner.
http://www.droidorigin.com/root-andr...loper-preview/
Xdevillived666 said:
Thanks man!! !The second link you sent me to no longer exists, though:-/
Ooops... Error 404
Oh! That's a 404. Please contact the website owner.
http://www.droidorigin.com/root-andr...loper-preview/
Click to expand...
Click to collapse
The forum software truncated the URL. Here it is: http://www.droidorigin.com/root-android-n-developer-preview/
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.
Hi, i have an X Compact 34.2.a.0.311 version (Nougat).
I need to install root and twrp with this version, how could i do it? If possible? (I have an unlocked bootloader)
dozzo94www said:
Hi, i have an X Compact 34.2.a.0.311 version (Nougat).
I need to install root and twrp with this version, how could i do it? If possible? (I have an unlocked bootloader)
Click to expand...
Click to collapse
Look in Xperia X Compact ROM and Kernels category, there is X Genesis kernel and TWRP..
You boot TWRP, flash the kernel and SuperSU and you are ready.
ondrejvaroscak said:
Look in Xperia X Compact ROM and Kernels category, there is X Genesis kernel and TWRP..
You boot TWRP, flash the kernel and SuperSU and you are ready.
Click to expand...
Click to collapse
It says i must "install the .zip file with twrp" , but how do I get the twrp? Because it says i need a phone with .198 ver.
dozzo94www said:
It says i must "install the .zip file with twrp" , but how do I get the twrp? Because it says i need a phone with .198 ver.
Click to expand...
Click to collapse
You can use 'fastboot boot twrp.img'
Sent from my SM-T813 using XDA Free mobile app
dozzo94www said:
Hi, i have an X Compact 34.2.a.0.311 version (Nougat).
I need to install root and twrp with this version, how could i do it? If possible? (I have an unlocked bootloader)
Click to expand...
Click to collapse
You can also have a look at this giude
Of course, as already suggested by @ondrejvaroscak you have to look in X compact forum section to get TWRP and kernel.
Please note that if you want to flash your DRM keys back (step 7 of the guide above) you need flashtool version 9.22.3 (also for this thanks to @ondrejvaroscak).
How to install recovery and root your x compact:
Follow this guide and install latest 'Customized UK' Firmware which is 34.2.A.0.311
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
- You will use flashtool to create your own custom kernel
- Flash custom kernel
2. Flash TWRP from here: https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
3. Boot into TWRP and flash SuperSU-v2.79-201612051815.zip
- Note: Did not enter password to decrypt device b/c don't know it
- Click Reboot system
4. SuperSu is installed and you are done.
you have two options for the kernel image; use flashtool and rootkernel (step 1. above) to make a stock boot.img that can be flashed with fastboot, or flash the genesis one if you did not backup/lost you keys, or want some more functionality/options. (with twrp this is important)
dozzo94www said:
It says i must "install the .zip file with twrp" , but how do I get the twrp? Because it says i need a phone with .198 ver.
Click to expand...
Click to collapse
it will do the job just fine.
whether you want to flash twrp or just boot it is up to you, use the command in post#4 to just boot it.
and yeah it does not matter if /data is encrypted just skip it in twrp, supersu can install itself systemless on encrypted /data partition initially using the cache partition to setup things. copy supersu 2.79 to a physical sdcard (that is not encrypted) flash it from there, and of cause do NOT wipe cache/dalvik after flash just reboot. the phone will reboot once while booting setting things up and backing up the original boot.img to /data also. after that your rooted.
personally for starters I would recommend the guide by @ondrejvaroscak
realtuxen said:
you have two options for the kernel image; use flashtool and rootkernel (step 1. above) to make a stock boot.img that can be flashed with fastboot, or flash the genesis one if you did not backup/lost you keys, or want some more functionality/options. (with twrp this is important)
it will do the job just fine.
whether you want to flash twrp or just boot it is up to you, use the command in post#4 to just boot it.
and yeah it does not matter if /data is encrypted just skip it in twrp, supersu can install itself systemless on encrypted /data partition initially using the cache partition to setup things. copy supersu 2.79 to a physical sdcard (that is not encrypted) flash it from there, and of cause do NOT wipe cache/dalvik after flash just reboot. the phone will reboot once while booting setting things up and backing up the original boot.img to /data also. after that your rooted.
personally for starters I would recommend the guide by @ondrejvaroscak
Click to expand...
Click to collapse
OK thks i have rooted...and how can I install Xposed?
dozzo94www said:
OK thks i have rooted...and how can I install Xposed?
Click to expand...
Click to collapse
I believe Xposed for nougat is still in progress.
I'm not able to fastboot into TWRP on my phone.
I have 311 Customized UK installed on my phone with custom stock kernel.
After I do 'fastboot boot twrp.img" my phone reboots and just goes to a blank screen.
Will flashing the twrp.img to recovery make any difference?
butters2 said:
I'm not able to fastboot into TWRP on my phone.
I have 311 Customized UK installed on my phone with custom stock kernel.
After I do 'fastboot boot twrp.img" my phone reboots and just goes to a blank screen.
Will flashing the twrp.img to recovery make any difference?
Click to expand...
Click to collapse
Are you sure you have proper TWRP for the device? I have 311 too and fast boot TWRP without problem.
ondrejvaroscak said:
Are you sure you have proper TWRP for the device? I have 311 too and fast boot TWRP without problem.
Click to expand...
Click to collapse
Figured it out, I was trying to boot TWRP_6.01 and it was not working.
I am able to fastboot TWRP_3.0.2.0.img.
Hi - I've read through almost every thread in this forum and, unless I am missing something - quite possible - I don't think that anybody has mentioned this problem.
I have a bootloader unlocked Boost Moto E4 and I can flash Squid's TWRP (I do get the "Image not signed or corrupt" message) and can boot from the bootloader after the flash into TWRP recovery. However, after I boot into the OS, the TWRP recovery gets overwritten with the stock recovery. Has anybody else bumped into this? Is there a step that I am missing somewhere to make TWRP permanent?
Thanks
D.
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
Your problem is the stock rom flashing the stock recovery when you reboot. If you flash twrp then reboot recovery once before booting the os, it should change a file in /system recovery-from-boot.p to recovery-from-boot.p.bak which will stop the stock recovery flash. You can also mount /system in twrp and use the file manager to change it manually.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Francesco Franz said:
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Click to expand...
Click to collapse
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Sent from my Moto E (4) using XDA Labs
amarc78 said:
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Click to expand...
Click to collapse
than do this flash over default recovery and do reboot. twrp recovery removed from recovery partition on next boot.
also do this flash twrp and do allow modifications. your device ain't gonna boot. if you didn't flash no verity thing.
rooting will make it permanent. it's the same case in both marshmallow and nougat too as OP states his problem in first post.
it will permanent by doing this
fastboot erase recovery (remove default recovery from recovery partition)
than install custom recovery. it will be there no matter if your device is rooted or not.
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
D97 said:
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
Click to expand...
Click to collapse
which step actually help you?
DE SEXIEST said:
which step actually help you?
Click to expand...
Click to collapse
Whatever you do don't run "fastbootboot erase" anything unless you know for sure what by you're doing or you can screw up your partitions. I have flashed twrp many times with only running "fastboot flash recovery...", then flashing one of numerous zips to disable dmverity and forced encryption. As long as you have the option in twrp under " mount" that says "mount system read only" not checked and you may need to reboot twrp afterwards, twrp should stick. Flashing Magisk directly after the stock rom should also solve your problem and disable dmverity.
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: