yashsingh1/xdaforums huggingface dataset:
[Nexus 9 General] bobjbain:
I am completely stock so it should have worked....
[Nexus 9 General] McChen147:
i was 100% stock as well. the OTA applied perfectly OK, the sig passed, everything was verified. very concerning to me that I'm having this problem, I have done so many OTA sideloads and never had any problem in the past. I hope mine is just an isolated incident and not a sign that something is wrong with the OTA. Is it possible that this OTA is only supposed to be applied to certain HW revs? I didn't think OTAs worked like that and would think the update script would check for something basic like that if that was the case. Can't believe even a factory reset doesn't fix it.

If anyone else has problems with the OTA, please post and let us know.

Lesson learned though....will make sure to set the bootloader to unlockable before any OTA again. I understand that this is probably for security reasons, but it also seems absurd that it makes it impossible to recover from such an unexpected error that should be easily rectified by flashing the factory image. Also, it appears that the unlockable setting might reset itself after some time, so you need to check this setting each time you think Android might break? Certainly would not give you protection all the time. There needs to be a better option to run with a secured and locked bootloader, but have some way of authorizing an unlock if you can't boot Android. Anyways, looks like my tablet will have to be exchanged.
[Nexus 9 General] stadicon:
I've got the OTA too, but i wasn't able to install since i am rooted and with custom kernel. I can see that the .zip contains some (small) vendor patches. The question is, could this fix any important issue on drivers and should developers actually include that patch to their 5.1.x ROMs to fix some hardware issues?
[Nexus 9 General] _litz:
Guys, this is a Nexus ... locked bootloader is NOT a requirement for taking an OTA.

There's also no reason (really) to lock a bootloader on a nexus, either ... so go ahead and unlock it to be safe.

As for flashing ... you need to fastboot flash the following from the factory image zip :

system.img

vendor.img

boot.img

(and if you have TWRP, recovery.img)

This guarantees your system is in a good state to take the OTA to 5.0.2.
[Nexus 9 General] VivaErBetis:
Can someone please publish the /system/build.prop file of 5.0.2 here? Thank you!
[Nexus 9 General] bobjbain:
Apart from the fact that, supposedly, your warranty is invalid if you unlock the bootloader!!

As for the second part you need to be unlocked to fastboot flash anything!

I, personally, never had any need to root my device so, accordingly, had no need to unlock the bootloader. However the OTA update seems to have fragged my N9 quite significantly and without an unlocked bootloader there is really nothing I can do. I am crying on the inside whilst desperately searching for a way to get my N9 up and running again.
[Nexus 9 General] _litz:
There was a link above to a method of formating the cache and userdata ... did that not help you?
[Nexus 9 General] bobjbain:
Nope, erasing cache in recovery took some time and end result was the same, no booting and can't erase cache in fastboot either because the bootloader is locked (see attached image)
[Nexus 9 General] _litz:
what partitions will it allow you to flash?

and/or, will it allow you to apply the entire zip file in one go?
[Nexus 9 General] bobjbain:
>fastboot update image-volantis-lrx22c.zip
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814205204 bytes
error: update package missing system.img

>fastboot -w update image-volantis-lrx22c.zip
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814205204 bytes
error: update package missing system.img

>

and

>fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
erasing 'vendor'...
(bootloader) Device State : Locked
FAILED (remote: Can not erase any partition while device state is locked!)
finished. total time: 0.163s

>fastboot flash cache cache.img
target reported max download size of 518205818 bytes
erasing 'cache'...
(bootloader) Device State : Locked
FAILED (remote: Can not erase any partition while device state is locked!)
finished. total time: 0.156s

>fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
(bootloader) Device State : Locked
FAILED (remote: Can not erase any partition while device state is locked!)
finished. total time: 0.162s

