yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] mr_rubbish:
The page on TWRP's site for the tablet offers multiple methods, but lists the "fastboot install method" as "no root required". This is the route I wanted to go along since I wanted the option of being able to push builds to it in future but without worrying about apps detecting root in the meantime. However, it seems that perhaps the instructions are incomplete (they made no mention of having to unlock bootloader as part of the process) or maybe they are not suitable for Marshmallow which may have introduced additional security or perhaps something else.

I think i'll look at flashing back to stock and then try again in a year or two! :D

---------- Post added at 07:10 PM ---------- Previous post was at 06:36 PM ----------

Thanks, I'll take that under consideration the next time I try it. Hopefully, it's easy enough to unroot after TWRP is installed.
[Nexus 7 (2013) Original Android Development] yosmokinman:
^You do not need to be rooted to flash twrp with fastboot. It's the other way around.

Since you know how to use fastboot don't use any toolkit thats just a middleman.

I don't know exactly what the problem is. When was the tablet made? I'm pretty sure the ones made in 2015 need to use the multirom twrp.img

Try running fastboot format cache after flashing the recovery for the hell of it?
[Nexus 7 (2013) Original Android Development] mr_rubbish:
It is a "2013" model (flo) so the images and stuff I selected for it are right. but for whatever reason the flash of the TWRP image didn't seem to take right (even after reflashing it 4-5 times). It lacked permissions to alter/mount the partitions it needed to. It left the tablet in a bootloop in the end.

So I decided to use some of the advice proposed by pkelly & coolek.

I did the following:

1. flashed latest stock rom to restore tablet back to working state

2. installed chainfire's auto root. (via fastboot)

3. installed TWRP manager app from play store

4. flashed TWRP through the app. (root needed)

5. rebooted to TWRP to confirm it works. It does.

6. reboot to android.

7. uninstall #SU

After that I flashed the AOSP 7 build from another thread and TWRP worked fine for this.

It's a convoluted way to go about things but it was fairly easy and each stage was clean.
[Nexus 7 (2013) Original Android Development] Jay Rock:
I'm in the same boat as [MENTION=7694808]mr_rubbish[/MENTION]. Followed the instructions straight from the twrp site but it seems I'll have to take the same route as above.
[Nexus 7 (2013) Original Android Development] mr_rubbish:
As a side note, I checked the TWRP instructions for my old HTC M8 phone and the section for "TWRP no root" is a cut and paste job, identical to that for the Nexus 7, whereas all the other methods were detailed and specific to the device.
[Nexus 7 (2013) Original Android Development] frov:
Hmmm, I had picked up a 2nd hand N7_2013 and threw on TWRP as I do on all other devices and I got into this bootloop. That was quite unexpected :eek:

Luckily I ran into this sequence, so first went back to stock and followed the steps above. Fine, now I got into TWRP as expected. Thanks guys! :)
[Nexus 7 (2013) Original Android Development] mr_rubbish:
I'm glad my many hours of brow-furrowing were able to help someone else avoid wasting time puzzling their way out of that mess! :)
[Nexus 7 (2013) Original Android Development] Sim-X:
Well finally I got this working. Thanks for sharing. I just used your method after getting stuck in a bootloop when flashing TWRP without doing this method. I just got this tablet just to mess around with so a lot of the information out there is outdated. TWRP booted first time no problem once I flashed using the app.
[Nexus 7 (2013) Original Android Development] Bingley:
I just did a full backup, flashed cm 14.1 with 7.1, then booted back, wiped everything, went to restore backup I did 5 mins beforehand and it didn't work, error: e: createTarFork() process ended with Error 255.

I mean, wtf, I only just backed it up, it didn't move from the device. I recall doing this the first time I set up this tablet and the restore didn't work.

Any solution yet?
[Nexus 7 (2013) Original Android Development] KevinX8:
You have to wait for either TWRP to release a new build themselves or someone else with the changes necessary to make backup and restore work on 7.0+, the way 7.0 and higher works now is that the system is sorted into different blobs than before meaning the old recovery method will not work on it so you will have to live without it
[Nexus 7 (2013) Original Android Development] rockingondrums:
Seeing as how this recovery is for both flo and deb, were any of you guys flashing to deb? I have a deb. Would like to not bootloop. Thanks!
[Nexus 7 (2013) Original Android Development] htb2050:
Works on deb. Just check the twrp website for downloads for deb.
[Nexus 7 (2013) Original Android Development] CorporalRE:
Boot Looping

