yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] volkerth:
Same here. clean flashing latest official + Banks GApps + new vendor, stuck at the boot (> 30 minutes).

Thereafter I tried the latest weekly + TR Gapps, which is working now.
[Nexus 9 Original Android Development] uzi2:
I'm experiencing the same issues as others have reported whilst updating from the latest weekly.

File appears to be good, but are you able to confirm MD5?

D3B5EB5F8217BCA36842CC39B38A4BAE
[Nexus 9 Original Android Development] NYCHitman1:
For those of you having issues, try this: https://plus.google.com/+JoshChasky/posts/RdFJRuMLDG5

Keep in mind that official nor weekly builds can be flashed to test builds and vice versa. Also, keep all test build chatter on the G+ conversation.

Thanks! :highfive:
[Nexus 9 Original Android Development] Dudmaster:
I just did a full factory reset on all partitions, got new vender, and flashed DU OFFICIAL-v10.3. SuperSU is a black screen, my file managers won't load either, and I'm idling at 100% RAM. WTF?

Edit: Yes, I've downloaded it multiple times
[Nexus 9 Original Android Development] mrshades812:
Yeah, I've given up on the past couple of builds myself. Going stock rooted for a while.

Waiting on an update....
[Nexus 9 Original Android Development] uzi2:
Not sure why you want to go back to stock. 10.3 not working for me either, so I will stick with the latest weekly for a while.
[Nexus 9 Original Android Development] NYCHitman1:
Enjoy stock ?
[Nexus 9 Original Android Development] glwilliams4:
Anyone having issues with installing apps after updating? The majority of my downloads are just pending in the Play store, or it will download but not install. At that point it just freezes up the whole device. I followed all directions in OP and used the Banks Dynamics gapps attached there.
[Nexus 9 Original Android Development] NYCHitman1:
Yeah, this is an issue. I'm hoping to have it fixed by Friday -- in time for the next weekly.
[Nexus 9 Original Android Development] glwilliams4:
Not to sound like an entitled child, but just to confirm, does this mean that until you fix it I won't be able to install apps from the Play store? Or is there something else I can do to temporary fix the situation on my end? I only ask because I'm going out of town tomorrow and I will need this working before then, so if there's nothing I can do I'll just flash something else to tide me over until you've gotten things sorted out.
[Nexus 9 Original Android Development] NYCHitman1:
Did you not make a backup of the prev version? If so, just restore to that for now.
[Nexus 9 Original Android Development] bigduff:
Is their anyway to turn off double tap to wake as of now ?
[Nexus 9 Original Android Development] NYCHitman1:
No, it's native to the Flounder kernel. Why do you want to turn it off?
[Nexus 9 Original Android Development] ZenithHammerhead:
I'm having an issue accepting SU requests. I try to click "grant" when prompted, and the system doesn't seem to recognize my touches. It also seems like the built in SU app doesn't support granting app post-request in the settings...any ideas?

Clean flashed!
[Nexus 9 Original Android Development] wifesabitch:
If you use Lux Auto Brightness then that's the problem. Myself and many others had the same issue.

If not, then I don't know.
[Nexus 9 Original Android Development] giute88:
Great ROM! Any plans to add some kind of split screen or multi window feature? :)
[Nexus 9 Original Android Development] NYCHitman1:
Not that I know of, but it's a bit too soon to tell.
[Nexus 9 Original Android Development] VermontKindBud:
ETA on camera fix?

I love this rom but I need my camera so I reverted to stock. Any ETA on the camera fix?
[Nexus 9 Original Android Development] NYCHitman1:
No.

EDIT: I assure you that it is something that is bothering me greatly as I enjoy communicating (video) with my relatives via Skype or Hangouts. It's been much more difficult to fix than I originally anticipated, but mostly because it doesn't make any sense why it's not working.
[Nexus 9 Original Android Development] TenderloinShadow:
Are there any ROMs out there with a multi-window feature for this tablet? Because I would be on that in a heartbeat lol.
[Nexus 9 Original Android Development] NYCHitman1:
Doubtful.
[Nexus 9 Original Android Development] Toxicoblivion:
Great ROM! For a minimal suggestion, maybe adding CPU & Battery temp as status bar icons (like the network indicator) would be a cool thing! Any which way, good job on making this tablet smooth!!!!!!!!!!!
[Nexus 9 Original Android Development] NYCHitman1:
Nah, sorry. You can use 3rd party apps to do that for you.
[Nexus 9 Original Android Development] ilatimer1:
Hey guys, I just installed the latest PA "Alpha" build and noticed that the camera is working. Is there a way to compare your ROM code to PA's and see why its not working on your ROM?
[Nexus 9 Original Android Development] NYCHitman1:
I've compared our code to just about any relevant source, but comparing to CAF bases don't do me much good since we're AOSP-based.
[Nexus 9 Original Android Development] ilatimer1:
Ok, I thought PA was AOSP based.
[Nexus 9 Original Android Development] Verttex:
I'm having a problem where after a few minutes of video, it just refuses to play unless I restart the stream. Both YouTube and Twitch have this problem. Even videos in the chrome browser.