:(

I am desperately trying to avoid the factory reset route not least because I don't think it will do a thing...
[Nexus 9 General] metaphz:
Flashed the four images to restore device, trying to sideload OTA however every time I go to recovery then in to sideload from ADB the PC can never find the device. Any thoughts? ADB and Fastboot work, except when trying to adb sideload LONG_IMAGE_NAME.zip
[Nexus 9 General] cam30era:
When you are in stock recovery, at the menu that has ADB sideload option, try to unplug and re-plug in the USB cable. This often solves that problem.
[Nexus 9 General] _litz:
I'm baffled ... it really seems like you're stuck in that no-man's zone where you can't do anything at all ...

I guess worst case you should still be under warranty?

It's too bad the Nexus devices don't have actual signed factory images; that's what you seem to need here.

What about trying to fastboot update (or update -w ) the whole parent tgz file (with the bigass hex number in the name) ? Or the tar that contains the zip?

Last resort, of course, would be a factory reset, but all that does is wipe userdata and the dalvik; basically returning you to "out of the box" condition with a boot (kernel) and a system (app), but nothing in cache, dalvik, or data; so the first boot sets all that up from scratch.

OTOH, you were able to format cache but NOT data, so maybe that's worth trying.

(if you're trying to save any data or apps you had on the tablet, I think you're beyond that point at this time)
[Nexus 9 General] metaphz:
Thanks for the quick suggestion, still no luck. Grrr... Windows seems to know I am messing with the device between menus because it makes the disconnect/reconnect sound. I thought these HTC's had a way to OTA from placing it on the device its self.
[Nexus 9 General] jde984:
For those having ota troubles, 5.0.2 factory images have been released.

https://developers.google.com/android/nexus/images
[Nexus 9 General] USBhost:
What! All that trouble updating to 5.0.2

To just get the vendor image was in *****
[Nexus 9 General] aikidoka25:
I sideloaded 5.0.2 wifi version without any issues. I did erase the cache before doing the update.
[Nexus 9 General] oldblue910:
Anyone get the OTA for the LTE model yet?
[Nexus 9 General] bjacks12:
Got the OTA notification while in a conference just now. I decided to be brave and allow it to download and install, rather than waiting and flashing the image which is safer. Fortunately it worked just fine. Can't say that 5.0.2 does though
[Nexus 9 General] velocity90:
Got the ota notification. Downloaded it, verified, tablet says its up to date without rebooting. Im still on 501. Reboot doesnt help. Why wont the ota install?

Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
[Nexus 9 General] cam30era:
If you are rooted, or have a modified kernel, or TWRP recovery it won't install. Have to be 100% stock.
[Nexus 9 General] velocity90:
Stock here

Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
[Nexus 9 General] atomikpt:
Have completely STOCK 32gb LTE no OTA here..

But "volantisg" for Nexus 9 (LTE) 5.0.2 (LRX22L) factory image is up on google..

Will wait for OTA.. or is there an OTA to manually flash?
[Nexus 9 General] oldblue910:
No. We don't have the OTA link for LTE yet. If you're willing to wait for it, I'd be most grateful. When you get the notification on your tablet, grab the URL from logcat before you update, and I'll put it in the first post. Thanks!
[Nexus 9 General] velocity90:
Update came again and now its updating :)

Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
[Nexus 9 General] bobjbain:
RMA'd :crying: :crying: :crying:

Wipe cache and data in recovery, no beans

Factory reset in bootloader, no beans
[Nexus 9 General] _litz:
There needs to be a word of warning added to the opening post of NOT accepting this OTA unless you either have an unlocked bootloader, or have checkmarked the option that ENABLES unlocking the bootloader.

There is a very clear brick path here when the OTA fails on a locked device.
[Nexus 9 General] Winesnob:
It's coming! Check out [MENTION=4418828]GoogleNexus[/MENTION]'s Tweet: https://twitter.com/googlenexus/status/596343795140194304?s=09

Get the link!
[Nexus 9 General] rolldroids:
In twitter its 5.1 but in Google+ its 5.1.1 - so I hope 5.1.1 is right ☺☺
[Nexus 9 General] tyvar1:
5.1.1 hype! :D
[Nexus 9 General] rmagruder:
Sascha confirmed to me on my G+ that it's 5.1.1. No worries.
[Nexus 9 General] yakuza75:
I have a stock Nexus 9 wifi and the 5.0.2 OTA update fails. The error message is:

/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates

E:Error in /cache/update.zip

(Status 7)

I have wiped the cache partition, no luck. Any suggestions?
[Nexus 9 General] lyubor:
You need to flash a clean factory image. I got that on mine after cleaning up root and replacing recovery. It wouldn't accept ota untill after a clean flash.
[Nexus 9 General] McChen147:
i learned that the hard way, i have a bricked nexus 9 from the 5.0.2 OTA. Completely stock and I did not unlock the bootloader or enable the unlocking of the bootloader beforehand. The 5.0.2 OTA applied without any errors, so I'm hoping that I can sideload the 5.1.1 OTA on top of what I have now and unbrick it. Cross fingers. Otherwise I"ll have to exchange it.
[Nexus 9 General] cam30era:
Your bootloader has to be unlocked to ADB sideload an OTA. Better start the RMA process.
[Nexus 9 General] McChen147:
Not true, I sideload OTAs on locked bootloaders all the time. That's how I did the 5.0.2 OTA. You only need to unlock the bootloader to flash the factory image.
[Nexus 9 General] cam30era:
OK
[Nexus 9 General] bobjbain:
My Nexus 7 (2013) just got the 5.1 OTA update, after applying software version is 5.1.1

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------

