yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] jfarthing84:
I'm trying to flash 4.4.4 onto my tablet which is seemingly experiencing this exact problem. However, the modified boot.img doesn't seem to work for me...
[Nexus 7 (2013) Q&A] Batfink33:
I'm wondering if the even later models of the tablet have changed again. No matter what I can't get TWRP to work using all the guides and TWRP versions posted on here, there seems something different or wrong. I've given up now.
[Nexus 7 (2013) Q&A] a4abbas:
Did you get it to work? I bought mine a week ago from amazon.com and I followed Cynaogen mode's wiki guide to get twrp but afterwards I couldn't get the partitions to show up :(

---------- Post added at 08:36 PM ---------- Previous post was at 07:38 PM ----------

I tried to install the recovery image from the first post on my Nexus 2013 flo. After installing that recovery my nexus is stuck into the boot loop then I turned it off and then relaunch the fastmode with button combination. I am not sure what to do now at this point I am really clueless. Please tell me if there is a workaround/fix for it!
[Nexus 7 (2013) Q&A] Batfink33:
No, I tried everything and couldn't get it to work, given up and using stock now.
[Nexus 7 (2013) Q&A] a4abbas:
I will really appreciate if you could please tell me how you went back to the stock? Mine is unable to find partitions since I flashed TWRP recovery into it. I have nexus 7 2013 wifi (flo). Please advice me or redirect me to the tutorial or a thread link. It will be enough if I could go back to stock and make everything work fine.
[Nexus 7 (2013) Q&A] Batfink33:
I flashed the stock recovery, simple as that, with TWRP it wouldn't boot buy with stock recovery it booted fine. I did a search on here for it, and found it (there's a thread on here somewhere with it) then flashed it with adb. It booted fine after that.
[Nexus 7 (2013) Q&A] a4abbas:
Thanks for your reply.

Can I follow this guide here: https://developers.google.com/android/nexus/images?hl=en ? However I am not sure if it includes stock recovery or not... I am confused or could you please give me a link to it? And please keep in mind that this device came with Lollipop I am not sure if it is necessary to tell you that.
[Nexus 7 (2013) Q&A] Batfink33:
I searched these forums for the stock recovery, someone has posted it in a thread although I can't find the thread now as I'm not at my PC. I then put the Nexus 7 into download mode and used the adb command "fastboot flash recovery" to flash the stock recovery onto the tablet. The device then booted fine. I would imagine you can flash the full stock ROM using adb like in the link you have posted as that should I think have the stock recovery in it. And yes, this was Lollipop I did it with.
[Nexus 7 (2013) Q&A] a4abbas:
You must be right. As this is stock provided with IMG file format so probably it has recovery... I will try this and let you know. Again thanks for replying and not being mean ;)

P.S. By download mode you mean fastboot mode. Correct?

-----

UPDATE: I flashed the stock file porvided on this page: https://developers.google.com/android/nexus/images?hl=en

After completing the process now, my device is just displaying the circle loading motion. OMG NOW IT HAS JUST SHOWED LOL I WAS JUST WRITING THIS TO YOU AND EVENTUALLY THE REGISTRATION SCREEN APPEARED! MAAANN I LOVE YOU THANKS FOR YOU HELP ITS BEEN TWO DAYS I HAVE BEEN DOING THIS AND THIS DEVICE IS NOT MINE so it was really frustrating for me to mess with someone elses device, again thanks for you feedback without this I was really helpless. :):):)

By the way on other thread outside XDA somebody suggested me this guide I am not sure if you have tried to do it to install custom ROM:

Since your Nexus shipped with Lollipop, you have to flash multirom modified TWRP. Here's the XDA thread[2] and here's a download link

Boot into bootloader

On your PC, put the patched TWRP in your adb directory

Fastboot flash recovery [twrpfilename].img

Boot into TWRP

Either adb sideload or just copy over and install a lollipop ROM
[Nexus 7 (2013) Q&A] Batfink33:
I already tried using the Multirom TWRP and it didn't work, I still got mounting errors. I've given up now on finding a solution for flashing custom Roms and kernels.
[Nexus 7 (2013) Q&A] ddagunts:
Hi all,

Does anyone have any access to the source of the "fixed" recovery (TWRP_multirom_flo_20150328.img) - I need to patch CWM to work with these newer Nexus 7s but am having a hard time finding information.

