yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] charesa39:
Okay. So I was able to run that command on my Windows PC using Cygwin. I have succcessfully unpacked it. Do you only modify the fstab file in the ramdisk folder? It looks like the only change in your modded boot compared to the stock boot is you removed the ",verify" after "wait" in the system and vendor lines using Notepad++ in the fstab file (along with the "forceencrypt" changed to "encryptable" of course)? Not sure if you would have the time to help me out on the whole vboot thing as well, which I assume is "verified boot". I've done a ton of searching tonight, but can't really find anything other than you need a boot image to be verified for ChromeOS. Although, I am kind of a noob, so I wouldn't be surprised if the answer was right under my nose this whole time. But a lot of this stuff almost seems like another language. Maybe you could write up some type of tutorial? Don't wanna burden you too much though. Or maybe you could point me in the direction of some helpful resources to learn what it is and how to do it? I'm definitely not opposed to learning new things. Thanks in advance for all the help!:D

EDIT: Figured out removing the ",verify" is how you remove dm-verity. Learning everyday. :D
[Pixel C Android Development] blue__grass:
Xceed-6.10-npreview?

Has anyone else not been able to update the su binary after flashing the xceed-6.10-npreview and installing pphussons superuser? Do we also have to flash su and apk? It was my understanding that it was built into the image?
[Pixel C Android Development] DanRyb:
You used Chainfire's 2.68 SuperSU or someone else's? I have tried what you stated and cannot get it to work. Tried 2.68 and tried the newer 2.70. All report a failure in TWRP and I am not rooted. :/
[Pixel C Android Development] Boal:
Am I blind or is this not linked in the first post? (I mean, "6.0.1 (MXC14G) with root".)
[Pixel C Android Development] Mortron_xda:
Bootloop with latest kernel and N preview. Is it normally? Or i doing something wrong?
[Pixel C Android Development] 530farm:
Yes. Used chainfires. Yeah, strange that it worked for me. Did you try it while encrypted and after flashing xceed?
[Pixel C Android Development] Grims:
I am having a hard time rooting this on the N preview image. I followed the root guide, flashed the su.img, and tried installing superuser from the playstore, the linked APK, and SuperSU. All with no luck. SuperSU just tells me it cannot install binaries.
[Pixel C Android Development] DanRyb:
No, wasn't encrypted. Clean flashed the N preview image and then flashed the Xceed boot image prior to booting up so that the device wouldn't be encrypted. Then I flashed SuperSU but it just gives me a failure. So you were encrypted then??
[Pixel C Android Development] 530farm:
I was encrypted. Flashes xceed, boot to twrp, had to adb push supersu 2.68,flashed supersu, rebooted
[Pixel C Android Development] DanRyb:
Hmm, OK thank you. I guess I will try everything over again and this time let my device encrypt lol.
[Pixel C Android Development] vevmesteren:
When installing the xceed mxc14d on start-up I am l told I need install an update, which reboots, brings me to TWRP, so no update is installed, can't get passt that. And when Android reboots I am bounced to same screen, "Your tablet needs to download an update and restart" but at second go, the "next" button doesn't even initialize the download any more, it just has the "Update Tablet" dialogue bounce back and forth...

Funky.

