yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] chickentech:
I know - that's why I was looking for TWRP - not MultiRom TWRP... Now that I've been using it I realize that it isn't too much different and I can just ignore the multirom stuff in it... but would still rather have vanilla TWRP installed.
[Nexus 7 (2013) Original Android Development] madbat99:
It's exactly the same besides that menu. If you don't have multirom installed, that menu does nothing. The dev of multirom said that if you uninstall multirom framework, the recovery is fine to keep, just ignore the extra menu. He even keeps it updated with official so you should be fine. It has all features of official.
[Nexus 7 (2013) Original Android Development] DaveImagery:
Noob question.

Does saving a TWRP system image to an external thumb drive, then onto a backup drive on my pc, and then moving it back onto the thumb drive for restoration, break it somehow? I've encountered this several times recently, where the backup restoration fails with error 255.
[Nexus 7 (2013) Original Android Development] madbat99:
It can corrupt, especially with large backups. It's not very common, but it happens. Set twrp to generate md5 sum with backups. Also set to check md5 upon restore. That way you know it hasn't (or has) been corrupted. Also make sure you have the correct file path on backups, so twrp can see them.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Looks like TWRP 3.0.0 is inbound for all supported devices, it's possible to check the status of the builds on their site too:

https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
[Nexus 7 (2013) Original Android Development] osm0sis:
3.0.0-0 build failed for flo/deb unfortunately, so we'll have a bit longer to wait:

https://jenkins.twrp.me/job/flo-prod/

https://jenkins.twrp.me/job/deb-prod/
[Nexus 7 (2013) Original Android Development] quickdraw86:
Darn. Oh well, I probably would've waited a bit to try it anyway to see how it was treating others. It takes me awhile to fully trust a new recovery version. Thanks for the heads up.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Yeah, perhaps no bad thing.... The last twrp I flashed hot of the press completely wiped my files!

Cheers.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Yeah, I'll try just about any ROM or kernel once, but am not as adventurous as I used to be with recoveries or radios. Some partitions are much more important than others lol.
[Nexus 7 (2013) Original Android Development] z31s1g:
A little treat until Jenkins produces something official:

twrp-3.0.0-0-flo_homebrew.img

Tested working backup and restore. Doesn't wipe anything unless you tell it to. ;)

Does not have F2FS support!
[Nexus 7 (2013) Original Android Development] semdoc:
When I needed to build TWRP, I remmeber I disabled building some parts in kernel - like PRIMA.. Then resulted recover was fitted to partition..
[Nexus 7 (2013) Original Android Development] osm0sis:
I wonder if [MENTION=3418703]Tasssadar[/MENTION] is going to do some official MultiROM updates again now that 3.0.0 is out. :fingers-crossed:
[Nexus 7 (2013) Original Android Development] z31s1g:
I only used zImage compression to get the image below the 10MB threshold.

Do you get an error trying to install the image?
[Nexus 7 (2013) Original Android Development] semdoc:
We are CM based AICP ROM. So I'm using mdmower's custom TWRP source to build..

Here are my trees:

deb: https://github.com/semdoc/device_asus_deb/commits/TWRP-mm6.0

flo: https://github.com/semdoc/device_asus_flo/commits/TWRP-mm6.0

And also: https://github.com/semdoc/kernel_google_msm/commit/85f907e09f5c2ed0ad4ebc4d2cd31437d866a8ae

With these, all is fine - booting, flashing etc...

And [MENTION=2719389]z31s1g[/MENTION], I want to thank you for your awesome work with New TWRP theme :)

Amazing job Man :):good::good::good:
[Nexus 7 (2013) Original Android Development] osm0sis:
Tasssadar to the rescue with new MultiROM builds!

http://xdaforums.com/showthread.php?p=65203196#post65203196
[Nexus 7 (2013) Original Android Development] gorilla p:
I assume this has a comparability fix for the eMMC change made to the recent batches of N7's?
[Nexus 7 (2013) Original Android Development] osm0sis:
No idea. Check his GitHub?
[Nexus 7 (2013) Original Android Development] redDEADresolve:
TWRP 3.0 does fix the eMMC bug that plagued the newer Android 5.0 shipped Nexus 7 flo's.

Don't see why the multirom image built off of it wouldn't.

You can use

fastboot boot twrp.img

to test it without flashing it. Assuming you rename the image to twrp.img
[Nexus 7 (2013) Original Android Development] gorilla p:
The multiRom version was actually the only one that worked, because someone compiled a 2872 update for it, which included the fix. There still hasn't been an official 2872 release for it.

