yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Killah1994:
Still get the same errors, even went back to 2.8.0.0.
[Nexus 7 (2013) Android Development] masterchiefb117:
I've tired all of them progressing backwards since 2.8.6 all the way down to 2.8.0. I reported on my thread that some of us that have build/ship dates marked on the box going back as 2014.12 have issues. My tabs are marked 2015.01 and 2015.02. Someone else has 2014.12. I'm thinking that some sort of revision was done on our tabs shipped with 5.x.x and making it harder. I'm planning an getting 2 more nexus 7 today one from Craigslist and another thru Fry's. The guy from Craigslist said he bought his last year so I shouldn't have any problems with his.
[Nexus 7 (2013) Android Development] Killah1994:
Mine says 2014.12 on the box
[Nexus 7 (2013) Android Development] masterchiefb117:
I searched 4.04 boot loader issues as I thought maybe it could of been out bootloaders. I did see some stuff on it being an issue but going back since early 2014. Doesn't fit in our situation though because they are completely "locked" out from and and fast boot. With ours we can and and fast boot at will even soft bricking and getting things back to stock no issue. Just the whole mounting thing in recorvey that you can't use, wugs root process not sticking due to mounting issues, and not being to flash anything.

---------- Post added at 08:48 AM ---------- Previous post was at 08:45 AM ----------

I'm wondering if its possible to downgrade the boot loader at will. The only reason I do t want to is because that's our only life line in the event of a soft brick.
[Nexus 7 (2013) Android Development] Killah1994:
Well you could try, but as for me I'm finished trying. I'll wait till wugfresh shines some light on this, really don't wanna do something I'm going to regret
[Nexus 7 (2013) Android Development] madbat99:
It might not be a problem with wugs. If it is, just try fastboot flashing without wugs.
[Nexus 7 (2013) Android Development] Killah1994:
Tried it, still get errors in recovery (unable to mount and such)
[Nexus 7 (2013) Android Development] jshamlet:
This may have been an early attempt at what Google has done with the Nexus 6 and Nexus 9. Both of those devices no longer permit the bootloader to be downgraded at all, and 5.1 brings the extra fun of not permitting the bootloader to be unlocked until you have unticked a box in the OS. (Which, obviously, requires a bootable OS...) The best part is that the setting doesn't persist reboots if you have enabled any security at all. I'm hoping the TWRP guys can figure out how to set that flag from within the recovery, though that won't really help if you screw up the OS install on the stock recovery.

Hate to say it, but the idea of Nexus devices being completely open developer devices is starting to go away, as they are becoming just as locked down as anything from Samsung, HTC, LG, etc. That isn't necessarily bad - it now means a thief can't trivially resell your stolen device by flashing a factory restore image over your tablet/phone, but it makes it significantly more scary if you need to do things that require the bootloader to be unlocked.
[Nexus 7 (2013) Android Development] Killah1994:
Going to give it one more go, going to go back to 4.3 then back up to lollipop. I'm going to see if that does the trick!
[Nexus 7 (2013) Android Development] skleper:
Let me know, because I have exact same issues.
[Nexus 7 (2013) Android Development] sarceneaux:
just took the N7 from the wife and had it rooted and unlocked in just a few mins because of this tool. THANK YOU. i love the one click methods of root. this tool is on another level. thank you for this. its greatly appreciated.
[Nexus 7 (2013) Android Development] masterchiefb117:
So Wugs updated his program to 2.05. gonna try again.

---------- Post added at 03:44 AM ---------- Previous post was at 03:13 AM ----------

Will that glimmer of light ended really fast. But I was able to flash Francos kernel though. I guess we'll see what i can do with stock rom *sigh...

---------- Post added at 04:06 AM ---------- Previous post was at 03:44 AM ----------

@WugFresh Sir can you look into our tabs. we are having problems and we dont know if its supposedly a revision done with the latest tabs sent out or something deeper.
[Nexus 7 (2013) Android Development] skleper:
I tried 2.05 yesterday, no luck.
[Nexus 7 (2013) Android Development] WugFresh:
Read through your posts, not exactly sure what the issue is. Seems really strange that its happening for multiple devices. I don't think google would lock out the recovery partition like that.

For testing purposes can you flash an older version of stock and then try to Sideload an official OTA zip, and see if that work's. If it doesn't work then the entire recovery partition is corrupted, or something is fundamentally wrong with the devices you purchased.