Thanks.
[Nexus 7 (2013) Q&A] lynnux:
Latest version (worked for me) is here: https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
[Nexus 7 (2013) Q&A] ddagunts:
Thanks, I'm looking for the source itself, I would like to see what changed to get these recoveries working.
[Nexus 7 (2013) Q&A] whenmunkysfly:
I got it to work by downloading the 4.4.4 version here:

developers . google . com/android/nexus/images?hl=en

then i replaced the boot.img in the download above with the modified file from earlier in this thread

then i used the Multirom file from earlier in this thread as instructed and everything worked great from there

I used Ubuntu in case that matters
[Nexus 7 (2013) Q&A] ddagunts:
You have TWRP on your device correct? I needed CWM. A quick writeup coming soon..
[Nexus 7 (2013) Q&A] ddagunts:
I'm too new to post links :(

I was trying to get Ubuntu Touch to install on one of these Nexus 7s. I posted a little writeup here: hxxp://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to

It's working boot and recovery images if you want to install Ubuntu Touch.

If anyone cares, here's a link to a working (I think) CyanogenMod recovery for our devices: hxxps://github.com/ddagunts/UTCWM_N7_patch/blob/master/cm-12.1-20150917-UNOFFICIAL-flo-recovery.img?raw=true
[Nexus 7 (2013) Q&A] lgkahn:
thanks this saved my bacon I have a new 2013 nexus 7. manuf. in may of 2015 and none of the custom recoveries worked.. they all couldn't mount the partitions so the map must have changed.. this file in the first post works.. newer twrp do not.. anyone have the change for the latest 2.8.7 version of twrp.. thanks again
[Nexus 7 (2013) Q&A] aymayo:
The wiki seriously needs to be updated so more people like me and others in this thread don't waste hours upon hours trying to figure out why their recovery won't mount anything.

Also is the latest TWRP meant to be fixed? Because it didn't work for me... only the multirom TWRP worked for me.
[Nexus 7 (2013) Q&A] a4abbas:
Totally agree! I wasted a lot of time on finding a solution for it. Only if they had updated it wouldn't have happened.
[Nexus 7 (2013) Q&A] aymayo:
Yep, and just to clarify I mean the wiki page for flo on cyanogenmod's website.

I know any user can edit the wiki page but I'm not quite sure how to phrase the problem without adding too much clutter to the page, maybe just a warning if you run into mounting errors to try the multirom recovery?
[Nexus 7 (2013) Q&A] itnorfolk:
Hi,

Has anyone successfully managed to get this to work with 5.1.1?

I've just bought a brand new Nexus 7 2013 (WiFi-flo) (LMY48G) and I'm planning on installing in a car. I need to root it using TWRP recovery and SuperSU before adding the "rom" I'm going to use.

I've been trying all day today but not managed to get it working and then found this thread (Thankfully!!!!). I'm hoping someone can help me get the TWRP actually working. I'm right up to installing the Custom TWRP Recovery section :)
[Nexus 7 (2013) Q&A] mr_fosi:
I haven't attempted it since I got mine working.

It's more important to me to have a machine that works.
[Nexus 7 (2013) Q&A] JackOfOwls:
I had a ***** of a time trying to get a custom recovery working for my new Nexus 7 2013 shipped with the 5.02 lollipop. Couldn't get TWRP to recognize any OS or partitions to backup. But because of this topic I finally had success. Thank you.
[Nexus 7 (2013) Q&A] HelenRedSea:
Hello all,

edit: solved! see at the bottom. ^-^'

I am too getting the "unable to mount" problem.. I feel completely lost..

