yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] hazard209:
I'm also experiencing the "No OS" error. Also the TWRP manager keeps crashing when trying to flash a recovery image. Sent the crash reports.
[Nexus 7 (2013) Original Android Development] sean222:
Latest SuperSU and Flashify worked great on my Hammerhead, did the EXACT same thing with my Flo and no go.

2.8.2.0 flashes OK with Flashify, I get into 2.8.2.0 just fine, no SD card access though! Even with latest SuperSU 2.30 :(
[Nexus 7 (2013) Original Android Development] Spyr0s:
2.8.2.1 is up
[Nexus 7 (2013) Original Android Development] Spyr0s:
no sdcard
[Nexus 7 (2013) Original Android Development] meekrawb:
Yeah, 2.8.2.1 still broken here too.
[Nexus 7 (2013) Original Android Development] madLyfe:
i no longer get the no os installed, but it just reboots back into TWRP when rebooting to system..
[Nexus 7 (2013) Original Android Development] sean222:
Same here, no SD card access on 2.8.2.1 :(

Flashed with Flashify and SuperSU 2.35 too.
[Nexus 7 (2013) Original Android Development] Spyr0s:
2.8.2.2 is up :p
[Nexus 7 (2013) Original Android Development] madLyfe:
this seems to be working for me now..
[Nexus 7 (2013) Original Android Development] sean222:
Thought you were joking!!!

Yes finally 2.8.2.2 works on Flo!!! SD card access is there :)
[Nexus 7 (2013) Original Android Development] Spyr0s:
Yup just flashed supersu 2.35 and finally im rooted
[Nexus 7 (2013) Original Android Development] meekrawb:
2.8.2.2 zips

Now that it works, here are the 2.8.2.2 zips.
[Nexus 7 (2013) Original Android Development] Dees_Troy:
I don't have a flo or deb so that makes updating this device a little more difficult. We ran into an issue where the bootloader was corrupting the command line, but only when flashing the recovery. When temporarily booting the image like we often do during testing, the corruption didn't occur. The corruption caused the recovery to boot with selinux enforcing which caused a lot of problems.
[Nexus 7 (2013) Original Android Development] szale9001:
Yes sir, it does!

And many thanks to the twrp team for this release. Without the device in hand, I'm sure it wasn't easy so thanks for the extra effort!
[Nexus 7 (2013) Original Android Development] bleuxeon:
Thanks a lot, worked for me.

But how can 2.8.2 be still in the download section for flo???

It will screw up things on a lot of flo devices...
[Nexus 7 (2013) Original Android Development] matt4321:
people will naturally go for the highest version 2.8.2.2 so it should be fine, who would download 2.8.2.0?

All versions usually just stay up, this is what I've seen with other devices even with versions that don't work
[Nexus 7 (2013) Original Android Development] jaibar:
Well, I am one of these people- or almost was.

You see, I read OP and installation instructions. It says to install TWRP manager from Google Play Store. Fine.

Now, I usually try to refrain from "manager" softwares- only got problems using these types of softwares such as ROM Manager that usually apply simple scripts in the name of the users, but somehow manage to screw things in a simple process of sending two command lines.

But if it is in OP instructions, and the software name implies it is from TWRP team, so I said okay, let's give it a try.

So I open this manager, put my device name, and then choose to install TWRP. The list opens and I can see indeed all the versions backward. But who will chose an older version?? As you said, people will go latest. Yep.

I chose latest version from the list- and guess what's the latest one in TWRP manager?? 2.8.2.0 :laugh: :laugh:

I guess lots of innocent will fall on this one, trusting the TWRP manager to be updated to latest version. Those who happened to check last posts in this thread will be ok...
[Nexus 7 (2013) Original Android Development] NYCHitman1:
That app is not made by the TWRP team. Dees does collaborate with the developers of it, but he is not officially affiliated with them at all.

However, I will say that I believe it's the best recovery tool we have available to us as root users on Android.
[Nexus 7 (2013) Original Android Development] jaibar:
Actually, the best recovery tool for android is 4ext recovery. Or was, unfortunately, as its Dev seems to have stopped for a while until he reworks from scratch. The dude had created the most advanced touch recovery years ago, while cwm was still an ugly green (or blue, don't remember)-colored hardware-button destroyer, and twrp was nonexistent. In his site he says nexus support in the future- no eta asking...

But sure, twrp is nice & cool, is maybe next best. I have it in most of my devices, and occasionally one can encounter some bugs or problems. In nexus 5 I had eventually switched to philz for quite a long time and it worked perfect- but i always prefer looks over functionality so I recently flashed twrp again. However, one has to keep in mind it is far from perfect, as can be seen from reading the last few pages of this thread.
[Nexus 7 (2013) Original Android Development] cujo6801:
I loved using 4ext. Recovery

Back in the day...

Sent from the "DOG" pound
[Nexus 7 (2013) Original Android Development] NYCHitman1:
4EXT was great when I had my 3VO, but the project is dead now, which makes it irrelevant.
[Nexus 7 (2013) Original Android Development] 1TonyC:
So tried to install TWRP 2.8.2.0 using TWRP Manager and am getting the "No OS Installed!" error. Any suggestions on how to fix the device? Thanks.

Edit: Sorry for the post without reading. I was able to get into the bootloader and get back into the system. Then I installed an earlier version of TWRP using TWRO Manager.
[Nexus 7 (2013) Original Android Development] LP6:
Reading the thread before asking is always a good policy. :)

You should actually install the newest version which should be 2.8.2.2 at the moment.
[Nexus 7 (2013) Original Android Development] antonholmstedt:
Looks like twrp website is down, anyone got the latest img and mind upload it to a mirror? :)