Also can you confirm 100% that you have been selecting the correct Nexus 7 device in the kit? There are four to chose from.
[Nexus 7 (2013) Android Development] Killah1994:
Pretty sure I've selected the correct nexus 7 on the toolkit, but I've tried the method of going back to 4.3 and it stays at the google logo, I'm going to go to KitKat and see if it passes the google logo, then give it a shot at rooting n installing recovery, but I don't think the recovery partition is corrupted though, because it does successfully install googles recovery... But sorta does with twrp (except we can't install or mount anything)
[Nexus 7 (2013) Android Development] WugFresh:
Please re-read my suggestion and try it. There are reasons I asked you to do that. You are free to try whatever you want, but if you want my help - then please report back with the results from the specific test I suggested.
[Nexus 7 (2013) Android Development] Killah1994:
Copy! So flash 4xx then sideload an ota update?
[Nexus 7 (2013) Android Development] WugFresh:
Yup. Make sure the ota zip you grab is for whatever build of KitKat you flash.
[Nexus 7 (2013) Android Development] Killah1994:
Ok, I installed 4.4.4 KTU84P , now going to sideload 5.0 LRX21P
[Nexus 7 (2013) Android Development] Killah1994:
Okk so after I did the sideload of the ota it didn't reboot, as you can see in the pic
[Nexus 7 (2013) Android Development] WugFresh:
Ok. As I suspected. I miss wrote before - what I meant to say was if this fails then your cache partition is corrupted (or unmountable for some reason), which does seem to be the case. This has nothing to do with google security, or rooting, or TWRP. Your cache partition simply will not mount for whatever reason (which is required for recovery operations) - not even for official google firmware. I am afraid its a hardware issue.

Your only troubleshooting options left are trying to wipe and format the cache partition and try flashing things again. You could even try just flashing the "cache.img" (from extracted factory pack) to the catch partition in advance utilities (fastboot flash).

If that fails, you might need to RMA.
[Nexus 7 (2013) Android Development] Killah1994:
thanks for the response, well i already booted back to 5.0.2, seems like it wont boot anything 4xx only 5xx, but should i just flash the cache img from the 5.0.2 factory pack?
[Nexus 7 (2013) Android Development] Killah1994:
ok so i did try it and still no avail, tried the 4xx & 5xx cache and still no avail, formatted and flashed, formatted and tried ... still no avail, so im going to call this device a DUB, and send it back. never buy a tablet from groupon lol
[Nexus 7 (2013) Android Development] TrentB:
Master Chief seems to be having the same issue with tablets from frys and best buy too so I wouldn't blame Groupon
[Nexus 7 (2013) Android Development] Killah1994:
your right, but still it seems groupon is shipping out defective devices like crazy, and even now best buy i think.....
[Nexus 7 (2013) Android Development] TrentB:
It still seems fishy that it's possible to flash back and forth with different stock roms with no problems and everything else works perfectly fine.
[Nexus 7 (2013) Android Development] Killah1994:
yeah its weird but as wugfresh said the cache partition maybe corrupted, and that's a hardware problem, the thing is even if i flash to 4.3 it wont boot, but once as i flash to 5.0 it boots and so on with 5.0.1-5.0.2 , so the best option right now is to return it, if i had known this was the issue i would have returned it last week, but since the post office is closed i have no choice but to do it monday.
[Nexus 7 (2013) Android Development] TrentB:
Putting in my rma on the Asus website. Site glitched out and said my rma had already been applied for with my serial number. Now the waiting game to see if I get an email. If not I guess I'll call Monday.
[Nexus 7 (2013) Android Development] Killah1994:
Did you get yours from Groupon
[Nexus 7 (2013) Android Development] TrentB:
Yeah I did. I'm a bit worried if I return it to them I'd just get another bad one.
[Nexus 7 (2013) Android Development] Killah1994:
I figured but I'm going the other route, I'm going to return it to Groupon then get the refund and buy it from amazon to see if I get the same defective unit.
[Nexus 7 (2013) Android Development] TrentB:
I mostly want to keep the deal (145 shipped) from groupon. Was the whole reason I picked one up. Don't feel like spending more.
[Nexus 7 (2013) Android Development] fcb1:
I tried returning to stock, something went wrong using this tool. Long story short, it's stuck on the Google logo. The bootloader is unlocked but usb debugging is not enabled. How can restore it like this? I can get into the bootloader though
[Nexus 7 (2013) Android Development] Killah1994:
On the toolkit flash+unroot method and select softbrick mode, then from there you should be good. It'll do the rest.
[Nexus 7 (2013) Android Development] fcb1:
I've tried but it says fastboot devices was not found.
[Nexus 7 (2013) Android Development] Killah1994:
Lol that's the main reason I bought it from Groupon because if the deal, I missed the deal so many times and this time I was like no I'm not going to miss it again, lol when I took the deal that's when I realize if its too good to be true then something is wrong.

---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------

Remove the USB, restart the bootloader then try again
[Nexus 7 (2013) Android Development] fcb1:
Well that's odd....I've been doing this over and over again and now it finally connected, thanks
[Nexus 7 (2013) Android Development] TrentB:
Any ideas how to get stock recovery back on my device? I have tried flashing stock and unrooting but the recovery doesn't seem to be going across. Flashing it manually won't work under advanced utilities because TWRP can't see anything.

Given devices from multiple retailers seem to be having issues, I am not gonna assume Groupon is the cause.

Crisis averted, I am just an idiot who didn't realize what stock recovery looked like.
[Nexus 7 (2013) Android Development] Killah1994:
You right but this is my first time with Groupon, given that, it's going to be my last lol
[Nexus 7 (2013) Android Development] TrentB:
Yeah, I got a chromecast from them in the past and that was fine. I just can't quite figure out why it would be a hardware issue but android can run fine and you can flashboot flash images fine.

Debating if I really want to go through with the RMA or just suck it up and do stock + root
[Nexus 7 (2013) Android Development] Killah1994:
You got a point there, but I'm a flashahloic, my nexus 5 is running simple AOSP, my nexus 7 2012 is running rastaPop, n what's my nexus 7 2013 running lol stock+no root+never a recovery, at the end do what feels comfortable to you, I'm returning this.
[Nexus 7 (2013) Android Development] TrentB:
Yeah, I used to be a total one. I'm trying to go with reliability over gimmicks. Just trying to decide if the few xposed mods are worth the trouble and added bonus when I can do some of that on my phone.

If Asus makes me pay to send it in I'll probably suck it up and hope some fix shows up.
[Nexus 7 (2013) Android Development] Killah1994:
I highly doubt there's going to be a fix, I was going to wait for 5.1 but I can't even side load googles ota updates, so with that said it's a hardware issue, and right now I feel robbed
[Nexus 7 (2013) Android Development] TrentB:
So I downgraded to KTU84P (4.4.4) and the stock recovery isn't able to mount anything for sideloading. However, I was able to successfully sideload from 5.0.1 to 5.0.2 via the stock recovery. There seems to be some issue with downgrading from 5.x to 4.x but not bouncing between different 5.x versions.

Random thought, but why does Chainfire's autoroot seem to have no problem mounting partitions?
[Nexus 7 (2013) Android Development] garrmack:
I have a groupon Flo as well and I too am unable to get access to the file system in recovery. It is interesting that chainfire's autoroot doesn't seem to have any problems mounting the problematic file paths...
[Nexus 7 (2013) Android Development] WugFresh:
That's a good sign that you could Sideload between 5.0.1 and 5.0.2. Try reflashing 5.0.1 and rooting. Should work.

Chainfire autoroot works differently - without recovery or cache, the root script is slipstreamed into the boot.img and is executed on boot.
[Nexus 7 (2013) Android Development] WugFresh:
See my response to Trent which explains why autoroot is different and doesn't explain your cache issues. I think Trent is on to something - he said Sideloading was successful for him on 5.0.1. Can you guys try that too.

Maybe its a bootloader issue after all.
[Nexus 7 (2013) Android Development] Killah1994:
Just now seeing this, going to give it a shot, even tho I already packaged up my unit for RMA, gonna give it a go, I'm going to flash 5.0.1 and try to root / recovery install.

[Update]

So even on 5.0.1 it's still not mounting, can root using cf-auto root but can't install recovery!

[Update 2]

Well I can sideload from 5.0.1-5.0.2, but in all still no avail of recovery.
[Nexus 7 (2013) Android Development] TrentB:
I can sideload via the stock recovery and root but likewise, custom recovery is still a no go.
[Nexus 7 (2013) Android Development] WugFresh:
This is truly odd. I am running out of troubleshooting suggestions but I feel like it can be fixed. Try flashing the latest bootloader, then try CWM instead of TWRP. I will let you know if I think of something else. I am thinking its a bad bootloader.
[Nexus 7 (2013) Android Development] TrentB:
I've tried CWM and it throws the same issues. I've tried downgrading to 4.02 and 3.14 bootloaders but haven't had much success with flashing any custom recovery or anything. Maybe 5.1 will update the bootloader again to something functional.
[Nexus 7 (2013) Android Development] Killah1994:
Yup did the exact thing n still no shot at recovery
[Nexus 7 (2013) Android Development] WugFresh:
You guys should start an XDA thread, detailing all the things you tried and explaining your problem clearly. It should be its own topic, and maybe another dev will have some insight. Or maybe other people will post in with the same problem, and you can try to find a common denominator.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] garrmack:
Looks like there's already a thread about this issue. New nexus 7s that shipped with 5.0.1: http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
[Nexus 7 (2013) Android Development] garrmack:
The fix is to use the recently updated mulitiROM version of TWRP. So if anyone is having this problem, use the MuiltiROM version of twrp and you should be good.
[Nexus 7 (2013) Android Development] masterchiefb117:
Im writing up a How-to thing. sorta awesome it was figured out bummed that I surplussed the Nexus tabs because I thought hope was lost.
[Nexus 7 (2013) Android Development] masterchiefb117:
Updated with new I do for new Nexus owners http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
[Nexus 7 (2013) Android Development] WugFresh:
Might be good to alert the TWRP devs of this issue and fix. Maybe they can merge in some changes to make regular TWRP work.
[Nexus 7 (2013) Android Development] wooddale:
Hi Wug