I have an older one, but configured newer ones for others (hard to beat at $109-119).
[Nexus 7 (2013) Original Android Development] nazfalas:
Thank you! Working fine on deb.

Edit:

Haha, spoke too soon. TWRP for flo obviously works great on deb, but when trying to flash something it will be detected as flo and refuse to continue.
[Nexus 7 (2013) Original Android Development] osm0sis:
Successful official builds in the last half hour, presumably they'll be up on the download site later today. :fingers-crossed: :)

https://jenkins.twrp.me/job/flo-prod/

https://jenkins.twrp.me/job/deb-prod/

Edit: The builds are live! :victory:

https://dl.twrp.me/flo/

https://dl.twrp.me/deb/
[Nexus 7 (2013) Original Android Development] Killer2326:
For people not to go through the DL trouble

Here is the easy DL I do not own this! And don't worry about warning i would show screenshot but idk how to take one on twrp. BTW guys if ur using a flo device I suggest the cyanogen ROM or pure nexus ROM but the pure nexus ROM has no support for smart cover at the moment, anyway guys enjoy twrp 3.0
[Nexus 7 (2013) Original Android Development] osm0sis:
Not sure why you bothered, it's super easy from the official site direct links I provided..
[Nexus 7 (2013) Original Android Development] anthony.wang:
Is anyone experiencing very slow flashing times with both flashing CM13 nightlies and/or Open Gapps packages?

On 2.8.6.0 flashing Opengapps maybe takes 3 minutes, but now it takes upwards of 10 minutes. And the table takes forever, I mean minutes, on the steps "gather device and ROM information" and "Performing system space calculations" --> this couldn't possibly (and hasn't before) take that long?

Also, I found that while flashing the above, if you let the screen "go to sleep" after the timeout, sometimes the flashing progress freezes, even when you wake up the device again (the progress bar sliding part still moves, but the progress never moves along afterwards, i.e. the flash never completes). When this happens, I have to reboot into recovery again and re-flash, while tapping the screen once in a while to keep it awake.

I'm on nightly CM13 with encryption and official TWRP 3.0.0-0.
[Nexus 7 (2013) Original Android Development] phoenixg36:
I also flash the last cm13 and it take a long time on my deb. First it looks like nothing happens but then on step is done and again looks like frozen. after a while it is finished and everything works. I'm not sure but I think my device is not crypted.
[Nexus 7 (2013) Original Android Development] osm0sis:
That's been reported on other devices as well, it's likely something they'll have to work out in 3.0.1.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Can confirm your issues and another problem. If you do let your device go into deep sleep, no amount of tapping will wake the device.

BTW, thanks to the twrp team for their hard work.

---------- Post added at 22:15 ---------- Previous post was at 22:10 ----------

Do you know if it is possible to revert to an earlier version of twrp?

Thanks.
[Nexus 7 (2013) Original Android Development] Jhall8:
Yes, just flash the prior version.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks mate.

One strange thing about all this is that even though I had to force a reboot after each .zip I flashed when twrp became unresponsive, they all stuck...by which I mean the ROM, gapps, su etc. I flashed ended in a successful boot.

Cheers.
[Nexus 7 (2013) Original Android Development] MashBill:
It is working on my flo, but it is very slow when flashing anything.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Just revert to 2.8.7.0 until it's fixed...

Cheers.
[Nexus 7 (2013) Original Android Development] Tool Belt:
Working just fine here.
[Nexus 7 (2013) Original Android Development] chaztro1892:
I agree, seems very slow when flashing.
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Slow flashes have been reported in 3.0.0.0 across multiple devices since 3.0.0.0 was released
[Nexus 7 (2013) Original Android Development] jimbob_sf:
I love v3 - awesome resurrection!

...but had to move back to, 2.8.7.x because of the slow flash and nearly endless boot after. All good with older version. I'm sure they'll figure it out.

I had to do it on any CM based ROMS for flo and v1awifixx (all MM). vs985 on aosp MM is fine.
[Nexus 7 (2013) Original Android Development] poondog:
For what its worth, I had this version on my tablet until today

The homebrew version seems to be flashing stuff at normal speed. The new one I got from the TWRP site (3.0.0-0-flo) was so slow, that when I flashed with 6% left, it ran out of battery before finishing (I flashed OMNI and Nano opengapps)

So for those who are experiencing slow speeds I would suggest the homebrew version that I quoted above :)
[Nexus 7 (2013) Original Android Development] osm0sis:
Good work testing! [MENTION=2719389]z31s1g[/MENTION], [MENTION=4878287]_that[/MENTION], might this help with a fix? :)
[Nexus 7 (2013) Original Android Development] Ted C.:
Homebrew and Wug's