It's definitely this Rom as I never had this problem on stock.
[Nexus 9 Original Android Development] NYCHitman1:
Fetch a logcat.
[Nexus 9 Original Android Development] Freak07:
I do not exactly know but banks has released his simple aosp rom. Maybe this can help you. You can just Google it or look in the general n9 section. There is no dedicated thread on xda but a community on Google plus.
[Nexus 9 Original Android Development] xtcdk:
I think OP knows what his doing ?

Hammerhead / Shamu / Flounder . DKWhq - www.jsand.dk
[Nexus 9 Original Android Development] SwoRNLeaDejZ:
What GApps did you install with the ROM? I have tried every version of DU (this official release and all the test builds) and never had any issues with video playback on YT, Twitch, Netflix, etc. I would go for a clean install, and don't restore any apps at all, and see if you can replicate the issue.
[Nexus 9 Original Android Development] glwilliams4:
Unfortunately no, didn't have enough room on the device to take a nandroid. Figured if I had issues I would just install stock again (which is what I was on) or try Paranoid. I just really like DU on my OPO, so I figured I'd give a shot on my tablet.
[Nexus 9 Original Android Development] NYCHitman1:
Just install the last weekly from 6/3. You'll be fine until the new weekly comes later this week.
[Nexus 9 Original Android Development] ZeroSkylineX:
I too am having an issue with this official build. I wiped cache, dalvik cache etc and it's suck on boot loop. I've restarted the tablet many times powered it off to try again after giving it a break and no go. I've reverted back to Official Build 10.2 and it booted no problem within minutes. I've tried to flash 10.3 and it stays on the boot loop for more than half an hour.
[Nexus 9 Original Android Development] NYCHitman1:
We've already established there's an issue for some of you. I don't need cosigner posts. They offer nothing to a development thread. Anyway, the issue has been resolved and will be available in time for the next weekly build.
[Nexus 9 Original Android Development] USBhost:
You should put a warning in the op
[Nexus 9 Original Android Development] NYCHitman1:
No need. People just need to read. Not going to cater to the lazy.
[Nexus 9 Original Android Development] lost eden:
How long should the first boot take? I've been sat on the splash logo for 30 minutes now, no reboots.

Nexus 9, latest TWRP, wiped everything, flashed stable DU, flashed recommended gapps, rebooted.... now waiting 35 minutes & still going.

Only thing that concerns me is that the device was encrypted & even after wiping everything it still asked me (by name) to put my unlock pattern in?
[Nexus 9 Original Android Development] Luigi7744:
Been stuck on a bootloop for 30 minutes and nothing. I think you should give people a heads up before considering this update a stable build. No
[Nexus 9 Original Android Development] NYCHitman1:
That's your problem. Not mine. You're in this situation because you didn't read. READ first.
[Nexus 9 Original Android Development] NYCHitman1:
Read people. It's fundamental and it certainly won't kill you. Stop being lazy.
[Nexus 9 Original Android Development] lost eden:
I did read. I read the whole of the first post several times, I read the Google Doc linked at the Google+ page & of course I spent a while googling around. When I didn't find an answer I posted a polite question, but after your rude response I'm now going to give up on this ROM & go elsewhere. You might be a great ROM developer, but you've certainly got a lot to learn when it comes to basic manners.
[Nexus 9 Original Android Development] NYCHitman1:
That's cool. Enjoy wherever you end up. :good:
[Nexus 9 Original Android Development] uzi2:
As others have reported, I was unable to boot 10.3 and I am also unable to boot Weekly 160617.

For me the latest stable version is Weekly 160603
[Nexus 9 Original Android Development] telc:
I can't boot this weeks weekly either. Tried Dirty then Clean. No joy.
[Nexus 9 Original Android Development] NYCHitman1:
You guys are doing something wrong then. The build boots fine AND I fixed the issue of root not working.

