Database Users

Install CWM on Locked Bootloader

Can i install CWM on locked bootloader?

Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.

Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App

@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"

SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.

GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium

Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.

GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App

Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.

Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.

well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me

Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.

junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.

[Q] Problem with TWRP in rooted and unlocked nexus 10

Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english

The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.

3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..

All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...

prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app

same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.

[Q] best way to upgrade TWRP ?

currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?

Use goomanager. It's by far the easiest since it's mostly automated.

mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,

oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?

mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD

Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app

theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP

you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.

Recovering data from factory reset Axon 7

Hey guys,
So about 3 weeks ago my Axon 7 reset itself in my pocket. This was days after I had updated to Android N. I have not used the phone since then as I have combing the internet for any possible way to recover the data from it. It would be nice if you can provide a solution that does not require rooting.
However, most solutions I have looked into need root access in some form or fashion, so I am not entirely averse to rooting. Since I am currently running Android N, I have been unable to find a way to root it without unlocking the bootloader (or root it at all). If the bootloader MUST be unlocked for me to be able to recover my data then could you please tell me a way to relock it afterwords. Also, I would prefer to return the phone to an unrooted condition after attempting data recovery since certain apps (such as Pokemon Go) will not run on a rooted phone.
The best solution I have found so far is that I root the phone (preferably without unlocking bootloader) and then dump an image of all the partitions for a recovery software such as Recuva, Testdisk, or Photorec to scan through. I am not sure if this requires flashing TWRP (I am an extreme newbie to this). I could potentially also just root the phone then try to run an android recovery software such as Asoftech. The last solution I have found is getting the phone to be recognized as a mapped drive for Photorec to scan successfully.
Presumably all of these methods NEED the phone to be rooted. If you have any ideas where these solutions can be implemented without rooting please post.
Before you ask, I did not have Google Photos sync on and had not backed up the data from it. Please only give pertinent solutions and not snarky remarks about how I should have been smarter and made backups and am now screwed. I realize that, but am hoping that maybe someone on here can help.

https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en
There's at least 3 guides on how to root the phone.

bornlivedie said:
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en
There's at least 3 guides on how to root the phone.
Click to expand...
Click to collapse
Sorry for my seeming ignorance. I'm quite the newbie to this. Can you please tell me if the process would be the same for Nougat B15? Because the following link gives instructions for rooting without unlocking bootloader, but does not appear to have the .zip file for the B15 software version.
Link: https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
If yes, can you please link me to these guides?
Thanks for the disk digger suggestion. I will be sure to try that.

tupurl said:
Sorry for my seeming ignorance. I'm quite the newbie to this. Can you please tell me if the process would be the same for Nougat B15? Because the following link gives instructions for rooting without unlocking bootloader, but does not appear to have the .zip file for the B15 software version.
Link: https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
If yes, can you please link me to these guides?
Thanks for the disk digger suggestion. I will be sure to try that.
Click to expand...
Click to collapse
It's the same, yes.
I used tennear's (not to be confused with tenfar) tool to flash signed TWRP:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
and then unlock the bootloader with this:
https://www.androidfilehost.com/?fid=24723757092307343
Here are the required drivers for your computer:
http://www.filedropper.com/qualcommqusbbulkdrivers
The recovery must be named recovery.bin and not .img or any other name/extension
And the command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery

bornlivedie said:
It's the same, yes.
I used tennear's (not to be confused with tenfar) tool to flash signed TWRP:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
and then unlock the bootloader with this:
https://www.androidfilehost.com/?fid=24723757092307343
Here are the required drivers for your computer:
http://www.filedropper.com/qualcommqusbbulkdrivers
The recovery must be named recovery.bin and not .img or any other name/extension
And the command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Click to expand...
Click to collapse
Thank you so much for this detailed explanation! One last question, is it possible to relock the bootloader after this? If not, does this work without unlocking the bootloader? And how difficult is it to unroot the phone? Again, I'm really sorry for pestering you with this.

tupurl said:
Thank you so much for this detailed explanation! One last question, is it possible to relock the bootloader after this? If not, does this work without unlocking the bootloader? And how difficult is it to unroot the phone? Again, I'm really sorry for pestering you with this.
Click to expand...
Click to collapse
Sorry, In fact, you can actually root without unlocking your bootloader, so don't flash that zip.
Just flash SuperSU 2.79
And yes, you can relock, but you must be completely stock before doing so.