First of all I need to clarify that I am nowhere near a knowledgable person in regards to rooting, flashing etc! I am a humble sociology student. :(

I mean, I read what most of you guys say here, and most of it seems gibberish to me(to the point where I feel mentally retarded lol).

However, if I'm good at something, this would be following instructions, and tbh that's why I decided to root my tablet.

So, yesterday was a wonderful day! Sun shining, birds singing, and also my Nexus 7 (2013 flo) arrived! yay!

So I decided to spend a day with the stock 5.2, holding hands, cuddling in bed, and generally making sure that the device works just fine.

Today I woke up and things were serious.. I knew it was time to say goodbye to the stock version.. So without second thoughts I started the rooting process.

I read some up-to-date guides, so I downloaded and flashed TWRP from their official site, and then tried to flash the latest cyanogen NIGHTLY rom, following the intructions on the Cyanogenmod wiki.

I kept getting the red mounting errors...

After multiple heart attacks and stroke episodes I decided to pull my self together and look for solutions.

I looked and looked and looked, and I ended up here which gave me hope, since from my understanding, people have managed to fix the problem.

I tried to follow the steps but I'm stuck on step 1.

I downloaded the TWRP img file provided, and flashed it.

I tried to start it, but I got stuck on the "teamwin" loading screen.

It won't take me to the menu.. instead every now and then it will flash a black screen for a split second and back to the "teamwin" loading screen.

I waited about 10 minutes for it to load but nothing.

Note

that when I flashed the TWRP img file I already had the latest TWRP version installed. Could that have to do with anything?

Oh lord help me! I don't know what to do..

I am sorry If I seem like a spoiled ignorant little girl but could someone suggest step by step what I can do to fix this (if there is anything to do ofcourse)? :crying:

Edit:

Ok, I managed to find what I did wrong.

I actually skipped the part where it said that I needed to root with "CF-Auto-Root", cause I thought that I was already rooted.

I rooted the tablet, flashed the recovery and installed the rom.

Everything worked like a charm!

Thank you for making this post!

And don't hate me for posting such a huge post.

hehe I feel like quite the fool right now. ^-^'
[Nexus 7 (2013) Q&A] Killah1994:
Has anyone tired the regular TWRP recovery (as in regular I mean not the multiROM TWRP) with marshmallow?
[Nexus 7 (2013) Q&A] lynnux:
This morning I tried flashing the regular TWRP image from the multiROM TWRP just to see what would happen. I'm running 6.0. It flashed fine, and it still has some of the same problems as before. It shows nothing in storage, 0mb, no files. When I reboot into system I get a message saying there's no OS installed, do I want to boot anyways, I say yes, and it boots fine. Root Explorer shows all files in storage as usual. I tried rebooting into recovery to see if a reboot would fix it, no.

So it works, partly. I'm not sure how you'd get it to recognize internal storage, though, so you could flash anything.

Does anyone know what the issue here is, and if there's an easy way to fix it? It would be nice to have unmodified TWRP going forward, even though the multiROM version is working fine for now.

Edit: In the end I reflashed the multiROM TWRP, which is working as usual.
[Nexus 7 (2013) Q&A] HelenRedSea:
Same here. Tried all that but it didn't work unless I had the multi.

What would be the merits of having an unmodified TWRP?

I mean the multiROM works as good as the normal one.
[Nexus 7 (2013) Q&A] lynnux:
It's probably fine as is. If something related to recovery started acting up it might be harder for a developer to solve, since we wouldn't know whether it was the modified recovery causing the problem or something else. I don't know what they did to modify it.
[Nexus 7 (2013) Q&A] Killah1994:
The only thing I can think of is the main developer of TWRP to add the commits that the MultiROM developer has, once he adds it the original TWRP should work for our devices.. I mean I don't mind having MultiROM TWRP, tbh I'm grateful for it. But it would be nice to have the official thing for our device.
[Nexus 7 (2013) Q&A] Elcs:
[EDIT]: Seems to be sorted. I used Fastboot Erase on the Recovery partition, installed the MultiROM TWRP .img via the Toolkit then rebooted into recovery via Toolkit. Showing as having internal storage and a different version of TWRP. Yay me!

Hopefully I am posting my request for assistance in the appropriate place.

I received a 4.4.something Nexus 7 WiFi (2013) a short while ago, promised myself I'd not tinker with it and it was about 48 hours before the bootloader was unlocked, device rooted and stock Lollipop 5.1.1 was happily working along. It wasn't until I thought "I love Xposed on my Kitkat Note 3. Let's take a look" that I discovered an issue within Recovery, I had issues mounting partitions and everywhere the Device suggested that there was 0mb internal storage despite everything working from an OS point of view.

This solution, trying to Format Data from within TWRP does not work. It fails the process.

Using TWRP Multirom img from the OP, I don't think my recovery is flashing as it appears to stay at the same version no matter what jiggery pokery I attempt.

I am still able to use the NRToolkit to lock/unlock the bootloader, root via cf-autoroot, flash versions of Android etc but the mounting/0Mb Internal storage/Recovery plagues the recovery element.

Any ideas before I consign this to the 'Well, the tablet still works as required but has this odd quirk I cannot fix' pile... any ideas?

Most grateful :)
[Nexus 7 (2013) Q&A] sgtfoo:
I recently got a N7 2013 from Amazon that came out of the box with 5.0.1 and it updated to 6 OTA. I flashed it back using nexus root toolkit to 5.1.1 and had to flash TWRP Multirom to be able to custom flash anything.