Make sure you're wiping system, data, cache, and dalvik prior to flashing the ROM and gapps.
[Nexus 9 Original Android Development] uzi2:
Is it not possible to update to this version (wiping only cache and art - installing only ROM)?
[Nexus 9 Original Android Development] NYCHitman1:
Well, we don't take bug reports on a dirty flash. Ultimately, I'm trying to figure out why some of you have issues and others (including myself) do not.
[Nexus 9 Original Android Development] uzi2:
It's always difficult to debug when it is not affecting everyone. If there is any testing I can do to help track down the issue, just shout...
[Nexus 9 Original Android Development] NYCHitman1:
I'm curious if it's our build box that puts out the official + weekly builds. Some bad ccache, maybe.
[Nexus 9 Original Android Development] uzi2:
Wouldn't that be affecting everyone? You would be able to replicate it.
[Nexus 9 Original Android Development] NYCHitman1:
Just theorizing. Side note: check your PM.
[Nexus 9 Original Android Development] temuri:
Hello,

I cannot boot the latest version either. And I've flashed the latest vendor.img.

[MENTION=2489052]NYCHitman1[/MENTION] Since so many of us are having a problem booting into DU, maybe it would be worth repeating yourself again and re-posting clear instructions on how to flash your ROM properly, indicating exactly which vendor.img needs flashing? I've managed to boot it, but from one of previous weeklies, but was seeing Android's error messages upon boot.

So maybe you could do us all a favour?

I've went through all 112 pages of this thread trying to see if I'm missing something - but it just fails to boot.

Thanks for your efforts.
[Nexus 9 Original Android Development] uzi2:
I have not been able to boot any DU build which contains the June security update, whether it's official, weekly or test branch.
[Nexus 9 Original Android Development] Lar5:
I was lazy this time and dirty flashed weekly 20160617 on top of weekly 20160603.

No problem here. Running just fine on my N9 :good:
[Nexus 9 Original Android Development] killswitx:
funny thing that happened is that i have flashed the vendor.img provided from you and then i have just flashed different rom. but when i booted into that rom it told me that i might not have the latest vendor.img weirdly...hmm
[Nexus 9 Original Android Development] temuri:
which vendor.img did you flash?
[Nexus 9 Original Android Development] Lar5:
I flashed the image from the latest factory image (MOB30M)

I just checked the md5 checksum and it matches the one earlier posted by NYCHitman1
[Nexus 9 Original Android Development] temuri:
This is what I'm doing:

1. Flashing MOB30M with flash-all.bat (it boots normally) - at this point attempt to go to recovery results in Android on its side with red triangle with an exclamation mark

2. Going to fastboot, flashing recovery with "fastboot flash recovery twrp-3.0.2-0-flounder.img"

3. Going to TWRP, wiping dalvik/cache/system/whatever else (all checkboxes)

4. Sideloading DU_flounder_6.0.1_20160617-0843.v10.3-WEEKLIES.zip

5. At this point if I try to reboot to system using TWRP's button results in warning that no OS is installed

6. Going to fastboot and flashing: "fastboot flash vendor vendor.img" from factory "volantis-mob30m"

7. Rebooting to system is stuck on animation logo for at least 20 minutes

Am I doing something wrong or different from you?

Thanks!
[Nexus 9 Original Android Development] Lar5:
Basicly no... I'm using TWRP 3.0.2.0 too.

Then copying the files i need to the device using Total Commander with an ADB-plugin.

Using TWRP to wipe everything except internal storage, install vendor.img and install DU and gapps.

Reboot and wait 4-5 min and then set up the account.

If i dirty flash, i just flash the zip-file. Not wiping anything or reinstalling gapps.
[Nexus 9 Original Android Development] KamiKhangoto:
I've got the same problem, how did you do the hard reset?
[Nexus 9 Original Android Development] tangiers:
Fwiw, I dirty flashed ver 3 and have no problems.
[Nexus 9 Original Android Development] uzi2:
Can we please have MD5s, so those of us who are getting stuck boots can at least check that we have good downloads.
[Nexus 9 Original Android Development] Lar5:
dd0e41fa9cca6151b604197bff3c3ac6 *DU_flounder_6.0.1_20160617-0843.v10.3-WEEKLIES.zip
[Nexus 9 Original Android Development] uzi2:
Thanks. That's what I have. Now to test my theory...
[Nexus 9 Original Android Development] volkerth:
After clean flashing (wiping cache, dalvik, system, data) 10.3-official didn't work last time, I tried the current weekly 06.24 together with the latest TR Gapps. Again no success. So I am still stuck with the 06.10 weekly. Anyone else? (By the way, I got no problems at all with my hammerheads, clean and dirty current weekly)
[Nexus 9 Original Android Development] jhwbg:
Same story here, nothing after the weekly from 160603 is booting.
[Nexus 9 Original Android Development] NYCHitman1:
For those of you having issues, I strongly recommend you follow [MENTION=4569781]Lar5[/MENTION] instructions.
[Nexus 9 Original Android Development] mrshades812:
You mean wipe and flash?

