Database Info

Encrypted phone now cant use CWM backup and adb

Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh

Anybody have any ideas?

Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks

Bump...................

voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps

Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards

kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot

kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks

voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.

Any luck???

kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted

voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?

kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.

voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img

kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .

voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent

kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok

voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees

kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck

Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/

[Q] HELP!!! Bricked Moto G GPE 5.0.1 No Device Found

Help Please!!! I need help reloading my Moto G 2013. I had android 5.0.1 running on it but I was not able to perform a device wipe. I read somewhere that encrypting and decrypting could be a workaround, so I decided to do that. Encrypting took less than 10 mins and the hone got stuck in a restart loop. So I tried flashing it with ADB and now I get the android man laying fat with the red triangle. I am guessing no more operating system.
I have tried making use of adb to load the rom but I keep getting the error no device found. I have tried every single process online. It is the google play edition xt1032 I have.
Thank you.

Can u reach recovery mode? Or bootloader

tdjeans said:
Help Please!!! I need help reloading my Moto G 2013. I had android 5.0.1 running on it but I was not able to perform a device wipe. I read somewhere that encrypting and decrypting could be a workaround, so I decided to do that. Encrypting took less than 10 mins and the hone got stuck in a restart loop. So I tried flashing it with ADB and now I get the android man laying fat with the red triangle. I am guessing no more operating system.
I have tried making use of adb to load the rom but I keep getting the error no device found. I have tried every single process online. It is the google play edition xt1032 I have.
Thank you.
Click to expand...
Click to collapse
That red triangle android robot is stock recovery. There should be a hardware key combination to wipe cache try searching on google. If all else fails then reboot to bootloader by using hardware key combination and perform a factory reset using fastboot.

Thank you for the help. I was able to get it fixed by flashing TWRP and the sideloading 4.4.4 on the phone. But I noticed the screen flickers for the first few minutes the phone is on. I also tried to update to 5.0.1 via OTA but after download, the phone restarted and instead of installing the 5.0.1, it booted to TWRP recovery. I want to know if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2542219, will I be able to remove the TWRP and have my stock recovery back and then be able to update via OTA. Also, I noticed I still cannot do a factory reset, the phone just restarts and everything remains the same.
skyguy126 said:
That red triangle android robot is stock recovery. There should be a hardware key combination to wipe cache try searching on google. If all else fails then reboot to bootloader by using hardware key combination and perform a factory reset using fastboot.
Click to expand...
Click to collapse

tdjeans said:
Thank you for the help. I was able to get it fixed by flashing TWRP and the sideloading 4.4.4 on the phone. But I noticed the screen flickers for the first few minutes the phone is on. I also tried to update to 5.0.1 via OTA but after download, the phone restarted and instead of installing the 5.0.1, it booted to TWRP recovery. I want to know if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2542219, will I be able to remove the TWRP and have my stock recovery back and then be able to update via OTA. Also, I noticed I still cannot do a factory reset, the phone just restarts and everything remains the same.
Click to expand...
Click to collapse
In order to do any factory resets or ota you must have stock recovery installed or else android cannot communicate properly with recovery for commands and such.

Ok. Thank you. I have reloaded to stock firmware and done an OTA update to 5.0.1.
skyguy126 said:
In order to do any factory resets or ota you must have stock recovery installed or else android cannot communicate properly with recovery for commands and such.
Click to expand...
Click to collapse

I finally was able to with TWRP.
instinctblade said:
Can u reach recovery mode? Or bootloader
Click to expand...
Click to collapse

[Completed] Can't install OTA update on HTC One M8

So, My phone was rooted and I unlocked the bootloader. I have relocked bootloader and flashed my stock recovery so I can update to Marshmallow. Here is the problem:
When the update downloads and verifies the phone usually reboots so it can download. The progress bar doesn't even finish and the phone opens the recovery which shows State 7 installation aborted. Running stock OS 5.0.1 Lollipop. Help is aprecciated

Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here

Recovery errors?
HeckNoTechnO said:
Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here
Click to expand...
Click to collapse
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.

DreamFantom said:
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.
Click to expand...
Click to collapse
I think in your situation to get stock recovery on your device you may want to use the RUU method.
Sent from my Nexus 6 using Tapatalk

For those wondering about XT1644 root

Just got my XT1644 G4 Plus 16GB here in America and brought it home for some testing.
Everything was a piece of cake, I did these things in order with no issues. There are other guides for these things all over XDA so I won't be giving detailed instructions.
Unlocked the bootloader here - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Installed TWRP from here. - http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
And flashed SuperSU from here - https://download.chainfire.eu/696/supersu/
When TWRP first boots it will ask if you want to run in systemless mode. Make sure you tell it YES!!!
Rebooted on the first try with no issues.

I have Xposed installed with a few modules and it works great.
Sent from my Moto G (4) using Tapatalk

Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.

mystx2112 said:
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
Click to expand...
Click to collapse
Can extract it from the stock ROM here: https://www.androidfilehost.com/?fid=24572369242687085

not sure if this is full proof i got bootloop

After flashing SuperSu 2.76 the phone is stuck forever at the "moto" logo. Is it because I'm using such a new version of SuperSu? Why do you use 2.46?

How long did it take to get the unlock code? I am waiting for a couple hours now...
LE: 4 hours... and finally I got the code.

Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.

craigl14 said:
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
Click to expand...
Click to collapse
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.

I can't get twrp to install. I keep getting told that the image is not signed or corrupt

First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.

SoNic67 said:
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
Click to expand...
Click to collapse
that's just it... I can't boot to twrp. It's not there.

Where? You can't find it on the SD by browsing in the recovery?

because that's just it, there's nothing in recovery. This has gotten so convoluted that I don't even know what I'm supposed to have where....

@davidkoby
Stock ROM Recovery starts with a "Dead Android" and "no command" written under it, it is you see or something else?

Does supersu need to be in systemless mode?

craigl14 said:
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
Click to expand...
Click to collapse
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.

sam9s said:
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
Click to expand...
Click to collapse
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.

craigl14 said:
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
Click to expand...
Click to collapse
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy

sam9s said:
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
Click to expand...
Click to collapse
Hmmmm...I don't know if you have XT1644. Most who have that version are still waiting on OTA I think and certainly didn't get it month's ago. It is the G4 Plus North American version. If you still have the box it will be on the UPC label. It will also be in your phone info in settings once your phone works again. Did your phone work fine before you tried to root it? Anyway, Nougat will not root with this method. If you can boot into recovery, try factory reset. If that doesn't work, you're going to have to reflash the Nougat ROM...make sure you get the right one for your phone. You will need to search around on this forum for instructions and which download to get, etc. Once you have Nougat up and running again, you will need to leave it unrooted or use one of the proven methods of root. Again, I don't think systemless supersu works for Nougat. I have no idea what bad key means. The only thing I've ever had is "N/A" come up in the unlock warning. Incidentally, you can get rid of the bootloader warning screen if you want to.

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.

After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?

audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.

Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.

audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!

I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.

TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?

I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...

download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck

hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...

kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda

audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.

kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/

Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...