Database Users

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)

root 4.2.2. without flashing customer recovery

Good morning guys,
I see a lot of threads here about rooting 4.2.2, but in all of them it is recommended to root the phone by installing zip archive from a custom recovery.
I don't want to change stock recovery - is there any way to root it by flashing img from adb? I did it in this way on 4.2.1, by installing CF-Auto-Root-mako-occam-nexus4.img file from adb.
Can anyone advice how to get root without flashing custom recovery?

I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.

Look at this How to thread in the general section, I copied and pasted relevant information. I kept a custom recovery and didn't try this method, but it says it will not flash a custom recovery.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.

You can flash custom recovery via fastboot, use it to install su.zip and when you will choose restart after that, you will have question about you want custom recovery permanently or not, if you choose no then after restart you will have stock recovery

scottspa74 said:
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Click to expand...
Click to collapse
I want to make installing of future OTA as simple as possible. So I will get root and freeze all the system apps i don't want to be run, but when OTA comes I will be able to install it and will not receive any error messages which i had during this OTA.
It seems like this is a good solution:
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
Click to expand...
Click to collapse
Do i understand correctly that this boots customer recovery on my phone from PC hard drive, but doesn't flash it to the phone? So, I'm able to install root.zip from it, but when i reboot the phone I don't have a custom recovery.

You can do as i mentioned in my post before or you can use as well command mentioned by ketjr81: fastboot boot nameofrecovery.img in both cases you will have had stock recovery after restart

Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.

fatum2002 said:
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
Click to expand...
Click to collapse
you find it in thread mentioned by ketjr81

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.

Z5 Premium Dual e6883 Rooting

So I've had a bit of a look around and there doesn't seem to be that many "noob" friendly rooting how to's, i have a z5 premium dual e6883 and i have unlocked the bootloader but have yet to root it.
I've tried and failed so is there anyone out there who can help me out.
i have never done this before and would like an experienced person to recommend a kernel or whatever it is that i need to root my device.
Kind Regards

shaxta said:
So I've had a bit of a look around and there doesn't seem to be that many "noob" friendly rooting how to's, i have a z5 premium dual e6883 and i have unlocked the bootloader but have yet to root it.
I've tried and failed so is there anyone out there who can help me out.
i have never done this before and would like an experienced person to recommend a kernel or whatever it is that i need to root my device.
Kind Regards
Click to expand...
Click to collapse
Check both development forums for how to do this. There are threads there on this.
Sent from my SGP311 using XDA Labs

This thread should help
http://forum.xda-developers.com/z5-premium/general/root-z5-premium-dual-t3381919
It's installing the custom kernel through adb then installing a recovery (twrp) through adb. After going into recovery (as the phone boots, wait for the notification light to turn orange, it takes about 5-7 seconds, then press and hold the volume up button), flash the SuperSU zip you downloaded from the forum. Now you're rooted.

houboy said:
This thread should help
http://forum.xda-developers.com/z5-premium/general/root-z5-premium-dual-t3381919
It's installing the custom kernel through adb then installing a recovery (twrp) through adb. After going into recovery (as the phone boots, wait for the notification light to turn orange, it takes about 5-7 seconds, then press and hold the volume up button), flash the SuperSU zip you downloaded from the forum. Now you're rooted.
Click to expand...
Click to collapse
Thanks, i tried following this thread and it was successful untill I tried to flash, I'm not really 100% sure what adb is either, i posted a comment on that thread with the error that happened through the command window.

shaxta said:
Thanks, i tried following this thread and it was successful untill I tried to flash, I'm not really 100% sure what adb is either, i posted a comment on that thread with the error that happened through the command window.
Click to expand...
Click to collapse
You would have to install adb, it is used through the command prompt. Installing the Sony flashtool would be really useful, it would install adb for you and you can install firmware updates (since once you root and install a custom ROM, you cannot update through OTA). Once you install all of the Sony drivers needed, your phone would be recognized when in fastboot mode and you can follow the command lines in that thread to install a custom kernel and recovery (twrp) to flash a ROM.