I think we are doing that and it still doesn't work. Wow
[Nexus 9 Original Android Development] jhwbg:
I use MOB30M vendor and bootloader 3.48.0.0135 if that can be of any help for you. I wiped everything many times. Let it boot for 45 minutes, still no luck. Tried open gapps and the one suggested in this thread, no luck here. So it looks like most of us do it like Lar5 suggest. I love your work, I run it on my 6P without any problems. Perhaps there are different revisions of the N9, maybe bootlooder version can be a problem. I really don't know. Keep up the good work and let's hope someone can find the problem.
[Nexus 9 Original Android Development] 12paq:
I followed these wipe recommendations exactly and everything booted up fine.

I was hoping that this would boot loop so I could pull and post a log for the developers instead of whining, but no, it booted fine.

In TWRP make sure you wipe each partition recommended, especially system.

Also if you have been running a kernel with anything forced or unforced flash that kernel with this ROM.

Glad to be back on DU. Thanks for the build!
[Nexus 9 Original Android Development] jhwbg:
Boot log

Hi, here is the boot log from my N9, I hope it can be of some use.
[Nexus 9 Original Android Development] NYCHitman1:
That log doesn't say anything.
[Nexus 9 Original Android Development] jhwbg:
Ok, well boot process stops there so no more information get logged.
[Nexus 9 Original Android Development] NYCHitman1:
At this point, it's clear that it's something weird going on with the few of you and your unit(s).

If I were you, I'd backup anything I have on my device and flash back to stock and then go through the motions over again. Somewhere along the way, you did something that is interfering with boot. I don't know if you're using FIRE-ICE kernel, which removes all se-contexts. However, what I mentioned above is what I would be doing if I were in your shoes.
[Nexus 9 Original Android Development] maelfilk:
Anyone has issues with music playback? When screen is off for a long time (like 15-20 minutes) the playback just stops (track progress bar is stuck, if i press play button nothing happens so i have to close and reopen player). Could it be some strange doze behaviour?

Yep, i think it's doze related, cause i was messing with its values and it seems to fine now that i returned everything to default.
[Nexus 9 Original Android Development] jhwbg:
I have tested this, full factory restore to Google stock 6.0.1 (MOB30M), booted up fine, then I flashed twrp 3.0.2.0.

I wiped

Dalvik / ART

System

Data

Cache

Installed official from 160610, and waited 20 min. unable to boot.

I wiped

Dalvik / ART

System

Data

Cache

Installed weekly from 160624, and waited 20 min. unable to boot.

I wiped

Dalvik / ART

System

Data

Cache

Installed weekly from 160603, success!
[Nexus 9 Original Android Development] NYCHitman1:
Don't have an explanation for you. It works (obviously) for myself and many others. I can only go based off of what I can reproduce, which this I cannot.
[Nexus 9 Original Android Development] jhwbg:
I understand, I am just trying to help. I am willing to test stuff if you or someone else get some ideas.
[Nexus 9 Original Android Development] jhwbg:
Kernel

I have managed to boot Official 160610 & Weekly 160624, I flashed DU, then ElementalX 4.14 kernel and last gapps.

I have no idea why this works. Anyone that can explain this for a beginner?
[Nexus 9 Original Android Development] volkerth:
Ok, after jhwbg's and 12pac's posts I tried it the same way: clean flashing DU latest weekly, then the EX kernel, then gapps.: Success!

Can someone explain, why that is working here with another kernel only? The last time I installed EX was on stock. With the DU 10.0 release I switched from stock, no custom kernel, only some low level tweaking (sound).
[Nexus 9 Original Android Development] 12paq:
I'll let the dev maintainers answer for sure, but my best *guess* is it has to do with the consistency needed with the ROM's kernel encryption or SELinux status and your device's existing encryption or SELinux status. I have had this issue before, but I have no idea how these kernels are compiled and why (or if) a custom kernel would help it boot. Curious, because Fire/Ice (which I use) and ElementalX are both different in this regard.

