Database Info

Did i brick it???

Hello
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated

moosehead11 said:
Hello
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated
Click to expand...
Click to collapse
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app

noahvt said:
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I've tried flashing stock Asus a few different times either form fastboot, twrp or sideload none seem to work...given i can't boot should i be worried if i decided to wipe data, format system or just doing a factory reset before trying again

What error does it give when you try to flash?
Sent from my sensational HTC Desire C

noahvt said:
What error does it give when you try to flash?
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?

moosehead11 said:
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?
Click to expand...
Click to collapse
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app

noahvt said:
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app

moosehead11 said:
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C

noahvt said:
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
So you are flashing the stock asus rom twice?
Sent from my GT-I9000 using xda app-developers app

Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?

sbdags said:
Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?
Click to expand...
Click to collapse
Yes...after flashing the ROM in twrp and rebooting i get the blue bar

moosehead11 said:
Yes...after flashing the ROM in twrp and rebooting i get the blue bar
Click to expand...
Click to collapse
And what happens if you leave it for 20 mins to boot?

sbdags said:
And what happens if you leave it for 20 mins to boot?
Click to expand...
Click to collapse
reflashing as we speak...i've left it going for about 30min on one attempt and it just kept "loading"
i did notice that if i check the file verification before flashing it fails to verify the zip...is that normal?
UPDATE: Left it for 2hrs while i sent out to do something when i got back still "loading"

Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C

noahvt said:
Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
is it normal for the zip to fail verification in twrp?

Yes it's normal disable that verification!
Sent from my sensational HTC Desire C

noahvt said:
Yes it's normal disable that verification!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Well i tried your method and still no go
What would happen if i tried an older Asus rom from the 4.1 bootloader...would that maybe fix things
Sent from my GT-I9000 using xda app-developers app

you could try BUT REMEMBER AFTER FLASHING IN FASTBOOT: FLASH THE 4.1 TWRP!!!!!!
Sent from my Transformer Pad TF300T using xda app-developers app

Can't read any Storage

Well, i tried to root my TF300t today, from 4.2.1 official ROM.
I installed TWRP 2.5.0.0 then 2.6.3.0 as well as some root files. Then i installed this rom,with the root file included as well as 2.6.3.1 TWPR.
I entered the OS, but i could not get WIFI.Then i rebooted to TWPR and since then i cannot do anything.
Firstly, TWPR asks me for some password which i have no clue what kind of pass it might be.
Then i pressed back, and i entered the TWPR menu, where i found out that i don't have access to and kind of memory.Neither internal or external SD as well as i can't log into OS.
Also, when i tried to do some wipes, i could not wipe dalvik cache.
When i go to restart to OS from TWPR, i get a message "No OS Installed! Are you sure you wish to power off?" message.
Also, i get this message: "Install SuperSU? your device does not apear to be rooted. Install SuperSU now?This will root your device"
This is doing absolutely nothing.It does not instal Root.
UPDATE: Ok.I managed to get ext SD card to be mounted.In ext sd card i have some android 4.4 (see above which version on the link) but i am unable to instal it.
Error Message : "Unable to open zip file."
When i try to instal root i get a Success Message but it keeps saying to me that no root installed.
Any idea what is wrong?

Probably the version of your bootloader does not match the version of TWRP you installed.
Can you get to the bootloader screen to check the exact version number on the top-left?
Sent from my TF300T using Tapatalk

f69m said:
Probably the version of your bootloader does not match the version of TWRP you installed.
Can you get to the bootloader screen to check the exact version number on the top-left?
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Bootloader screen has these:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol

TheoKondak said:
Bootloader screen has these:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
OK, that is the latest version.
Did you pick the TWRP with -42 in the name or scanno's version from the OmniROM thread?
The latter should be used for 4.4-based (kitkat) ROMs.
Neither the -ics nor the -jb versions work with your bootloader.
Sent from my TF300T using Tapatalk

f69m said:
OK, that is the latest version.
Did you pick the TWRP with -42 in the name or scanno's version from the OmniROM thread?
The latter should be used for 4.4-based (kitkat) ROMs.
Neither the -ics nor the -jb versions work with your bootloader.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
I used the 4.4-based TWPR.
Well, i think that the problem occured when i cleared the System Data.Now system data shows 0mb (Internal Storage (0mb) ).Also, if i try to wipe System or data or internal storage i keep geting a "failed" message.
E: Unable to wipe '/data' probably because i don't have access to it.

You need to reboot fully into android after flashing recovery. That's why twrp doesn't work and asks for password when u don't.
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4

I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?

TheoKondak said:
I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?
Click to expand...
Click to collapse
Thats a ME301 ROM you linked too. Did you mean the tf300t version of it?

TheoKondak said:
I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?
Click to expand...
Click to collapse
Try erasing most partitions via fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot erase misc
fastboot erase recovery
Then reflash TWRP and try again.
Somewhere in the threads is a list of all partitions you can erase, but above list should be a good start.
EDIT: Instead of flashing TWRP, you might first flash Asus ROM via fastboot and boot that.
Then reflash TWRP, wipe and flash custom ROM.
Sent from my TF300T using Tapatalk