After going through this thread, I noticed

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/487

SO here's hoping the TWRP team fixes this in a new recovery version.

Can anyone confirm if flashing a different kernel fixes this?
[Nexus 7 (2013) Q&A] lew-hand:
Where is the install for ElementalX_2.15? I flashed 4.4.4 then your boot.img and TWRP multirom and it now loads fine in ROM and TWRP.

I'm now trying to install CM 11 but it just got stuck on the boot logo.

Is there a certain version of CM i need to use?
[Nexus 7 (2013) Q&A] Tarv:
Finally.

Wish I found this thread 3 hours ago. Thanks for the tip, MultROM TWRP worked for me, installed a custom ROM just fine.

Until I found this thread, tried the latest TWRP and CWM, both would not mount the partitions. Thought it was something I was doing, but I'm literally sitting here with two Nexus 7 2013's and one was working, one wasn't.

:P
[Nexus 7 (2013) Q&A] sensati13:
Needed newer version of TWRP_multirom_flo

FYI - There is a newer version of "TWRP_multirom_flo" available (TWRP_multirom_flo_20150630.img) from the following thread:

http://xdaforums.com/showthread.php?t=2457063

This may be helpful to those who seem to have received an even NEWER version of the Nexus 7 2013 (flo). I received mine from the Groupon deal a couple weeks ago. The OP recovery version listed here wasn't able to fully boot (went into bootloop) with the Nexus 7 version I received, however the newer 20150630 version did work fine.

Hope this helps someone.

s13
[Nexus 7 (2013) Q&A] omari_jalagania:
Mine Nexus 7 (flo) stucks on boot after flashing TWRP_multirom_flo this
[Nexus 7 (2013) Q&A] hachiroku:
i was having trouble with TWRP for about a week and a half and didn't understand that the Multirom had their own version of TWRP which works perfectly.

since i had the corrupt TWRP how i installed was to goto the Google play store and download Multirom Manager. once installed this app will confirm you have root access. proceed to install the first two check boxes. I unselected kernel update. after booted all was working as it should.

Thanks everybody!

---------- Post added at 10:09 PM ---------- Previous post was at 10:08 PM ----------

if you can get to bootloader you can fix your device. from bootloader you can push a new recovery image, or a full factory restore. you'll need adb and the appropriate files to get moving.
[Nexus 7 (2013) Q&A] derekroberts:
Thanks

I tried a lot of things to fix this problems. I put the supersu.zip on a microsd and put that in a microsd/usb adapter and connected that to the tablet with a usb3.0/miniusb adapter and then loaded from usb instead of internal storage and everything did "seem" to install correctly but the tablet never had root access after rebooting. This new TWRP build allowed to install from the internal storage instead and everything is working now. Much appreciated, thanks for your efforts.
[Nexus 7 (2013) Q&A] Killah1994:
TWRP 3.0.0.0 OFFICIAL BUILD NOW WORKS WITHOUT ERRORS

Gave it shot today using flashify and it booted fine without any errors.
[Nexus 7 (2013) Q&A] OneDon:
Yeah same thing on my end, it also works with later versions of twrp. Guess they finally fixed it but installation is slow as hell. But worth it tho.
[Nexus 6 Q&A, Help & Troubleshooting] aclb5:
I am on T-Mobile Nexus 6 with 5.0.1, rooted with NRT (used Chainfire + TWRP Recovery). I have been expecting to get a notification to update to 5.1 within the device, but haven't gotten anything, even when I manually check for updates from the device (Settings > About > Update). Do I need to do something manually since I am rooted? I also looked for the 5.1 M build on Google's repository and couldn't find it. Thanks for the help!!
[Nexus 6 Q&A, Help & Troubleshooting] DebianDog:
Over the air will not apply with a custom recovery. you can be patient and wait for M (NRT will update < 12 hours after Google does) or you could flash a stock recovery and OTA.

If you wait and use NRT there will be an option for the M version and then you can just do a flash to that version with the retain user option

Sent from my Google N6 on VZ
[Nexus 6 Q&A, Help & Troubleshooting] chris6278:
theres a stock, rooted T-Mobile build in the development section. Just flash that
[Nexus 6 Q&A, Help & Troubleshooting] OGMCVilleTC:
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Except the method posted immediately before your post.
[Nexus 6 Q&A, Help & Troubleshooting] OGMCVilleTC:
I'll look for it. Thanks for the info.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] m0biusace:
Updated to lollipop rooted via this manner, third method

