yashsingh1/xdaforums huggingface dataset:
[Nexus 9 General] Gold Ribbed:
Anyone else have trouble with google stock roms download. After excepting t & c it no longer takes you to the list. Ota still ok.
[Nexus 9 General] .MoHaMaD:
data/data/com.google.android.gms/shared_prefs/update.xml
[Nexus 9 General] Iceman66:
November security patch is available for download:

https://developers.google.com/android/images

NRD91N for Flounder and Volantisg.
[Nexus 9 General] Iceman66:
February security patch is available: https://developers.google.com/android/images
[Nexus 9 General] Iceman66:
Fresh factory images available for Volantis and VolantisG with March security patches: https://developers.google.com/android/images
[Nexus 9 General] GedBlake:
I received the March security OTA notification around an hour or so ago.

Having only reflashed (via fastboot) my Nexus 9 a couple of days ago completely from scratch (and then rooting it and installing the systemless AdaWay adblocker), I was a little bit hesitant to apply this new update, but with Chainfires FlashFire app, it was pretty straightforward.

First boot afterwards took a good five minutes though, but eventually it did boot and all is now good :cool: :)

Rgrds,

Ged.
[Nexus 9 General] Younex:
May I ask if your N9 is enrolled in the beta program ?
[Nexus 9 General] GedBlake:
Hi, Younex...

No. I never enrolled it. Any particular reason for asking?

As far as I know, the Nexus 9 will no longer receive updates, other than the monthly security patches, so it won't receive 7.1.2 for example, so I don't see much point now in enrolling it in the beta programme.

Rgrds,

Ged.
[Nexus 9 General] Younex:
Some people said that enrolling it gives faster updates, but in my case it's been the opposite... I received the March patch yesterday, this is probably the fastest I've gotten an update as far as I remember :)

Thanks for the answer, have a good day :good:
[Nexus 9 General] sbtwister:
Never mind ;)
[Nexus 9 General] Brendo:
Had been in the beta program, but never any way to leave it (without data loss) since they stopped supporting it. Finally got an OTA notification today. Install update and looks like no longer in the beta :)

Security patch: 5 Oct 2017

Version 7.1.1

Build: N4F27P
[Nexus 9 General] TheManii:
How did you get LRX21L on yours? Did you flash a factory image without flashing every piece?

You need the correct recovery to flash it.
[Nexus 9 General] gsbobbyd:
Same here i do have LRX21L but old version of recovery, I have not flashed anything i just update when i turned on my nexus first time that's all.
[Nexus 9 General] techiedj:
LFW73W ota error

Same LFW73W ota error on mine as well. Did out of the box LRX21L ota as well. Also used cf-auto-root but that shouldnt matter. Going to try flashin recover from old LRX21L factory image and try again.
[Nexus 9 General] oldblue910:
You have root, therefore the OTA won't flash. In Lollipop, if the system partition has been modified in any way, shape, or form, the OTA will fail. It no longer patches individual files but instead patches the system partition as a whole blob. You need to download the LRX21L factory images and flash system.img and boot.img, then run the OTA again.
[Nexus 9 General] gsbobbyd:
My tablet is still un-rooted. I don't know why its happening.
[Nexus 9 General] techiedj:
Thanks [MENTION=3423169]oldblue910[/MENTION] !!! Well then, that makes root a much bigger pita than just having to uninstall/cleanup the system partition as before. Sadly after reflashing system and boot and trying to sideload the ota now im getting this error (pic below). I had root, adaway (restored orig host), busybox, and stickmount. Not sure what to try next without resoring to a full wipe/flash. :(
[Nexus 9 General] oldblue910:
Ah hell, man, you may need to reflash all the .img files and lock your boot loader...ouch...
[Nexus 9 General] TheManii:
You didnt flash vendor, you need to flash everything if you use a factory image
[Nexus 9 General] Gryphie:
I got that error too. My nexus 9 is completely stock, not rooted or anything.
[Nexus 9 General] oldblue910:
Is the bootloader unlocked?
[Nexus 9 General] Gryphie:
No, it's locked.
[Nexus 9 General] TheManii:
One last reminder: if anyone is actually still on LFW73W, please make note of what version the bootloader is on it.
[Nexus 9 General] BennyJr:
Is there a new bootloader somewhere?
[Nexus 9 General] TheManii:
HTC Nexus 9 - Official Roms - xda wiki

There is a bootloader version I do not have a rom for, and I dont know the bootloader included in the initial rom.
[Nexus 9 General] techiedj:
Correct @ TheManii !!! After flashing vendor it compained about system again for some reason, so i reflashed that again and cache and was offered the ota gain after booting up and it completed without sideloading this time! /shew Its been awhile sine I messed with flashing on my 2012 n7 (whish is STILL booting btw lol). Appreciate the help folks!
[Nexus 9 General] BennyJr:
I'm getting this same error and i am not rooted. It says im not running the 21L release, but the OS is. Should I flash the 21L .img? I'm thinking so.

Edit: just flashed the system and recovery and it boots
[Nexus 9 General] mtva24:
Good lord that was painful...I'm rooted and bootloader unlocked.

It took me 2 hours to realize i needed to extract the tar twice lol

Took me 30 minutes to realize that I needed to abort the flash-all.bat theory and flash the files individually (system, recovery, boot, cache, & vendor)

Took me 30 minutes of freaking out after seeing the green android after a factory reset to just let the device do its thing

I'm going to bed lol
[Nexus 9 General] McChen147:
during setup of the tablet, it forced the OTA to be installed. I did not manually flash anything, nor did i root or unlock the bootloader. all completely stock, out of the box. From other posts, it seems like others have this same config with the recovery and the OS being different builds which is causing this OTA zip to fail. Not sure if this config is intended or a bug....if it is intended, hopefully there is another OTA out there that will work!
[Nexus 9 General] sladflob:
Yep, same boat here, tablet updated to 21L on setup but recovery is still at 73W. I held off unlocking/rooting it because I wasn't (and still aren't) sure that I'd be keeping it.