Installing Factory image from source, by by root for now :(
[Pixel C Android Development] dkryder:
cheep5k8, just FYI, after flashing the MXC14G kernel/twrp procedure upon reboot to android for first time google went through the restore thing and having had SuperSU 2.66 previously installed google went ahead and installed it again. so far i have not had any issues with it. anyway, i'm back with a cheep5k8 modded pixel c. Thank you.
[Pixel C Android Development] drewski_1:
OTA typically fail with modded systems (including TWRP). Flashing latest Factory Image manually is probably best, then root from there.

Sent from my Moto X
[Pixel C Android Development] dkryder:
imho, this notice should be displayed at the beginning of guides for rooting nexus phones along with the disclaimers for damage that might result because it just can not be taken for granted that it is common knowledge or already understood by anyone who is using the guide.
[Pixel C Android Development] Magnus579:
I performed the root procedure tonight including twrp/su.img/xceed.img/superuser.apk etc. Everything works well with a few exceptions. On reboot of the device I constantly get a 30 second wait telling me how my bootloader is unlocked and OS detection disabled - is there a way to supress this message/30 second wait? Next, I'd like to re-encrypt the device given I've formated /data and it's not encrypted (note, want to be protected in case the device is stolen).

Re-attempts to encrypt go into encryption/reboot then simply reboot again into Android. Encryption never completes. Is it possible to support encryption for those that want it?
[Pixel C Android Development] drewski_1:
30 second delay is Google suckage - haven't seen a way to suppress / disable.
[Pixel C Android Development] dkryder:
you would need to ask cheep5k8 to build a kernel that allows encryption. i think this current one is no encrypt
[Pixel C Android Development] backslashV:
cant flash anything

hello,

I erased everything using the fastboot commands (cache, system,userdata,recovery,boot,bootloader) and now I can't flash them back. Keep getting "FAILED (remote: unsupported command)" error despite having an unlocked bootloader.
[Pixel C Android Development] cheep5k8:
Yeah... I've added a way to fix this in TWRP. If you still have it installed, boot into it, go to "Advanced" and then "Fix Fastboot". It's a Pixel C issue, check the start of the thread.
[Pixel C Android Development] backslashV:
unfortunately I have nothing installed. I wiped everything thinking it is the same as all other nexus devices I owned. Is there a way now?
[Pixel C Android Development] cheep5k8:
Do you have root in any way? If not, the only way is to relock the bootloader and then unlock it again.
[Pixel C Android Development] backslashV:
I was rooted. I have tried locking and unlocking but it doesn't make any difference. I still get "FAILURE" when trying to flash anything.
[Pixel C Android Development] cheep5k8:
Sorry, I've accidentally clicked on thanks.

OK so, best is if you could give me all information that you have (what is currently installed on the device, and what exactly Fastboot says).

I'll try to think of a way and get back to you later.
[Pixel C Android Development] backslashV:
so I erased everything using the fastboot commands (cache, system,userdata,recovery,boot,bootloader) and now I can't flash them back. Keep getting "FAILED (remote: unsupported command)" error despite having an unlocked bootloader. (basically nothing is installed right now)

There is an interface which has 5 options: 1) restart this device 2) switch to fastboot mode 3) reboot into android recovery 4) turn off this device 5)switch to usb recovery.

I did the unlocking relocking using option 2. Here you can see the photo of the interface I see: http://imgur.com/VPhb7Y0

Thanks in advance.
[Pixel C Android Development] cheep5k8:
That interface is the actual bootloader.

What does "fastboot getvar secure" say?
[Pixel C Android Development] backslashV:
this is what I get:

secure: yes
finished. total time: 0.016s
[Pixel C Android Development] cheep5k8:
If you get secure: yes, don't have TWRP installed, and relocking the bootloader doesn't help we've got a problem. I'll get back to you once I'm home.
[Pixel C Android Development] teshxx:
Hey cheep5k8...did you ever get a chance to release stock, rooted mxc14g boot img?
[Pixel C Android Development] cheep5k8:
Google hadn't released the stock image for MXC14G so technically I wasn't able to make that image. I'll check again.

On another note, I charged my Pixel and then left it in my drawer for about a week since I had no time for development (or even perusing). The result... (this is on xceed 6.10 mxc14g)
[Pixel C Android Development] teshxx:
Thanks bud and your kernel looks amazing. Keep up the good work Sir.
[Pixel C Android Development] Onraad:
[MENTION=4867279]cheep5k8[/MENTION] I just made a small donation to thank you for your work. Without root I wouldn't be as happy with my Pixel C! Have some weizen this weekend from me ;)
[Pixel C Android Development] cheep5k8:
Weizen it will be! :highfive:
[Pixel C Android Development] backslashV:
Yup I never flashed twrp, I always boot it. Are you home yet?
[Pixel C Android Development] Scarfacez2007:
is still work 6.0.1 (MXC14G) with root or I have to wait?
[Pixel C Android Development] hagbardceline23:
Would it be possible to include a network Filesystem (NFS or cifs) in the next Release ?
[Pixel C Android Development] drewski_1:
it works. there's an XCeeD MXC14G kernel in the OP
[Pixel C Android Development] cheep5k8:
Sure, I can enable it in the kernel config, but I can't promise that it will work properly, we'll have to test that.
[Pixel C Android Development] cheep5k8:
Been home, back to work and home again, but I'm home now.

Are you sure you re-locked the bootloader, then unlocked it again and it still says secure: yes?
[Pixel C Android Development] backslashV:
Yes sir, it still says secure after locking and unlocking.
[Pixel C Android Development] cheep5k8:
Wellllllll... Not sure how to say it, but I'm very afraid that if you have no root shell, then you have no option at this time other than to send it in to Google for RMA.

