yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] chairshot215:
Honestly have been meaning but have not tried MultiROM. Looked over at the thread and see allot of mention about the boot.img and modifications. If I had to guess with the limited knowledge I have would say if not working is not so much the Kernel but the boot.img in the same way that both the Stock / AOSP zips posted are the same exact Kernel inside but changes made to files like the init.rc inside the 5.1.0 boot.img that creates the file system and sets permissions among a score of other things caused 5.1.0 from booting properly after updating and flashing the boot.img. As developers we use the name Kernel but there is much more inside than the actual Kernel. In some cases can be more than a dozen other scripts and other files inside. Will need to try and learn a bit about MultiROM. Out of curiosity was it Stock or CM giving you issues?

Little more reading and looks like not everyone including CM has updated to include new bootloader version checks to include new bootloader from the 5..1.0 update. So for example I needed to change the bootloader version in CM source or nightly builds will not flash in TWRP without errors.

Maybe an update on this if flashing CM version, seems latest CM12 is receiving errors flashing with some recovery versions and must be installed via adb / fastboot. Article was not specific on the reason but may be the cause.
[Nexus 5 Android Development] chairshot215:
Added updates to version 3.4.42 for both 5.1.0 and under. The 5.0.2 zip should work for all stock and AOSP Roms from 5.0 - 5.0.2. Because of changes in 5.1.0 boot.img 5.1.0 will not boot when used with a lower Android Version.

Slightly disappointed as today had planned on posting full Starship Rom but now updating for 5.1.0 so maybe another week maybe two
[Nexus 5 Android Development] russian392:
So any details on what this kernel does? Or is our just close to stock?
[Nexus 5 Android Development] chairshot215:
CM12 Kernel is on hold until 5.1.0 version update. No reason testing anything new until can confirm everything will still work next week. Also figures the same week I had planned on posting the full Starship Rom the 5.1.0 update hit so now am back in testing optimizing phase for a bit longer.
[Nexus 5 Android Development] chairshot215:
3.30.2015 update

Linux version has been updated to version 3.4.55

All MR1 changes added to the 5.1.0 AOSP Kernel have been merged into the Kernel

https://github.com/Starship-Android...mmit/8ed8c47ff15f1c5fdd6707f7a52f76110aed6cbf

4.6.2015 update

Not much on the AOSP/Stock side. Wanted to post a cm12 update so decided to post the AOSP/Stock kernel earlier than I would normally with a few Linux version update patches. With that said updating the Kernel only takes a minute or so and not like asking to flash a new Rom. Kernels are easy and these days faster to flash than g-apps. Also used the 5.1.0_r3 source to compile the boot image for 5.1 instead of 5.1.0_r1 source I had been using. Honestly though did not check if anything changed that is packed into the boot.img along with the Kernel between r1 & r3 so may or may not make any difference what so ever.
[Nexus 5 Android Development] chairshot215:
Forgot, marked the cm-12.1 kernel as beta just because cm-12.1 is pretty much beta. Otherwise the Starship 12.1 Kernel is the Starship CM12 Kernel merged with the Cyanogen 12.1 Kernel . Not that the two had been far apart to start but the 12.1 CM Kernel merged into the Starship cm12 kernel clean as a whistle with 0 conflicts. Was pretty happy about that so going foreword will just be working on the 12.1 Kernel with the Starship cm-12 Kernel soon going the way of the 5.0 - 5.0.2 Stock/AOSP Starship Kernels.

Now finally since the actual Starship Rom I have been working on since the darn preview release ending as mostly caf based with CM-12.1 coming together can start updating from 5.0.2 into 5.1 as had just finished going over the first draft and was about to post when the 5.1 update hit. Otherwise wanted to post the first draft and then go over the entire Rom a second time looking over the theme images, features and optimizations with a magnifying glass.
[Nexus 5 Android Development] chairshot215:
Have updated both Stock / AOSP and cm-12.1 Kernels up to Linux 3.4.65 with a few other additions and weeding. Has and been running pretty sweet on both so far.