Fastboot won't let me flash the individual .img files from the factory images as I'm still locked so sideloading is my only chance to force the update. It'll be interesting to see if it works when I am actually offered an OTA update.
[Nexus 9 General] foxmeister:
How are people sideloading the latest OTA?

ADB is working fine when the tablet is booted, but when in the sideload from ADB option, device manager shows up an unknown device (Volantis).

Thanks,

Dave
[Nexus 9 General] toyface:
Having issues sideloading this as well, device basically disappears when trying to sideload, looks like they changed this in Lollipop as well.

Also, I can't seem to get the images to flash in fastboot, either. It says waiting for device each time, despite the fact adb and fastboot work fine on my PC. I'm unwilling to unlock my bootloader and there's no way we should have to to fix a mess up from Google.

Tom.
[Nexus 9 General] mtva24:
Here was the dealio for me (figured this out when i was unlocking my bootloader, also had this issue with my n7)

1. Settings - build # 7x

2. Developers options ...enable usb debugging

3. Storage - hit the 3 dots menu button-> usb storage->switch to camera ptp

4. Now type "adb devices" in cmb

5. Now type "adb reboot bootloader"
[Nexus 9 General] toyface:
It's not so much the adb side of things I can't get to work, that works fine, but when I reboot to recovery I cannot sideload and I can't flash the images in fastboot, either. Probably just another Windows 8.1 f*&k up.
[Nexus 9 General] mtva24:
And all the files are extracted in platform tools (not a folder in platform tools)? You held shift, right clicked platform tools and selected "open command window" here?
[Nexus 9 General] Gryphie:
No point trying with the images if you are unwilling to unlock the bootloader as it needs to be unlocked to flash images.
[Nexus 9 General] Travelawyer:
Has anyone yet retrieved the OTA-Update to LRX21Q?
[Nexus 9 General] oldblue910:
Yes. Check the first post.
[Nexus 9 General] KinetiClutch:
Seems like UK / EU hasn't had the OTA pushed as yet.
[Nexus 9 General] mykchan:
I updated with the forced OTA immediately after first boot. Unfortunately it is looking more and more like El Goog messed something up and the 2nd OTA won't apply - generic "Error", and then rebooting prompts me to install the OTA again.

I decided to sidestep this and just flash the LRX21Q factory image. I enabled "Allow OEM Unlock" from developer options and proceeded to do just that, but flash-all.sh gives this output:

checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7812 KB)...
OKAY [ 0.569s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.734s]
sending 'recovery' (8434 KB)...
OKAY [ 0.616s]
writing 'recovery'...
(bootloader) Device State : Unlocked
OKAY [ 0.751s]
erasing 'system'...
OKAY [ 0.887s]
sending 'system' (1771468 KB)...
FAILED (remote: data length is too large)
finished. total time: 3.585s

I have already updated my ADB but I'm still getting the above... any ideas why/what I have to do to be able to flash the 1.8GB system.img?
[Nexus 9 General] mbirth:
Why is your system.img this large? IIRC mine was short of 1GB.
[Nexus 9 General] mykchan:
Only after looking into the ZIP (image-volantis-lrx21q.zip) - i thought its large size this would be relevant but I guess not.

