yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] madbat99:
I didn't mean to imply it was something wrong with twrp, I meant the n9 doesn't like restoring it. Restoring all partitions, including vendor, won't boot. Restoring everything except vendor, boots fine.

Haven't tried restoring vendor along with flashing the matching bootloader.

Never really had a reason to restore an old vendor anyways.

And not spreading misinformation at all, sharing experiences. I've spoken to many people, none of whom could successfully restore vendor and bootup. I tried all this when I first got the nexus 9 and was curious about vendor.
[Nexus 9 Original Android Development] Gold Ribbed:
OK so not a big deal but on 2.8.7.1 I can save but TWRP cannot mount Vendor and so fails to restore.

Flashed 2 ROMS and had no issues. Now on AICP.
[Nexus 9 Original Android Development] Gold Ribbed:
Would flasong latest CM13 update firmware and Vendor? The is it OK to flash other ROMs?
[Nexus 9 Original Android Development] cpstar:
how can I get a version for Nexus 9 LTE which product info is flounder_lte?
[Nexus 9 Original Android Development] jskup:
Anything we can do to help with a 3.0.0 build? Gerritt and Jenkins both seem to be having a lot of issues on flounder these days
[Nexus 9 Original Android Development] NYCHitman1:
Downloads are already up for Flounder.
[Nexus 9 Original Android Development] NYCHitman1:
Use Flounder recovery. The trees are unified under Flounder. The only difference is your vendor.img
[Nexus 9 Original Android Development] jskup:
Thanks much, I must have missed it. I appreciate the work and responsiveness.

Edited: Found it. I must have posted before it was up there.
[Nexus 9 Original Android Development] DanteGR:
Hello all.

So I just moved to v3 and tried to take a nandroid which seemed to complete ok despite saying at the end "unable to unmount system - device or resource busy".

Anyway, I then tried to wipe cache, dalvik and system and the exact same message as above came up and this time the system wipe could not be completed.

I cannot also flash anything at the moment the above error.

Tried googling it but to no avail.

Any ideas anyone?

Thank you in advance :)
[Nexus 9 Original Android Development] maelfilk:
You could try and got to previous twrp version. I suppose you rebooted recovery several times and it didn't help? Did you check/uncheck "mount system"?
[Nexus 9 Original Android Development] DanteGR:
Thank you for your reply.

Currently I'm away from the tablet and I only tried unmounting the system to no avail.

I'm not sure the recovery rebooting could help but I will try ASAP.

Thank you again
[Nexus 9 Original Android Development] fhem:
[MENTION=912474]Dees_Troy[/MENTION] I am having the same issue w/ v3. It appears that when making or restoring a backup the system is not being unmounted. It requires rebooting back into twrp to unmount system.

Thanks for your hard work and continued support. If you need me to do any testing please ask.

Thanks again.
[Nexus 9 Original Android Development] cpstar:
I've been using flounder version in my nexus 9 LTE, all work fine but only one thing. That's when using TWRP to make OTAs, it will get an error message about this is a flounder devices but flouder_lte are needed.

The log is here

I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
I:Installing mapped zip file '/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: mmapped 260 ranges
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
sysutil: mmapped 260 ranges
[B]script aborted: This package is for "flounder_lte" devices; this is a "flounder".[/B]
[B]This package is for "flounder_lte" devices; this is a "flounder".[/B]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file

I don't know whether I did the right thing and flashed the right recovery image. https://twrp.me/devices/htcnexus9.html?
[Nexus 9 Original Android Development] DanteGR:
My problem was also in wiping system. Same error occurred

Swiftkeyed from my 1+2 A2003
[Nexus 9 Original Android Development] fhem:
If you wipe sys after making backup you will get the message ---> need to reboot to twrp before wiping system after making backup. I do not get that message when wiping system.
[Nexus 9 Original Android Development] DanteGR:
Yeah most probably. All sorted now thank you [emoji4]

Swiftkeyed from my 1+2 A2003
[Nexus 9 Original Android Development] MRobbo80:
????????????????????????????????

Amazing wicked love you man!!!!!!!!!!!!!
[Nexus 9 Original Android Development] chasmodo:
Flashed it via fastboot on stock, unlocked and rooted LRX21Q. Tried to wipe cache, TWRP coudn't mount it and just hung. Now I'm stuck at bootanimation.

Recovery.log: http://paste.omnirom.org/view/d3b49365
[Nexus 9 Original Android Development] USBhost:
lol it looks weird

also formatting cache dose not seem to work
[Nexus 9 Original Android Development] MotoFlasher:
First MEGA BIG THANKS! :highfive: :good:

Flashing via fastboot worked fine! Backup, MOAB.zip, etc all zip´s flashed fine ... :good:

A small thing but I think that you aware of it (resolution)... but of this, the world will not perish. ;) :silly: "It is a German saying"
[Nexus 9 Original Android Development] thebrainkafka:
Anyone tried to root via TWRP?
[Nexus 9 Original Android Development] MotoFlasher:
My N9 was rooted, in front of the recovery flash, but flashed, out of pure curiosity :), the new SuperSU BETA 2.23 over it (SuperSU2.18 N9) ... and so far all best. All root apps work good!
[Nexus 9 Original Android Development] b-17:
Flashify now works fine after update from playstore.

Just installed recovery as well.
[Nexus 9 Original Android Development] thebrainkafka:
Is there a flashable ZIP available?
[Nexus 9 Original Android Development] Max128:
The application crash for me when I select and I want flashed. Not a big deal, I downloaded in the website the recovery.img and I flashed manually it works well.

Anyone know when CWM go out? I'm more familiar with it.

Thanks
[Nexus 9 Original Android Development] jd1639:
https://www.androidfilehost.com/?fid=95784891001612665 I use a PIN lock and it doesn't seem to flash for me. Try it and let me know. It didn't crash my device.
[Nexus 9 Original Android Development] Dees_Troy:
I suggest you become familiar with TWRP. Mainline development on CWM has all but stopped. Further, it's much more difficult to impossible to decrypt the always encrypted data partition of the Nexus 9 with CWM. I think you might be able to do so via adb, but that means you need a computer present in order to do much in recovery.
[Nexus 9 Original Android Development] jd1639:
CWM is poorly supported. I recommend getting use to twrp.

Edit, lol I'm too slow.
[Nexus 9 Original Android Development] pantmunu:
Ok. So i was on the aosp lolipopalooza rom. Flashed the recovery v2.8.2.1 via flashify ... backed up my current rom and whe i tried to.reboot back.to system im booting back.to.recovery . Tried couple of times but no luck. Still nooting into twrp
[Nexus 9 Original Android Development] jd1639:
I had the same problem with flashify. Seems it wipes the system partition. Do you have a nandroid? Just restore that.
[Nexus 9 Original Android Development] pantmunu:
Haha. Crap. No . Well ill just sideload again.
[Nexus 9 Original Android Development] Max128:
Ok guys, you all recommending TWRP! I will keep it!

Dees_Troy: Yes I saw that the data partition is encrypted, but why Google made this more encrypted?

CWM is dead?
[Nexus 9 Original Android Development] mrshades812:
Silly question...

Should I add vendor to my nand backups? I'm assuming yes... just weird to see that there. :)
[Nexus 9 Original Android Development] jd1639:
I didn't and the nandroid restored fine. To be honest I didn't even see vendor there until you mentioned it.
[Nexus 9 Original Android Development] jlokos:
I side loaded TWRP, it installed fine and did backup without vendor also. Backup confirmed and rebooted. All is well. Great job TWRP team.
[Nexus 9 Original Android Development] z31s1g:
[MENTION=912474]Dees_Troy[/MENTION]

First things first: Thanks for releasing TWRP for volantis so quickly.

First thing I tried was to apply my theme to it, but unfortunately the ui.zip doesn't seem to get picked up. Is theme support still WIP, or are there other things to consider beside the naming of the folder and the zip?
[Nexus 9 Original Android Development] NYCHitman1:
Don't use OTA's then?
[Nexus 9 Original Android Development] cpstar:
Ehhhhhhh....

Can I modify the build.prop or some files like it to change flounder to flounder_lte? Will it work?

I'm using complete stock rom except SuperSU and recovery. So OTAs are the easy ways to keep the system new.
[Nexus 9 Original Android Development] Captain_Throwback:
This should be fixed with the latest version.
[Nexus 9 Original Android Development] fhem:
Looks like v3.0.0-2 did the trick --- thanks.
[Nexus 9 Original Android Development] enriquejones666:
Well, there's your problem. Your entire device needs to be stock to take official OTAs.
[Nexus 9 Original Android Development] dmantilal:
I think SuperSU beta (systemless) can be installed without causing OTA interference.
[Nexus 9 Original Android Development] madbat99:
Only if you do it properly. You have to only boot twrp (not flash) and not modify your system in any way.
[Nexus 9 Original Android Development] corkiejp:
TWRP 3.0.1-0 Released

TWRP 3.0.1-0 Released

Was wondering does this version support Android N on encrypted devices?