Basically the only thing that could unbrick your Pixel now would be an officially signed recovery "OTA" ZIP that you would flash in the stock recovery that would contain the one command that unlocks fastboot. But since no such ZIP exists I'm afraid you have no other choice but to send it in. :(
[Pixel C Android Development] backslashV:
Thanx for your help. I wonder what Google does to unbrick in this situation cause the stock recovery is erased as well.
[Pixel C Android Development] cheep5k8:
What do you mean by the stock recovery is "erased"? The entire device is blank?

EDIT: There are at least a few ways to unbrick the device ...if you have a hardware lab.
[Pixel C Android Development] backslashV:
Yes it's blank.
[Pixel C Android Development] Magnus579:
cheep5k8, is there a way to use/enable encryption on the Xceed release? Love the kernel and would like to encrypt my storage in case my pixel c is lost or stolen.
[Pixel C Android Development] cheep5k8:
It's still an outstanding issue. I'll look into encryption as soon as I get some free time again, it's very important to me too.
[Pixel C Android Development] hagbardceline23:
That will be great ! If you need someone to test the network Filesystem ... Just let me know...
[Pixel C Android Development] drewski_1:
[MENTION=4867279]cheep5k8[/MENTION]

i flashed the N-preview and now can't flash your kernel. i'm getting the following error

same error trying to re-flash TWRP

i saw you had a similar error in the following link. i'm not semi-bricked and can boot into the OS fine . . . except now i'm encrypted because i booted with the stock kernel . . .

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-discuss/iJ3OK797CQ0

is the fwtool you say you built what you used to fix it? and if it was can you upload it and walk me through what to do? was it just Stephen Barber's command

fwtool vbnv write dev_boot_fastboot_full_cap 1
[Pixel C Android Development] manaka3161:
Can I ask a question?

In the top post, cheep5k8 said

The N Preview boot image comes with [MENTION=1915408]phhusson[/MENTION]'s Superuser support; you just need to install the Superuser APK from the Play Store!

However, some say they cannot root N. Especially they cannot install Superuser from neither apk nor PlayStore.

So, what I want to know is whether we can root N or not, actually.
[Pixel C Android Development] cheep5k8:
Yes, that is the command. It's part of my TWRP build. BTW if fastboot says that, you are semi bricked: you can't flash anything in fastboot.

There's a link to fwtool in one of the first pages, sorry can't post a new link right now
[Pixel C Android Development] drewski_1:
found the post with fwtool http://xdaforums.com/showpost.php?p=64777133&postcount=96

unfortunately, taking the N-preview overwrote TWRP and am not rooted so looks like i can't run the fwtool command in android to fix . . . :(
[Pixel C Android Development] Scarfacez2007:
how you get update MXC14G with root?
[Pixel C Android Development] drewski_1:
You can follow the guide linked in the OP

http://xdaforums.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183

---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------

I have the URL for the N-preview OTA zip . . . oh wait, just saw he has no stock recovery
[Pixel C Android Development] drewski_1:
Bit the bullet and Locked / Unlocked Bootloader and fastboot is working again along with your TWRP [emoji106]

Sent from my Moto X
[Pixel C Android Development] minieod:
I can install the Superuser apk. But it won't give me root.
[Pixel C Android Development] drewski_1:
+1. issue with the binaries on N-preview
[Pixel C Android Development] minieod:
has anyone successfully rooted running android n? it says it should work, but doesnt look like anyone is chiming in with it?