Stock / AOSP 3.4.65 Kernel boot.img has been compiled using the 5.1.1 AOSP Source and tested on both 5.1.0 & 5.1.1 with no issue and as mentioned above running pretty sweet.
[Nexus 5 Android Development] B@RRY78:
I cant install on aicp 5.1.1
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
Very weird behaviour:

1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).

2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.

3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.

Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(

Tried "fastboot erase cache" as well...

Any ideas?
[Nexus 4 Q&A, Help & Troubleshooting] C4SCA:
u flashed stock doing fastboot -w update?
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?

What you mean "-w update" is that a parameter for the fastboot flash command?
[Nexus 4 Q&A, Help & Troubleshooting] greg17477:
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://xdaforums.com/nexus-4/help/qhsusbdload-problem-t2253874

cheers
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
Had it charging for hours before flashing, so battery cant be the problem..

But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.

Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird
[Nexus 4 Q&A, Help & Troubleshooting] C4SCA:
dont do fastboot erase cache. Do fastboot format cache.

reinstall the correct google usb drivers manually (http://xdaforums.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)

try to flash 4.2.2 and see if it boots up using the flash all bat.

that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..

Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...

Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh
[Nexus 4 Q&A, Help & Troubleshooting] halloga:
I had the same issue and this worked for me

https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.

In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.

So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
[Nexus 4 Q&A, Help & Troubleshooting] halloga:
I know this situation man, I spent many hours too and finally solution came out that simple :) Hope you solve it soon :)
[Nexus 4 Q&A, Help & Troubleshooting] zroice:
well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.

This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.

When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.

So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...

Must be bootloader or hardware issue im quite sure..
[Galaxy S 5 Q&A, Help & Troubleshooting] XDA Visitor:
It was fine until first charge. Yellow bands also appear when it is charging with power off. I have sent it back to shop but very interested in any suggestions!
[Galaxy S 5 Q&A, Help & Troubleshooting] K_Bag:
Thanks - How do I find this thread ? Can't seem to find it in the S5 forum page...
[Galaxy Note 3 Q&A, Help & Troubleshooting] soo55:
hello,

I'm not able to root my n900 under the last firmware 4.4.2 using "CF-Auto-Root-ha3g-ha3gxx-smn900" ! Odin3 gives me a message "Failed" in red, and my n900 blocked, I was obliged to update the firmware with Odin3 to unblock it!

any idea ? is CF-Auto-Root-ha3g-ha3gxx-smn900 working with the last firmware 4.4.2 ?

thanks in advance.

soo
[Galaxy Note 3 Q&A, Help & Troubleshooting] cousinit99:
Wrong forum there slick..

Try Galaxy Note 3 Q&A, Help & Troubleshooting
[Galaxy Note 3 Q&A, Help & Troubleshooting] soo55:
ok thanks; I'll do that ...
[Galaxy Note 3 Q&A, Help & Troubleshooting] plazaman91:
Is it the international or a carrier specific?

Try this link see if it helps:

http://xdaforums.com/showthread.php?t=2466423
[Nexus 9 Android Development] deadman96385:
Info

First of all i would like to state i do not own this device so i rely on testers.

This build does boot with the included prebuilt kernel but i would recommend flashing USBHost's fire and ice kernel

Caf Based
[Nexus 9 Android Development] deadman96385:
Bugs

V4A does not install the driver for now

Contacts has white on white issues Fixed

Ambient display does not work Fixed

Vibrate on touch does not work Fixed

Initial camera launch may fc but 2nd time will be fine
[Nexus 9 Android Development] vboyz103:
Awesome...been waiting for a feature-filled 5.0.2. Will try now
[Nexus 9 Android Development] buffal0b1ll:
Booted just fine with Fire-Ice kernel and 64bit ARM Gapps from lollipopolooza thread (took about 10 minutes to get to welcome screen so be patient).

It's snappy and solid. Only issues I could find are listed in post 3.