Hmmm, I sideloaded the 5.0.2 OTA with a locked boot loader, got no reported errors but it bricked my device too!
[Nexus 9 General] rolldroids:
That is good to hear as I have got a nexus 7 too. But I am only impatient for the nexus 9 update. Hopefully the link will be captured today ?
[Nexus 9 General] McChen147:
Apparently this is happening to quite a few other people too....nothing to do with the bootloader being locked or unlocked or sideloading, looks to be a bug with 5.0.2 or the OTA I guess. Since 5.1.1 is already rolling out, might as well try sideloading that and see if it unbricks it before exchanging it.

http://www.androidpolice.com/2015/0...d-5-0-2-update-bricks-nexus-9-for-some-users/
[Nexus 9 General] cam30era:
Yes, you're right. But if one unlocks their bootloader, at least they have a path to fix it.
[Nexus 9 General] McChen147:
Yes, definitely! What's most important to know is that on Lollipop on the Nexus 6 and 9, Google changed the way the bootloader unlocks. You must enable the option to unlock the bootloader in developer options in Android before you can unlock it. Of course in cases like mine where you can't boot Android, you're screwed. I think Google changed it to prevent a thief from bypassing the new factory reset protection by flashing fresh images. But it also creates problems when one needs to legitimately recover a device. So it is a good idea to at least enable that option before applying system changes like an OTA even if you don't unlock the bootloader. One can then change it back after a successful OTA if one is worried about anti-theft security. Will definitely be doing this before any OTA after this experience!
[Nexus 9 General] _litz:
The problem here is a simple, basic, error in the script itself ...

They way google wrote it, it does the following:

Verify system; upgrade system

Verify vendor; upgrade vendor

Verify boot; upgrade boot

so think about this a sec ... what happens if the vendor verify fails ... you have already upgraded system.

No problem, you think, I'll just run the OTA again. Except, system is now 5.0.2. It won't pass verify.

So ... now you're stuck. And with this new bootloader unlock limitation, if you can't unlock, you're now screwed.

What google should have done (and what I would have demanded had this crossed my QA desk for verification), is that all three verification steps happen BEFORE any upgrading occurs.

It's a very simple software premise : verify your environment BEFORE changing it.

Nexus has no provision for a RUU like, say, a HTC M8 ... where you have signed packages the bootloader will flash. If we had those, we have a path back to a factory fresh unit on a locked bootloader. But we don't, so the only recourse is RMA.

And ... someone - PLEASE - put a warning in the OT about this, so people don't continue to brick their units.
[Nexus 9 General] McChen147:
Interesting analysis, thanks for posting.

In my case at least, I don't think the failure was due to the script. I passed all of the verifications and each modification stage applied with no errors. Seemed like an ordinary OTA to me....until I rebooted.
[Nexus 9 General] cam30era:
Just found this. How to solve your 5.0.2 OTA soft brick > http://m.androidcentral.com/what-do-if-android-502-update-sends-your-nexus-9-bootloop-tizzy
[Nexus 9 General] McChen147:
Thanks....that does seem to help some people, but not others. Unfortunately, I'm in the latter category, a cache wipe and factory reset did nothing for me. Gonna wait for the 5.1.1 OTA zip and sideload that and see what happens. Google said it would start rolling out today, hopefully someone gets the URL soon!
[Nexus 9 General] inick73376:
I need the OTA link for Nexus 9 LTE 5.0.2? Does anyone have it?
[Nexus 9 General] Winesnob:
Edit: What??? LRX21Q from 21L? That's a little dated.
[Nexus 9 General] RusherDude:
Thats an old link He probably confused LRX22L with LRX21L.
[Nexus 9 General] nyasha1935:
How did you run the new adb and fastboot, I've updated it but can't run it
[Nexus 9 General] cam30era:
If you are using Ubuntu (or any flavor of Linux) this is a pretty good guide > http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
[Nexus 9 General] marcomsousa:
OTA 5.1.1 LINK -> https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
[Nexus 9 General] oldblue910:
I'm guessing it won't let you get past that screen?
[Nexus 9 General] datdirtyscrew:
Yes sorry. I was trying other things but it won't let me.
[Nexus 9 General] oldblue910:
Yeah with Lollipop not allowing OEM unlocks without changing a setting in developer options, I'm basically giving up on getting the initial firmware as there's really no way to get it now. Oh well. Thanks anyway fire your help! ?
[Nexus 9 General] radaloel:
Hi, guys!!Is anyone able to share the calendar apk from your N9 Rom? Or at least confirm if it is the new announced 2.4 google Calendar? Thanks in advance!!
[Nexus 9 General] USBhost:
Here you go
[Nexus 9 General] TheManii:
Could you pull all of /system while you're at it?

