yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] cheep5k8:
NRD90M

xceed v8.02 built from NRD90M sources is UP!!

Download here: https://dl.srvr.tech/ryu/xceed/NRD90M/
[Pixel C Android Development] Bless1:
If I'm on the official N build rooted I can just flash this in recovery? Sorry for the noob question just making sure
[Pixel C Android Development] cheep5k8:
Actually it's like a boot.img which you need to flash using fastboot. Also make sure to re-install SuperSU afterwards (in TWRP) as it's the stock ramdisk, unmodified, and does not contain any changes neccessary for root.

Some people have requested a flashable ZIP... I'll try to make one when I get around to it :)

EDIT: Forgot that TWRP 3 allows flashing of boot images, so yeah, that should work.
[Pixel C Android Development] Alxoom33:
Worked just fine with TWRP dragon 3.0.2-21. Thank you!
[Pixel C Android Development] Paulskiii:
will this allow me to access exFAT via OTG?
[Pixel C Android Development] Bless1:
In recovery were should I flash this kernel to? System or boot IMG? Just would like to make sure seeing how the pixel-c is different
[Pixel C Android Development] cheep5k8:
Boot.

If you flash this to system you'll have to reinstall a factory image again :p
[Pixel C Android Development] r_nation:
I apologize in advance, can somebody please tell me the correct procedure to upgrading to N coming from latest August OTA(L), xceed ..tried the way via flash vendor,flash system,flash boot xceed. Couldn't get past Google bootup so had to relash August OTA w/ xceed, I appreciate any help
[Pixel C Android Development] cheep5k8:
Here's how I did it:

- boot into bootloader

- flash vendor

- flash system

- flash latest xceed (v8.02-NRD90M)

- flash new bootloader

- boot straight into TWRP (in fastboot, press and hold power+vol up, wait, then select boot into Android recovery)

- flash latest SuperSU

- reboot system

That worked for me. After installing SuperSU, the tablet will reboot once at the Google logo, but should work fine after that (it did for me after exactly following the above steps)
[Pixel C Android Development] penguinyaro:
What about coming from stock (NRD90M) including stock recovery?