---------- Post added at 11:52 PM ---------- Previous post was at 11:44 PM ----------

FIXED by downloading the new Android SDK from Google and utilising the new adb & fastboot, instead of relying on (outdated) Ubuntu repositories
[Nexus 9 General] donatom3:
Count me as another person who got the ota when I first opened my tablet. I have lrx21l but I have the old recovery. Mine is completely stock, no root or unlocking changes were made.
[Nexus 9 General] gianptune:
Bad news for those of us who have rooted and/or modified /system partition. Once you change the build fingerprint in recovery to match what the update expects, it will try to flash it. However, they are verifying and patching the partition itself rather than individual files. All I've done is write su binary to /system and thats enough to make the verification fail (ie no updates).

I'll have to flash a stock /system image before it will accept the update, and a lot of you will, too.
[Nexus 9 General] Deathbyfugu:
I'm in the same boat as you. Stock, locked BL, unrooted. On the LRX21L build that it pushed once the tablet was turned on but it never updated the BL. I hope they push a secondary OTA addressing this discrepancy. I really don't feel like wiping my tablet and unlocking just to flash the factory image -_-
[Nexus 9 General] donatom3:
I actually just unlocked and went the stock image route. It looms like the restore process is better than it's been in the past.its actually putting all my icons back in the right place on the launcher.
[Nexus 9 General] Deathbyfugu:
Alright I'm convinced. I'm about to start the whole process. Do you have the 16 or 32 gig device and did you get the bug described in the update section at the bottom of the page?
[Nexus 9 General] donatom3:
I have the 32 ,and after all this my system show a it has 32 GB of space. You're wiping anyway with the unlock so what a an extra wipe at that points.
[Nexus 9 General] BennyJr:
I use windows 8.1 and it worked for me. Try extracting the img and just flashing system.img.
[Nexus 9 General] donatom3:
I had no problem with windows 8.1. All I had to do was make sure I was actually in recovery then while in recovery I manually installed the driver.
[Nexus 9 General] ky3bmu4:
The same here. Fully sock, locked BL (And I am not wishing to unlock it yet, because I am still considering to get rid of the device) and unrooted. Received an LRX21L update from the box, but the BL remained the old one. Gosh I want that update badly.
[Nexus 9 General] oldblue910:
Yeah it appears that Google is going to need to send out another OTA. Everyone, keep an eye out. If you get an OTA, check the filename in logcat. If it's different than the one in the first post, post it here!
[Nexus 9 General] kikikaka:
I was at LRX21L, completely stock. I just received a OTA ... but failed with the same "LFW73W" problem mentioned in the earlier posts.

how come google release a problem OTA ...:(
[Nexus 9 General] McChen147:
this is a pretty embarrassing mess up by Google.....this isn't some kind of subtle bug, any kind of basic QA should have caught this
[Nexus 9 General] oldblue910:
Wouldn't be the first time. They had the same issue with GRI54 on the Nexus S. They eventually just released a full ROM package to people as an OTA that updated everything. That could be what they'll do here. Sit tight. You'll get your update. :D
[Nexus 9 General] kikikaka:
seems they blindly run a script to diff the 2 image build and generate a ota patch but not sure what actually user have in hand and not even tested the ota on a retail device.
[Nexus 9 General] oldblue910:
Guys here's what happened:

When you took your Nexus 9 out of the box, it had LFW73W on it. You were forced to OTA to LRX21L during setup. Normally, with every OTA, the recovery gets updated as well so that the recovery and ROM match version numbers. That didn't happen. Instead, something was wrong with the LFW73W > LRX21L OTA and it left you with an LRX21L ROM but a LFW73W recovery.

When you go to flash this new LRX21Q OTA, it's asking the recovery what the build fingerprint is, since it should always match the ROM. Well in this case, the recovery is reporting LFW73W while the OTA is expecting LRX21L. Therefore it's failing.

To fix this, Google will almost certainly release a new package that can handle this discrepancy.
[Nexus 9 General] nicholz:
It took me quite awhile last night - ended up factory restoring, unlocking boot loader and then was able to flash each part of the full factory image individually as others have mentioned - I tried adb side loading first but the device would disappear every attempt. I had success by entering ptp mode which allowed computer (win 7 64 ult) to see and correctly load drivers from nexus. Then I was able to fastboot reboot and the computer maintained the connection. I had to make sure that ( after extracting the original factory image TWICE ) all the disc image files were in the root of the platform tools folder - not in a sub folder. The batch command did not work but I was able to flash each individual image successfully and then I reran chainfires auto root.
[Nexus 9 General] thebrainkafka:
Nice
[Nexus 9 General] TheBiles:
Did anyone else get an OTA today? I got an error trying to install it. I'm assuming it's because I'm rooted.

Edit: Now it says I'm up to date. Build number LRX21L.

Sent from my XT1254
[Nexus 9 General] brushrop03:
See post #106
[Nexus 9 General] doubleho:
can I just wait for the ota,unroot using supersu then update and reroot?
[Nexus 9 General] TheManii:
Not on a N9, if you touch /system at all you'll need to reflash a factory image.
[Nexus 9 General] Gormsen:
Root needs to be updated to the new kernel, as you gain root by flashing a tampered boot.IMG ;)