https://twrp.me/devices/htcnexus9.html
[Nexus 9 Original Android Development] Captain_Throwback:
I didn't see any mention of issues in this thread. What is the issue exactly? Where's the recovery log?
[Nexus 9 Original Android Development] corkiejp:
Haven't tried Android N yet, waiting until it has support from TWRP, ElementalX Kernel, TiBu, etc)

Just read that TWRP may bootloop on some devices, and guessed it might have the same issues as when Marshmallow was released, not been able to access encrypted devices.

Does TWRP work without problems on encrypted Nexus 9 with Android N?
[Nexus 9 Original Android Development] Captain_Throwback:
We can't fix a problem we're not even sure exists. Only way to know is for someone to try it. You seem like the most logical candidate.
[Nexus 9 Original Android Development] wijnsmalaurens:
twrp on nexus 9 N developer previeuw flouder doesen't load only splash screen no twrp folder created

bootloader-flounder-3.48.0.0135

unlocked
[Nexus 9 Original Android Development] rbeauch:
I just installed TWRP 3.0.1.0 on my Nexus 9 and I'm not able to decrypt the device. I keep entering the passcode and it's not accepted as valid. I downgraded back to 3.0.0.2 and it works fine. Any idea as to why?
[Nexus 9 Original Android Development] z31s1g:
A patch for fixing CM13 pattern decryption broke the text input box for the pin. Affected all devices. It has been fixed and updates are being built while we speak. Should arrive shortly.
[Nexus 9 Original Android Development] DowntownRDB:
Issue appears to be fixed in 3.0.2-0. No issues with passcode or decrypting. Thanks Dees_Troy :good:
[Nexus 9 Original Android Development] ElwOOd_CbGp:
any buddy have any ideas how to solve this....

can't delete backups.

rm -rf /storage/emulated/0/TWRP/BACKUPS/...

rm -rf /sdcard/TWRP/BACKUPS/...

isn't working in terminal emulator or in TWRP terminal.

File managers aren't working and neither is TWRP delete backup

tried other versions. all it does is force a reboot.
[Nexus 9 Original Android Development] USBhost:
rm -rf /data/media/0/TWRP

rm -rf /data/media/TWRP # if the top one does not work
[Nexus 9 Original Android Development] ElwOOd_CbGp:
same thing even with adb. I've had to use twrp to delete stuff I moved st sdcard with twrp but never not been able to. Only thing I can think I've got that's different besides newer version of twrp is data and cache formatted as f2fs
[Nexus 9 Original Android Development] USBhost:
chmod it to 777

Then try again
[Nexus 9 Original Android Development] ElwOOd_CbGp:
I tried that too. I was able to go thru and delete each individual file until I get to the vendor and system.img part of the backup, which I guess is ok
[Nexus 9 Original Android Development] corkiejp:
Flashed Android N DP2 on my Encrypted Nexus 9 last night, latest TWRP just bootloops. Is there logs for TWRP, somewhere on the device, that I could post here?
[Nexus 9 Original Android Development] Captain_Throwback:
I actually looked into this. It does bootloop, but if you let it keep bootlooping it'll eventually get to a decrypt prompt. So the issue is (obviously) that it can't decrypt. I haven't figured out how to fix that yet.

The only possible solution I've come up with is building TWRP with N source, but that's a lot more difficult than it sounds.
[Nexus 9 Original Android Development] corkiejp:
Eventually got the Prompt for password. My Pin Code didn't work.

Probably not worth while building TWRP with N source until the final release.
[Nexus 9 Original Android Development] sttw1fa:
Didn't know where to post this...but it seems most appropriate here. I've done a good bit of searching and trying fastboot things with no fix so far. Not a noob with adb and fastboot, but I goofed something somewhere.

My N9 bootloops to TWRP 3.0.2-0 constantly (even after a process of wiping/formatting reflashing stock image and recovery). I can get into Fastboot (status shows UNLOCKED). During the boot process (to TWRP), the N9 gives the 'Device is Corrupt, can't be trusted message'. It doesn't ever boot the system.

Originally, the N9 came with April 6.0.1 Marshmallow (April security patch). I then used corkiejp's method of unlocking the bootloader, rooting, and loading ElementalX. Was working great, but wanted some extra few things of a custom ROM.

Went through the process of installing fhem's noobbuilds rom (as it had the May security update), but had an issue with SuperSU (it didn't show up). He suggested to go back to stock and start over......

Was trying to get back to stock on my N9 using this guide Unlock bootloader-Flash Stock

But, even after following the steps line by line (twice now), I only get a bootloop to TWRP 3.0.2-0, but, can get to fastboot screen.