I was running xceed on Marshmallow, but upgraded to N via flashing the factory image. In the process, TWRP somehow got lost and I was left with no recovery (not even stock, I didn't flash it). This was prior to your release of the latest kernel. When I saw this new kernel, I decided to try it out. I flashed your kernel, then TWRP, but when I booted into recovery, the internal storage wasn't mounting (listed as 0MB). Furhtermore, I was unable to boot into the system. I kept getting shot back into recovery. I tried a number of things including reflashing everything according to your steps, just flashing the stock kernel, etc. However, the only way I was able to recover was flash all the stock images (vendor -> system -> boot -> recovery; didn't flash the bootloaded again, I figured I had done that enough). I am not a little lost at what I should do.
[Pixel C Android Development] r_nation:
Thank you Mr.Cheep5k8. I think you meant power+volume down in fastboot tho. Did your above method exactly but after Google logo pixel kept booting into twrp, I then went back to fastboot, fastboot reboot and booted into N! Thanks again sir REALLY appreciate your help.
[Pixel C Android Development] shattered519:
I arrived at this thread because of claims that the xceed kernel, in multiple instances, solved the ubiquitous wifi issues that owners are having (the network dropping issue seems to be solved on the consumer nougat release). Can anybody familiar with the history of this thread confirm or deny this to be true? Whether I attempt to utilize this kernel depends solely on whether this is a viable fix for the debilitating wifi issues I am facing. Thanks in advance!
[Pixel C Android Development] Bless1:
So I recovery flashed the kernel to the boot and got into a boot loop that keep sending me into recovery i'm on the newest TWRP 3.0.2-21 and that's the first time that's ever happen to me. So I thought I might of had a bad download so after re-flashing back to stock and rooting again I tried once more and got the boot loop again what gives any ideas
[Pixel C Android Development] whoamigriffiths:
Did you flash supersu after flashing the kernel?
[Pixel C Android Development] r_nation:
I can definitely confirm at least on marsh with latest xceed I have no issues in regards to wifi connectivitity or ANYTHING ELSE. The other night I literally played blitz brigade(server sided) for 4 hours which speaks on a higher levelthan just connectivity. I'm actually going back to marsh incriminating figure out correct method.

---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------

-when I know correct procedure-
[Pixel C Android Development] shattered519:
That's certainly good news. However, did you have any issues with your wifi connectivity before you flashed xceed? Also, I made the (perhaps ill informed) decision to proceed with the August OTA, is the kernel compatible with the consumer nougat release, or am I going to have to flash an earlier stock image to get this to work? Thanks again!
[Pixel C Android Development] r_nation:
I literally rooted my pixel straight out of the box, I cannot speak on the wifi issues prior xceed. I can tell you I don't have any wifi issues, I highly recommend xceed..if your going to N the kernel is in OP xceed-v8.02-NRD90M.img
[Pixel C Android Development] Bless1:
Ok so I recovery flashed the kernel successfully and booted up after trying one more time. Don't know what the issue was before but all good now. Any suggestions on tweaks for this kernel?
[Pixel C Android Development] Alxoom33:
I never had these so called "Wifi issues" so I'm not sure what you are talking about. If you have a defective tablet, you should return it and get one that works correctly.
[Pixel C Android Development] shattered519:
To be sure, your Pixel C gets the same network speeds at a distance from your router with multiple walls in between as your other connected devices? Because if so that's very impressive indeed; I'd say 90% of the posts I've seen regarding Pixel C wifi performance are complaining that they get around 50%-60% of the network speeds of another device at a given distance from the router. My personal Pixel C's wifi performance degrades severely when used in another room, even when all my other devices show expectedly nominal network up/down speeds. From what others have been saying, RMAing this device doesn't help their situations, so I'm looking for a software fix instead; by most indications it's a software issue.
[Pixel C Android Development] Samt434:
Hi cheep5k8,

I'm working on porting xorg and weston on the pixel C, and for this i would need the sources of your lastest kernel.

I can't find it on your github (v 8.02)

Am i missing something ?! :)
[Pixel C Android Development] cheep5k8:
I'm really lazy with pushing :)

But to tell the truth, I really just checked out my latest branch (I think dragon-n-preview-4) and rebased it in git on the stock kernel branch. It rebased/applied completely clean without any need of manual intervention, so I just built it and voila :D
[Pixel C Android Development] Paulskiii:
I'll ask again, does this support exfat access via OTG? Thanks
[Pixel C Android Development] tim.malone:
Marshmallow

Love the kernel. I can't seem to find the marshmallow versions anymore. I've gone back to Android 6 because it performs better with some apps and I'd love to be running this kernel. Am I just missing the link?
[Pixel C Android Development] Samt434:
Thanks ! I will try this !
[Pixel C Android Development] a.f.x.:
Unfortunately, since I switched, I do get a random reboot about once a day (low usage).

I did set it up from scratch.

cheers

afc
[Pixel C Android Development] acrickie:
I just did a quick test, I have two USB drives, one formatted with NTFS and one with EXFAT.

Neither are recognised by my Pixel C which is running the Android N with this kernel, however if I open them with "Stickmount" they both work fine.

Hope that answers your question.
[Pixel C Android Development] EddieK23:
My Pixel C is saying there is an update, I'm not sure if I should install it and possibly overwrite the kernel or remove my root. Anyone know what I should do?
[Pixel C Android Development] Alxoom33:
What Android version are you on? NRD90R Android N 7.0 or something else?
[Pixel C Android Development] EddieK23:
I'm on NRD90M Android 7.0 with xceed's latest kernel.
[Pixel C Android Development] Reuben_skelz92:
Will this work on nrd90r?
[Pixel C Android Development] Alxoom33:
It's probability the R update[emoji6]

---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------

Yes, although made for the earlier version.
[Pixel C Android Development] EddieK23:
But would going from my NRD90M to NRD90R overwrite xceed's kernel is what I'm asking.
[Pixel C Android Development] Alxoom33:
Yes, of course it will. You will need to reflash the custom kernel after updating.
[Pixel C Android Development] drewski_1:
the incremental OTA from M->R will probably fail because of the custom kernel.

there are the full OTA files you can install from here https://developers.google.com/android/nexus/ota

re-rooting is easy. flash with SuperSU 2.78-SR1

iirc, even the Full OTA did not overwrite my TWRP . . . don't quote me on that . . . but it's easy to re-install too along with Xceed Kernel ;)
[Pixel C Android Development] Alxoom33:
Are you going to update your kernel based on the new 7.0 Android source?
[Pixel C Android Development] Reuben_skelz92:
Same question
[Pixel C Android Development] nigelhealy:
I guess apart from a little HTC 10 experience, the dev [MENTION=4867279]cheep5k8[/MENTION] has left the XDA building.