Hi, maybe someone could point me in the right direction, for no reason whatsoever I decided to to root my Nexus 7 2013 Mob30x flo, I downloaded the above Recovery TWRP 3.0.2-0. :) Using Fastboot on my LinuxMint Machine, I first un-locked the bootloader, and then Flashed the above twrp recovery, all seemed well after reboot, the TWRP interface popped up, then nothing but error msgs, unable to load data, unable to decrypt, etc. then at the point it tried to change the recovery file name to Twrp from the stock file, it went into a loop, starting over again until it got to the same point :( This morning using fastboot I wiped all user data and cache, and the Nexus, factory reset itself and booted up normal. :D so I'm all back to square one, I replaced PhilzTouch on my Samsung S5 with the twrp3.0.2-0 recovery last week using the same procedure, and all went well, yes I did use the variant for Nexus, I am a bit wary at the moment to go though it all again, and would greatly appreciate any help/suggestions on the matter. Many Thanks in advance. Dave. PS. It's a great recovery BTW :)
[Nexus 7 (2013) Original Android Development] htb2050:
was your device encrypted when you did this? I haven't encrypted my n7 so maybe encryption had something to do with this. any ways just flash SuperSU zip to root your tablet and then get TWRP recovery root from playstore. select your device and it will auto download and install the recovery for you. then just install any ROM or whatever ever you plan to do with it. This is by far the most fool proof method. nothing can go wrong.
[Nexus 7 (2013) Original Android Development] CorporalRE:
Hi, htb2050, Many Thanks for your quick response, I was wondering about encryption, after reading the changelog at the start of the thread, to my knowledge I don't remember having encrypted anything, (that doesn't mean I didn't) I use a PIN to lock the screen, and SmartLock to disable it, when I'm at home, which I hadn't disabled before flashing, may have caused a problem, however I shall do as you say, and get SuperSU on first and try again. Thanks again, Dave... PS. I don't intend to do much with the Nexus, it just sits there on top of my computer begging me to interfere with it, I read somewhere on xda " Don't fix it if it ain't Broke, and don't Break it if you can't fix it ;)
[Nexus 7 (2013) Original Android Development] amppcguru:
Why does the OP say version 3.1.0-0 is available using the official TWRP App or download from main site, yet it shows that the latest version is still only 3.0.2 for Flo? Is there a new version out yet for flo or not?
[Nexus 7 (2013) Original Android Development] DorianX:
3.1.0 Is officially out but not for Nexus 7 maybe we don't have an official maintainer any more

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 7 (2013) Original Android Development] Gabenoid:
There is no TWRP 3.1.0 in twrp app. Stop lieing! Upload somewhere else the recovery or change the topic name back to previous version.
[Nexus 7 (2013) Original Android Development] osm0sis:
The officially supported devices are all on a thread template so they get updated easily, don't be so dramatic.
[Nexus 7 (2013) Original Android Development] osm0sis:
So, the issue is definitely that there is no maintainer for flo/deb, despite it still being considered a currently supported device: https://twrp.me/devices/asusnexus72013wifi.html

People should ask their favorite active ROM developers for flo to see if they'd be willing, and we can likely get the ball rolling again. :)
[Nexus 7 (2013) Original Android Development] wyldkard:
Looks like someone made the unofficial one possible for the flo and deb

https://xdaforums.com/nexus-7-2013/orig-development/recovery-twrpflo3-0-3-0-t3564280/page2
[Nexus 7 (2013) Original Android Development] osm0sis:
Ah yes, looks like [MENTION=5480152]followmsi[/MENTION] is doing a good job keeping it up to date.

[MENTION=5480152]followmsi[/MENTION], you should become the official maintainer; you probably just need to touch base with the TWRP team on IRC. :D
[Nexus 7 (2013) Original Android Development] followmsi:
Thanks for your feedback ..

Yes, maybe I will take over maintenance for the flo/deb devices ... depends on the expectations and on the work load :)
[Nexus 7 (2013) Original Android Development] pkelly517:
Don't forget dragon!
[Nexus 7 (2013) Original Android Development] followmsi:
Never :)
[Nexus 7 (2013) Original Android Development] TKruzze:
Installed the official TWRP 3.1.0.0 Recovery on my Nexus 7 Flo today and can't get steaming adb backups to my PC to work. Anyone else have it working properly?
[Nexus 7 (2013) Original Android Development] borxnx:
Can you provide more details? Step by step, what did you do that didn't work?
[Nexus 7 (2013) Original Android Development] TKruzze:
I've got it working now, but the solution will not be obvious to anyone else who encounters this...