bornlivedie said:
Sorry, In fact, you can actually root without unlocking your bootloader, so don't flash that zip.
Just flash SuperSU 2.79
And yes, you can relock, but you must be completely stock before doing so.
Click to expand...
Click to collapse
So in summary:
Download tennear's axon7tool and use it to flash SuperSU 2.79.
Then do the following and I should be able to perform an image dump?
Name file recovery.bin and not .img or any other name/extension
And use this command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Question: So in a comment in his guide, tennear mentions that the tool writes out the raw partition when taking the backups. So, theoretically, can I just use the tool to write out an image of the system partition for a program like TestDisk to scan?
(TestDisk and PhotoRec are programs that can scan through mapped drives or partition images in order to recover data from them)
If this is not possible, is flashing SuperSU enough to give me the permissions to perform an image dump without unlocking bootloader? And to go back to unrooted condition do I just unflash SuperSU?
(Sorry for all these questions. I really appreciate your help. You're a real lifesaver since I've been wrestling with trying to recover data from the phone for almost a month.)

tupurl said:
So in summary:
Download tennear's axon7tool and use it to flash SuperSU 2.79.
Then do the following and I should be able to perform an image dump?
Name file recovery.bin and not .img or any other name/extension
And use this command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Question: So in a comment in his guide, tennear mentions that the tool writes out the raw partition when taking the backups. So, theoretically, can I just use the tool to write out an image of the system partition for a program like TestDisk to scan?
(TestDisk and PhotoRec are programs that can scan through mapped drives or partition images in order to recover data from them)
If this is not possible, is flashing SuperSU enough to give me the permissions to perform an image dump without unlocking bootloader? And to go back to unrooted condition do I just unflash SuperSU?
(Sorry for all these questions. I really appreciate your help. You're a real lifesaver since I've been wrestling with trying to recover data from the phone for almost a month.)
Click to expand...
Click to collapse
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.

bornlivedie said:
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.
Click to expand...
Click to collapse
This leaves the bootloader untouched which is awesome. I really appreciate the help.
So, flashing SuperSU 279 gives me the super user privileges I need to perform an image dump of the data partition correct (will be using adb shell for this)? Or qualifies the phone as having root access for software like DiskDiggerPro to be able to scan and recover files from?
Out of curiosity, what exactly is it that the axon7tool does? I got the impression that it can write out raw images of the boot, recovery, and gpt partitions separately and then can be used to flash the signed TWRP. Is this not true? Does it only read those and flash the signed TWRP? And if it can write raw images can it write an image of the data partition? I'd guess not, but wanted to know your thoughts.
I know I said last question like many questions ago, but final question, what is the process to unroot the phone (in case it turns out I can't use certain apps in a rooted condition)? Do I just remove the signed TWRP and SuperSU279?
I really truly appreciate all the help you have provided. You are truly a lifesaver. (There aren't enough thanks that I can give.)

Pretty sure you have to unlock to root but good luck.

bornlivedie said:
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.
Click to expand...
Click to collapse
So I have managed to successfully flash the SIGNED TWRP but every time I try to flash SuperSU from the zip file you linked TWRP crashes. I read on another post that I should try the SuperSU v2.79 SR3 version but TWRP crashes while trying to install it too. (By crash I mean it freezes while installing and then turns the device off. Upon reboot, the SuperSU app is not present on the phone.)
Is there any way I can successfully flash SuperSU without having to format data or unlock bootloader?
EDIT: I just tried to use adb sideload through TWRP to flash SuperSUv2.79 and in the command window it successfully got to ~75% before it stopped, the phone turned off, and it gave an error of " * failed to read command:" When the I tried the same with SuperSUv2.79-SR3, it got to ~77% before stopping, turning off and giving the same error.
Any ideas why this might be failing and how to fix it?

tupurl said:
So I have managed to successfully flash the SIGNED TWRP but every time I try to flash SuperSU from the zip file you linked TWRP crashes. I read on another post that I should try the SuperSU v2.79 SR3 version but TWRP crashes while trying to install it too. (By crash I mean it freezes while installing and then turns the device off. Upon reboot, the SuperSU app is not present on the phone.)
Is there any way I can successfully flash SuperSU without having to format data or unlock bootloader?
EDIT: I just tried to use adb sideload through TWRP to flash SuperSUv2.79 and in the command window it successfully got to ~75% before it stopped, the phone turned off, and it gave an error of " * failed to read command:" When the I tried the same with SuperSUv2.79-SR3, it got to ~77% before stopping, turning off and giving the same error.
Any ideas why this might be failing and how to fix it?
Click to expand...
Click to collapse
You need to flash tenfars b27 and follow his guide.

lafester said:
You need to flash tenfars b27 and follow his guide.
Click to expand...
Click to collapse
So downgrade to B27 then follow his guide?

tupurl said:
So downgrade to B27 then follow his guide?
Click to expand...
Click to collapse
If you want root without unlock.

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.