XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]

cheep5k8

Senior Member
Sep 26, 2012
587
1,066
0
Berlin
Exceed the limitations /// XCEED kernel
Only for Pixel C

If this technology provides value to you a donation for the time spent creating it is very welcome!











NOTE: The screenshots are actual screenshots from my Pixel C, though your mileage might slightly vary.

DOWNLOAD LINK:

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

But please make sure you first read the....

:: IMPORTANT WARNINGS

  • If you want to flash SuperSU, you MUST use at least version 2.72, which has support for ChromeOS boot images. Under no circumstances flash any version of SuperSU below 2.72!
  • Do not set the min CPU frequency below 204 MHz in Kernel Adiutor, etc. This will most likely not work properly and lead to unintended sideeffects like video/audio tearing up in playback and possibly random reboots. Before reporting any issues make sure you did not set the min CPU freq below 204 MHz

:: INSTRUCTIONS


:: G+ community


:: THANKS

  • TeamWin (_that, DeesTroy) for giving me the right pointers to port TWRP
  • Chainfire, for making SuperSU
  • Stephen and Furquan from ChromiumOS
  • @phhusson for help with diverse topics
  • @oRAirwolf for fantastic installation instructions

and everyone else

:: SOURCE
 
Last edited:

tw1tch175

Senior Member
Dec 28, 2010
515
199
0
I am unencrypted and have flashed the boot.img multiple times but SuperSU isn't installed. I tried installing it manually and it says no binary installed.
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,066
0
Berlin
I am unencrypted and have flashed the boot.img multiple times but SuperSU isn't installed. I tried installing it manually and it says no binary installed.
Might be that you need the right SuperSU app installed. The su binaries, etc, are in the boot image, but whatever app you're using isn't looking in the right place. Maybe if you try indeed reflashing 2.66 in TWRP, SuperSU might detect that the kernel is already patched and just install the necessary app (I will test it all over after wiping my Pixel C clean).
 

dkryder

Senior Member
Sep 26, 2013
447
108
63
hello. the boot image appears to be working here also. thank you.
i also had to flash the supersu 2.66 linked above. thanks to tw1tch175 for the heads up and link.
i'll second motion you need donate tab.
 

ZiggSVO

Senior Member
Apr 4, 2008
1,131
243
0
Wasilla, AK

tw1tch175

Senior Member
Dec 28, 2010
515
199
0
You get force closes after uninstalling an app or trying to uninstall an app? Does it actually finish and only has that slight hiccup or does it further hamper things after uninstalling an app?
It crashes before it starts. I've tried the stock way and through Titanium Backup.

Boot into TWRP and wipe the cache (seriously this time!). That fixes it.
I'll try it again, getting tired of hearing that beep on the 30 second lockout screen :p

Edit: No dice still crashes
 
Last edited:

cheep5k8

Senior Member
Sep 26, 2012
587
1,066
0
Berlin
It crashes before it starts. I've tried the stock way and through Titanium Backup.



I'll try it again, getting tired of hearing that beep on the 30 second lockout screen :p

Edit: No dice still crashes
That fixed it for me, I'll take another look. (Yeah that 30 second boot lockout is very annoying.)

EDIT: It must have been a coincidence. I wiped the cache, and right after that I could uninstall apps. Now it's broken again, and wiping cache does NOT fix it. I'm looking into it.
 
Last edited:
  • Like
Reactions: brando56894

tw1tch175

Senior Member
Dec 28, 2010
515
199
0
That fixed it for me, I'll take another look. (Yeah that 30 second boot lockout is very annoying.)

EDIT: It must have been a coincidence. I wiped the cache, and right after that I could uninstall apps. Now it's broken again, and wiping cache does NOT fix it. I'm looking into it.
I'm not sure TWRP is actually wiping cache properly. If I clear cache and dalvik cache it runs way too fast and I don't get the "Upgrading apps...." when booting.
 

dkryder