Users have reported problems with updating via OTA when rooted, so why don't you just flash the OTA in stead of waiting for it? ;)

Smashed down on the mighty Nexus 9
[Nexus 9 General] doubleho:
tux,so I gonna make a titanium backup before doing anything I am not familiar with, should I back up all user apps + user data or just user apps only?
[Nexus 9 General] Gormsen:
Backup user apps + data for those apps (you could backup GEL if you want to, for easy setup). Don't backup any user data other than that. Transfer the backup files to a computer/cloud since some users report that you need a full reflash of the factory image, which will wipe the tablet.

I wasn't rooted prior to flashing the OTA.

My advise would be to read the other threads as there's plenty information already there ;)

Smashed down on the mighty Nexus 9
[Nexus 9 General] cor_mann:
So I had a different experience. I apologize if someone already reported this.

I got my N9 yesterday around 7pm EST. I saw the news about the update this morning. I kept waiting to be notified about an update. Didn't receive anything all day. Just checked my build #. Turns out I received the "Q" build yesterday during the initial forced OTA.

I was wondering why my unit seems so much more stable than all the reviews report.

I suppose some people who got their N9s yesterday and forward may already have the update and not know it. Of course, most people in this forum are smarter than me and probably noticed it immediately.
[Nexus 9 General] fyrchela:
OTA error

Hey guys,

Just a quick heads up. So I'm running completely stock LRX21L fw version (no root) and yesterday I received an OTA update notification (I guess it's the "Q" update; 37.3 MB to download) after manually hitting "Check for updates" button.

But After downloading, installing and restarting the device, I've got an error on my screen (It's just a green android and "Error" - nothing else). So I restarted my tablet by holding down the power button and everything came back to normal, but I'm still on "L" fw version.

I tried to update twice and I guess it's something wrong with the OTA itself so I'm waiting for correct one.

N9 Wifi-Only 32GB LRX21L
[Nexus 9 General] Gormsen:
This is the same problem that most other users are reporting. Something went wrong when we were force to update to the first OTA, it didn't update the recovery, and because the latest OTA checks looks for a specific fingerprint in the recovery, this results in an error.

If you're unlocked, then flash the OTA by yourself through fastboot ;)

Smashed down on the mighty Nexus 9
[Nexus 9 General] muhsli:
Hi guys,

I've been following this thread from the beginning so I know what is up with the faulty OTA. I installed the update after unboxing my device, so it's very likely that I've got the very same version irregularity as many other did.

I'm in the EU, and I haven't recieved the LRX21Q OTA yet, so I decided to either sideload it or to flash factory image if sideloading wouldn't work due to mentioned fact above.

However I'm stuck, so if anyone here doesn't have any suggestions I'm afraid I'll just have to wait for the OTA to arrive, and pray for that it is the corrected one.. :crying:

What I have tried so far:

Sideloading via ADB - I wouldn't come so far in the process, as I really can not enter the recovery. From HBOOT, when I try to enter recovery, I end up with this screen https://s3.amazonaws.com/pushbullet-uploads/ufgrH6a-JhkxykesIvjgWQNqe6rMZOC1pcygnWT0/20141114_100453.jpg.

Flashing the factory image - The device is recognized by ADB. After I reboot into the bootloader and fastboot, my laptop won't find the device anymore.

I've enabled USB-debugging, OEM unlocking etc..

I tried switching from MTP to PTP, still the same.

Android SDK is up to date and I'm working it on a Ubuntu laptop with zero other USB peripherals connected.

What to do.. what to do... :confused:
[Nexus 9 General] daniii88:
After booting into bootloader, you have to install the latest google usb drivers (from windows device manager)...
[Nexus 9 General] muhsli:
Well, as I mentioned I'm on Linux ;)
[Nexus 9 General] daniii88:
my fault, sorry :)
[Nexus 9 General] muhsli:
No worries :)

FYI I sorted it and I'm now finally running LRX21Q :D

