yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] MrAwesome75:
Even though I just did it this past weekend, I flashed recovery and stock and rooted and un-rooted so many times to try to fix this before I found this solution, I can't remember exactly what I did that fixed it. But, I think what I did was flash (with ADB) the modified TWRP.img first. Then I rooted using CF-AutoRoot (with ADB). Then, downloaded the normal TWRP file for my device and flashed that using Flashify (on device). I think that last step might be the step you're missing. I did the same thing the first time I tired, thinking that was the only recovery needed, then re-read the OP and realized it says to also flash your normal recovery after you're done flashing the modified TWRP.img.

I'm going to do this again for my brother's N7, so if I am wrong, I'll find out and edit this post. In the meantime, I hope this helps.
[Nexus 7 (2013) Q&A] vaximily:
I'm not sure how to flash with ADB (I do have minimal fast boot & adb installed, just not sure of the commands / process).

I haven't used CF-AutoRoot, but I'm not sure why / how that would affect the ROM booting, so skipping that step shouldn't make a difference...

As for going to the normal TWRP, my experience has been that it can't read the file system properly, causing errors (also, what is Flashify? I just use Fastboot for this stuff).

Can you clarify the step by step a bit better if you get it figured out, please?
[Nexus 7 (2013) Q&A] vaximily:
OK, I see the difference here... you installed CM 12.1 (5.1.1) which doesn't require much effort - that piece works fine for me.

The issue I'm having, is getting 4.4.4 to run - the new boot.img allows Factory 4.4.4 to run, but not CM 10.2 or CM 11.

Thanks for the input!
[Nexus 7 (2013) Q&A] HampTheToker:
I believe whatever code was patched in the modified 4.4.4 boot.img linked to in this thread would also have to be patched to any other pre-5.0.1 boot.img that you want to flash regardless of whatever rom it's included in.

I would suggest finding whoever is maintaining the CM rom that you're trying to flash and refer them to this thread and ask nicely if they would patch the CM 10.2 or CM11 boot.img for you.
[Nexus 7 (2013) Q&A] vaximily:
Ah hah! That makes PERFECT sense. It just clicked (in my head) that boot.img is the boot up process for the ROM, so OF COURSE the Factory boot.img wouldn't work for CyanogenMod.

So, who wants to volunteer to make a modified boot.img for CM11 for the Nexus 7 2013 Wi-Fi (FLO)? ;):p:confused::eek:
[Nexus 7 (2013) Q&A] HampTheToker:
Yeah, the modified boot.img would probably be just fine on most pure AOSP roms prior to 5.0.1, but anything based on CM or other such custom AOSP roms will need to be patched. I had hoped that wouldn't be the case, but sadly it is.

If you PM the developer/maintainer of those roms that require the patched boot.img, I'm fairly confident they won't have any problems adding it.
[Nexus 7 (2013) Q&A] HampTheToker:
I left a reply in flar2's ElementalX kernel thread in the original development section asking if he could take a look here and help us out with a patched custom kernel for AOSP and CM-based roms. Hopefully, he'll get us fixed up so we don't have to settle for stock lollipop/pure AOSP. Plus, it'd be nice to have Xposed back. There are more than a few modules that I'm really really missing right now.
[Nexus 7 (2013) Q&A] HackedBotato:
Took me a while to figure this out, since Nexus Root Toolkit didn't work, so I tried CF Auto-Root. TWRP and CWM failed, but MultiROM fixed it. Should have read this thread earlier!
[Nexus 7 (2013) Q&A] Spikbeatz:
Just so I'm clear, in order to get TWRP working on a CF rooted N7, build date of 2014.12, that is having the exact same issues as mentioned in his OP, I have to use MultiROM?

Could I just use the modded TWRP img file listed in the 2nd post? Also, If I do install MultiROM, it neccessary to install a secondary ROM? In other words, if all I want to do is get a custom ROM installed, GAPPS installed, TWRP installed and running, and have root and NOT use MultiROM to it's full capacity, would I need to have a secondary ROM in that slot?