if you have, can you please outline what steps you took? (what boot.img/kernel you have used, what else you flashed or stored (su.img? phh superuser.apk? supersu rc-2.70.zip?)

my points of failure:

1- superuser.apk does nothing, no granting, no apps prompts "do you want root" , just "no binaries, too bad"

2- trying twrp flash of supersu returns a failure when it tries to modify the ramdisk:

Boot image patcher

- Finding boot image

--- boot image: /dev/block/mmcblk0p1

- Extracting ramdisk

--- failure, aborting
[Pixel C Android Development] dkryder:
minieod, you might want to give skip's setup a try. he has released a new package i read and he seems to be looking for testers. as far as cheep5k8's just read the first post and that install guide and do the steps in order. i can confirm that supersu 2.66 apk does not harm the device just do not flash the .zip. get the .apk out of the .zip and install it.
[Pixel C Android Development] minieod:
can you point me to what you are referencing from skip (mskip, yes?) i dont see anything about N package or asking for testers.

so , youre using adb push su.img to /data , and supersu 2.66 apk installed in the os to root android n?
[Pixel C Android Development] dkryder:
The root has taken place after the flash of the modified kernel and the placement of the su. The supersu .apk

Just gives you a means to control the root.

As far as N goes at the present i would suggest phhusson autobuild for the N kernel, i used the basic eng but noverity seems to get good

Results also and i would suggest install of 2.68 supersu .apk. use cheep5k8 twrp. I ran N for the first weekend i hadmy tablet a couple weeks ago and

Used that mostly from the reviews in the thread and also that his build bot does afairly stock modified. Although i used it for only 2 days the split screen did not impress me and that was big reason for using it. So i switched to cheep5k8 xceed on that Mxc14G i think it is. I'm doing well with this. It provides me with good tablet to read and email and movies. I have N on my nexus 9 so i can get my experience of it from that. I have 56p and it will not update to 56x even after a factory reset.
[Pixel C Android Development] minieod:
awesome. so you had success on android n , with phh's "boot-ryu-NPC56P-su-noverity-r191.img" and supersu 2.68. ill give that a shot

edit: tried using phh, stuck in bootloop.

ill wait til xceed releases something in the future based on pixel's released kernels

edit: for anyone reading, this is actually horrible advice, do not even try that. loading phh's kernel has completely locked my system back up, forcing me into endless bootloops. twrp relocked itself. and i had to reformat the tablet
[Pixel C Android Development] dkryder:
if you flashed 2.68 then you did not understand what i wrote. i wrote to use the .apk from the .zip. also, did you format data? many people have problems by not following the steps in proper sequence. there is a guide but this is what i did.

fastboot mode

flash twrp

reboot into recovery[twrp] using physical buttons power/vol down sends

to menu,

select android recovery

in twrp format data

in twrp select reboot bootloader

flash kernel

reboot back into recovery using keys vol dn/power

scrn goes off, keep pressing vol dn until coreboot list

select android recovery

mount /data [check data in mount menu]

adb push su.img /data

unmout /data [goto mount uncheck data]

mount /system [check system in mount menu]

delete /system/bin/install-recovery.sh using file manager

unmount /system [uncheck system on mount menu] ,<--reboot twrp/bug in unmount

in twrp reboot to system, setup device

install superuser.apk & busybox

from adb, adb install Superuser.apk

install busybox from play store

did you delete install-recovery.sh?

things will work if you just read, take notes, do the sequence in proper order. so, i do not think it was so much my horrible advice but your lack of reading, taking notes and doing the steps in proper order. i'll say that in 3.0.0.0 twrp there is a bug that prevents unmount of /system. the way i handled it was to reboot into twrp as a step to achieve unmount. this had been suggested in forum reading. the bug is fixed in 3.0.0.2 but cheep5k8 will update when he has time.
[Pixel C Android Development] brando56894:
deleted
[Pixel C Android Development] drewski_1:
thanks guys! just got root with boot-ryu-NPC56P-su-nocrypt-r191.img and PHH Superuser installed from Play Store

i think TWRP has a patch to prevent reverting back to the stock recovery . . . at least i didn't delete that install-recovery.sh file and have rebooted many times and still have TWRP :fingers-crossed:
[Pixel C Android Development] minieod:
yup, can confirm. nocrypt works, noverity = reboots and relocks twrp encryption
[Pixel C Android Development] YevOmega:
Hey [MENTION=4867279]cheep5k8[/MENTION], did you end up adding NTFS or exFAT Flash Drive support for OTG use, like you said you might? Thanks!
[Pixel C Android Development] cheep5k8:
I didn't really get around yet to make a new version of xceed, but I've not forgotten... ;)

I probably will not have time to do it until coming weekend or so, but I'll (try my best...) not to forget about exFAT and NTFS. (I really need some kind of planning tool for xceed even if there's not too many things to remember at any given time.)
[Pixel C Android Development] oRAirwolf:
Take your time and know that your work is greatly appreciated by many.
[Pixel C Android Development] YevOmega:
Funny story. I tried an NTFS formatted flash drive, and it worked with stickmount. Thanks though.
[Pixel C Android Development] Avencore:
I can confirm this. It works on my pixel too.

Gesendet von meinem SM-G928F mit Tapatalk
[Pixel C Android Development] YevOmega:
Which USB C adapter do you use? I'm still trying to find a good one. Thanks!
[Pixel C Android Development] Avencore:
The one from Google store. Not cheap but works fine and has a good built quality.