Edit: Never mind, site is up again :)
[Nexus 7 (2013) Original Android Development] coolek33:
Check again or check your connection.
[Nexus 7 (2013) Original Android Development] Nomad1600:
Help! On a Nexus 7 2013 Wifi (Flo), running SlimKat(4.4.4). Tried to update TWRP to 2.8.2.2 via TWRP Manager from Play Store. It appears it failed, and when I went to Recovery (TWRP) it shows its 2.8.2.0, it says "No OS Found" and nothing appears in Backups so I can't restore a nandroid. I tried attaching to my laptop and my laptop doesn't appear to recognize the tablet. Am I completed hosed? If not, can someone step me through what I can do to get back to a working ROM? ﻿

---------- Post added at 06:48 PM ---------- Previous post was at 06:38 PM ----------

I held down power button and got back to SlimKat. Since I failed using TWRP Manager is there a better/foolproof wasy to update to 2.8.2.2? ﻿

UPATE: Used Flashify to update TWRP to 2.8.2.2 and all is good now.
[Nexus 7 (2013) Original Android Development] sriharsha2172:
http://techerrata.com/browse/twrp2/flo

While trying to download from the above link, Download stuck at 99.99%. later found zip from previous posts in this thread but when flashed the recovery from fastboot, it still shows 2.8.2.0 in the recovery, I'm confused whether it is installed or not
[Nexus 7 (2013) Original Android Development] crypticc:
Hi

Is there something up with flashing OTA upgrades on these more recent recoveries?

The latest 5.0.1 upgrade gave error as per link here>

script aborted: Package expects build fingerprint of

google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.

http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/issue-upgrading-5-0-0-to-5-0-1-nexus-7-t2965677

Curiously CWM gave a different error. It was reporting a current device key of KOT9H which I haven't had for some time. It seems to me that the OTA is checking base of recovery.img somehow - I do not recall needing to worry before.

Bypassed by installing via fastboot from Google factory images for now- but I remain curious.

Thank you

Chris
[Nexus 7 (2013) Original Android Development] snickle:
2.8.2.2