I do want to thank you for doing this thread. I spent a solid 4 hours trying to figure out why TWRP was showing 0 MB on the internal memory, yet a ROM toolkit or any file explorer app could see the data in the folders to include the CM12 ROM zip and the GAPPS zip, but couldn't stay awake to search anymore. Then this morning, I found this thread.

Cheers sir!
[Nexus 7 (2013) Q&A] HampTheToker:
You don't have to use MultiRom. The modded MultiRom TWRP recovery is basically the same as official TWRP with just a few things added to make it useful for MultiRom. If you don't want to use MR, you can just ignore anything pertaining to it and just use it as you would normally use TWRP.

Keep in mind that any rom or kernel prior to 5.0.1 (even official firmware) may flash fine, but it won't boot unless the boot.img has been patched for whatever revision Asus implemented for newer tablets.
[Nexus 7 (2013) Q&A] Spikbeatz:
So if I flash the tweaked twrp img that is for multirom and don't use multirom itself, will twrp see or mount the internal memory so then I could flash whatever Rom I chose?
[Nexus 7 (2013) Q&A] HampTheToker:
You should be fine flashing anything 5.0.1 or better.

The MultiRom part of this recovery is there if you want to use it. If not, then just ignore it.
[Nexus 7 (2013) Q&A] Spikbeatz:
Yes. It's on 5.0.1.

Coolness! Thank you
[Nexus 7 (2013) Q&A] 8thphloor:
nexus 7 2013 brand new with latest build 5.1.1....unlocked..no problem...flashed custom recovery..ok...rebooted in recovery...can't mount anything...panic...tried with another recovery...same panic...tried to flash factory image and done again the process...no f*#@kin way...then i saw this thread...and a light at the end of the tunnel...followed the procedure through adb and flashed twrp-multirom...

and.....tadaaaaaaaaaaa....all is workin like a charm...

twrp showed sdcard correctly and when i tried to reboot it asked me if i wanted to install supersu...i choosed to install it and reboot...tadaaaaaagainn device rooted!!!!

so in my case i didn't need cf-autoroot but twrp did the job...

i had to say thank you to op for his precious hints.....great great guide ;)
[Nexus 7 (2013) Q&A] SwoRNLeaDejZ:
Has anyone thought to submit this to the TWRP team? There is obviously something in the Multi ROM TWRP that isn't in the original version that makes it work. I'm are DeesTroy could fix it and make it work. Just a thought.
[Nexus 7 (2013) Q&A] Jayrod76:
Just wanted to say that this has to be one of the most aggravating things I've run into in a very long time. Decided to get a N7 off of new egg.. It shipped on 5.02. Finally had a chance to tinker and spent the last few days trying everything I could to get any recovery to work correctly! Many flashes and choice words were involved before this thread was found! Presently on DU,fully twrpd and running great now. Thanks to whomever figured out this ridiculous mess!
[Nexus 7 (2013) Q&A] 8thphloor:
done ;)

http://xdaforums.com/showthread.php?t=2380100
[Nexus 7 (2013) Q&A] SwoRNLeaDejZ:
Attaboy ;)
[Nexus 7 (2013) Q&A] SwoRNLeaDejZ:
If a theme Dev can't figure it out, what hope is there for the rest of us? Lol...
[Nexus 7 (2013) Q&A] 3316556:
[URGENT]Hello i apologize in advance for the wall of text but I know how annoying it can be when someone is just like "my tabuwet is bwoken heap" so, Im having issues flashing anything lower than android 5.0. I can provide you with any info you need. It all started when my previous flo's screen broke, I sent back to Asus they send me a new one and It came with 5.0.1 pre installed. I hate lollipop so I went to install 4.4.4 with googles stock image (I DID REPLACE THE STOCK 4.4.4's recovery with twrp in the zip) flashed it fastboot showed all went well but, when I boot it stayed at the google logo forever (not the boot animation). So I then rebooted into recovery and it says could not mount cache, so I begin flashing stock images under 5.0 as well as twrp imgs and multirom I love me some multirom ?(I know that flashing 5.0 and up works perfectly) I find out that 4.4.4 and below are like cryptonite for this thing. (Worked fine on prev n7fhd flo) this crap is so damn frustrating I've been at this for more than a MONTH Now to no avail. So I've given up and now asking you guys for help. I CAN TELL YOU THIS IS NOT A HARDWARE PROBLEM so if you think it is its NOT! I've ruled that out. If you wonderful people need more info I can make a video taking you through the whole thing!