I'm going to make a thread requesting a rom dump soon anyway, if you could do that for me then I can just skip making a thread.
[Nexus 9 General] usaff22:
If you don't mind me asking, would you be able to dump the system partition of your device? There's a good guide here.

Thanks!

Didn't see your post until after I posted mine and refreshed the page :P
[Nexus 9 General] USBhost:
Some one already did that

http://xdaforums.com/showpost.php?p=56483032&postcount=19

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

Doesn't that need root
[Nexus 9 General] usaff22:
Nevermind, the post you linked seems perfect.
[Nexus 9 General] TheManii:
If you're just dumping system, you dont need root.

If you want to dump the bootloaders or not simply get loose files (ie make a system.img) you'd need root, or a custom recovery (which includes root while in it)
[Nexus 9 General] bbszx:
The first boot ... hold button 'power' + 'down'
[Nexus 9 General] TheManii:
That's before the initial ota correct?
[Nexus 9 General] bbszx:
After Update:
[Nexus 9 General] TheManii:
COuld you do an adb bugreport and upload it?

The ota filename might still be in it if you didnt wipe data afterwards.
[Nexus 9 General] bbszx:
Yes, bevor initial Update
[Nexus 9 General] SoLdieR9312:
HBOOT 3.43.0.0114

OS-n/a

Build number: LRX21L
[Nexus 9 General] metpolds:
DELETED..... Incorrect post
[Nexus 9 General] oldblue910:
There's an OTA rolling out today for the Nexus 9. Just a minor bugfix OTA. If anyone gets it, please post the full URL here before you update (which you can get from logcat). If anyone needs instructions on how to do this, let me know. Thanks!
[Nexus 9 General] StuMcBill:
How do you know this?
[Nexus 9 General] USBhost:
Thanks man
[Nexus 9 General] lyubor:
Love you. Thanks a lot!
[Nexus 9 General] qbking77:
Here's a video showing how to manually update your device:

https://youtu.be/ZNEXCY-wHpw
[Nexus 9 General] oldblue910:
Thanks! First post updated!
[Nexus 9 General] oldblue910:
As an aside, 5.1.1 is only rolling out for the Wi-Fi model. The LTE model is still receiving the 5.0.2 OTA at this stage. Further, we still do not have the 5.0.2 OTA link for the N9 LTE. If you get the update, PLEASE get the link out of logcat before you update. If you don't know how to do that, let me know and I'll be happy to help you.
[Nexus 9 General] cam30era:
No love.. :crying:

100% stock 5.0.2 everything.

"Finding update package...

Opening update package...

Verifying update package...

Installing update package...

Verifying current system...

/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates

E:Error in /sideload/package.zip

(Status7)

Installation aborted."
[Nexus 9 General] lyubor:
I get that as well after achieving root at some point. A complete userdata wipe is the only thing that let me update again. Might as well flash the factory image then without wiping data (or manually).
[Nexus 9 General] cam30era:
I just saw that the factory image for 5.1.1 was posted. Flashing that now.
[Nexus 9 General] oldblue910:
Are you rooted? Also, if you flashed the factory images then immediately tried to apply the OTA, you can't. You have to flash the factory images and let the system boot normally at least once.
[Nexus 9 General] cam30era:
No, I am not rooted. Flashed the 5.0.2 factory image last week when it hit the Google servers.

---------- Post added at 04:25 PM ---------- Previous post was at 04:15 PM ----------

Just fastboot flashed the 5.1.1 .img files. All is good. Thanks for your feedback. :)
[Nexus 9 General] bgcngm:
How do you guys pass the screen of Android with the red exclamation sign? I tried VOL-UP + POWER and VOL-DOWN + POWER but no go.
[Nexus 9 General] cam30era:
Press and hold power. Then press and release volume up.
[Nexus 9 General] Hashbang173:
See here for a video demonstration: https://youtu.be/n6mS-2cnRfc?t=2m10s
[Nexus 9 General] tyvar1:
Thanks! :D
[Nexus 9 General] _litz:
OTA zip worked fine for me here ...