Edit: contacts, vibrate on touch, and ambient fixed in 1/9 build
[Nexus 9 Android Development] vboyz103:
Flash went fine with TWRP 2.8.3 recovery. However, upon booting I got System UI force closing maybe because I have encryption forced?

I flashed both stock and fauxkernel and gapps in other rom but no go. System UI fc'ing loop prevented me to enter my passcode to decrypt the /data partition.
[Nexus 9 Android Development] USBhost:
Cheers another new ROM!
[Nexus 9 Android Development] EverythingPortable:
Nice. I'll test the rom later today = )
[Nexus 9 Android Development] JustusIV:
I use this on my N6 and love every minute of it....
[Nexus 9 Android Development] buffal0b1ll:
I found a workaround for the white on white Contacts problem.

Download https://www.androidfilehost.com/?fid=95832962473400203 and extract the Contacts.apk.

Rename existing system/priv-app/Contacts.apk to Contacts.bak and inject the one above, set perms to rw-r-r and reboot.

---------- Post added at 11:00 AM ---------- Previous post was at 10:47 AM ----------

OP #2 recommends Fire-Ice kernel

That's what I used and things are up and running decrypted with no UI FC's.
[Nexus 9 Android Development] TenderloinShadow:
Hey, love that some of the big time AOSP ROMs are making it to this device.

What is the battery life like on this ROM? At stock, I can get a good 4-5 hours of battery life with heavy use (web browsing, gaming, etc).

Also, weird off topic question, which model of the N9 is flounder, and which is volantis? I have the 32gb wi-fi only version, which is it?
[Nexus 9 Android Development] USBhost:
Ok i know this is odd

flounder / volantis = wifi only

flounderlte? / volantisg = LTE
[Nexus 9 Android Development] TenderloinShadow:
thanks. my big question is do I have a founder or a volantis? since they're both the wifi only model, does it matter? if I have a volantis and flash this flounder rom, will it cause me problems?

i have the 32gb wifi only version in black, and it was one of the first models released, if that helps.
[Nexus 9 Android Development] USBhost:
There all the same

So flounder is volantis

likewise

volantis is flounder
[Nexus 9 Android Development] buffal0b1ll:
Battery - too early to tell. ROM just came out. But if it helps: I had about 95% yesterday when I flashed LS, had about 3 hours of SoT and casted to Chromecast for a few hours and still had 30% left this morning

Flounder/Volantis - short answer. They are the same thing. They are both names for the wifi only version. volantis is the google factory image name, flounder is the rom dev's name
[Nexus 9 Android Development] xtcdk:
Love it

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] Ishwara Sandesh C M:
Nice rom.. :thumbup: :)
[Nexus 9 Android Development] tyvar1:
Awesome with more Roms for this great device! :D
[Nexus 9 Android Development] jlokos:
Thanks for the find on the contacts.apk. It works great. I used the fire & ice kernel also; Except for other items shown in post 3, everything is working. Great job op and LS team.
[Nexus 9 Android Development] gregulator:
I also had the same issue. I've gone back to stock, rerooted, and it still came back. I'm going to try swapping out all of the variables, kernel, gapps etc. and will report back.
[Nexus 9 Android Development] EverythingPortable:
Here is a video running the ROM:

https://www.youtube.com/watch?v=xrCXCuhKShw
[Nexus 9 Android Development] oediv:
can this run on the lte version?
[Nexus 9 Android Development] buffal0b1ll:
New 1/9 build is up

Change log:

[ ] Contacts fixed: Stock contacts reverted, now it's black on white

[ ] Ambient display fixed

[ ] Vibrate on touch working

[ ] Liquid optimizations

[ ] Thyrus dark material settings, framework

[ ] Faster erase/flash times