This is a bad feeling, the Pixel C sold in too few quantities to get enough dev / interest. It was the awkward bastard child with too much in-breeding.
[Pixel C Android Development] cheep5k8:
Not at all :)

I just didn't really get to the kernel again, but I haven't give up on it or anything of that kind.
[Pixel C Android Development] jeston:
Anybody check to see if this works with the 7.1.1 preview?
[Pixel C Android Development] Alxoom33:
It's too old, I would wait for an update.
[Pixel C Android Development] jeston:
Yeah, that's my plan so far. Was just hoping someone else was crazy enough to try it out :P

Hopefully [MENTION=4867279]cheep5k8[/MENTION] is able to find some time to update this for us!
[Pixel C Android Development] Alxoom33:
Nope, 7.1.1 running too well right now to break it with an old 7.0 beta version kernel. I'm sure it will be updated from Dragon sources in good time.
[Pixel C Android Development] jeston:
Here's hoping [MENTION=4867279]cheep5k8[/MENTION] shows back up to give us some goodness now that 7.1.1 final is out... Fingers crossed!
[Pixel C Android Development] cheep5k8:
Hey guys,

I just wanted to say I'm not dead, and neither is the xceed kernel project. There's just been a LOT going on, I couldn't even begin to explain if I wanted... anyhow, I'll be launching my own first paid app this weekend and hopefully I'll get around to rebuilding the kernel as well.. if not this weekend, then rather soonish either way.. it's been long overdue.

Thanks everyone for sticking around, you won't get disappointed by yet another dev simply leaving. Promise.
[Pixel C Android Development] jeston:
Glad to hear you're still with us! :good:
[Pixel C Android Development] fiver5:
Good to hear from you. I broke my Pixel digitizer this morning and instead of replacing am going over to the Samsung darkside for now so just wanted to say thanks for all the kernels. Will check back in on your app release but won't be back in these parts of the forums anymore. Take care man and good luck!
[Pixel C Android Development] je55ter:
So I've been running an old version of xceed kernel (March 8, 2016 build), and it crashes/freezes a lot. I was hoping to update to a more stable version but I'm still on Marshmallow. Don't want to update to Nougat until Xposed is supported. So is there a more stable version build for Android 6.01? And if so, where can I find it (my dns does not recognize dl.srvr.tech)?
[Pixel C Android Development] tdurhamjr:
URL for 8.02 Kernel download not working

Hey guys,

The url for the 8.xx kernel is not working. Is there another url that I can use?
[Pixel C Android Development] Avencore:
hey [MENTION=4867279]cheep5k8[/MENTION]. Missing your great kernel on Nougat since without your kernel the Wifi on this tablet is really bad. Hope you find the time to develop an update.

greetings Avencore
[Pixel C Android Development] michaave:
I'm really wanting to download this kernel, but the URL doesn't seem to work anymore. Are there any mirrors? Any new builds? My tablet keeps forcing encryption on me...
[Pixel C Android Development] Alxoom33:
Xceed has not been supported for a long time now. Kernel is not current.
[Pixel C Android Development] followmsi:
Have a look here ..

https://xdaforums.com/pixel-c/orig-development/lazyflasher-make-install-custom-kernels-t3537487

JUST WANT TO DISABLE VERITY/ENCRYPTION?

You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and*flash*it!

It's already set up to automatically disable verity and make encryption optional.

Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at:*https://build.nethunter.com/android-...y-opt-encrypt/

It should work on any and all kernels!
[Pixel C Android Development] drewski_1:
your last "no-verity-opt-encrypt" link is truncated so doesn't work
[Pixel C Android Development] followmsi:
It's just copy paste from the original link above ..

Here again the original XDA ..

https://xdaforums.com/pixel-c/orig-development/lazyflasher-make-install-custom-kernels-t3537487

There you find the full link ..

But here again as well ..

https://redirect.viglink.com/?forma...build.nethunter.com/android-...y-opt-encrypt/

Hope this one works .. ;)

Cheers
[Pixel C Android Development] drewski_1:
That redirect link didn't work either :( , but I got it from the XDA thread :good:

https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Pixel C Android Development] cheep5k8:
9.00

Hey guys,

xceed 9.00 based on Android 7.1.2 kernel is here! Find all info in the first post.

Cheers

EDIT:

Maybe a few words of explanation for why it took so long; I think I owe everyone an explanation lest everyone just stops using this kernel...