Senior Member
Sep 26, 2013
447
108
63
i'm not seeing the crash from uninstalling. but i do have a question, do you also get the crash when accessing the securities setting, settings/security? a suggestion would be to do storage & usb/cached data wipe. also, try using play store to uninstall and see what result is
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,066
0
Berlin
i'm not seeing the crash from uninstalling. but i do have a question, do you also get the crash when accessing the securities setting, settings/security? a suggestion would be to do storage & usb/cached data wipe. also, try using play store to uninstall and see what result is
There is an issue with the keystore service and TLK (nvidia's hardware security stuff). So far no luck, looked into it for the past hour or so but to no avail yet. I'm staying on it.
 

ZiggSVO

Senior Member
Apr 4, 2008
1,131
243
0
Wasilla, AK
i'm not seeing the crash from uninstalling. but i do have a question, do you also get the crash when accessing the securities setting, settings/security? a suggestion would be to do storage & usb/cached data wipe. also, try using play store to uninstall and see what result is
Still crashes using play store
 

dkryder

Senior Member
Sep 26, 2013
447
108
63
i think there may be a work around for this if in fact what i'm gonna suggest has anything to do with it but in this post
http://forum.xda-developers.com/showpost.php?p=64535045&postcount=68
superchilpil gives a link for a modified vendor image that resolved the settings/security crash. that was happening
in another modified boot image thread. anyway i am using it now.
as i said before, i'm not seeing the uninstall crashes. i'm not going to say it is a workaround because i do not know for
a fact, but, it is the only thing i can think may be different between what my setup is and what others may be.
 
Last edited:

ZiggSVO

Senior Member
Apr 4, 2008
1,131
243
0
Wasilla, AK
i think there may be a work around for this if in fact what i'm gonna suggest has anything to do with it but in this post
http://forum.xda-developers.com/showpost.php?p=64535045&postcount=68
superchilpil gives a link for a modified vendor image that resolved the settings/security crash. that was happening
in another modified boot image thread. anyway i am using it now.
as i said before, i'm not seeing the uninstall crashes. i'm not going to say it is a workaround because i do not know for
a fact, but, it is the only thing i can think may be different between what my setup is and what others may be.
fastboot flash vendor xxx.img
results in

ADB and Fastboot>fastboot flash vendor ryu-vendor.img
target reported max download size of 268435456 bytes
erasing 'vendor'...
FAILED (remote: unsupported command)
finished. total time: 0.009s
 

tw1tch175

Senior Member
Dec 28, 2010
515
199
0
fastboot flash vendor xxx.img
results in

ADB and Fastboot>fastboot flash vendor ryu-vendor.img
target reported max download size of 268435456 bytes
erasing 'vendor'...
FAILED (remote: unsupported command)
finished. total time: 0.009s
Mine is not telling my this for all fastboot commands :(

For some reason my bootloader version is Google_Smaug.7132.239.0 and it won't let me update using fastboot

Just used getvar and for some reason secure is set to yes
 
Last edited:

cheep5k8

Senior Member
Sep 26, 2012
587
1,066
0
Berlin
Mine is not telling my this for all fastboot commands :(

For some reason my bootloader version is Google_Smaug.7132.239.0 and it won't let me update using fastboot

Just used getvar and for some reason secure is set to yes
I'm having the same problem after flashing SuperSU 2.66. I think "secure: yes" just means that secure boot is enabled/possible, but I'm not entirely sure there.

EDIT:

"fastboot flashing get_unlock_ability" returns '1', so it means the bootloader can be unlocked (??)

There's still the option to run "fastboot flashing unlock_critical", but I'm a bit wary of that right now.
 
Last edited:

tw1tch175

Senior Member
Dec 28, 2010
515
199
0
I'm having the same problem after flashing SuperSU 2.66. I think "secure: yes" just means that secure boot is enabled/possible, but I'm not entirely sure there.

EDIT:

"fastboot flashing get_unlock_ability" returns '1', so it means the bootloader can be unlocked (??)

There's still the option to run "fastboot flashing unlock_critical", but I'm a bit wary of that right now.
"Unknown command"