[ ] mac permissions for google apps.
[Nexus 9 Android Development] jlokos:
Thanks for the heads up. Although contacts are fixed. They don't seem to display horizontal, only vertical. Everything else is humming. It's good to see our device well supported.
[Nexus 9 Android Development] buffal0b1ll:
True dat. I noticed that contacts don't rotate landscape on AICP either. Maybe an upstream thing?
[Nexus 9 Android Development] USBhost:
right now no
[Nexus 9 Android Development] buffal0b1ll:
Follow post 11 directions to fix contacts so they are rotating landscape and match dark material settings and framework.
[Nexus 9 Android Development] ayysir:
I got a AOSPA build to work on LTE not sure for LS
[Nexus 9 Android Development] USBhost:
True

Did not think of that
[Nexus 9 Android Development] phillysmako:
Hey guys I may need a little help, I flashed the 1-9 update clean install I flashed ROM gapps then su then rebooted and it booted but kept getting system ui force close and the first screen said please wait while your tablet is encrypted and it had a timer so so I rebooted to boot loader and flashed the fire and ice kernel img via fastboot and still wouldn't boot I hopped into recovery and all my data is gone I tried wiping cache and dalvik but it failed and said unable to munt storage. Any ideas why this happened and how I can fix it ? I flashed the 64 bit gapps from Lollapalooza and I came from the stock rooted ROM
[Nexus 9 Android Development] USBhost:
When fire-ice did not boot

Can you do an adb logcat
[Nexus 9 Android Development] phillysmako:
well I tried I different boot.IMG that is decrypted after it didn't boot with fire and ice. Its still not booting I'm downloading the factory img right now just in case. Do you want me to try and flash your kernel again and try to get an log cat? I can:)

Edit: it booted but I keep getting setup wizard force close. Won't get past it its just a black screen. Do you think flashing fire and ice kernel will fix that issue? I know it's a long shot but I'm just thinking of different ideas. Also is there anyway to wipe the tablet in recovery without erasing the os? Like just wipe system and then reboot and not lose my os, if that makes sense. I only ask this cause if I wipe and it erases my os I don't have anything to flash cause my internal storage got wiped.
[Nexus 9 Android Development] USBhost:
Yes pls I would like to know what happened
[Nexus 9 Android Development] phillysmako:
Check my edit post. It booted but not good.
[Nexus 9 Android Development] USBhost:
Can you try with file ice

Also about the system

You can't wipe system and keep the os

You can use mtp in recovery

To move files to internal storage
[Nexus 9 Android Development] phillysmako:
I flashed the test.6 img and formatted cache via fast boot in going to wait again to see if it boots and if it don't I'll run a logcat, although i don't know how I'll send it to you cause I won't be able to get it off the tablet cause I'm probably going to have to flash the factory IMG. To get it booted again.
[Nexus 9 Android Development] USBhost:
You need to format cache to f2fs or it won't boot

Just use adb to get the logcat

Edit: what recovery are you using
[Nexus 9 Android Development] phillysmako:
I'm using the regular twrp the latest one. And I just formated the cache to f2fs so we'll see

Should I try using your nodded version?
[Nexus 9 Android Development] USBhost:
KK
[Nexus 9 Android Development] phillysmako:
I think formatting the Cashto f2fs fixed it:D. Its android is upgrading. That's the farthest I've gotten yet so we'll see thank you man!!
[Nexus 9 Android Development] USBhost:
Cheers!! :fingers-crossed::laugh::good:
[Nexus 9 Android Development] phillysmako:
it worked :):):):) thank you again!

Edit: quick question it's a easy one I promise, what do you suggest to use for performance for the CPU quiet power management? Userspace balanced or runnable?
[Nexus 9 Android Development] USBhost:
Well on balanced

Somtimes the screen won't turn on every so often

I have not tested runnable

But going by the definition

Runnable is for performance
[Nexus 9 Android Development] xtcdk:
Delete
[Nexus 9 Android Development] badwiring:
I had a rough time with the install, the same fc's, not being able to decrypt. Even restoring a backup didn't do it. I'd post how I got around it but I didn't know what I was doing and probably shouldn't have been doing it.