Extra info: 1)After flashing twrp with android 5.1.1 and below it shows a sea of mounting errors.

2)Every other recovery has the same mounting errors as stock twrp.

3)The only way to get twrp to work is if I use multiroms twrp zip as my recovery

4)tablet out of warrenty

Used d mesg to find out what twrp was whining about and the only clear error was error -22

Thanks to everyone who has taken the time to read the wall of text.

---------- Post added at 07:35 PM ---------- Previous post was at 06:56 PM ----------

I am not trying to flash 5.0 I'm forced to use it BC I CANT FLASH 4.4.4! I dont think its twrp I think its the emmc partition maybe idk any info would be great. These are the errors I get when flashing KitKat. m.imgur.cm/wUNMvQc,FJLOXyd,8cis4qN,rms9SGF
[Nexus 7 (2013) Q&A] HampTheToker:
Read this thread (it's really not that much to read) then delete your wall of text when you figure out that this issue is known and has been addressed already.
[Nexus 7 (2013) Q&A] 3316556:
Addressed meaning a fix or...
[Nexus 7 (2013) Q&A] HampTheToker:
Wow, read and you'll see. It's less than 100 posts. You're in the right place, though.
[Nexus 7 (2013) Q&A] 3316556:
Look buddy I'm new to this site you can tell by looking at the links in the post they are not complete. and idk where to search so if you think I'm
[Nexus 7 (2013) Q&A] HampTheToker:
http://xdaforums.com/showthread.php?p=59688231

http://xdaforums.com/showthread.php?p=59787876

http://xdaforums.com/showthread.php?p=60323461

Just a thought: if you're having so much trouble reading through this thread and finding the answers that have already been provided, then maybe you shouldn't be trying to root your N7. Most of us here have experienced enough to know that you can easily brick your device if you're attempting these things half-cocked. The whole point of reading through a thread like this is to learn what does or doesn't work and how to recover your device if something goes wrong or doesn't work as expected.

I'm not trying to be mean. I'm just letting you know that you'll be doing yourself a favor by reading and learning first and then attempting whatever it is you're trying to do. The number one rule here is that your problems are rarely unique, so search and read and try to learn what others have done to fix it before posting in order to avoid a ton of "Help me! Help me!" posts in any given thread.

Trust me, learning to search through these forums for answers before asking repetitive questions is much easier than it seems.
[Nexus 7 (2013) Q&A] 3316556:
2 things. 1 thank you for being so kind and patient i appreciate that! 2 i know quite a bit about flashing i've been flashing rom after rom after kernel after kernel i may have messed up a couple of times but they were nothing i could not fix with a simple stock firmware flash with odin or fastboot or so i thought until i ran into this problem. i apologize for my lack of punctuation i am 16. Thank you again for the links kind sir!:laugh:
[Nexus 7 (2013) Q&A] Cendrix:
Tags

It took me a long time, and actually someone else found this forum for me.

To further help people in the future who run into the mounting issues, you should tag things people will quote

to reach this such as,

E: Can't mount /cache/recovery/log

Or something similar. I'm relatively new to some forums, but I thank you for posting this, it was a great help!
[Nexus 7 (2013) Q&A] Shawnki91:
Just wanted to leave my thanks here for this thread and the accompanying files in OP.

I spent the greater part of 4 hours trying everything to install TWRP. I have a lot of experience with Android and custom recoveries and ROMs and was surprised to see that of all devices, my Nexus was the hardest to flash recovery. I just ordered my Nexus from Amazon a few days ago and it came with 5.0.1 out of the box which explains why 99% of recovery and rooting methods online are non-applicable to this device. Might be worthwhile to have this added to the thread re: recovery and rooting with a moniker indicating "If your device came with 5.0.1 OOTB and having mounting errors with other recoveries. methods.......TRY THIS!"

At any rate, this worked and I am grateful. Thank you!
[Nexus 7 (2013) Q&A] neonfxp:
got it working thanks for the info, if you to are having this issue, clear your schedule for a few days and with all the mis information you should be able to get it rocking in a couple days, only took me about 26 hours working on it.
[Nexus 7 (2013) Q&A] bo8:
FINALLY!!! My Nexus 7 ordered off Amazon.ca and received earlier this month is finally rooted on 5.1.1 and TWRP properly loaded and running without the "can't mount /xyz" errors! Thank you masterchiefb117!
[Nexus 7 (2013) Q&A] dohlfhauldhagen:
Doesn't work for me...

Hello. I just got my Nexus 7 flo yesterday. I was able to unlock the bootloader, install twrp, and root. However, when I boot into TWRP I still get a ton of mounting errors, and it says I have 0mb of internal starage. Android can see everything fine though. I have tried flashing older versions via fastboot, and I have tried flashing this version. Nothing makes a difference. I have followed the instructions exactly. Is there something I am missing? I am running 5.1.1. Is this too late of a version? Thank you for you help.

---------- Post added at 02:17 PM ---------- Previous post was at 01:50 PM ----------

Sorry, I figured it out. I downloaded 5.0.1 from google and reverted to stock and started over. I then reflashed the multirom TWRP posted in this thread and it worked! Finally!
[Nexus 7 (2013) Q&A] captain_boom:
I just wanted to drop a note and say thanks for posted the multirom boot!

Has anyone had any success in downgrading? I am interested in downgrading to 4.4.4 and it appears that the new revisions are reaking havoc on using external wifi cards. I was thinking about giving 4.4.4 a shot.
[Nexus 7 (2013) Q&A] OlDrunk:
YAY!

This post needs to be sticky or something! I was bout return the danm nexus cuz I thought it was fudged. This saved my day, Cheers to MasterChief I owe you a beer for starting this thread and Cheers to rsusami for the fix!

Question about the 4.4.4 boot.img , once downgraded can any nexus7 kitkat ROM be flashed?
[Nexus 7 (2013) Q&A] ccmpbll:
WORKS!

I can confirm that this works with the latest TWRP_multirom_flo_20150410.img from http://xdaforums.com/showthread.php?t=2457063

I second that this needs to be a sticky. Would have saved me some time.

Thanks for posting this!
[Nexus 7 (2013) Q&A] dgauze:
I finally got this to work after many tries.

Anyone have any insight into why that custom recovery works and the standard twrp build does not?

I tried installing the standard twrp build after getting cm12 on the device, but no luck. Seems hackish to have to use a custom bootloader on such a common device.

---------- Post added at 03:29 AM ---------- Previous post was at 03:12 AM ----------

If this is the case, it should be a simple fix. That's good news. The new storage parts must have a different UUID or something.
[Nexus 7 (2013) Q&A] tvsteve:
Solved, See below.

Trying to put 4.4.4 on one of these "new" N7's but here's what I get trying to write in fastboot.

C:\Users\TvSteve\7root>fastboot -w update image-razorg-ktu84p.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-04.02

Baseband Version.....: none

Serial Number........: 0ab53cab

--------------------------------------------

checking product...

FAILED

Device product is 'flo'.

Update requires 'deb'.

Well Google wasted a lot of my time. The images on there site, https://developers.google.com are all mixed up. The 4.4.4 for the N7 WIFI is for the mobile. This is the correct 4.4.4 and it worked on the first try;http://www.skipsoft.net/?wpdmpro=nexus-7-wifi-2013-razor-android-4-4-4-kot49p.

BTW this just came from Newegg and is advertised as coming with 4.3
[Nexus 7 (2013) Q&A] redDEADresolve:
The fix also worked for me. Thanks for the help.

Does anyone know what causing these recovery mounting errors?
[Nexus 7 (2013) Q&A] MsockoR:
So the steps to do this is to:

1. Flash the recovery image, in my case the FLO version.

2. Flash 4.4.4 onto the Nexus 7.

My question is when and how do I flash the boot.img?

Thanks!
[Nexus 7 (2013) Q&A] travelingbard:
I am only making assumptions but it appears that:

1. there was a hardware revision with the built in SD card

2. There was a firmware change that would soft-brick the device when attempting to roll back to an older version of stock Android

I am going to attempt these suggestions one more time but my experiences with N7 WIFI 2013 can be summarized as:

1. Any flashing of android 4.x leaves me with the Google Splash screen with the rooted phone icon (black background, white Google and icon).

2. Reverting to flashing any version of 5.x will allow me to use the tablet like normal

3. loading bootloader.img and recovering only leaves me with Android 5.x

I'm sure there's user error involved hence the one last round of testing.

The tablet was sourced from Amazon [Product Query ID=B00DVFLJDS , NEXUS 7 FHD by ASUS Tablet]

I am merely seeking a Nexus/stock android device that either is shipped or "flash-able" with Android KitKat. :fingers-crossed:
[Nexus 7 (2013) Q&A] SoftwareFailure:
Patched 2.15

Hi,

As suggested by flar2 I build the kernel myself after having modified the mmc.c part. I'm sharing it here because it may help someone.

This boot.img is based on the 2.15 version of ElementalX for stock/AOSP 4.4.3/4.4.4 ROMs.

Edit : I forgot to mention that you need first to install ElementalX_2.15 and choose all options you want in Aroma installer, then flash this patched kernel. I only tested Double-tap wake gesture and USB+OTG.
[Nexus 7 (2013) Q&A] zergrusher2010:
I have the same mounting errors and the TWRP multiboot ROM indeed worked. Mine was ordered from Amazon last week and is a Nexus 7 2013 (manufactured 3/2015). However, I want to go back to 4.4.4 but the messages in this thread do not give a clear link to a VERIFIED working 4.4.4 boot.img ROM link. I got the Google screen freeze like everyone else after flashing stock 4.4.4. WHY did ASUS have to screw with the hackability of these devices? I'm trying to get a Kali NetHunter 1.21 loaded which is a KitKat package (Lollipop version is buggier) and I think it modifies the kernel so I don't know if it will re-brick after I install that following a 4.4.4 load with a modified boot.img.
[Nexus 7 (2013) Q&A] MsockoR:
Are you referring to the boot.img from the dropbox link?
[Nexus 7 (2013) Q&A] MsockoR:
Here's how to get 4.4.4 working on your tablet.

1. After your flash the Google 4.4.4, you will see the Nexus 7 frozen on the Google logo with the unlocked lock.

2. Download the dropbox file from this post: http://xdaforums.com/showpost.php?p=60323461&postcount=48 and pull the "boot.img" file from the zip and place it where you execute adb.

3. Hold the power button to shut off the tablet.

4. Press the power button and the down volume button to get to the bootloader screen.

5. Plug your tablet into your computer and adb into your tablet.

6. Run the following command: fastboot flash boot boot.img and afterwards you should be able to get back into stock KitKat.

Best of luck to getting you to your ROM, I haven't gotten that far yet.
[Nexus 7 (2013) Q&A] Dr.Frost:
Internal storage not mounting, still stuck

Hello, I was trying to root my nexus 7-flo (2013) 5.1.1 with CF-auto root(which worked via sideloading) with a custom recovery (TWRP).

However, I wanted to install Xposed and learned that it required installing an ARM sdk for my device. Attempting to do so, I learned that without connecting the tablet to the computer, it would load the stock recovery mode (the one with the red triangle and horizontal android) and not the custom recovery that i thought i installed. The only way to get into the custom recovery was to flash it with fastboot every time. While in the custom recovery, I noticed my device said I had "0MB of internal storage" and that the logs in the TWRP recovery (both 2.8.7.0 and 2.7.0.0) said

E:Unable to mount '/data'

E:Unable to mount 'system'

E:Unable to mount 'cache'

These are a few examples of the many errors i read after looking at the logs.

I can't wipe/format the data as it is telling me that there is no data at all.

I can still reboot the system fine with root permissions (also I unlocked the bootloader, just to throw that out there).

I'm stuck. I even used Wug's Nexus Rootkit and it kept "waiting on device" every time it got to recovery mode.

Any help would be greatly appreciated, I was looking forward to getting Xposed after getting this nifty device in the mail from Amazon a few days back.

Thnx again :)