The main reason was that the guys running my previous build server simply cancelled it and everything on it was deleted; the most important stuff was safe on github, but the general setup and additional changes were only present on the build server. A lof of what makes your build setup work simply lies in the structure of everything set up, as surely everyone building kernels or AOSP knows, and that was all gone.

I was quite fussed off about that, and at the beginning didn't feel like getting back to make a new setup just then. Work was very time-consuming and stressful, and so it just lingered on. Even though I never abandoned the tablet in my heart, I just couldn't get around to create a new build setup, either because of time constraints or because I was still bummed about the original build server.

Then today I just kinda synced the AOSP source code and went from there...

I'm sincerely sorry that these personal circumstances led to this project, and all of you being abandoned for a year or so.

I now have an independent setup for the kernel on my Macbook and am in the process of backing everything up onto github so that a restart from scratch, should it be neccessary, should become mostly painless.

Maybe the one or other Pixel C owner still finds this project useful. I personally would be very grateful, and happy about someone cherishing my work!

That said, whatever the ROM or kernel of your choice, we're all Pixel C users, and even though this tablet has been mostly abandoned by Google when it wasn't supported that well from the start, we're going to keep it alive for a long time to come. I am sure.
[Pixel C Android Development] drewski_1:
woah, blast from the past. welcome back!
[Pixel C Android Development] st0nec01d:
Glad to finally try out this kernel, only got the Pixel C a few months ago so my first time using the kernel. Working nicely indeed. :D
[Pixel C Android Development] tim.malone:
Just flashed the latest. Working great so far. Thanks!
[Pixel C Android Development] hagbardceline23:
is cifs support still in ?
[Pixel C Android Development] je55ter:
So, I assume I shouldn't flash this on a 6.0 rom. Any chance of getting a download for the last stable 6.0 based build? I don't want to upgrade until Xposed sports nougat.
[Pixel C Android Development] Alxoom33:
Thank you for your great work! I'm a bit concerned about flashing with dm-verity disabled. Dosen't that pose a serious security risk?
[Pixel C Android Development] cheep5k8:
Good point. It should be, unless while rebasing the config option for this has been deleted/reset in dragon_defconfig. I'm going to check for this and other possibly lost config options and upload a 9.01 build today.
[Pixel C Android Development] cheep5k8:
This is the last Marshmallow build I still have backed up on my GDrive:

xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g.img

https://drive.google.com/open?id=0B9fx05P4rFbiZjFfSmE1TkR3Tnc

I hope it works with MXC89* builds, because setting up the environment to make Marshmallow builds would be a pain in the butt at this time :eek:
[Pixel C Android Development] cheep5k8:
Well, in theory it makes tampering with your device potentially unnoticeable. Someone could grab your tablet, modify /system, return the tablet and you wouldn't know.

That said, flashing SuperSU also disables dm-verity, as do many other custom kernels (also for other devices, I mean), so this is not a super-special-case.
[Pixel C Android Development] drewski_1:
Super SU removes it too, I believe

Edit: what he said ^^^^^^
[Pixel C Android Development] cheep5k8:
Hey guys,

Just letting you know that my filehost dev account has been approved. You can now find the kernel downloads here:

https://www.androidfilehost.com/?w=files&flid=172974

As for 9.01, I only came home, I'm going to build a 9.01 with all previous options enabled (CIFS, etc.) It will take a couple of hours until I can get it done though (but not a year!)
[Pixel C Android Development] Alxoom33:
Thank you both![emoji3] Learn something new every day!
[Pixel C Android Development] cheep5k8:
Hey,

9.01 is up (on androidfilehost, please see first post). I've re-enabled CIFS and a few other useful options. Because of this the kernel image is a bit larger than 9.00, so don't be alarmed!

Cheers
[Pixel C Android Development] cheep5k8:
Aaaaaaaaaaannnnnnnd 9.02 is up (I had an option enabled that led to reboots in 9.01. Should be safe now.)
[Pixel C Android Development] Alxoom33:
Thanks, I'll give it a try!

Edit: Working great! Do you have recommended settings, or settings that you like for your Pixel C. Cpu, Governer, etc...?

Thanks.
[Pixel C Android Development] NYCHitman1:
Any plans to update the kernel source?
[Pixel C Android Development] Alxoom33:
I had to revert to my standby kernel, since 9.02 caused random reeboots in my Pixel C running 7.1.2 stock April update.
[Pixel C Android Development] st0nec01d:
Having the same problem here.
[Pixel C Android Development] cheep5k8:
Okay, first of all thanks for the feedback.