Any help/ideas greatly appreciated.
[Nexus 9 Original Android Development] corkiejp:
If your still seeing TWRP, you haven't successfully flashed a fully stock image. As you can get to fastboot/bootloader, you could use Nexus Root Toolkit to flash the factory image, from it's soft brick/boot-loop tool.
[Nexus 9 Original Android Development] tetsuhito:
hi evry oneim' looking for some help

Since i update my N9 to Mob30g

Twrp won't work correctly

I'can't instal 3.0.2.0, the only on i can use is 3.0.0.0

I'm try to root with the su sytemless and Elemental

it's say done but in the parameters there's no elemental

and Su won't work

I also try a factory reset from twrp, say done succesfully

but when i reboot the N9 it was not reset.

Any Idea ?

thanks
[Nexus 9 Original Android Development] montbazon:
Sorry could you let me know how you do solve this problem?

Actually I'm with you. My N9 has mobile. And TWRP for N9 rejects my command just like you.

Could we ask to someone? or we need to keep our device all stock?

I'm just using stock rom, twrp and ice and fire kernel.
[Nexus 9 Original Android Development] NovaSlim:
Hi, I succesfully unlocked my flounder and flashed the latest twrp, however when I reboot into recovery(either from the bootloader menu or with adb fastboot recovery it shows me the "no command" window and nothing happens, what am I doing wrong?

nvm, I tried again and it worked this time.
[Nexus 9 Original Android Development] corkiejp:
[MENTION=5281524]NovaSlim[/MENTION]

Quoted from the TWRP site, where you downloaded from. TWRP needs to be boot first after flashing.
[Nexus 9 Original Android Development] PieceKeepr:
I just recently got a Nexus 9 and I have been trying to figure out exactly what I need to back up in order to do a full restore in the event that I need to. Maybe I'm not searching the right terms but can't find any documentation about it. I'm pretty sure I don't need vendor and vendor image as long as the ROM I would restore is built for my current image. I'm not sure about system image though. On my phone I back up system, data and boot but the Nexus has system and system image so I'm not sure if I need both.

Any help with understanding what the various images contain and what I need for a usable backup would be appreciated.
[Nexus 9 Original Android Development] DowntownRDB:
[MENTION=2654020]PieceKeepr[/MENTION] On all my tablets I only back up system, data and boot. I do not back-up cache, recovery or vendor. Several people in this thread have had restoration failed with unable to mount vendor partition which is why I do not back-up vendor in TWRP. However, I do keep a copy of latest vendor zip on the tablet just in case I need it sometime. Hope this information is helpful.
[Nexus 9 Original Android Development] placebo_domingo:
Would formatting userdata in fastboot make it possible to flash? I'm going on the belief that 'fastboot format userdata' will decrypt.
[Nexus 9 Original Android Development] Captain_Throwback:
Even if that works, it'll just re-encrypt when you boot into Android (unless you patch the boot.img to prevent it). In which case, you can just wait until TWRP stops looping and finally gets to the prompt, cancel the decryption prompt and Format Data/Wipe Encryption in TWRP. So I'm not sure how that would help.
[Nexus 9 Original Android Development] corkiejp:
Will you now be building TWRP for the Nexus 9 encrypted? With Android Nougat near completion.
[Nexus 9 Original Android Development] Captain_Throwback:
N source won't be merged into TWRP until Nougat is released. And then I'm sure it'll take [MENTION=912474]Dees_Troy[/MENTION] a while to merge in the changes. So be patient - it'll come.
[Nexus 9 Original Android Development] placebo_domingo:
I flashed a modified boot image then did a data format, then flashed twrp. I got twrp to load without bootloops!.. but I also managed to blow away the OS. LOL.

Learn by destroying. :p
[Nexus 9 Original Android Development] nanaandoh:
Where could I find the modified boot image?
[Nexus 9 Original Android Development] corkiejp:
If you root the device, supersu will modify the boot image to enable decryption.
[Nexus 9 Original Android Development] thebrainkafka:
Is there a New Version supporting Android N?
[Nexus 9 Original Android Development] Captain_Throwback:
Yes.
[Nexus 9 Original Android Development] thebrainkafka:
3.0.2.1 does not show content of internal storage.... Any idea why?
[Nexus 9 Original Android Development] Captain_Throwback:
Shows fine for me - Are you on Nougat? If not, just use 3.0.2-0.
[Nexus 9 Original Android Development] thebrainkafka:
Yes in N
[Nexus 9 Original Android Development] Captain_Throwback:
Recovery log?
[Nexus 9 Original Android Development] thebrainkafka:
Where can i find it?
[Nexus 9 Original Android Development] Captain_Throwback:
Advanced -> Copy Log
[Nexus 9 Original Android Development] fhem:
Working fine for me also -- but I wiped and reformatted all before flashing N images and new twrp. I started N with 100% clean slate
[Nexus 9 Original Android Development] tushar.phogat:
How to unmount data,cache etc in 3.0.2.0
[Nexus 9 Original Android Development] iarejohnsmith:
So I've seen people talk about the looping-encryption problem here, so here are some new details from a worst-case scenario I had yesterday.

Tried to install Dirty Unicorns, had never flashed a vendor before, so accidentally flashed one meant for Nougat instead of the latest for Marshmallow.

*My tablet has always been encrypted.

Nougat vendor + TWRP 3.0.2-0 = looping-encryption problem

Nougat vendor + TWRP 3.0.2-1 = works

Marshmallow vendor + TWRP 3.0.2-1 = looping-encryption problem

Marshmallow vendor + TWRP 3.0.2-0 = works

So basically, I haven't been able to get 3.0.2-1 working on M, at all. If you're encrypted and on Marshmallow, stay on 3.0.2-0, do not try to use -1. The issue is some combination of TWRP encryption and vendor-related files (like I said I have very little knowledge of vendor, so that's all I can say).
[Nexus 9 Original Android Development] Captain_Throwback:
You're only supposed to use -1 if you're running N. If you're on M, use -0. You figured it out, exactly :).
[Nexus 9 Original Android Development] Taomyn:
Which model of N9 and is this just non-stock ROMs? I've been running -1 since it came out on my encrypted N9-LTE, have dirty flashed stock ROMs each month without issue. My procedure has always been:

Boot to bootloader.

Flash all new images (I extract the main archive into the separate images, so I don't overwrite data).

Reboot and wait for encryption PIN entry, then power off (therefore it does not fully boot into the tablet).

Boot into bootloader again.

Flash latest TWRP.

Boot into recovery.

Enter PIN.

Flash latest SuperSU.

Reboot and wait for it all to happen.

Has never failed me so far.
[Nexus 9 Original Android Development] bteljuice:
I do not have a password on my Nexus 9 and whether i flash 3.0.2-0 or -1, I still get the decrypt data. I even tried "default_password" with no avail.

Now i can't flash anything.

Any help?
[Nexus 9 Original Android Development] fhem:
I assume you can get into your bootloader ---->hold power button and volume dn -----> now latest factory images . Basically just wipe clean and start over.
[Nexus 9 Original Android Development] dictionary:
Your device is encrypted, so you won't be able to do anything really. If you want to, you'll have to transfer everything to your computer if you have a ROM that'll boot already flashed. If not, you might be and to transfer everything with an adb pull, but not sure. Otherwise, nothing much you can do I'm afraid. At least to the best of my knowledge. Sorry
[Nexus 9 Original Android Development] ipdev:
Happened to me once. I just hit continue (no password) and twrp seemed to decrypted my device. (?) Not sure what was wiped as a result. (I was wiping and flashing a new rom at the time. ;) )
[Nexus 9 Original Android Development] secaplus:
Hi

Format data and be sure to flash a kernel that don't crypt your data (elementalx for example) before run your Rom the first time.

Envoyé de mon HTC One_M8 dual sim en utilisant Tapatalk
[Nexus 9 Original Android Development] frov:
I was a bit anxious to root my new 2nd hand N9 (I have quite some other, rooted devices). I read on it being encrypted and so. So after factory reset and some use I flashed in the latest stock image of October and went forward from there: I took Chainfire auto-root and used that to get to root level. With that I could run the TWRP app and flash in 3020-1. I rebooted imm. into recovery and I was happy to see the familiar entry screen of the latest TWRP. So all is well on the N9 and all root apps run OK, like AdAway (systemless). The End :)
[Nexus 9 Original Android Development] henderjr:
I have a second hand N9 coming and am going to try this same process. I'm pretty well versed with flashing (Hero, EVO, EVO LTE, M8, Note 5, Nexus 7, and a couple off brand tablets). Not sure if it'll come with L on it or not but if it doesn't I'll get to latest and then use auto-root and twrp app to flash twrp. So many old threads out there it's hard to tell what works with latest android and what was for L or M. Thanks
[Nexus 9 Original Android Development] enriquejones666:
Use 3.0.1 for M and 3.0.2 for N.
[Nexus 9 Original Android Development] fhem:
I think L was like 2.8.xxxx

3.0.2 M

3.0.2-1 N