Thank you very much.
I did wipe all these couple of times.Some of them deny access or there are no data at all to delete so i get a failed message.
So, let me sum what i have to do.
1. Install Stock Asus 4.1.1 http://forum.xda-developers.com/showthread.php?t=1893714
2.Install a new TWRP openrecovery-twrp-2.6.3.0-tf300t-ICS.blob
3. Go in TWRP do a data wipe, cache wipe
4.Flash a new custom rom.
5. Flash latest TWRP.
Please confirm that these are the correct steps.I got chills after this adventure!Even though i am familiar with android rooting and ROM flashing, TF300t seems to be a whole new chapter.

TheoKondak said:
Thank you very much.
I did wipe all these couple of times.Some of them deny access or there are no data at all to delete so i get a failed message.
So, let me sum what i have to do.
1. Install Stock Asus 4.1.1 http://forum.xda-developers.com/showthread.php?t=1893714
2.Install a new TWRP openrecovery-twrp-2.6.3.0-tf300t-ICS.blob
3. Go in TWRP do a data wipe, cache wipe
4.Flash a new custom rom.
5. Flash latest TWRP.
Please confirm that these are the correct steps.I got chills after this adventure!Even though i am familiar with android rooting and ROM flashing, TF300t seems to be a whole new chapter.
Click to expand...
Click to collapse
Yeah, thanks to Asus for all those incompatible bootloader versions.
Those steps look basically right to me, just some remarks:
Pick the latest Asus ROM 10.6.1.27.5. If you don't find it in the tread, download from Asus web site.
According to your bootloade version, make sure it is the "WW" version (not "US" or "JP", etc.).
After step one, before flashing TWRP, actually boot into the Asus ROM once.
Step 5 should not be necessary, as flashing a custom ROM should leave your recovery untouched.
Sent from my TF300T using Tapatalk

Well!I am happy to anounce that i am in my 4.4.2 ROM!Not sure if this is the best Kitkat outhere, but at least my device is not bricked!Thanks all for the help!
I followed the sequence of moves as i posted it above!Thanks everyone for helping!

Stuck on Asus boot screen after custom rom flash

I've flash a couple of custom roms onto my TF300T in the past, recently i tried Omni 4.4.2 but now the pad won't boot past the Asus splash screen. The screen dims / brightens / goes black periodically but never gets past this screen.
I can get back into TWRP 2.7.0.1, I attempt to restore a backup of a previously working state, I've tried to flash different roms, I always factory reset / wipe Dalvik Cache & Cache under advanced.
I can connect with adb too so I'm hopeful there's something that can be done.
I keep reading I need bootloader 4.2, this is what I currently have:
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.4.2.9-20120809" A03
But where do you get updated bootloaders? I can't find them anywhere.

Dude, latest version is 10.6.1.27.5! So I guess you have to flash the latest ASUS ROM first and start all over again...
--> http://www.service.asus.com/#!downloads/c1wax
-search for "TF300T"
-select your model
-select Android as OS
-choose your ROM version (WW or US, depending on where you are living)

Thanks, with fastboot I flash the 4.2 WW Asus rom / blob. Then fastboot flashed recovery of the correct TWRP for 4.2 bootloader. Now I'm off to flash a kitkat rom
UncleManuel said:
Dude, latest version is 10.6.1.27.5! So I guess you have to flash the latest ASUS ROM first and start all over again...
--> http://www.service.asus.com/#!downloads/c1wax
-search for "TF300T"
-select your model
-select Android as OS
-choose your ROM version (WW or US, depending on where you are living)
Click to expand...
Click to collapse

bob_harris said:
Thanks, with fastboot I flash the 4.2 WW Asus rom / blob. Then fastboot flashed recovery of the correct TWRP for 4.2 bootloader. Now I'm off to flash a kitkat rom
Click to expand...
Click to collapse
this is my 1st post. Same problem. Here is my situation.
tf300t unlocked and rooted( it was) I suspect I have lost root.
I was running CM nightlies about 2 times a month. It was very stable. then out of no where it started a boot loop. It would boot untill the profile page would be visible for 6-7 seconds and then reboot.
1st thing I did was install an earlier update but nothing changed.
2nd I wiped delvik, system and cache.
3rd fastbooted US_epad-user-10.6.1.27.1.zip (just the blob) stuck at Boot loop
that removed recovery, so I fastbooted twrp 2.5.0.0
then did a install of the above zip file. that too removed recovery. and stuck at boot loop. (asus)
I have tried so many thing my head is spinning.
please Help