I don't think it's anything to do with LS, just the state I was in before flashing and my ignorance. This was going to happen no matter what.

Having gotten past that, it's awesome. I prefer a dark UI. Stock Lollipop does look very nice, but I'd rather not have all the bright cheerful colors forced on me. (But I loved AICP's blinding bright boot animation.) Battery life has been great. I've used LS on a number of devices and it's been teriffic. (Clock app force closes so I just installed another one.)
[Nexus 9 Android Development] jlokos:
That's what i did on the first. I didn't think it was necessary on the 1/9 build, but I'll do it again. I didn't notice contacts on the AICP build.
[Nexus 9 Android Development] Saschwatch:
Upon trying to flash I get an error saying that this file is meant for flounder and my device is a volantis. I know these are the same thing, so I wonder why the error.
[Nexus 9 Android Development] USBhost:
Flash twrp 2.8.3.0
[Nexus 9 Android Development] virajxp1:
hey guys getting this problem when trying to flash(i know im a noob) can anyone help? (says error executing updater binary)
[Nexus 9 Android Development] bamfsig45:
Re download the ROM, happened to me first time.
[Nexus 9 Android Development] Rjporter:
decrypted?

Do I need to decrypt my tab so this ROM will work? I can't boot with my password after a clean install.
[Nexus 9 Android Development] mrshades812:
I have a request. :)

Can someone give the rundown on the steps needed to decrypt and get this rom flashed? I understand most of it, including the cache format, but some of it is confusing when it comes to decrypting and the boot image flashing steps. It would help a lot of people out and more of us would be running this ROM right now, if it wasn't such a chore. =/

Thanks!
[Nexus 9 Android Development] El Nino1977:
Its not necessary to decrypt the device to flash the ROM, I'm running it fine being encrypted.

But you just have to flash a decrypted kernel and completely wipe device (back up SD storage off before hand) in recovery before flashing the rom and gapps.
[Nexus 9 Android Development] MrPhilo:
If I flash this ROM with F2FS Cache and Data, will I still be on F2FS? Just the System will be on EXT4?

Or does anyone know how to change the script for F2FS?
[Nexus 9 Android Development] Megaflop666:
Anyone else having problems flashing other kernels with this ROM? I have tried Elemental X, and Faux Kernel and both go into a 20+ minute bootloop.

I have attempted to run adb logcat during the boot up and boot loop but terminal just stays at - waiting for device - for several minutes and then gives me the "Unable to open MTP device '[usb:001,019]'.
[Nexus 9 Android Development] upNsmokeAllDay:
Its because SElinux is disabled in this Rom.

Fire and Ice kernel seems to work fine with it.
[Nexus 9 Android Development] kalel90:
So I can only assume i'm an idiot at this point because I cannot get encryption to disable no matter what i do. I've flashed fire and ice kernel. I factory reset. This doesnt work. Ideas?
[Nexus 9 Android Development] buffal0b1ll:
Move all your sdcard card stuff you don't want to loose to PC.

Download ROM, 64bit ARM Gapps, and FireIce on your PC.

In recovery, Advanced Wipe everything (cache, system, data, dalvik, internal storage).

In recovery, connect USB to PC and go to Mount and Enable MTP.

Copy ROM, Gapps, and FireIce to sdcard.

Flash rom, gapps, and FireIce.

Boot to system.

You should be decrypted when you go to Settings Security now.

Move whatever you want from your PC/sdcard backup back to device over MTP USB.
[Nexus 9 Android Development] Megaflop666:
Fire and ice is working well. What are the 64 bit gapps? I've been using pa gapps full modular gapps with it.
[Nexus 9 Android Development] kalel90:
I wiped everything. I then flashed rom/gapps/fireice in that order. It booted up and still shows as encrypted. Ideas?
[Nexus 9 Android Development] buffal0b1ll:
If those Gapps work, great. 64 bit are in lollipopolooza thread

---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------

I flash rom kernel then Gapps. Not sure if that makes a difference.