Works great, no issues for me at this time.... :D
[Nexus 7 (2013) Original Android Development] g2uzer:
Thanks for the hard work, I'm using the link from OP, and like its been mentioned before its slow to flash. At first I kept rebooting cause I thought it was getting stuck lol , other than that I couldn't restore the first back up I did. Not sure why , it failed At 50 %. Regardless I was able to flash PureNexus after a few retries, Thanks again for your time and work!
[Nexus 7 (2013) Original Android Development] cdonald:
I flashed the homebrew version over the official 3.0.0.0 and now my flo shows internal storage/data as 0 mb and empty when I'm in recovery. However, upon booting to system, everything is still there as it is expected to be. Any ideas why this is happening and how to remedy it?

Edit: I think it messed up my partitions because my /data and /cache are formatted as f2fs. Had to format data, install the official twrp, and reinstall everything to get my internal storage working properly on f2fs again.
[Nexus 7 (2013) Original Android Development] g2uzer:
My available storage is showing about 1/4 of what i should have since I just wiped everything including internal sd. I have read somewhere if I lock and unlock my bootloader I should get all my storage back, question is if I can lock my bootloader running a custom ROM or do I need to flash stock before I lock it and unlock it? Anyone had this issue after flashing twrp or is it more of a custom ROM related? I just noticed it today but I never paid attention right after I flash twrp. Thanks
[Nexus 7 (2013) Original Android Development] osm0sis:
Sounds like you flashed userdata.img by mistake, it isn't set up for 32gb devices. Try to use ResizeFS in TWRP under Advanced Mount, and if that doesn't work, no need to lock and unlock, just: fastboot format userdata
[Nexus 7 (2013) Original Android Development] g2uzer:
Where exactly is ResizeFS? I looked under advance and only see copy log, fix permissions, file manager ,terminal command, reload theme and ABD side load

And under mount it's system, data,cache,USB otg and disable MTP thanks for your help,

Also fastboot format data under wipe is the other option?
[Nexus 7 (2013) Original Android Development] osm0sis:
Sorry, Advanced Wipe, and if ResizeFS doesn't work then fastboot format userdata is the command to use.
[Nexus 7 (2013) Original Android Development] murdoch1:
Twrp homebrew

Hi. I can't find the homebrew 3.0.0.1 file. would someone please link to the file please?? I'm running a flo nexus 7.
[Nexus 7 (2013) Original Android Development] z31s1g:
EDIT:

Link removed, don't know anything about a 300-1 homebrew.
[Nexus 7 (2013) Original Android Development] BladeRider:
Would like to know are there any development on going for the TWRP for Flo/deb?
[Nexus 7 (2013) Original Android Development] z31s1g:
Development is ongoing for TWRP in general. Flo is just another device that receives a build of a new release.

If you're asking if "there's a person focusing on improving TWRP for Flo (device maintainer)", that would be Dees_Troy. But he's the listed maintainer for most of the supported devices, so naturally he can't focus on the device to the same extend other device maintainers do (there are maintainers that only work on HTC or Samsung devices for example).

So, if there's something amiss with the flo build, it needs to be brought to Dees_Troys attention. The IRC channel (link is in OP) seems the best way to get in contact.

Otherwise nothing will improve, as there's no "dedicated" device maintainer monitoring this thread.
[Nexus 7 (2013) Original Android Development] meekrawb:
If no one else is going to do it, I will try the IRC channel tomorrow. Been away for awhile and was pretty confused when it took 7 minutes to flash SuperSU. Glad I am not the only one.

Took less than a minute to get an answer on IRC.

[17:52] <meekrawb> Looking for some help with version 3.0.0-0 on Flo. We are having the slow flashing problem.

[17:52] <jcadduono> open twrp terminal, type "rm /sbin/modprobe"

[17:52] <jcadduono> at least i think thats the temp solution...not sure

[17:53] <jcadduono> i heard that from a guy who knows another guy whos cousin tried it

Note: Pretty sure you have to run the rm /sbin/modprobe command every time you boot into TWRP.

SuperSU flashed pretty fast after that.

Hopefully it works for flashing ROM's as well.
[Nexus 7 (2013) Original Android Development] osm0sis:
It should. Here's the why and how of it, and a link to the commit which will work around it for the next build:

http://xdaforums.com/showthread.php?p=65942841#post65942841
[Nexus 7 (2013) Original Android Development] spainter:
Version 3.0.1-0 fastboot to memory well and comes up a lot faster
[Nexus 7 (2013) Original Android Development] xtacb4:
Is anyone getting "size of image is larger than target device" when trying to flash twrp-3.0.1-0-flo.img ? I tried both in TWRP flash image and via adb fastboot flash recovery.