Don't know exactly what the problem is but I think it may have happened when I used the toolbox to go from Kit Kat to Look Lollipop I seem to have lost a whole bunch of storage. I never noticed it I made two nanoids when I first did it was stock for awhile then flashed Beanstalk awhile back. There was n up date so I went to make nanoid of Bean just in case and there wasn't any room. I don't have a lot of stuff on the tab no music no videos I pretty much use it just to read news at night and see what's going on in my Facebook world. Near as I can figure I lost about half my storage 16 GB. Thanks.
[Nexus 7 (2013) Android Development] madbat99:
Factory reset should fix it.
[Nexus 7 (2013) Android Development] wooddale:
You mean a factory reset in twrp or the phone itself either way no big deal I got the time.
[Nexus 7 (2013) Android Development] madbat99:
In tablet settings. After a clean flash of a factory image sometimes storage doesn't display properly (shows lower than actual). But a factory reset clears it up.
[Nexus 7 (2013) Android Development] WugFresh:
http://www.wugfresh.com/faqs/incorrect-internal-storage-space/
[Nexus 7 (2013) Android Development] wooddale:
So where is that gonna leave me then stock Lollipop? Still rooted / twrp? I don't usually do FDR that way if I sell the phone I do a FXZ or same thing I did to get here lol.
[Nexus 7 (2013) Android Development] WugFresh:
Factory reset won't kill root, just wipe data. You can just wiping cache first. If you have TWRP you can do the wipe in that as well:

Wipe > Advanced Wipe > tick cache

Then if that doesn't work do it again without advanced wipe, and just wipe.

Backup stuff first if you wipe.
[Nexus 7 (2013) Android Development] wooddale:
Thanks that's almost to easy.
[Nexus 7 (2013) Android Development] pow pow:
can i use this to unroot my nexus 7 running on 5.1? I am planning send it service center because of the multitouch screen issue.
[Nexus 7 (2013) Android Development] madbat99:
Yes. Pick your device, pick the correct build and click flash stock + unroot. When it asks choose to not wipe data if you want to keep all data.
[Nexus 7 (2013) Android Development] WugFresh:
For sure. Just flash stock + unroot, then OEM lock.
[Nexus 7 (2013) Android Development] pow pow:
thanks WugFresh! yo the man!
[Nexus 7 (2013) Android Development] wooddale:
I tried both ways twice no go actually came up less because Bean was bigger than one of my stocks. I guess next step would go back to go right.
[Nexus 7 (2013) Android Development] Philly Jim:
Okay so I've only used this awesome tool kit to root all my nexus devices , now I'm thinking of going back to stock so I can get the oem update for my N7 , try that first , then my N6 , sound's stupid but since I've never done this before I figured can't hurt to ask ......is it as simple as connecting my N7 then hitting unroot then flash stock..? sorry for the noob question but once I do it i'll know for life since I will continue to buy Nexus devices as long as they keep making them ............then after I return to stock , just wait until my device say's there's a new update ? Thank's in advance for any help .....it will be greatly appreciated.....:confused:
[Nexus 7 (2013) Android Development] madbat99:
Yes that's all you do. Pick the right build of course. You know you can just apply the update with the toolkit. What version are you on and what version are you trying to update to?
[Nexus 7 (2013) Android Development] Philly Jim:
5.02. To 5.1
[Nexus 7 (2013) Android Development] madbat99:
There is no 5.1 for nexus 7(2013) yet. But when it becomes available you can just update with toolkit. Download the factory image of 5.1 then choose that as your build. Then do flash stock + unroot and choose your downloaded image. Also select "no wipe" so you keep your data and apps. Or wait until someone posts the URL for the update zip and download that. Then use toolkit to adb sideload it.
[Nexus 7 (2013) Android Development] pretty pixel:
Unlock bootloader, root and install TRWP