Before I attempted a streaming backup, I backed up my device using the TWRP app to a USB-OTG device. Apparently, this action will default the app to USB-OTG for the next backup operation. If that next backup operation is done using the TWRP streaming option. it will immediately fail with an error that it can't mount storage. Until I went into the Backup settings of TWRP and manually changed the Storage setting to Internal Storage (from USB OTG), the streaming operation would not work.

So, if your previous backup was NOT made to your device's internal storage, the streaming backup option will always immediately fail with an error that it can't mount storage.
[Nexus 7 (2013) Original Android Development] coolsilver:
Any chance this could be added? Not like many more system images will be coming since support is ending one day soon. It's a nice feature on my Nexus 6 that I can load the image from OTG direct to /system and then install supersu in one go for new updates.
[Nexus 7 (2013) Original Android Development] osm0sis:
I agree. I've always felt all Nexus devices should have this since system.img factory images are readily available. I think we need a maintainer though. Maybe [MENTION=5480152]followmsi[/MENTION] can once he's officially in the role? :) :fingers-crossed:
[Nexus 7 (2013) Original Android Development] followmsi:
Still not sure if I will take over the flo/deb devices .. we will see.

Right now I am working on TWRP for the dragon device - to make it official .. hopefully soon :)

Will keep on playing with "my" TWRP version for the next time ..

"My" flo/deb ramdisk is lzma comrpessed - this way we can pack a lot more "stuff" into the recovery.

The official version still uses gzip compressed ramdisk.

Anyway .. I have made a fast repack of the existing build .. as it's a small fstab change only.

To enable system.img flashing via TWRP ...

TWRP_flo_3.1.0-4-v2017-03-31.img

TWRP_deb_3.1.0-4-v2017-03-31.img

Cheers
[Nexus 7 (2013) Original Android Development] osm0sis:
Ah, never realized it was that easy! Thanks. :)

Edit: For future reference, the change is an added line in /etc/twrp.fstab:

/system_image	emmc	/dev/block/platform/msm_sdcc.1/by-name/system	flags=flashimg=1

:good:
[Nexus 7 (2013) Original Android Development] DorianX:
Hey [MENTION=5480152]followmsi[/MENTION] do you know if is possible to increase the maximum flashable zip limit per session from 10 to maybe 15-20?

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 7 (2013) Original Android Development] followmsi:
10 are not enough per session ? :)

Had a quick look ... here seems to be one part ..

https://github.com/omnirom/android_bootable_recovery/search?utf8=✓&q=zip_queue_index&type=

Have a try and change the values ...

static string zip_queue[10];

if (zip_queue_index >= 10) {

Not sure if there is more relevant code .. ?

You need to compile TWRP with the changed values and test it ...

Good luck !
[Nexus 7 (2013) Original Android Development] DorianX:
Not for me ? I usually flash 15-16 zip's on a clean install, thanks I'll take a look

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 7 (2013) Original Android Development] NeoChontrix:
Is there any know bug or so that the touch screen of the nxus 7 flo is not working in the recovery?
[Nexus 7 (2013) Original Android Development] spainter:
I have the 2013 Nexus 7 Deb and everything works fine here.
[Nexus 7 (2013) Original Android Development] NeoChontrix:
IDk what my problem was after hiting the back of the tabltet a bit it started again and the touch screen is also working again....
[Nexus 7 (2013) Original Android Development] spainter:
Glad you have it working
[Nexus 7 (2013) Original Android Development] Aerobatic:
Seems time to open case and push cables into slots.
[Nexus 7 (2013) Original Android Development] skrewie:
I am on twrp 2.7.1.0 can I flash this or should I upgrade something before ?
[Nexus 7 (2013) Original Android Development] ssceddie:
Does TWRP wipe the internal storage if I wanna do a fullwipe before I wanna flash a new Rom? I ask this, because my USB is broken....I wanna Store the Rom-zip on the Storage, do a wipe and install the new Rom. Is that possible or is TWRP wipe the hole internal space?
[Nexus 7 (2013) Original Android Development] Nevermindthelabel:
Only if you tell it to. A normal factory reset will only wipe apps and data. You have to go into advance wipe to erase internal storage
[Nexus 7 (2013) Original Android Development] ssceddie:
Ok, thats mean, if I switch from marshmallow to nougat Rom , I have to go to advanced wipe and choose Data, System, Dalvik and Cache and then I can flash the new Rom zip from internal storage?
[Nexus 7 (2013) Original Android Development] Nevermindthelabel:
You can, most of the time a factory reset is all you will need. But that will leave internal storage untouched
[Nexus 7 (2013) Original Android Development] dnle71:
Hi! It appears that there's no new images for flo on both download sites (https://eu.dl.twrp.me/flo & https://dl.twrp.me/flo).
[Nexus 7 (2013) Original Android Development] osm0sis:
No maintainer.
[Nexus 7 (2013) Original Android Development] rajsris:
I thought the maintainer was followmsi
[Nexus 7 (2013) Original Android Development] osm0sis:
Nope:

