Database Users

[RECOVERY][APP][TWRP/CWM/PhilZ]Recovery Collection

After @Envious_Data and me discovered that there is no real collection for the most up-to-date recoveryimages, for both stock and AOSP based Roms we decided to create this thread in order to change this.
Recoverys:
CWM Recovery 6.0.5.1
PhilZ Touch Recovery 6.59.0 (CWM Version 6.0.5.1)
TWRP 2.8.3.0 (2.8.1.0 recommend as 2.8.3.0 is not starting on some Roms)
Installation
Download the recovery images in the Download section reboot your phone into fastboot mode and execute the command
Code:
fastboot flash recovery *name of the recoveryimage you downloaded*.img
in fastboot.
When you want to flash it from your phone, navigate into the folder where you downloaded the recoveryimage and execute the command:
Code:
dd if="*name of the recoveryimage you downloaded*.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
as root in Terminal Emulator.
If you are lazy you can also use my App, M5-Settings. It automatically downloads the most up-to-date recoveryimage to your externel SD Card and flashes the recoveryimage to your FOTAKernel Partition.
Download:
CWM Recovery
PhilZ Touch Recovery
TWRP
M5-Settings
Sources:
CWM Recovery
PhilZ Touch Recovery
TWRP (download currently linking to the reupload prebuilt 2.8.1.0 official recoveryimage, never builds will be compiled from source)
M5-Settings​
XDA:DevDB Information
Recovery Collection, Tool/Utility for the Sony Xperia Z2
Contributors
Myself5, Envious_Data
Version Information
Status: Stable
Created 2015-01-10
Last Updated 2015-01-12

Reserved

Ding
Reserve post incase i want to post anything

Hi Both,
I want to get the M5Kernal and flash it on a CM12 that has cyanogenmod recovery
So which Recovery do you suggest and which version which will make this process an easy one.
I tried to flash TWRP (forgot the version) but it would show everything pixelated with horizontal lines making nothing readable nor functional.
Edit: I have flashed Philz, flashed M5KernelV2 and guess what, phone stuck at "Android is upgrading.. Starting apps" for the past 3 minutes.
I'll give it some time and update
Edit: So it wouldn't boot and I had to wipe it fully and tried again, all good.
Best of all, the recovery actually "sticks"
Regards

Hmm, you should probably mention that you need to unlock your bootloader first? unless I'm mistaken..

behelit said:
Hmm, you should probably mention that you need to unlock your bootloader first? unless I'm mistaken..
Click to expand...
Click to collapse
Not exactly
You cant use fastboot on xperias if the bootloader is locked
I dont think fotakernel/recovery is a part of the bootloader (likely hence why we cant boot right into recovery)
You do need a custom kernel to use recovery
But to install it i think is a different case, im not experianced all too much with locked bootloaders so this info is based off of a conversation between a bunch of devs

can I use this one on a ROOTED STOCK ROM in 4.4.2 and build .137?!

mcjez15 said:
can I use this one on a ROOTED STOCK ROM in 4.4.2 and build .137?!
Click to expand...
Click to collapse
as the post above yours says, you need a custom Kernel to use a FOTAKernel Partition. I'd recommend Advanced Stock Kernel by AndroPlus or AndroPlusKernel

@Myself5 i tried instal twrp from your awesome app after an format and updated my device to lollipop stock and back to cm12 but anytime the device boot in cyanogenmod recovery its somthing with bootloader changed at lollipop?

Will any of the recoveries work on Locked Bootloader running Android 5.0.2?

CrazyGamerGR said:
Myself5 i tried instal twrp from your awesome app after an format and updated my device to lollipop stock and back to cm12 but anytime the device boot in cyanogenmod recovery its somthing with bootloader changed at lollipop?
Click to expand...
Click to collapse
Hum should be working fine... I'll take a look at it, got to update the recovery anyways.
yavhin said:
Reserved
Click to expand...
Click to collapse
Dafuq ?

When will there be a recovery for lollipop?

All recoverys are already compatible with Lollipop.

I thought the "fastboot flash recovery...." command is not valid on Sony's world as the recovery partition is combined in kernel? I always thought the kernel and the recovery must be united then flashed with "fastboot flash boot ....." command? Am I wrong?
Sent from my Xperia Z2 using XDA Free mobile app

_delice_doluca_ said:
I thought the "fastboot flash recovery...." command is not valid on Sony's world as the recovery partition is combined in kernel? I always thought the kernel and the recovery must be united then flashed with "fastboot flash boot ....." command? Am I wrong?
Sent from my Xperia Z2 using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
the recovery partition isnt 100% independant so you need a kernel that supports fotakernel (recovery partition)
but they are separate, boot and recovery

Myself5 said:
All recoverys are already compatible with Lollipop.
Click to expand...
Click to collapse
wut? So you mean philz recovery is working for locked bootloaders if I update to lollipop? Is there any guide on how to flash the recovery when updated?

really ?
Myself5 said:
All recoverys are already compatible with Lollipop.
Click to expand...
Click to collapse
hey so can you tell me where to find a compatible one with my z2 5.0.2
thx

romdroid. said:
wut? So you mean philz recovery is working for locked bootloaders if I update to lollipop? Is there any guide on how to flash the recovery when updated?
Click to expand...
Click to collapse
As the post right above yours says, you need a kernel which supports loading Recoverys from FOTAKernel Partition (if you run stock, I'd recommend either advanced Stock Kernel or AndroPlus Kernel, both made by @AndroPlus), which both need a unlocked bootloader in order to work, so the answer to your question is no, it does NOT work on locked bootloader, for LB you might want to try XZDualRecovery.
ryan42680 said:
hey so can you tell me where to find a compatible one with my z2 5.0.2
thx
Click to expand...
Click to collapse
You are kidding me, right? READ THE OP!

I did and i didnt find nothing. As far as i know we need to run a bat file to fix it if you are running stock xperia lp. You can find a link in their thread.
http://forum.xda-developers.com/showthread.php?p=59879026

Recovery doesn't stick
So I downloaded your awsome m5-settings app and tryed to installed twrp recovery on my z2, running cm12. Booted into recovery, and twrp came up (instead of cm recovery). But it doesn't "stick". I can't press any buttons, and after approximately 10-20 seconds the phone reboot normal again. I've tried to use cwm also, but twrp still shows up and doesn't work. Last resort I tried philz, but still got twrp.
I also tried to run fotacwm img, thru terminal emulator. But nothing works.
All I want is a custom recovery that works, since CM 12 recovery is useless!!
Btw. I'm a noob, so please be gentle against me
Ps: I added a screenshot of the phone details. It's in Norwegian, but I guess you understand (sorry)

[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

Android N Root Working(Explained)

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/

TWRP (Boost) flash doesn't stick

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.