shaxta said:
Thanks, i tried following this thread and it was successful untill I tried to flash, I'm not really 100% sure what adb is either, i posted a comment on that thread with the error that happened through the command window.
Click to expand...
Click to collapse
first, download latest SuperSU and put it in your SD CARD
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
now ...
@khab.bros posted and collected modified kernels at
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!nwxUXSCY
main thread is
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
update your device to latest .254 rom
just download the E6883 Boot.img file from above
flash kernel by using FLASHTOOL
http://www.flashtool.net/downloads.php ( click the thunder button >> fastBoot Mode>> select kernel to flash >> it will ask u to connect device while holding volume UP key, (make sure device is switched off) , after deduction it will ask the location of the kernal, point it to the E6883.img file)
and you are DONE!!!!!!!!!
boot your device,
toggle volume up while on WHITE screen (led light goes amber)
you will go recovery,
install from sd card,, flash the super SU,
reboot,
DONE

Thanks
YasuHamed said:
first, download latest SuperSU and put it in your SD CARD
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
now ...
@khab.bros posted and collected modified kernels at
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!nwxUXSCY
main thread is
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
update your device to latest .254 rom
just download the E6883 Boot.img file from above
flash kernel by using FLASHTOOL
http://www.flashtool.net/downloads.php ( click the thunder button >> fastBoot Mode>> select kernel to flash >> it will ask u to connect device while holding volume UP key, (make sure device is switched off) , after deduction it will ask the location of the kernal, point it to the E6883.img file)
and you are DONE!!!!!!!!!
boot your device,
toggle volume up while on WHITE screen (led light goes amber)
you will go recovery,
install from sd card,, flash the super SU,
reboot,
DONE
Click to expand...
Click to collapse
Thank you so much!
It was so simple i just didnt have the right files.
It worked flawlessly with your advice, thanks again much appreciated.

Stuck
YasuHamed said:
first, download latest SuperSU and put it in your SD CARD
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
now ...
@khab.bros posted and collected modified kernels at
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!nwxUXSCY
main thread is
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
update your device to latest .254 rom
just download the E6883 Boot.img file from above
flash kernel by using FLASHTOOL
http://www.flashtool.net/downloads.php ( click the thunder button >> fastBoot Mode>> select kernel to flash >> it will ask u to connect device while holding volume UP key, (make sure device is switched off) , after deduction it will ask the location of the kernal, point it to the E6883.img file)
and you are DONE!!!!!!!!!
boot your device,
toggle volume up while on WHITE screen (led light goes amber)
you will go recovery,
install from sd card,, flash the super SU,
reboot,
DONE
Click to expand...
Click to collapse
thanks for the reply
Im stuck yet again after flashing super SU and rebooting its now stuck on the "Android is starting... starting apps" its been on this screen for about an hour now and the battery will most likely die soon, is there a way to fix this? was there something i did wrong? i followed the steps correctly.

shaxta said:
thanks for the reply
Im stuck yet again after flashing super SU and rebooting its now stuck on the "Android is starting... starting apps" its been on this screen for about an hour now and the battery will most likely die soon, is there a way to fix this? was there something i did wrong? i followed the steps correctly.
Click to expand...
Click to collapse
seems like u downloaded wrong boot.img (kernal)
what is your device???
this kernal is ONLY for .254 update (released 6july2016)
if you have flashed wrong kernal! then DOWLOAD FULL ftf file (2.5GB using FLASHTOOL (experifirm))
and FLASH original .254
than dowload stock modified kernal and flash kernal as i told above...

YasuHamed said:
seems like u downloaded wrong boot.img (kernal)
what is your device???
this kernal is ONLY for .254 update (released 6july2016)
if you have flashed wrong kernal! then DOWLOAD FULL ftf file (2.5GB using FLASHTOOL (experifirm))
and FLASH original .254
than dowload stock modified kernal and flash kernal as i told above...
Click to expand...
Click to collapse
This is what i have on the modified kernal site you provided, there isnt a .254 i downloaded and flashed the .253 version.

Help
Can somebody please help me out.

shaxta said:
Can somebody please help me out.
Click to expand...
Click to collapse
sorry for the typo .253 is the latest one, go in side the folder .253 and download your versions .img file
rest procedure is unchanged as explained before

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.