It has been a while since I messed with this stuff, I have to admit, and naturally the fault was with me. I tried this all in the rush due to hunger yesterday, and forgot to check that I had my permissions straight in the udev rules. ofc not.. :rolleyes:
[Nexus 9 General] Gryphie:
If you ever need to get to recovery again you have to hold volume up and power at the screen you posted a pic of.
[Nexus 9 General] muhsli:
I actually tried that. The device rebooted after a few seconds and booted up normally
[Nexus 9 General] bobbyd-nexus:
Is there any official statement from google regarding this OTA issue ?
[Nexus 9 General] oldblue910:
Nope, and most likely, there won't be. You'll just wake up one day with a new OTA update available.
[Nexus 9 General] bobbyd-nexus:
love that surprise updates for nexus...
[Nexus 9 General] hill67:
Got my 3rd n9 last week and it installed the new firmware 21Q out of the box. I live in the Netherlands. It definitely runs so much smoother. I was wondering if I can root the device with the one click file from rootjunky (nexus 9 ROOT.zip)?
[Nexus 9 General] doubleho:
I rerooted it with cf autoroot after I updated to 21Q

u can find the link on original android development's chainfire thread
[Nexus 9 General] techiedj:
Looks like another ota (LRX21R?) with a fix for the recovery issue maybe? Haven't tried it yet...

http://android.clients.google.com/packages/ota/google_flounder_volantis/b82e84d593421e9635621f4de702525612e11411.re_signed-volantis-LRX21R-from-LRX21Q-factory-recovery-ok.zip

Edit: and it failed LoL ... Looks like the last OTA did not update the 21L recovery either!

Edit2: Looks like it patches System, Vendor, and maybe boot, and verifies recovery must be LRX21Q first.
[Nexus 9 General] EthanFirst:
updater-script

getprop("ro.build.fingerprint") == "google/volantis/flounder:L/LFW73W/1491895:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/volantis/flounder:5.0/LRX21Q/1573789:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/volantis/flounder:5.0/LRX21R/1573874:user/release-keys" ||
abort("Package expects build fingerprint of google/volantis/flounder:5.0/LRX21Q/1573789:user/release-keys or google/volantis/flounder:5.0/LRX21R/1573874:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

Script check fingerprint L/LFW73W or 5.0/LRX21Q or 5.0/LRX21R but abort message is 5.0/LRX21Q or 5.0/LRX21R
[Nexus 9 General] McChen147:
I took a look at the upgrade script.....looks like this OTA is to upgrade from LRX21Q to LRX21R and also allows the upgrade for those that have the LFW73W recovery but with the LRX21Q OS? i would guess that out of the box some people got a LFW73W to LRX21Q OTA which also did not upgrade the recovery, just like the LFW73W to LRX21L OTA that a lot of us got.

At least Google is apparently aware of the recovery problem, hopefully there should be a version of this then out there that does a L to R upgrade that also allows for the LFW73W recovery.
[Nexus 9 General] Mephisto_POA:
is this newer OTA update working then?
[Nexus 9 General] KinetiClutch:
It might have been pulled.

By the sounds of it, it fixed one problem and missed the other issue.

Hopefully, will be addressed. Like the above said atleast google have recognised the issue.
[Nexus 9 General] McChen147:
Can't say for sure as I'm still stuck on L, but if you are on Q, this ota should get you to R and fix your recovery.

Keep an eye out for the L to R version of this, if the fixed Q to R is rolling out, there's a good chance that is rolling out too. Hopefully somebody can capture that URL for us soon
[Nexus 9 General] jamalau:
Hallo, cane anyone tell me how do i instal the OTA manually, i´ve nothing found about this , in this Thread!
[Nexus 9 General] iigrs:
here you go

http://www.androidcentral.com/how-manually-upgrade-your-nexus
[Nexus 9 General] jamalau:
Thanks, and i don´t need to rename the OTA.zip ?
[Nexus 9 General] mbirth:
LRX21R OTA fails for me, too. Currently running LRX21Q from factory image. Flashed factory system.img before. Error message is:

Verifying current system...
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:8000256:3172d86057339cb034c308640c1d7f838fbbe0a7:8000256:bd283cc9efc84629ac759697293bd159f9bf9caf" has unexpected contents."
E:Error in /sideload/package.zip
(Status 7)

EDIT: LNX seems to be the boot partition. So I'll try flashing the factory boot.img.

EDIT2: Okay, after reverting boot and system partitions to factory, the sideloaded OTA worked fine.
[Nexus 9 General] iigrs:
No you don't have to copy and paste the file name into adb command.

make sure you have the last ADB 1.0.32, otherwise it won't be able to sideload.