edit: I have flo.
[Nexus 7 (2013) Original Android Development] iluvatrix:
I don't face this in deb flashing via twrp manager
[Nexus 7 (2013) Original Android Development] xtacb4:
I cant flash it with twrp manager as it does not show this last version. :crying: I have flo.
[Nexus 7 (2013) Original Android Development] boardlord:
Because the image for deb is under 9MB as it should be. The image of 3.0.1-0 for flo is over 11MB so the build is almost certainly derped.
[Nexus 7 (2013) Original Android Development] Valsorim:
Tried to flash w RASHR, recovery partition is 10MB and as noted TWRP is 11.2MB file for Flo
[Nexus 7 (2013) Original Android Development] Nomelas:
im on flo and just unlocked bootloader and flashed twrp 3.0.0-0, it tried to boot into recovery but I get a wall of red text and then it reboots again, repeat:

could not mount data unable to find crypto folder

unable to mount storage

Failed to mount '/data' (argument invalid)

etc....

halp?!
[Nexus 7 (2013) Original Android Development] g2uzer:
Try flashing a older version
[Nexus 7 (2013) Original Android Development] boxcar8028:
yeah, same here. had to flash back to 3. 0
[Nexus 7 (2013) Original Android Development] VipKattKool:
can't flash 3.0.1 because 'size of image is larger than target device'
[Nexus 7 (2013) Original Android Development] osm0sis:
Yup. It's larger than our 10mb recovery partition. Could probably steal the smaller sbin binaries from the deb image and put them into flo to make a working one.. Hmm.

Edit: Nope. Most of the size difference is in the zImage, not the ramdisk. But, that might still work, since they share a kernel.. ;)
[Nexus 7 (2013) Original Android Development] osm0sis:
deb's ramdisk looks more up-to-date, with the /supersu directory removed and the /vendor directory (containing keychains) added, so I made those two changes to flo, copied the /sbin contents from deb to flo (which adds missing f2fs binaries and likely code in the recovery binary to match) and used deb's smaller zImage. Tested and looks like it all works! :cowboy:

So here's one to play with until we get a 3.0.1-0 reupload or 3.0.1-1 to officially fix the flo build issues. :good:

[ Attachment removed now that a newer version is available ]
[Nexus 7 (2013) Original Android Development] Jhall8:
Thank you very much! Working perfectly on my Flo. :)
[Nexus 7 (2013) Original Android Development] xtacb4:
Was able to flash it, seems to be working, thanks!
[Nexus 7 (2013) Original Android Development] Aerobatic:
Seems OK
[Nexus 7 (2013) Original Android Development] yiannis1621991:
Does the latest version fix the bug in 3.0 that flashing files was taking forever?
[Nexus 7 (2013) Original Android Development] osm0sis:
Yup. Check the OP. It's in the official changelog. :good:
[Nexus 7 (2013) Original Android Development] mbdw:
I just recently upgraded to 6.0.1 and got the 'size of image is larger than target device' error when I tried to flash TWRP 3.0.1 using adb (was previously on stock recovery). I've tried (using adb) to go back to 3.0 and earlier versions, as well as the stock recovery, but I keep getting the "no command" error when I go into recovery.