P.S. When trying to download apps from the play store, i get the error "194, app could not be downloaded".

anyway, thnx again

***EDIT***

Resolved, installed multi-rom and backed up everything, thanks for the links
[Nexus 7 (2013) Q&A] MrRedx:
just fixed everything my devices is running cm12.1 now

thank's for every one for help this saved my tab
[Nexus 7 (2013) Q&A] mr_fosi:
I have a N7 2013 FLO that shipped with 5.x. I didn't know that this was a problem until I tried reverting to 4.4.4 and had it bork on me.

I figured I'd post the the process I went though to find success.

1) Screwed up the tablet by attempting to use Wugs NRT.

2) Cursed and flailed my hands about in the air.

3) Discovered I still had access to fastboot and recovery but that recovery was giving mounting errors and therefore wouldn't flash anything.

4) Cursed more and flopped on the ground like a landed fish.

5) Made my way to this thread and read through the first two pages which gave me TWRP Multiboot and my first taste of success.

6) Booted TWRP, noted that the mounting errors were gone and promptly tried to flash CM 10.2 + gapps.

7) Got stuck on the Google + Unlocked screen, cursed some more and stamped my feet like a 4 year old child.

8) Finished reading the thread and discovered the modified boot.img.

9) Downloaded the official Google 4.4.4 and extracted the contents.