danwhite99 said:
this is my 1st post. Same problem. Here is my situation.
tf300t unlocked and rooted( it was) I suspect I have lost root.
I was running CM nightlies about 2 times a month. It was very stable. then out of no where it started a boot loop. It would boot untill the profile page would be visible for 6-7 seconds and then reboot.
1st thing I did was install an earlier update but nothing changed.
2nd I wiped delvik, system and cache.
3rd fastbooted US_epad-user-10.6.1.27.1.zip (just the blob) stuck at Boot loop
that removed recovery, so I fastbooted twrp 2.5.0.0
then did a install of the above zip file. that too removed recovery. and stuck at boot loop. (asus)
I have tried so many thing my head is spinning.
please Help
Click to expand...
Click to collapse
Shoot me an email, I may have a solution
[email protected]
Thx Josh

[Q] Asus Transformer tf700 freezing randomly

During normal use of the Asus it will freeze. The screen stays frozen until I shut down the tablet manually. When I start the tablet again it boots up and works normally but it is only a matter of time before it freezes again.
I have tried to cold boot it but all that happens is I hold the volume and power buttons down it vibrates but the screen just stays black and there seems to be no affect.
I have limited knowledge with these kind of things but any help is greatly appreciated, thank you in advance.

What's your situation?
Are you on stock? Which version?
Rooted?
Custom rom/recovery? Which one?
If you're on stock it seems to be time for a factory restore from Settings.
Backup everything you care about off the tablet (you can use Asus Backup for this), then go to Settings > Backup & reset and reset the tablet.
Reboot and restore the backup. If you get the same behaviour, do the factory reset again but install your apps a few at a time from the Play Store and test the tablet in between. One of them could be the culprit.

berndblb said:
What's your situation?
Are you on stock? Which version?
Rooted?
Custom rom/recovery? Which one?
If you're on stock it seems to be time for a factory restore from Settings.
Backup everything you care about off the tablet (you can use Asus Backup for this), then go to Settings > Backup & reset and reset the tablet.
Reboot and restore the backup. If you get the same behaviour, do the factory reset again but install your apps a few at a time from the Play Store and test the tablet in between. One of them could be the culprit.
Click to expand...
Click to collapse
It is running android 4.2.1.
Yes it is rooted.
It is a custom recovery. The Recovery is Team Win Recovery Project v2.7.1.1
The Kernel Version is 3.1.10-03bcdcb1 [email protected]#1 Fri Mar 29 17:0432 CST 2013
The Build is JO4OD.WW_epad-10.6.1.14.4-20130329660
I have successfully done the factory reset but it froze in the setup area. I did eventually manage to get through but it still freezes as usual.

Kaij said:
It is running android 4.2.1.
Yes it is rooted.
It is a custom recovery. The Recovery is Team Win Recovery Project v2.7.1.1
The Kernel Version is 3.1.10-03bcdcb1 [email protected]#1 Fri Mar 29 17:0432 CST 2013
The Build is JO4OD.WW_epad-10.6.1.14.4-20130329660
I have successfully done the factory reset but it froze in the setup area. I did eventually manage to get through but it still freezes as usual.
Click to expand...
Click to collapse
Should have elaborated I guess....
Do not do that factory reset from Settings or the bootloader again with a custom recovery installed! You can end up in a nasty forced reboot to recovery loop...
Ok, you are on a current recovery, your bootloader is up to date enough for JB based roms but I would not try to run KitKat roms on it.
Did you ever run a custom rom? Just to confirm your bootloader version, boot with Power and Volume Down buttons and read the tiny script.
That's the only sure way to determine your bootloader version.
If you are on 10.6.1.14.4 you can head over to the Development section and download CROMi-X 5.4.
Boot to TWRP, choose Wipe and just swipe the button to prepare your tablet for a clean installation of CROMi-X.
Once that is done flash CROMi-X 5.4 in TWRP.
If you want to run a KitKat based rom you should update your bootloader first.

berndblb said:
Should have elaborated I guess....
Do not do that factory reset from Settings or the bootloader again with a custom recovery installed! You can end up in a nasty forced reboot to recovery loop...
Ok, you are on a current recovery, your bootloader is up to date enough for JB based roms but I would not try to run KitKat roms on it.
Did you ever run a custom rom? Just to confirm your bootloader version, boot with Power and Volume Down buttons and read the tiny script.
That's the only sure way to determine your bootloader version.
If you are on 10.6.1.14.4 you can head over to the Development section and download CROMi-X 5.4.
Boot to TWRP, choose Wipe and just swipe the button to prepare your tablet for a clean installation of CROMi-X.
Once that is done flash CROMi-X 5.4 in TWRP.
If you want to run a KitKat based rom you should update your bootloader first.
Click to expand...
Click to collapse
[/CODE]
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
[/CODE]
This is what it says in the boot loader screen.
I have wiped the stock ROM through TWRP and installed Chromi-X 5.4.
Once I boot into android the screen freezes after a short while in setup.

Kaij said:
[/CODE]
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
[/CODE]
This is what it says in the boot loader screen.
I have wiped the stock ROM through TWRP and installed Chromi-X 5.4.
Once I boot into android the screen freezes after a short while in setup.
Click to expand...
Click to collapse
I think it would be worth you flashing the bootloader and twrp package in the first post of CROMi-X Reboot once after then flash the rom again.

[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...