Gesendet von meinem SM-G928F mit Tapatalk
[Pixel C Android Development] YevOmega:
Key words. Not cheap. I got a C to A cable in the mail today, so I'm now ok with connecting to comp. Now just need a good way to connect my USB A flash drive. Sorry for the OT [MENTION=4867279]cheep5k8[/MENTION]. Hope you don't mind.
[Pixel C Android Development] Freak07:
[MENTION=4867279]cheep5k8[/MENTION]

Thanks for the time you put into this Kernel for the Pixel.

On the tegra k1 that runs the n9 one could Set a certain CPU and GPU Offset for voltage. Do you know if any of this is also the case for the x1 of the Pixel? I had a look but couldn't find the files. I thought maybe you could know. Thanks in advance.
[Pixel C Android Development] Mike02z:
Hi guys. I just picked up my Pixel C today. What the OP noted works perfectly for MM. When I try to do it after installing the N preview, using the N patched boot and flashing su.img then Superuser. APK everything looks successful but I don't have root. I followed the step by step exactly. Is there some other way to root the N preview? Sorry if this has been asked but I did search.
[Pixel C Android Development] Mike02z:
Thanks to [MENTION=5458181]dkryder[/MENTION]'s excellent write up I finally got root on N.
[Pixel C Android Development] followmsi:
Time for the monthly M security release .. OTA is online but no full images yet.

Looking forward for new xceed kernel and maybe a new stock rooted kernel too ?
[Pixel C Android Development] hagbardceline23:
Maybe with CIFS/NFS included ? ;)
[Pixel C Android Development] followmsi:
Maybe ;)

Here is the full image .. M5C14J

https://dl.google.com/dl/android/aosp/ryu-m5c14j-factory-b714e9bd.tgz
[Pixel C Android Development] cheep5k8:
Yeah well the thing is Google needs to update the dragon-kernel git repository first before I can make a new stock rooted image (haven't really checked yet ;) ), and to make an updated xceed version they need to update and tag the kernel source at chromiumos git, which usually takes a few days, and then I will need to test the kernel for stability for a little while, so I'd say you can expect a new xceed version+stock rooted image about next weekend or so. :cool:
[Pixel C Android Development] followmsi:
Take your time .. The current xceed kernel is running fine on the new build.

Cheers
[Pixel C Android Development] charesa39:
Sweet! Hopefully Google (eventually...) updates the dragon-kernel git so we can get a fresh stock/rooted image. Appreciate all the work you do for this device!
[Pixel C Android Development] cheep5k8:
Ehh... I made an xceed v7.0-PREVIEW boot image which is based off the branch that will eventually get tagged (so it might not be precisely the same as Google's factory image update release, but at least more or less), but my Pixel C is being funny and isn't recognized in fastboot.

I had this issue once and not sure how I fixed it (I think I need to charge it fully once and then it works again). Or maybe a different cable.

Anyway, here's the boot image IF anyone wants to try it; mind that I haven't really tested it myself (but should be OK):

xceed v7-PREVIEW

I'm not really asking to test it, but if someone wants to here it is ;)

EDIT: OK, found a cable that works with fastboot. Strange issue but w/e. The kernel seems to be working great so far. I'll test it for stability, and when Google has actually tagged M5C14J I'll rebase again and then we'll have v7.

EDIT #2: This preview build doesn't have CIFS enabled but I am firmly keeping that in mind and the RELEASE version of v7 will have it (and I'll try to do something for OTG as well as USB modems)

EDIT #3 Ok, I'm getting reboots with this kernel, need to look into what the exact reason is
[Pixel C Android Development] dkryder:
i was getting some strange fastboot stuff this time also. something to do with too many links. anyway i think it was a cable thing also or a driver issue. new cable and delete/install driver. it is ok now.
[Pixel C Android Development] beardymcgee:
whats funny is that every release you have ever done, I've never had any reboots from anything i do, always stable as...

also is there any possibility i can make governor changes again or is it still borked?
[Pixel C Android Development] Freak07:
So far I had no reboots. Is there an scenario to trigger them?

Also @ cheep5k8 are there any further changes regarding wlan? My reception seems to be better than the latest 6.10 kernel.
[Pixel C Android Development] cheep5k8:
This really needs a fix both in Android and the kernel, couldn't get around doing it yet....

I've created a Trello board for xceed where you can track my progress (more or less :P)

https://trello.com/b/45IcIwc2/xceed

And one for TWRP:

https://trello.com/b/OO1VpcXb/twrp-pixel-c