I am purchasing a Nexus 7 2013 and want to unlock the bootloader, root and install TWRP straightaway with the Toolkit. I would be grateful if someone could advise me whether I should carry out this procedure out of the box - with no firmware updates applied. Or, should I firstly update to the latest firmware release - Lollipop, then unlock bootloader, install TWRP. Many thanks in advance.
[Nexus 7 (2013) Android Development] madbat99:
You want to unlock boot loader right away as it wipes all data. For root and all, you can do it anytime. You can use the toolkit to update after unlocking. It will flash the whole factory image instead of just doing the ota update. Most say a factory image flash works out better than ota.

My opinion,

1. Unlock boot loader

2. Update to version you want

3. Root and install twrp

4. Profit
[Nexus 7 (2013) Android Development] pretty pixel:
Thank you for the advice. So, to confirm, can I update OTA to Lollipop as soon as I get my device. Then, unlock, root and install TWRP using the Toolkit? Or, do I need to do it in your order - unlock the bootloader first then update to Lollipop?
[Nexus 7 (2013) Android Development] WugFresh:
Yes. Either way, it makes no difference.
[Nexus 7 (2013) Android Development] pretty pixel:
Many thanks :)
[Nexus 7 (2013) Android Development] pretty pixel:
TWRP Key Combination

Can I also confirm the key combination for booting into TWRP Recovery please? Thank you.
[Nexus 7 (2013) Android Development] pretty pixel:
Regarding step 2, do I use the 'Sideload OTA Update' function of the Toolkit? Also, where is the best place to download the latest factory image for the Nexus 7 2013? Thanks.
[Nexus 7 (2013) Android Development] WugFresh:
If its a new device, you probably will get OTA notifications - meaning you can just let the device update without the kit. If you want to use the kit and skip dealing with OTA updates, just use "Flash Stock + Unroot" button. In there you can let the toolkit automatically download the factory image for you. There are also links on that interface for downloading them yourself.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] pretty pixel:
Many thanks for the advice. Nexus devices are new to me, coming from Samsung and Sony :)
[Nexus 7 (2013) Android Development] juliooooo:
Any idea, when the toolkit is updated and able to root on 5.1 for the Nexus 7 2013 Flo?
[Nexus 7 (2013) Android Development] mdamaged:
Asking for ETAs on XDA is a no-no. If you can't wait, just root it manually, it's almost just as easy.
[Nexus 7 (2013) Android Development] juliooooo:
ups ok, got it
[Nexus 7 (2013) Android Development] madbat99:
Just download the factory image and pick "flash stock and unroot" and select no wipe. And wugs roots 5.1 just fine.
[Nexus 7 (2013) Android Development] WugFresh:
Somehow I didn't realize that they posted that the same time as the N4. I just added it, with full support.
[Nexus 7 (2013) Android Development] chriscosta77:
Love this toolkit.

Figured I'd just post this info for those who couldn't sideload the 5.1 update...

Sideloading the 5.1 update from 5.0.2 refused to complete because of the modified system files from previous rooting. So, I just flashed 5.1 over 5.0.2 without clearing userdata. Then I ran the root procedure (even though I had SuperSU survival mode enabled) with custom recovery to get the updates to SuperSU and TWRP.

Everything seems to be running smooth! :good:
[Nexus 7 (2013) Android Development] WugFresh:
Yup. As explained here :)

FAQs - Can I still take an OTA after I unlock and root?
[Nexus 7 (2013) Android Development] JohnSpawnVFX:
I did it yesterday and I can confirm it also. :)
[Nexus 7 (2013) Android Development] chriscosta77:
Whoops!

I didn't set it to Force Flash ... Everything should be ok, right? lol :silly:
[Nexus 7 (2013) Android Development] bamtan2:
Can we not undo the root to make the OTA work?
[Nexus 7 (2013) Android Development] madbat99:
Yes. Flash stock and unroot. Then ota will work. Either flash factory image with fastboot or use toolkit to do it. But why take ota when you can just update with toolkit.