http://xdaforums.com/note-3-att/general/update-procedure-lollipop-5-0-oc1-t3063760

Using the stylus in S-note is an exercise in frustration now. The phone seems to miss every fifth stroke or so when writing out a word quickly, compared to kitkat. Tested three different stylus (stylii?) on two different AT&T Note 3 both updated to lollipop via the same manner, both have the same problem.

What makes me think this is a software problem is that action note works just fine. Furthermore, I have a T-mobile note 3 running lollipop and S-note works just fine. Thinking it was the screen assembly of the AT&T note 3 I actually just swapped the screen from the tmobile to the AT&T, and the problem still persists.

Anyone with similar experiences?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] kuttyjoe:
Yep. Exact same problem. My phone is not rooted. The stylus writing seems to only be a problem within S Note. Writing elsewhere has no problem. I reinstalled Kit Kat and it's back to normal, but I'd like to reinstall Lollipop. It was rather nice otherwise although, I think it used more battery.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] dandroid7:
Ditto... bummer, I use the stylus all the time in s note
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Rickforet:
Same problem here with Canadian Note 3. Only on SNote. I hope there's a fix somewhere.
[Galaxy S III Mini Q&A, Help & Troubleshooting] joeroni:
I've tried unlocking all but after too many hours of reading,searches,downloads,installs than virus removals and rooting and money. Used my credit card 3 times for sim unlock at online companies. All three screwed me but got money back from one. I think cause they are Canadian phones.

They gave me these reasons and a few more. Than kept my money.

The phone is blacklisted by the provider or reported lost or stolen

It is now illegal within the USA to unlock Phones purchased after January 26th 2013, if your phone was purchased after this date it cannot be unlocked.Although this model is generally un-lockable, there are instances where codes cannot be generated.

The IMEI number submitted was incorrect.

I check on these and none pertain to these phones n the imei # was correct.

In Canada its Not illegal here to unlock if you own the phone out-rite.

I'm looking for an honest place online that sells the imei or just the sim unlock codes for a good price. The average price from the networks like rogers

here is $50 and that's half of the phones worth. I'm retired can't afford that.

Right now I'm trying to unlock my Samsung galaxy S3 mini.

Anyone know a $5 to $10 site?

I own all four cells.

Sony Erricson xperia X10a Rogers Canada

Huawei Ascend Y300-0151 Rooted Bell .

Samsung Galaxy Ace 2e SGH-T599V Wind

samsung galaxy S3 mini, Canadian Model SM-G730W8 Rogers

Android 4.4.2

SW-VER G730W8VLUAMK1

smg730rfmc
[Galaxy S III Mini Q&A, Help & Troubleshooting] joeroni:
Hey Joeroni I understand why you don't want to pay $50 to unlock a $100 phone.

But we can't really help with any recommendations cause we might offend someone

here that sells codes or software.Even though you have been ripped off from

some online companies.There are many ways here to unlock your phone but we

understand that one click root n unlock is much harder than stated and many

have bricked their phones.Which you can't afford to do.Like when you one click

root n unlock your Canadian Huawei Ascend Y300-0151.Its rooted n modem unlocked

but still locked to Bell.So learn roms now. Besides there are so many softwares

for Samsung that don't do your Canadian Samsung Galaxy S3 Mini, Canadian Model

SM-G730W8. Which you found out after hours n hours of reading n trying. We also

don't like answering people that are not geniuses already at this stuff. Not

even suggesting on the easiest software that you can buy credits that definitly

works on your Canadian phones.

So rather than learning to do your own phones here. Why don't you just quit

trying and pay the $40 and go to the corner shop n have them do it.Them shops

are popping up all over the place. Sound right?
[Galaxy S III Mini Q&A, Help & Troubleshooting] themountig:
lost or stolen phones

If less people bought "lost or stolen" phones there would be lots less lost or stolen phones.
[Galaxy S III Mini Q&A, Help & Troubleshooting] joeroni:
And like I said they are not stolen or blacklisted. They are difficult because they are Canadian and software little diff. They are mine. You see while some sell software others codes n so fourth. Its all about money now. This site used to help people now it seems like all retail just want money now or THEY GET IGNORANT if your a newbie and not a genius at roms n stuff. Or I guess putting out money to the site. To have to pay half of what the phones are worth just to unlock them is wrong. Most learned how to do it from this site for years. Now I get they must be stolen.