I made some changes to the kernel timing config that apparently don't work out with the Pixel C. If you can live without CIFS then I recommend you stay with 9.00. Save for CIFS (and the reboots...) nothing is really new in .01/02.

I will remove the .01/02 downloads for the time being so everyone else is spared the reboots (and again my apologies to everyone who had already installed .01/02)
[Pixel C Android Development] Alxoom33:
Thank you for all of your hard work and insights. But, what does CIFS do, or how is it be used in the context of our Pixel C?
[Pixel C Android Development] oRAirwolf:
Well if nobody else steps up, there is an unmolested pixel c that I am happy to root and do whatever with. I will take it to work with me just in case.
[Pixel C Android Development] DaConcho:
Mine is unlocked already. Just need to flash twrp and the boot image as soon as I get home. What do I need to do to get the dump of the NVRAM?
[Pixel C Android Development] cheep5k8:
A ZIP with some libraries and a few tools. They need to be in specific locations (I was doing this all in /vendor).

If you boot into TWRP and do it from an adb shell in TWRP, that's fine, but you'll need to create a /vendor directory and do it all in there (just then don't mount the real vendor).

I'm preparing everything right now, I'll make another post when it's done.
[Pixel C Android Development] DaConcho:
Sounds good. I won't be home for maybe ~3 hours but I'll do it as quickly as I can.
[Pixel C Android Development] cheep5k8:
[MENTION=6170032]DaConcho[/MENTION]

OK so here's the TAR file.. I made it a tar archive instead of ZIP because it preserves permissions. It includes all libraries and binaries for this to run. Don't worry, TWRP has tar installed to unpack this.

tpm.tar

Basically, you boot into TWRP and then copy the tpm.tar file over to the sdcard (or anywhere else applicable).

Then you "adb shell" into TWRP, when there, you create a directory /vendor, go INTO the directory and then unpack tpm.tar. Make sure /vendor isn't already mounted (although it would, actually, not be a real problem, since this overwrites nothing and vendor isn't as protected as /system).

Depending on which version of tar TWRP has installed you need to either run "tar xf path/to/tpm.tar" or "tar -x -f path/to/tpm.tar", one of them should work.

Once you get this working, you need to go into /vendor/bin/tpm, and there run tcsd. Simply run "./tcsd". Make sure it runs: there should be now a file /vendor/run/tcsd.socket, if it's not there, you'll need to get back to me (BTW it might be useful if we communicated via Hangouts or something? If that's OK for you.)

So assuming the tcsd runs, go into (or make sure you are in) /vendor/bin/tpm, then, for a test, run:

./tpm_version

The output should be:

WARNING: linker: ./tpm_version: unused DT entry: type 0xf arg 0x463
WARNING: linker: /vendor/lib64/libtspi.so.1: unused DT entry: type 0xf arg 0x138c3
TPM 1.2 Version Info:
Chip Version: 1.2.133.32
Spec Level: 2
Errata Revision: 3
TPM Vendor ID: IFX
Vendor Specific data: 85200050 0074706d 3439ffff ff
TPM Version: 01010000
Manufacturer Info: 49465800

The WARNINGs are really irrelevant, they're about the libraries in the tar file but they're meaningless for our purposes.

If you get THIS far, please post or contact me otherwise, since then we can start with the actual procedure!
[Pixel C Android Development] cheep5k8:
OK.. that'll get a bit late for me, USUALLY, but this has priority so I'll be here (I get notifications about posts via email so I'll be quick to respond).
[Pixel C Android Development] cheep5k8:
Just for reference, if anyone else also wants to try, these are the commands you need to run for the relevant info. Just make sure you ever, ONLY run tpm_nvread and NEVER by accident tpm_nvwrite or any other tpm_nv* command!!!!

Make sure you NEVER run 'tpm_nvrelease' by accident instead of 'tpm_nvread'. Best is if you delete 'tpm_nvrelease' right away since we will not ever need it.

So this is it. I will paste my output for reference. These are the NVRAM blocks where I SUSPECT that the relevant flag is set:

./tpm_nvread -i 268435457 -s 20

00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000010 00 00 00 00

./tpm_nvread -i 4103 -s 10

00000000 02 03 01 00 01 00 00 00 00 7a z

./tpm_nvread -i 4104 -s 13

00000000 02 4c 57 52 47 01 00 01 00 00 00 00 55 LWRG U

The flag we need should be in one of these areas. Many values might differ from my Pixel C to anyone elses, so this might not be too easy, but like I'm always saying, let's take it a step at a time :)