• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[HOWTO] [GUIDE] Repairing corrupted /data partition

Search This thread

cadbomb

Senior Member
Jun 22, 2010
148
101
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited 30 minutes and decided it wasn’t going to finish, so I powered off. As an avid and experienced ROM flasher I knew this could hurt, and knew it was an inevitable requirement.

Upon rebooting back to recovery (I had already wiped /system /data, etc. in preparation for a new ROM) I found that I was unable to mount /data and subsequently /sdcard. I received a few different errors depending on which recovery I attempted (fastboot flashed). I was given neat things like “Enter password to decrypt /data” – TWRP, or “E: Unable to mount /data, invalid argument”, “E: Error mounting /data”, “E: Error mounting /sdcard”.

During all of this I realized I could get an ADB shell going from within Philz recovery (I am not sure if TWRP or CWM do this, nor did I try). After much research, and very much to my dismay, I was unable to find a complete guide or walkthrough for how to go about recovering from this. This is the procedure I glued together from my own digging and manual learning of the commands required. This procedure may or may not work in all cases but is a viable step to recovering your /data partition before going the nuke & pave route with the factory image!

(NOTE: I’ll try to keep this as simple as possible. I am not a dev. I do this for fun/learning in the little free time I get and am not typically available to assist, so please use this only if you feel comfortable with the material. Flashing a ROM/Kernel/etc. is one thing. Digging in the innards of the Android partitions/file system is a whole other beast! To be VERY clear: I am not responsible for damages or loss incurred by the use or misuse of this information.) Also note, if you have an ADB enabled recovery, you can probably try this process against your devices partitions as well.

The following instructions assume you are unable to mount /data or /sdcard on the Nexus 5 and are receiving errors. This also assumes that the wipe /cache function is not resolving the issue for you (as this seems to work for some depending on the issue).


Prerequisites:

- Philz recovery for LGE Nexus 5 (http://forum.xda-developers.com/showthread.php?t=2565174)
- Android ADB interface drivers and software (Available from existing root toolkits and SDK)
- Fastboot executable (Also available from existing root toolkits and SDK)
***Note: I performed all of this from Windows 8. The toolkit I used was Wug’s Nexus Root Toolkit (http://forum.xda-developers.com/showthread.php?t=2517778). If you are a Windows user, read and follow the toolkit instructions to install the drivers. Use the Advanced Utilities[Launch]->Manual Input[Launch CMD Prompt] to bring up a Command prompt and perform the steps below.
- For simplicity, ensure that the ADB and Fastboot binaries are in the same location if you are gathering these binaries from the SDK or other source.
- Create a folder that you can later use to pull recovered files from your phone. (if so desired)​

Terminologies used:

- Terminal = Command Prompt (Windows), Bash/etc (Linux), Terminal (MacOSX)
- Fastboot = Application that interfaces with the Bootloader (flash/wipe partitions, etc)
- ADB = Android Debug Bridge (Provides an interface to interact with Android filesystem)
- Binaries = Files containing executable code (for this context, ADB and Fastboot applications)
- Bootloader = Think of it as the EFI or BIOS equivalent for your phone. (Accessed with VOLDN+PWR)
- Recovery = CWM/TWRP/Philz (We will be using Philz, as this was what I used to write this guide)​

Steps:

1. Install all required drivers and prerequisites listed above.
a. Use Wug’s toolkit or whatever method gets your drivers installed for your OS.​
b. If you are not familiar with this process, then please research!​

2. Power off your phone and connect via USB to your PC.

3. Power your phone into the bootloader by holding the PWR+VOLDN keys

4. In a Terminal, browse to the location of your fastboot binaries. (See prerequisite note for Wug’s)
a. Enter ‘fastboot devices’ to verify that your phone is detected. If it returns a “<serialnumberofdevice> fastboot” then you may proceed. If it does not, please check your driver installation and start over.​

5. Flash and boot to Philz recovery:
a. Extract the ‘recovery.img’ file from Philz Recovery ZIP and place in the same location that fastboot and adb binaries are located.​
b. Enter ‘fastboot flash recovery recovery.img’ (without quotes) in the Terminal. This will write the new recovery.​
c. Once complete (takes a brief second usually), use the VOLUP/DN keys until the Bootloader shows “Recovery Mode” and press the power key. Your phone should now be booting into Philz recovery.​

6. Use ADB to launch a root shell from within Philz recovery
a. Ensure that the drivers are now detecting your device as an ADB ready device by entering: ‘adb devices’. If it returns “<serialnumberofdevice> recovery” then you are ready to proceed. If it does not, please verify your ADB driver installation and check again.​
b. Enter: ‘adb shell’ to gain full root shell access to the Android file system. (You should see a “~#” prompt to show that you’re now in a root shell)​

7. Attempt repair of /data partition. This partition includes /sdcard and dalvik. (/sdcard is linked to /data/media) At the ~# prompt:
a. Enter: ‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’​
b. You should now be prompted to repair or fix errors. Press [Enter] key to use the default answer of (y) for yes. If you are not, then this fix may not apply to you.​
c. Continue pressing [Enter] until the process completes.​
d. Proceed to next step if you have gotten this far.​

8. Attempt to manually mount the data partition.
a. We are going to mount /data as read-only for now. To do this, enter: ‘mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data’​
b. If mount is successful, it will simply drop down to the next blank shell prompt. If it fails, you will receive an error. If you receive an error, then the repair has failed.​
c. If you did not receive an error, you can now browse to your /data and /sdcard partitions. This is accomplished by entering: ‘cd /data’ for /data, and ‘cd /data/media/0’ OR ‘cd /sdcard’ for your /sdcard (/sdcard is a link that will drop you directly to /data/media/0)​

9. BACKUP YOUR ENTIRE SDCARD TO YOUR COMPUTER!!! (Optional, but highly recommended)
a. Enter: ‘adb pull /data/media <path_on_computer>’​
b. <path_on_computer> will be a folder you created in the prerequisites.​
c. Wait for this process to complete.​

Congratulations! You may now proceed to launch recovery and flash at will. I highly recommend after making the backup in step 9 that you perform a full factory reset to correct any potential lingering issues with the partitions. You can then push the files back to your /sdcard by mounting /data as RW using ADB shell through Philz recovery (please reference the ‘mount’ and ‘adb’ command utilities for information about how to do this).

If you find yourself in the unfortunate position to have to use this, please share your results in the forum for others. If you find something does not work, please post it (I will check occasionally and update as I can). I do not frequent my PM’s, and again, I am not available to provide support. Please understand this and use at your own risk.

If this helped you, then my job here is done :). Thanks for reading!

(I am not affiliated with any of the devs that provide these tools. Be sure to thank them if you used their tools, as they deserve all credit for enabling and teaching us to do these things – even when we do break our own stuff!)
 
Last edited:

matteventu

Senior Member
Feb 17, 2009
689
170
26
Lodi
Really helpful guide, I corrupted the data and cache partition while updating (via official OTA by sideload) to 4.4.1 (full stock Nexus 5), and I had to format all flashing then factory image and losing all the data...

Now if it does happens another time, I'll know what to do.

Thanks :)
 

jd1639

Recognized Contributor
Sep 21, 2012
16,832
5,401
Minnesota
Good write up but, I don't recommend tool kits. You can do all this with fastboot commands. You could just flash userdata image with fastboot
 

razholio

Senior Member
Mar 18, 2011
624
143
As a Linux admin, I'd wanna format /data after pulling off any files I wanted to keep rather than just rely on fsck . Is that an option? Is mkfs even on the recovery?

Sent from my BN NookHD+ using xda app-developers app
 

ywt474000158

Member
Apr 3, 2012
28
2
Thanks for sharing.
My nexus5 cant mount cache partition and i cant flash to stock factory,this maybe helpful.
Thank you again.
 

akash3656

Senior Member
May 3, 2010
1,728
851
As a Linux admin, I'd wanna format /data after pulling off any files I wanted to keep rather than just rely on fsck . Is that an option? Is mkfs even on the recovery?

Sent from my BN NookHD+ using xda app-developers app

I'm no Linux admin but there's a wipe /data button which does that in TWRP and also probably in CWM.

Sent from my Galaxy Nexus using Tapatalk
 
  • Like
Reactions: agriff

tidoubleger

Senior Member
Apr 18, 2012
50
4
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:

e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata

The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>


My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself
 
Last edited:

jd1639

Recognized Contributor
Sep 21, 2012
16,832
5,401
Minnesota
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:

e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata

The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>


My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself

Have you tried this yet http://forum.xda-developers.com/showthread.php?p=47156064
 

tidoubleger

Senior Member
Apr 18, 2012
50
4

Yes I tried it by using the flash-all.bat, flashing individually, and even Wug's toolkit as a last resort there but got nothing. When flashing the bootloader and radio it sends over fine but then gives me FAILED (remote: flash write failure) and finishes. When trying to flash the system or userdata it gives me FAILED (remote: failed to erase partition) and ends.
 

jd1639

Recognized Contributor
Sep 21, 2012
16,832
5,401
Minnesota
Yes I tried it by using the flash-all.bat, flashing individually, and even Wug's toolkit as a last resort there but got nothing. When flashing the bootloader and radio it sends over fine but then gives me FAILED (remote: flash write failure) and finishes. When trying to flash the system or userdata it gives me FAILED (remote: failed to erase partition) and ends.

I'm thinking your emmc went bad. Rma is probably your option right now
 

jd1639

Recognized Contributor
Sep 21, 2012
16,832
5,401
Minnesota
Well as far as Google knowing it, if I am able to successfully reset the tamper flag and lock the bootloader am I good to go or will they still find out?

If all your positions are corrupted I doubt you'll be able to reset the tamper flag. But also, no one will be able to see the tamper flag. But try to reset it and try to relock the bootloader. I don't think anyone will be able to tell if you modified anything or not.
 

tidoubleger

Senior Member
Apr 18, 2012
50
4
If all your positions are corrupted I doubt you'll be able to reset the tamper flag. But also, no one will be able to see the tamper flag. But try to reset it and try to relock the bootloader. I don't think anyone will be able to tell if you modified anything or not.

Hmm, I can see that the tamper flag is still true even after running that zip because it still fails because it can't mount /cache. I'm getting the feeling that the partitions aren't corrupted but have just been wiped or something. When I booted into TWRP through fastboot I was able to adb push to the sdcard and it showed up in the list when trying to install a zip, however the Internal Storage still read 0MB. I won't be able to RMA it for a few more days so if any other ideas come about, I'm all for it as I'd rather not have to RMA this lol
 

jd1639

Recognized Contributor
Sep 21, 2012
16,832
5,401
Minnesota
Hmm, I can see that the tamper flag is still true even after running that zip because it still fails because it can't mount /cache. I'm getting the feeling that the partitions aren't corrupted but have just been wiped or something. When I booted into TWRP through fastboot I was able to adb push to the sdcard and it showed up in the list when trying to install a zip, however the Internal Storage still read 0MB. I won't be able to RMA it for a few more days so if any other ideas come about, I'm all for it as I'd rather not have to RMA this lol

In twrp 2.6.3.4 have you tried going into wipe and then format data?
 

tidoubleger

Senior Member
Apr 18, 2012
50
4
In twrp 2.6.3.4 have you tried going into wipe and then format data?

Yeah it fails due to being unable to mount /cache.

@tidoubleger I am going to call in some RCs that were having this problem on an N7. They eventually got it sorted and up and running. They might be able to help.

@demkantor @MameTozhio @kilometers4
Fellas, would you be able to help this person out the same way you did here.

Thanks Woody, I appreciate the call to arms :D I'm currently at Disneyworld, so I won't be able to test anything until this evening but will do my best to answer questions until then
 
  • Like
Reactions: fozknots

kilometers4

Senior Member
Mar 6, 2012
3,453
2,860
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:

e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata

The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>


My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself

I had the same problem. This is how I got it sorted.
follow these steps and you should get it sorted

fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
once it flashes, boot into recovery.
format sdcard (i believe it is)
Now adb sideload ROM and gapps

I have class until this afternoon, but that should get it fixed
If you have any hangups post it here and I'll help you when I'm free.

Good Luck
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 71
    I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited 30 minutes and decided it wasn’t going to finish, so I powered off. As an avid and experienced ROM flasher I knew this could hurt, and knew it was an inevitable requirement.

    Upon rebooting back to recovery (I had already wiped /system /data, etc. in preparation for a new ROM) I found that I was unable to mount /data and subsequently /sdcard. I received a few different errors depending on which recovery I attempted (fastboot flashed). I was given neat things like “Enter password to decrypt /data” – TWRP, or “E: Unable to mount /data, invalid argument”, “E: Error mounting /data”, “E: Error mounting /sdcard”.

    During all of this I realized I could get an ADB shell going from within Philz recovery (I am not sure if TWRP or CWM do this, nor did I try). After much research, and very much to my dismay, I was unable to find a complete guide or walkthrough for how to go about recovering from this. This is the procedure I glued together from my own digging and manual learning of the commands required. This procedure may or may not work in all cases but is a viable step to recovering your /data partition before going the nuke & pave route with the factory image!

    (NOTE: I’ll try to keep this as simple as possible. I am not a dev. I do this for fun/learning in the little free time I get and am not typically available to assist, so please use this only if you feel comfortable with the material. Flashing a ROM/Kernel/etc. is one thing. Digging in the innards of the Android partitions/file system is a whole other beast! To be VERY clear: I am not responsible for damages or loss incurred by the use or misuse of this information.) Also note, if you have an ADB enabled recovery, you can probably try this process against your devices partitions as well.

    The following instructions assume you are unable to mount /data or /sdcard on the Nexus 5 and are receiving errors. This also assumes that the wipe /cache function is not resolving the issue for you (as this seems to work for some depending on the issue).


    Prerequisites:

    - Philz recovery for LGE Nexus 5 (http://forum.xda-developers.com/showthread.php?t=2565174)
    - Android ADB interface drivers and software (Available from existing root toolkits and SDK)
    - Fastboot executable (Also available from existing root toolkits and SDK)
    ***Note: I performed all of this from Windows 8. The toolkit I used was Wug’s Nexus Root Toolkit (http://forum.xda-developers.com/showthread.php?t=2517778). If you are a Windows user, read and follow the toolkit instructions to install the drivers. Use the Advanced Utilities[Launch]->Manual Input[Launch CMD Prompt] to bring up a Command prompt and perform the steps below.
    - For simplicity, ensure that the ADB and Fastboot binaries are in the same location if you are gathering these binaries from the SDK or other source.
    - Create a folder that you can later use to pull recovered files from your phone. (if so desired)​

    Terminologies used:

    - Terminal = Command Prompt (Windows), Bash/etc (Linux), Terminal (MacOSX)
    - Fastboot = Application that interfaces with the Bootloader (flash/wipe partitions, etc)
    - ADB = Android Debug Bridge (Provides an interface to interact with Android filesystem)
    - Binaries = Files containing executable code (for this context, ADB and Fastboot applications)
    - Bootloader = Think of it as the EFI or BIOS equivalent for your phone. (Accessed with VOLDN+PWR)
    - Recovery = CWM/TWRP/Philz (We will be using Philz, as this was what I used to write this guide)​

    Steps:

    1. Install all required drivers and prerequisites listed above.
    a. Use Wug’s toolkit or whatever method gets your drivers installed for your OS.​
    b. If you are not familiar with this process, then please research!​

    2. Power off your phone and connect via USB to your PC.

    3. Power your phone into the bootloader by holding the PWR+VOLDN keys

    4. In a Terminal, browse to the location of your fastboot binaries. (See prerequisite note for Wug’s)
    a. Enter ‘fastboot devices’ to verify that your phone is detected. If it returns a “<serialnumberofdevice> fastboot” then you may proceed. If it does not, please check your driver installation and start over.​

    5. Flash and boot to Philz recovery:
    a. Extract the ‘recovery.img’ file from Philz Recovery ZIP and place in the same location that fastboot and adb binaries are located.​
    b. Enter ‘fastboot flash recovery recovery.img’ (without quotes) in the Terminal. This will write the new recovery.​
    c. Once complete (takes a brief second usually), use the VOLUP/DN keys until the Bootloader shows “Recovery Mode” and press the power key. Your phone should now be booting into Philz recovery.​

    6. Use ADB to launch a root shell from within Philz recovery
    a. Ensure that the drivers are now detecting your device as an ADB ready device by entering: ‘adb devices’. If it returns “<serialnumberofdevice> recovery” then you are ready to proceed. If it does not, please verify your ADB driver installation and check again.​
    b. Enter: ‘adb shell’ to gain full root shell access to the Android file system. (You should see a “~#” prompt to show that you’re now in a root shell)​

    7. Attempt repair of /data partition. This partition includes /sdcard and dalvik. (/sdcard is linked to /data/media) At the ~# prompt:
    a. Enter: ‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’​
    b. You should now be prompted to repair or fix errors. Press [Enter] key to use the default answer of (y) for yes. If you are not, then this fix may not apply to you.​
    c. Continue pressing [Enter] until the process completes.​
    d. Proceed to next step if you have gotten this far.​

    8. Attempt to manually mount the data partition.
    a. We are going to mount /data as read-only for now. To do this, enter: ‘mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data’​
    b. If mount is successful, it will simply drop down to the next blank shell prompt. If it fails, you will receive an error. If you receive an error, then the repair has failed.​
    c. If you did not receive an error, you can now browse to your /data and /sdcard partitions. This is accomplished by entering: ‘cd /data’ for /data, and ‘cd /data/media/0’ OR ‘cd /sdcard’ for your /sdcard (/sdcard is a link that will drop you directly to /data/media/0)​

    9. BACKUP YOUR ENTIRE SDCARD TO YOUR COMPUTER!!! (Optional, but highly recommended)
    a. Enter: ‘adb pull /data/media <path_on_computer>’​
    b. <path_on_computer> will be a folder you created in the prerequisites.​
    c. Wait for this process to complete.​

    Congratulations! You may now proceed to launch recovery and flash at will. I highly recommend after making the backup in step 9 that you perform a full factory reset to correct any potential lingering issues with the partitions. You can then push the files back to your /sdcard by mounting /data as RW using ADB shell through Philz recovery (please reference the ‘mount’ and ‘adb’ command utilities for information about how to do this).

    If you find yourself in the unfortunate position to have to use this, please share your results in the forum for others. If you find something does not work, please post it (I will check occasionally and update as I can). I do not frequent my PM’s, and again, I am not available to provide support. Please understand this and use at your own risk.

    If this helped you, then my job here is done :). Thanks for reading!

    (I am not affiliated with any of the devs that provide these tools. Be sure to thank them if you used their tools, as they deserve all credit for enabling and teaching us to do these things – even when we do break our own stuff!)
    3
    I would try formatting the partitions separately and then flashing new firmware/software
    fastboot erase system
    fastboot erase cache
    fastboot erase userdata
    fastboot erase recovery
    fastboot erase boot
    Then I would extract these images from here
    https://developers.google.com/android/nexus/images#hammerhead
    And start with bootloader
    fastboot flash bootloader nameofbootloader.extension
    .img .nb0 whatever
    Then
    fastboot flash radio nameofradio.img
    (maybe modem can't recall on these so look for modem if need be)
    fastboot flash recovery nameofrecovery.img
    fastboot flash system
    fastboot flash userdata
    fastboot flash cache
    And so on
    If any errors please post all input/output from cmd in codewraps here or pastebin link
    3
    Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:

    e2fsck: 1.41.14 (22-Dec-2010)
    e2fsck: Superblock invalid, trying backup blocks...
    e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata

    The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>


    My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself

    I had the same problem. This is how I got it sorted.
    follow these steps and you should get it sorted

    fastboot erase system -w
    fastboot erase boot
    fastboot erase recovery
    fastboot flash bootloader bootloader.img
    fastboot flash recovery recovery.img
    once it flashes, boot into recovery.
    format sdcard (i believe it is)
    Now adb sideload ROM and gapps

    I have class until this afternoon, but that should get it fixed
    If you have any hangups post it here and I'll help you when I'm free.

    Good Luck
    2
    Nice guide I'm sure this is going to be very useful for a lot of people. :thumbup::thumbup:

    Sent from my Nexus 5 using Xparent BlueTapatalk 2
    2
    Ok can you try it from here:
    fastboot flash recovery recovery.img (use this recovery if you have a grouper tab http://techerrata.com/browse/twrp2/grouper)
    once it flashes, boot into recovery.
    format sdcard (i believe it is) (keep in mind this will obviously wipe all of the data from the device)
    Now adb sideload ROM and gapps

    Hey Kilometers, he is having trouble with the N5 "Hammerhead", so make sure that you curtail your responses towards that. I know your issue was with the N7, but since the issues were extremely similar is why I ask.