Nexus 7 devices which ship with android 5 need revised storage drivers

Looks like Asus changed eMMC hw revisions, and kernel need to accommodate this.
Actual change in flo's kernel tree is here:
commit fa842060088619d2de9986c5c5d588d0f40534e3
Author: hsuan-chih_chen <email address hidden>
Date: Mon Oct 13 10:55:00 2014 +0800

    mmc: add 5.0 emmc support

    bug: 17968808 Kernel change for new eMMC v5.0 parts for FLO/DEB

    Change-Id: Ia18152457fe3ff70401b199c267fa37374b9d544
    Signed-off-by: hsuan-chih_chen <email address hidden>

diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index dc4b125..ea1eca7 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -293,7 +293,7 @@ static int mmc_read_ext_csd(struct mmc_card *card, u8 *ext_csd)
        }

        card->ext_csd.rev = ext_csd[EXT_CSD_REV];
- if (card->ext_csd.rev > 6) {
+ if (card->ext_csd.rev > 7) {
                pr_err("%s: unrecognised EXT_CSD revision %d\n",
                        mmc_hostname(card->host), card->ext_csd.rev);
                err = -EINVAL;

I believe the importance of this bug is critical.

On Monday 16 November, I took my Asus Nexus 7 (flo) to Asus Serice Australia to have them unbrick it fom an unsuccessful downgrade from 5.1.1 performed by myself. - It transpired that with the tools Asus provide their service centres they are unable to downgrade to KitKat [specifically versions 4.4.4 and 4.4.2] from Lollipop. I was told that if I had a receipt and if it were in its warrenty period that they would have replaced the Motherboard to be able to fulfill my request of a downgrade. He requested my telephone in the case that he could find a solution.

This bug affects the 2013 model Nexus 7, not the 2012 model Nexus 7 with which I was able to perform a successful downgrade after my queries at bug 1499636.

Status changed to 'Confirmed' because the bug affects multiple users.

There is a manual fix available from the community at https://github.com/ddagunts/UTCWM_N7_patch/