10) Used fastboot to flash cache, system, userdata, then the modified boot.img.

11) Profit!

12) Decided I didn't want to stick with 4.4.4 lest I trip upon a pushed out 5.x update.

13) Flashed CM 10.2 again and got stuck in Google + Unlock screen.

14) Flashed modified boot.img again, rebooted and waited through a long (35+ min) apparent boot loop.

15) Booted recovery, did a factory reset, and tried boot again just for the heck of it. Didn't work.

16) Used fastboot to reflash the stock 4.4.4 system.img, userdata.img, boot.img.

16) Booted fine.

17) Applied CF-AUTO-ROOT.

18) Followed the instructions here to make sure I don't accidentally get the push update.

19) Decided that this is good enough for now.

Next day, found that OTA update had been downloaded once I connected to Wifi. So...

20) Via adb root shell, remount /cache as rw and pulled /cache/update.zip off and onto my PC.

21) Deleted /cache/update.zip.

22) Tapped update notification on the Nexus screen and confirmed restart and install.

23) Tablet didn't restart even after 2 min, so I adb rebooted it and confirmed that the update install didn't occur.

I'll see what happens the next time I connect to Wifi and report on it here.
[Nexus 7 (2013) Q&A] Batfink33:
This is strange, i tried flashing the TWRP in the original post and that recovery started bootlooping at the TWRP screen. I'm obviously doing something wrong there. I flashed the original stock recovery back and everything was fine and the tablet booted. I've never had TWRP loop at the TWRP screen on any device?