Whenwill it be available via twrp manager?
[Nexus 7 (2013) Original Android Development] gohabs93:
I got the NO OS . I then I power off device and now it does not turn on anymore. It gets detected by windows as Qualcomm HS-USB QDLoader 9008

Edit: Nevermind...works now
[Nexus 7 (2013) Original Android Development] Gareee:
I flashified the update, but it looks like I no longer have the extended reboot menu on lollipop...is there one everyone recommends?
[Nexus 7 (2013) Original Android Development] kindofabuzz:
I use the Rebooter shortcut that comes with ROM Toolbox Pro.
[Nexus 7 (2013) Original Android Development] Gareee:
I've got a reboot widget now, but I kind of miss having one tied into the power button.
[Nexus 7 (2013) Original Android Development] meekrawb:
2.8.3.0 zips

Here are the 2.8.3.0 zips.
[Nexus 7 (2013) Original Android Development] magarto:
Cannot decrypt data with new release.
[Nexus 7 (2013) Original Android Development] LittleConfucy:
If I update the Recovery, would the theme persist?
[Nexus 7 (2013) Original Android Development] mrshades812:
It will have some issues. Themes have already been updated for the latest release.
[Nexus 7 (2013) Original Android Development] rockingondrums:
None of the settings (date, brightness) seem to stick between reboots, and my data partition won't mount anymore.

I'm using a flash drive to flash things now.
[Nexus 7 (2013) Original Android Development] idCyber:
How can I mount my USB OTG flash drive with NTFS in TWRP 2.8.3.0 ? I have a Kingston DataTraveler microDuo 2.0 16GB . It gets recognised if it's FAT32 but I really need NTFS for large files. Someone help with a solution please.
[Nexus 7 (2013) Original Android Development] HowardZ:
I also could not decrypt using cyanogenmod 12 on nexus 7 lte model
[Nexus 7 (2013) Original Android Development] meekrawb:
2.8.4.0

2.8.4.0 zips.
[Nexus 7 (2013) Original Android Development] LP6:
2.8.2.2 is the last one which can decrypt my deb.
[Nexus 7 (2013) Original Android Development] magarto:
I was going to say the same. Only 2.8.2.2 decrypts device.
[Nexus 7 (2013) Original Android Development] stanglifemike:
I've yet to flash Lollipop, but finally getting ready to since Google has ironed out a lot of the bugs. I just read through the last few pages and don't see anyone mentioning problems with 2.8.4.0. So is it safe to assume the only issue people are encountering is not being able to encrypt?

SwiftKey'ed from my Note 4 using XDA Premium HD
[Nexus 7 (2013) Original Android Development] meekrawb:
It seems that is the only problem.

2.8.5.0 was just posted today. No more need for zips if you have 2.8.4.0, you can just flash the 2.8.5.0 .img.
[Nexus 7 (2013) Original Android Development] stanglifemike:
Awesome.Thanks for the info, quick reply, and all you do for TWRP!!
[Nexus 7 (2013) Original Android Development] meekrawb:
I am not a team member, just an enthusiast. :)
[Nexus 7 (2013) Original Android Development] stanglifemike:
I know, but you're always here answering questions to help others, and posting links for the latest versions. You're definitely an asset to this thread! :)
[Nexus 7 (2013) Original Android Development] petran_7:
Since you have 2.8.4.0 you can also install images from twrp. You just select the option in the installation screen and you go on.

I just installed 2.8.5.0 from the image and it works nicely!
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Flashify works good as well

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] jabbermacy:
Techeratta Downloads

SUCKS A$$

-- never completes...
[Nexus 7 (2013) Original Android Development] hlxanthus:
[MENTION=912474]Dees_Troy[/MENTION] screenshot seems broken on the 2.8.5.0 build, thought I would point it put. Or maybe it is just me. Works on my n6 . .
[Nexus 7 (2013) Original Android Development] LP6:
Has anyone tested whether 2.8.5.0 can handle encrypted partitions?
[Nexus 7 (2013) Original Android Development] ericguichard:
It works fine. If you're using a pattern, just replace dots with digits as if it were a phone dialer.
[Nexus 7 (2013) Original Android Development] LP6:
It didn't work with 2.8.3.0 and 2.8.4.0 which is why I asked. Thank you.