And: https://twrp.me/devices/asusnexus72013wifi.html ("Maintainer: None")

Though I'm still hopeful [MENTION=5480152]followmsi[/MENTION] might reconsider since it would be cool to see his improvements make their way into official builds. :D
[Nexus 7 (2013) Original Android Development] followmsi:
The dragon TWRP is official since April 1st :)

I have asked them for flo/deb maintenance too.

For sure I will not "push" to get this role.

I personally don't need a maintainer "sign" on the TWRP website.

For example I still can make a gerrit TWRP change for the flo/deb devices to add the "missing" /system_image partition into fstab.

Just have sent an email to the TWRP team to trigger the 3.1.1 builds for flo / deb devices.

Enjoy your weekend ..
[Nexus 7 (2013) Original Android Development] rajsris:
Thanks for taking on this work [MENTION=5480152]followmsi[/MENTION]! I'm sure there are lots of Flo/Deb users who are thanking you like me!
[Nexus 7 (2013) Original Android Development] nicky-xda:
Yes, there are for sure, myself included :)
[Nexus 7 (2013) Original Android Development] dnle71:
Just a heads up, the latest image is now available thru TWRP's download sites!
[Nexus 7 (2013) Original Android Development] tombraga:
i made today the update from 3.1.0 (which was working very nice) to the new 3.1.1 - now i lost my TWRP recovery totally.

I made the update with the official twrp app from google store and then tried to reboot to recovery, but it stops on bootloader fastboot.

there i choose revovery mode, but already appears bootloader.~

there is secure boot enabled, is that correct?

so i power off and then i can boot normaly to my system, root is already enabled, but i cannot access more to my TWRP.

what can i do?

followmsi - can you help me please??
[Nexus 7 (2013) Original Android Development] followmsi:
Yes, got email from TWRP team .. flo version is ready.

But the Deb version has problems .. build problems.

Not clear when the Deb version will be ready.

Just to let you know ..

---------- Post added at 10:29 ---------- Previous post was at 10:12 ----------

Just download 3.1.1 img file and flash via fastboot.
[Nexus 7 (2013) Original Android Development] tombraga:
sorry, i am not very into this all, how i flash via fastboot? need to connect to my desktop? thanks a lot for your great help
[Nexus 7 (2013) Original Android Development] followmsi:
The first Google hits ..

https://xdaforums.com/showthread.php?t=2277112

http://www.makeuseof.com/tag/use-adb-fastboot-android/

Cheers
[Nexus 7 (2013) Original Android Development] tombraga:
first thanks for your help

now i found everything and remembered how i installed first time TWRP.

but now i got the problem, that in cmd the nexus is not found, but the drivers are all installed on my windows 10 notebook. and last time it was working.

also i can find and open the directories of the Nexus in windows explorer, so the nexus is connected.

i also tried to swich the different options for connections USB, Fotos, midi etc. but not working in cmd window, device could not be found....

after my succesful instalation some months ago i got 1-2 windows 10 update, can it be that something changed??

but my Nexus is connected, i can see it on explorer window...
[Nexus 7 (2013) Original Android Development] followmsi:
Boot into fastboot mode and install fastboot drivers.

And read, read and read ;)

Good luck !
[Nexus 7 (2013) Original Android Development] dnle71:
Oh, yes! I forgot that this thread is for both devices. I only have flo and I wasn't paying attention to deb. Thanks!
[Nexus 7 (2013) Original Android Development] tombraga:
not lucky...

i tried once more in cmd with adb reboot bootloader, then got:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device ´(null) not found

and now i lost also my root, my god.

and also the developer settings don´t appear more in settings and when i toggle 7 times over the build number there is the message that already developer is activated

everything was so fine until i made the TWRP update today...what happened??
[Nexus 7 (2013) Original Android Development] tombraga:
i could recover, thanks for the help - finally i used nexus root toolkit