Oddly first time I ran it, it said my system was 5.0.1.

Come to find, the 5.0.2 OTA didn't update either the bootloader OR recovery.

Had to flash both (along with fresh copies of boot/system/vendor), then sideload the OTA.

Went flawlessly.

Still waiting for all the apps to reinitialize in the dalvik to see how it runs.
[Nexus 9 General] bobjbain:
Would appear that someone at Google has been reading your post :good:
[Nexus 9 General] hdtvpower:
Is it really? I have not heard or seen anybody with a LTE 5.0.2 OTA update.
[Nexus 9 General] oldblue910:
Google released factory images, which only happens when an OTA is official. It doesn't appear that people are getting it yet, though.
[Nexus 9 General] _litz:
I wish I could lay claim to it, who knows ...

It just baffles me they would push something like that publicly in the first place ... one of the first, basic, tenets a QA Engineer learns early in their career is "test for variety permutations and situations" ... if all you ever test for is the ideal configuration, and the ideal situation, you're not really doing any kind of quality testing.

I go through this all the time with my developers ... I open a defect for, say, "you click here, then here, then here, and it crashes". And the answer from the developers, invariably, is "why would anyone do that?"

All I can say, in answer, is : "have you met our users?"

---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------

Why can't anyone with a LTE 9 simply flash from the factory images?

All you need is the following :

bootloader, recovery, system, vendor, boot

You can easily do that by hand, and you won't lose data.

Root is ridiculously easy too ... simply fastboot boot the TWRP recovery image, then sideload supersu.zip.

Then you're ready on 5.0.2 for a 5.1.1 OTA ... or you can hold out, and do the same with 5.1.1 and jump directly to it.
[Nexus 9 General] sean.trinidade:
+ 1. Actually, it's even easier to upgrade via RUU - simply open up the bat file and remove the "fastboot erase userdata" row and the "-w" from the last fastboot update and result! :)
[Nexus 9 General] atomikpt:
Well what is the degree of certainty you have that it works?

Has someone else tried (flashing factory image 5.1.1 on LTE?)
[Nexus 9 General] miknik85:
I attend the OTA update, thanks :)
[Nexus 9 General] cam30era:
It's a good idea to "Quote" with a post like this. I've no idea which previous post you're referring to, and I suspect no one else does either.
[Nexus 9 General] atomikpt:
U're right, I've edited my post.

It is about flashing factory from 5.1.1 on LTE model.
[Nexus 9 General] WinterApocalypse:
I'm debating very heavily on flashing the WiFi image on my LTE, just because I'd rather lose my lte temporarily and have a functioning tablet. I'll let you know how it goes.
[Nexus 9 General] atomikpt:
Even if LTE does not work I think I will flash it as well.

Let me/us know.
[Nexus 9 General] sean.trinidade:
Done it this way several times with my Nexus 7. It's the main reason why I left my N9 stock unrooted this time round.. It's just not worth the hassle!

Based on my experience with the Nexus 7 3G, there isn't any difference in the (files contained in the) RUU between the WIFI and Modem versions... Mainly the radio.img. However, if you are going this route I would recommend flashing the files separately rather than run the actual RUU script!

Also, be careful not to mess up your partitions. I know with normal htc devices they are sometimes quite flakey when doing stuff like this!
[Nexus 9 General] WinterApocalypse:
Oh I'm definitely flashing all the images manually. Having used both the HTC One m7 and m8, and converting between stock and gpe, I'm aware of the partition nightmares. Lol
[Nexus 9 General] WinterApocalypse:
Just finished booting! Everything seems to work, apart from the Cellular components missing. Flashaholics, you're good to go! Just extract the image and flash the .img files. No need to wipe either!
[Nexus 9 General] oldblue910:
Why would you flash a WiFi-only ROM to an LTE tablet? Doesn't that completely defeat the purpose?
[Nexus 9 General] xeni:
Nub question, but how do I download the OTA using the link in the OP? For some reason I get taken to the google docs and then it prompts to pick winzip or another tool and it just never gives me a download optin.
[Nexus 9 General] WinterApocalypse:
Because the LTE version doesn't have 5.1.1 yet, and even 5.0.2 is damn-near unusable. I'd rather be able to use my tablet and lose the LTE while waiting for my update then have a useless tablet with LTE. :)