Edit: 2.8.5.0 couldn't handle encryption either, had to revert back to 2.8.2.2.
[Nexus 7 (2013) Original Android Development] |Logic|:
No 2.8.5.2 yet?
[Nexus 7 (2013) Original Android Development] coolek33:
Maybe it's necessary. 2.8.5.2 got some fixes for some devices I think. Maybe it's not needed for Flo.
[Nexus 7 (2013) Original Android Development] ems328i:
Been getting website not available error message for all TWRP pages for the last hour, anyone else?

Any mirrors available?
[Nexus 7 (2013) Original Android Development] meekrawb:
You should try a different browser. I have rarely had an incomplete download from techerrata.
[Nexus 7 (2013) Original Android Development] kthejoker20:
Twrp is not decrypting cm12 to install updates. No crypto....
[Nexus 7 (2013) Original Android Development] kamistral:
Read a few of the latest posts in this thread before posting (keep the thread clean) - already many people reported that encryption works with a older release like 2.8.2.2 ;)
[Nexus 7 (2013) Original Android Development] Crossvxm:
Nooooo! I finally got a N7 2013 again and TWRP's page is down...

:crying:
[Nexus 7 (2013) Original Android Development] coolek33:
Fine here.
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Try using flashify

Sent from my VS985 4G
[Nexus 7 (2013) Original Android Development] magarto:
Is there any new bugless release as of 2.8.2? I mean, working decryption
[Nexus 7 (2013) Original Android Development] Goodtill:
I am having an issue with 2.8.5.0 in my new N7 that I just got today. The unlocked bootloader and root has been setup. Both of these have been verified working . I am getting 0 MB in my TWRP when booting into it. It also show that it is unable to mount any partition. I am running OEM 5.0.2 Lollipop that I downloaded from Google and loaded it with fastboot after erasing all the partitions. It does not see any of my Zips (roms, Kernels) when I hit load.

I want to be able to load roms with my recovery so i can find the one that works best for my needs.

Can this be a hardware issue?

---------- Post added at 08:10 PM ---------- Previous post was at 07:28 PM ----------

Ok so I have the same issue with Clockwork recovery Mod?? What gives, the N7 loads and boots fine, but neither recovery has access to the file system? ES file explorer can get to root access and I can look at everything.
[Nexus 7 (2013) Original Android Development] magarto:
If you have encrypted device, try with 2.8.2
[Nexus 7 (2013) Original Android Development] Goodtill:
Tried that and it does not work. It still shows 0mb of memory and unable to mount anything in the system, cache or data. I tried to downgrade to 4.4.4 with an factory image and adb but it just went into bootloop after the Google screen.

The interesting thing is that 5.0.2 works fine and I have root. It has the stock 3.4.0 kernel.
[Nexus 7 (2013) Original Android Development] TrentB:
I am having the same problem with my brand new nexus 7. I can install twrp but it can't mount any partitions. Bootloader is unlocked and Android can access everything fine. There is no encryption setup.
[Nexus 7 (2013) Original Android Development] idCyber:
On 2.8.6.0 I can't wipe , flash to any partition. It says it can't mount them.
[Nexus 7 (2013) Original Android Development] _delice_doluca_:
Interestingly, I can flash and successfully run a CM 12 installation with Google Apps on TWRP (tried on 2.8.6.0-5.0-4.0) how ever when I try to factory reset my tablet from the settings (Android settings itself, not on the TWRP) the device restarts and shows TWRP blue screen like it is going to start the recovery but it just blinks like that endlessly. I have tried 3 latest TWRPs but nothing helped. I am not sure this is a CM 12 bug though. Any idea?
[Nexus 7 (2013) Original Android Development] Woody:
I have seen nothing but problems in the N5 section about 2.8.6.0. As far as I am concerned it is broken on the N5; bad flashes, not being able to restore backups, phantom system/apps data being wiped. Seems to be similar issue going on over here too. I haven't update my N7 yet and probably won't until these issue level off a bit more.