i don´t know, what i made wrong when i tried to update this morning with twrp app from google play store..??
[Nexus 7 (2013) Original Android Development] rajsris:
We could close this thread now that the official TWRP is back...
[Nexus 7 (2013) Original Android Development] osm0sis:
This is the official thread...
[Nexus 7 (2013) Original Android Development] rajsris:
Whoops my mistake! Followmsi had a separate unofficial thread which can be closed for less confusion
[Nexus 7 (2013) Original Android Development] Petermira:
Any one knows why i can see the CPU temp in the Touch recovery and i cant under the Android operating system? I am running crDroid 3.3 ROM with elementalx 6.07!

Regards
[Nexus 7 (2013) Original Android Development] klaust58:
Maybe because TWRP has the right code for this and crdroid not... :cowboy:
[Nexus 7 (2013) Original Android Development] PlayersHeaders:
Twrp freeze bug

Hi, this TWRP also has this bug here https://xdaforums.com/oneplus-3t/help/twrp-stuck-splash-screen-t3541037

This is what worked for me :)

Best regards

Juri
[Nexus 7 (2013) Original Android Development] DaveImagery:
I see latest version is 3.2.1. What is the "Download PGP Signature" link below the 3.2.1 download link? I don't know what to do with that. Does that get flashed as well?
[Nexus 7 (2013) Original Android Development] spainter:
That is so you can check the file you downloaded for errors. You don't flash it. On Flo and Deb all you have to worry about is the image file .img
[Nexus 7 (2013) Original Android Development] DaveImagery:
Okay, many thanks :)
[Nexus 7 (2013) Original Android Development] BhNeP:
After a lot of searching after I started getting the Error 255 message (for the system partition) after trying to restore my flo's Resurrection Remix 5.8.5 ROM with TWRP 3.2.1 I came across this thread. A possible solution I found might be the app [root]Flashfire. It can make complete backups that can be written to internal memory, USB-OTG or even pc harddrive through ADB.
[Nexus 7 (2013) Original Android Development] colinjoseph:
The TWRP website instructions say download the official TWRP app from play store (recommended) and follow the instructions. When I try to download the app on my laptop it fails. I can't download it onto my tablet because it is not working. That is why I am trying to flash TWRP. But I need TWRP on my laptop in order to flash it to the tablet.
[Nexus 7 (2013) Original Android Development] osm0sis:
Alright, time to necro-bump this thread. 😈

flo is still being officially built thanks to automation and some minimal-intervention upkeep by the TWRP devs; deb hasn't been so lucky, (but really just needs a maintainer).

Now that flox is a thing official TWRP of course won't work for it anymore. @kiraryu found there are some simple changes to the official TWRP flo .img that are possible to support flox without needing a full rebuild, but unfortunately hasn't created a thread or released them anywhere other than AFH.

Since repacking .img files and injecting ramdisk changes has always been my bread and butter, I diff'd official and the repacks and found it's mostly prop value name changes, and the addition of /vendor to the fstabs. Well then, this is exactly the kind of thing my AnyKernel3 project was designed to do, so to make this process easier going forward for all, get the exact changes out there, and allow everyone to do it themselves, here's a flashable zip to automate it all! :cowboy:

N7-13_TWRP_flo2flox_Injector_Addon-AK3-signed.zip: [XDA] [AFH]

Installation is easy, simply flash the latest official TWRP .img, then boot to recovery or use FKM to flash the TWRP flo2flox AK3 zip, then reboot to recovery to see the effects. Flashing it by mistake over itself has no ill effect since I fully utilized AK3's change-checking functions.

Happy hacking! 🤘
[Nexus 7 (2013) Original Android Development] sirxdroid:
Are there still Nexus 7 tablets out there that work?
[Nexus 7 (2013) Original Android Development] ipdev:
My deb and flo(s) are running lineage 18.1 :D

Cheers. :cowboy:
[Nexus 7 (2013) Original Android Development] osm0sis:
Yep, flox'd mine (with @k23m's badass CROSS sysrepart-ultimate.zip preset) a month or two ago, so all this is spin-off development from me wanting to get it working how I want. :p
[Nexus 7 (2013) Original Android Development] BLewis4050:
:cautious:
[Nexus 7 (2013) Original Android Development] taadow1030:
Hello and thank you for creating this update. I have a Deb that I'm trying to convert to Flox. When I flashed the zip, I received an error 1 (unsupported device... aborted installation). Please advise if I'm I missing a step.
[Nexus 7 (2013) Original Android Development] colin p:
My N7 2013 finally "blew up" last December, or at least the battery popped the screen off. I had been using it as a clock for a couple of years. That role has now been given to my N4.
[Nexus 7 (2013) Original Android Development] BLewis4050:
Does this still work for new TWRP 3.7, or is it even still needed?