Any suggestions on how to fix the error?
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Download the recovery file in post 644, try using the apps flashify or TWRP manager
[Nexus 7 (2013) Original Android Development] mbdw:
Thanks! Worked perfectly, even through adb (not rooted right now, so I couldn't use flashify or twrp manager)!
[Nexus 7 (2013) Original Android Development] PizzaDroid:
Same issue here when I try to flash the downloaded file. It's 11MB instead of 8.6 MB for version 3.0.0

TWRP Manager has the same issue.
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Post 644 has what you need...
[Nexus 7 (2013) Original Android Development] PizzaDroid:
I don't know Post 644. Can you give me a hint please.

Gesendet von iPhone mit Tapatalk
[Nexus 7 (2013) Original Android Development] jaibar:
The hint is to open post #644 and download the zip file from there.

What more hint do you need??
[Nexus 7 (2013) Original Android Development] maximusmullivan:
My answer was pretty straightforward...find post 644 and download the recovery img from it. That's what you're looking for
[Nexus 7 (2013) Original Android Development] biohaz55:
TWRP 3.0.2-0

TWRP 3.0.2-0 is now available with a size of 8.7MB
[Nexus 7 (2013) Original Android Development] osm0sis:
Perfect, and it's got everything changed that I mentioned in my post that was different. :)

Thanks for playing, folks!
[Nexus 7 (2013) Original Android Development] k23m:
TWRP 3.0.2-0

Is it the "ElementalX-5.00" branch of https://github.com/flar2/flo being used in the TWRP 3.0.2-0?
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Has anyone noticed files disapering after downloading? [Twrp 3.0.2.0]

Cheers.

Edit: It was not a twrp issue, it something else entirely...
[Nexus 7 (2013) Original Android Development] MT2-User:
Thanks to 3.0.2.0, now it only takes less than 2 minutes to update OMNI ROM (+flashing SupetSU)! It took more than 30 minutes before.
[Nexus 7 (2013) Original Android Development] Valsorim:
Have issue w twrp yesterday when converting to f2fs for data and cache, PureNexus + Elemental kernel would not boot. After going back into twrp to wipe noticed data + cache showed as still ext4. In the end did full wipe and reflashed w ext4, everything works fine. But conversion to f2fs is borked somehow now
[Nexus 7 (2013) Original Android Development] NoN1979:
Use TWRP 3.0.0 or 2.7.0 for f2fs
[Nexus 7 (2013) Original Android Development] htb2050:
Is anyone else seeing really sluggish performance on 3+ twrps? It takes more than 10mins to flash a single rom and gapps whereas on 2.8 it takes less than 2mins. I have reverted back for now.
[Nexus 7 (2013) Original Android Development] pkelly517:
Update to the latest.

Or

rm /sbin/modprobe
[Nexus 7 (2013) Original Android Development] coolsilver:
Any chance of this being built with image flashing to /system like on some other devices?
[Nexus 7 (2013) Original Android Development] osm0sis:
I hope so!; I've been saying for awhile that I'm surprised that the Nexus device aren't already all built with that by default since they have readily available Factory Images.
[Nexus 7 (2013) Original Android Development] technique00:
Hey guys, I just purchased a used Nexus 7 (2013) on swappa. its running 6.0.1, Build number M0B30P, Kernel 3.4.0-g1fc765b. The bootloader is unlocked. Do I have to flash the factory KK image before installing TWRP, or can i flash openrecovery-twrp-2.8.5.0-flo.img via SDK as is? Thanks a lot
[Nexus 7 (2013) Original Android Development] alfick3:
You should be able to just flash the latest TWRP.
[Nexus 7 (2013) Original Android Development] technique00:
Thanks. So to be clear, I should be able to flash the latest TWRP specifically for the NEXUS 7, even though it was for KK and my device is on Marshmallow? Don't suppose you cold send a link? thx
[Nexus 7 (2013) Original Android Development] alfick3:
There latest TWRP is actually 3.0.2 and can be gotten here: https://dl.twrp.me/flo/

Edit: you are planning to flash via fastboot, right? That's the best way to do it, in my opinion.
[Nexus 7 (2013) Original Android Development] technique00:
yes, planning to flash via fastboot indeed. Thanks a lot!
[Nexus 7 (2013) Original Android Development] mr_rubbish:
Nexus 7 (flo) now boot loops

Reading about the release of TWRP 3.0.2.0, I thought I'd give it a try on my spare Nexus 7 (flo) tablet.

So I:

- Enabled dev mode

- enabled USB debugging

- installed all the latest ADB bits

- jumped into the bootloader

- unlocked bootloader (edit)

- agreed to data wipe, let it reboot (edit)

- pushed TWRP.IMG (v3.0.2.0) to the device

- fastboot rebooted

Now it is stuck in a boot loop where TWRP tries to write to the system to prevent the stock ROM from reverting the recovery. I've tried pushing v2.8.7.0 and it doesn't seem to make any difference. Pushed v3 again and it brought up the Android animated screen and just held at that screen for 10+ mins. Rebooting got me into the TWRP menu but it doesn't seem to be reading the partitions correctly.

At present it's back to the boot loop. attached is a screenshot of TWRP as it tries to run the 'OpenRecoveryScript'. Lots of errors as it fails to mount any of the partitions it needs to.

Any suggestions on how to fix this?
[Nexus 7 (2013) Original Android Development] coolek33:
Shouldn't it be to root before twrp push? Anyways I'll be flamed here for what I say... For such users (U screwed it already though) there are toolkits :p wugs nexus root toolkit is the simplest and laziest tool for you. Flash stock first and then wug your device.
[Nexus 7 (2013) Original Android Development] pkelly517:
You also have the option of using Chainfire's auotoroot.

There are a few tricks that must be followed, in a particular order, to achieve a lasting TWRP. It may also be that you are encrypted.

Anyhow, good luck.