One thing that you might want to try [MENTION=393746]delice_doluca[/MENTION] is going into your TWRP folder and deleting the .twrp file. This has shown to be a solution for not being able to boot fully into Recovery. Delete the .twrp file and reboot the OS. Then reboot into recovery (but I suggest reverting to a working build before 2.8.6.0 to save some headaches until this is figured out).
[Nexus 7 (2013) Original Android Development] davidmueller13:
Has anyone a flashable zip for 2.8.6.0(flo)?
[Nexus 7 (2013) Original Android Development] coolek33:
And why do you need one? Anyway I would wait with the update if I were U. There're some issues with 2.8.6.0. People are having problems with flashing gapps etc. Don't know how it's on Flo but n5 thread is full of such reports.
[Nexus 7 (2013) Original Android Development] Mawth:
I've been using 2.8.6.0 on my N7 flo without problem. Flashing roms and gapps no problem. Making and restoring nandroids no problem.

I have not updated my N5 to 2.8.6.0, since as you say, lots of forum posts about issues. I will stay with 2.8.5.3 on the N5 since it's my daily driver and 2.8.5.3 is working reliably for me.

Finally, using a flashable .zip to install recovery is a scary proposition in my experience; if you're not careful and the script isn't perfect, you could be be looking at a brick. Much safer and smarter to flash recovery.imgs using fastboot.
[Nexus 7 (2013) Original Android Development] andy_rose:
You can flash img. directly in twrp.
[Nexus 7 (2013) Original Android Development] danmaman:
you don't need a flashable zip!!!!!!!

-download twrp.img for flo

-put it /sdcard/TWRP (i have it there)... or wherever you want

-reboot into recovery

-press install

-go to /sdcard/TWRP

-press in the right corner bottom "Images"

-select the .img file

-select "recovery" -----don't select "Boot"

-swipe to confirm

-reboot one again into recovery

-reboot system------->thats it:good:;)

cheers
[Nexus 7 (2013) Original Android Development] kindofabuzz:
If they have a very old version of TWRP they can't do that.
[Nexus 7 (2013) Original Android Development] Aerobatic:
Here are the .ZIPs for those who have CWM or TWRP prior to 2.8.4.0
[Nexus 7 (2013) Original Android Development] taiguy:
can't find crypto footer

Did a quick thread search but didn't find anything. Has anyone else run into TWRP (2.8.6.0) not being able to mount the /data partition and then also saying it can't find the crypto footer?

It basically makes the recovery useless since I can't wipe anything or install anything if /data is unmountable.

This error but I'm on FLO, not DEB.
[Nexus 7 (2013) Original Android Development] jisoo:
2.8.2.2 should still work.but later versions are broken.
[Nexus 7 (2013) Original Android Development] Gorgtech:
I can use later versions too , nothing broken here. In case you mess up TWRP, you need to remove all traces of a "older" TWRP recovery ( eg. the folder, settings, themes ) and flash the newest version through FASTBOOT. Using other methods like eg. "flashify" are dangerous ( this tool managed to cause serious trouble once )..

Edit: If one partition cannot be mounted, also consider to grab yourself the latest Factory Image and simply flash the damaged data again.
[Nexus 7 (2013) Original Android Development] idCyber:
2.8.5.0 works great
[Nexus 7 (2013) Original Android Development] toonarmy4life:
Hey ppl

Is it possible to flash bootloader.IMG taking from stock 5.1 using twrp? As i don't have a PC I'd like to upgrade my bootloader from 04.04 to 04.05.