Again, just speculation here.
[Nexus 9 Original Android Development] volkerth:
For anyone who wants to try: Dirty flash worked also for me. Restored my backed-up weekly 06.03 installation, dirty flashed DU weekly 06.24, then ElementalX, then TR Gapps. Booting, no FCs, no errors.
[Nexus 9 Original Android Development] uzi2:
This suggests that the issue lies with any changes made to the kernel after 0603, (which was the last build before the June security update).

It is strange that it is only affecting some devices and not others, but at least the devs have a definite pointer as to where the problem lies.
[Nexus 9 Original Android Development] NYCHitman1:
I have no control over why it works for some and not others. It doesn't make sense from a logical standpoint. It either should not work across the board or should work across the board. For reasons unknown, it works for some (myself included, as I've indicated numerous times previously) and others not. I have a few dedicated people that I can rely on for testing and none of them have issues.

I don't have much spare time, but when some time does become available -- I'll rebuild the kernel from scratch again.

EDIT: If any of you are interested -- shoot me a PM and I'll send you a boot.img when it's ready.
[Nexus 9 Original Android Development] uzi2:
It is very frustrating when you cannot reproduce the issue and equally frustrating for those that cannot fix it.

I'm not sure you need to rebuild the kernel from scratch as the kernel in build 0603 appears to have no issues for anyone.
[Nexus 9 Original Android Development] NYCHitman1:
It doesn't take long to rebuild the kernel -- I know it sounds like some long winded event, but it won't take more than 20 minutes to get all the ducks in a row and then test.

Previous offer still stands for those of you experiencing problems.
[Nexus 9 Original Android Development] uzi2:
I have now successfully updated from 0603 to 0624 by using the boot image from 0603.

The issue must be a change to the kernel since 0603
[Nexus 9 Original Android Development] NYCHitman1:
See my previous post #1236.
[Nexus 9 Original Android Development] uzi2:
Yes, I've read you're post and the edit.

I'm more than happy to test any kernel you produce.

I was only suggesting that a review of commits to the kernel since 0603 is more likely to strike gold than a rebuild from scratch.

And, of course, the superSU script, which alters the kernel.
[Nexus 9 Original Android Development] NYCHitman1:
In retrospect, I think I may have an idea as to what is going on here :)

Stay tuned! :highfive:
[Nexus 9 Original Android Development] NYCHitman1:
For those of you that PM'd me -- check your Inbox. Follow the instructions I provided :)

Fingers crossed!
[Nexus 9 Original Android Development] NYCHitman1:
If you folks don't mind -- http://goo.gl/forms/v73Arer2GrX9uax83

I've discovered that this is an issue of encryption vs decryption.
[Nexus 9 Original Android Development] NYCHitman1:
The issue has been resolved and merged into source upstream.
[Nexus 9 Original Android Development] ZeroSkylineX:
Thank you, I'm happy that you listened to your fans and did the right thing. If I can make a suggestion for next time, please take your criticisms a bit more lightly. Just because there's something wrong with the boot process, does not always mean it's a user issue. For a while, you neglected to acknowledge it was an issue with the ROM and that it was a user issue because we didn't "read".

I'd understand if it works for you but a vast majority here indicated that it was stuck on a bootloop. Us posting here serves two purposes. It's to inform you, the developer and other users from falling into the same fate. Judging from the posts alone, more users had issues than a successful boot. Also considering it's a categorized as a stable rom, we have higher expectations of less bugs and issues.

Myself personally, I ONLY download and install Stables so I did not expect a Stable rom to boot loop. I'm glad that you finally investigated the matter further after hearing the concerns from various members but I felt that you should've looked into it much earlier instead of neglecting it. It was not looked into until it was already late June/early July, which was on schedule for the 10.4 release. I was originally just going to skip 10.3 as a whole, but I will try it out anyway now that you provided a fix. Other than that man, keep up the good work and I appreciate all that you do. I have DU installed on all my devices and couldn't be happier.
[Nexus 9 Original Android Development] uzi2:
My experience suggests that there is still an issue with the kernel or superSU script introduced after 0603.

I have attempted to update from 0624(0603 kernel) to 0702 and am unable to boot.

Restoring the boot.img (0603) from my backup solves the problem.

I will try a clean install later...

Clean install will not boot.

Problem not yet solved unless the reversions somehow didn't make it into the 0702 build
[Nexus 9 Original Android Development] NYCHitman1:
The fix didn't make it into the weekly yesterday.