CM12S Enable Built-in Root [New OTA: YNG1TAS17L]

[inscythe]

Hi all,

Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.

I grabbed a debuggable boot.img from the official CM servers here:

http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img

EDIT: New OTA [YNG1TAS17L]:

http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img

Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.

I have only tested it using TWRP, flash on your own risk.

Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.

 

[Vivek_Neel]

Or just flash the SuperSu zip via recovery.

Sent from my A0001

 

[black.ic3]

Outstriped! I was thinking to make Debug kernel, but they released it sooner

 

[itwin504]

Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.

 

[reaper90]

works fine here, thanks!

 

[inscythe]

Or just flash the SuperSu zip via recovery.

Sent from my A0001

Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?

 

[smoschi]

thank you , works perfectly!

Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?

thx:good:

 

[Link_of_Hyrule]

Works great please keep this updated with each OTA if possible!

 

[droidextra]

Or just flash the SuperSu zip via recovery.

Sent from my A0001

That did not work for me

 

[srgudhka]

That did not work for me

sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.

 

[inscythe]

sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.

I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.

If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.

If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.

 

[Wisiwyg]

I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.

If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.

If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.

SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.

 

[luckylui]

All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!

 

[inscythe]

SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.

I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.

SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.

 

[ten_tickles]

Hi all,

Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.

I grabbed a debuggable boot.img from the official CM servers here:

http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img

Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.

I have only tested it using TWRP, flash on your own risk.

Is there any way to make this work with franco kernel r41? Thanks...

 

[inscythe]

Is there any way to make this work with franco kernel r41? Thanks...

I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.

SuperSU works in this case because it relies on an init.d su-enabling service.

Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...

 

[Link_of_Hyrule]

If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.

 

[SimonTS]

If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.

Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?

 

[Link_of_Hyrule]

I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.

 

[inscythe]

If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.

Not that hard to make, right? But super practical to keep this if you often jumping ROMs.

Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?

Sorry, was doing overtime at work. I've updated the OP too.