Thanks in advance.
[Nexus 7 (2013) Original Android Development] gyakusetsu1215:
Use terminal emulator.
[Nexus 7 (2013) Original Android Development] jazzruby:
Just want chime in before you proceed; TWRP can flash boot.img (kernel) and recovery.img (recovery) - bootloader if even possible seems risky

just sayin'

-JR-

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] taiguy:
I installed 2.8.5.0 using the TWRP app. After I found out that was broken, I tried flashing 2.8.6.0 (didn't show up in the TWRP app) using Flashify after downloading the IMG file. Same story. Guess I'll try re-installing using fastboot.
[Nexus 7 (2013) Original Android Development] kindofabuzz:
I used Flashify on my S2 about a year ago and it bricked it hard. Never again.
[Nexus 7 (2013) Original Android Development] madbat99:
Flashify has come a loooong way since then. It works flawlessly to install img files. Also recovery flash que is pretty nice.
[Nexus 7 (2013) Original Android Development] maximusmullivan:
Been using flashify on N7, old S4 and now my G3 with no issues

Sent from my Nexus 7 2013
[Nexus 7 (2013) Original Android Development] jaibar:
Me too. Problem is, however, that when everything is going fine you won't complain about flashify (or similar applications). Then, it usually takes one single time when something gets FUBARed, and your device gets bricked that makes you change your mind.

For example, I've used ROM manager for a long time in the past, and everything was always fine. Thousands of users probably will testify the same.

For me, that was until the single time I tried to use it to flash cwm recovery into a brand new LG device (yeah, everything was configured correctly, it recognized the device model etc). Got me a real paperweight hard brick. No more toolbox for me since then- always flash stuff directly via recovery, fastboot, whatever.

So sure, everyone can use these nice flashing tools, just use them with care. One single time pressing on the wrong "next" button may end up doing damage...
[Nexus 7 (2013) Original Android Development] Hanny:
Encryption (password enabled) for NANDROID Backup is not working for TWRP 2.8.6.0 on my flo with bootloader 04.05. It returns with "Backup Failed" at the very end of my backup (boot, system, data). Tried different combinations (disable MD5 check only, disable compression) and it is only by not enabling any encryption for the backup (No Encryption) can the backup be successfully done. Such encrypted NANDROIDS are possible on the last version I installed, which is 2.8.4.0.
[Nexus 7 (2013) Original Android Development] z31s1g:
This is a known bug across all devices and it's being worked on. Should be fine again in the next update. If you rely on encrypting backups, stick to 2840 for now.
[Nexus 7 (2013) Original Android Development] Aerobatic:
I may be wrong, but I believe problems with decryption started with 2.8.3.0 (see "-Reduce library requirements for 5.0 L decrypt" in TWRP changelog), so IMHO we should suggest using 2.8.2.2.
[Nexus 7 (2013) Original Android Development] z31s1g:
I don't use encryption for backups and I don't know what change might have broken the functionality. The only thing I do know is that devs are aware of the problem.

So my statement can be read as "use whatever version works".
[Nexus 7 (2013) Original Android Development] Aboody Zomar:
failed To sysMapFile

i have TWRP 2.8.6.0 installed on LG G3 (D855) and whenever i try to flash anything on TWRP i get this ERROR : (E: Failed to sysMapFile '/external_sd/.... .zip' )

but the weird thing that backup and restore are both working fine without any problems, the only only problem i get if i wanted to flash a zip file !!

would anybody suggest a fix for this annoying error !!

Thanks in advance !! :)
[Nexus 7 (2013) Original Android Development] Aerobatic:
This thread deals with TWRP for Nexus 7 (2013), not for LG G3. Anyway, GoodleSearch showed that people are encountering this and are dealing with it changing versions of TWRP to 2.7.x.x or 2.8.1.x or 2.8.2.x.

Unfortunately, first version for D855 is 2.8.3.0 https://dl.twrp.me/d855