[ROM] CleanCore N5 | MMB29S | 100% Lean Stock | 01/19/2016

[luloo]

I will try that later today and report back. Thanks Vomer.

Edit: The search I just did on systemless root shows that it's Beta SuperSU 2.52, which is the one I used already

I just tried the latest SuperSU v2.56 still no luck. Already upgraded to 6.0 so been using the following steps with no luck.

1. Boot into TWRP
2. Flash boot.img file
3. Flash SuperSU v2.56
4. Flash blu_spark kernel

Not having any luck. Would I need to wipe and reinstall CleanCore again? Just trying to get root.

If I wanted to go back to Lollipop from my TWRP backup, am I able to just restore the backup or is there anything else that I need to do?

 

[JaymzTA]

I just tried the latest SuperSU v2.56 still no luck. Already upgraded to 6.0 so been using the following steps with no luck.

1. Boot into TWRP
2. Flash boot.img file
3. Flash SuperSU v2.56
4. Flash blu_spark kernel

Not having any luck. Would I need to wipe and reinstall CleanCore again? Just trying to get root.

If I wanted to go back to Lollipop from my TWRP backup, am I able to just restore the backup or is there anything else that I need to do?

I'm in the same boat as you. Hopefully we can get this figured out.

 

[drac0]

I stand corrected. I'll try it out in a bit. Thanks.

Edit: drac0, I did as you instructed and I am still unable to get root. I'm completely at a loss...

Hmm I cant figure it out, did you reflashed /system partition or your ROM before flashing 2.56 systemless root? This is a must if you want it to work properly, otherwise some SuperSU libs kill each other if you have both version installed.

Try this, wipe only your /system partition with cache and dalvik of course. Then dirty flash ROM and then repeat systemless procedure all at once flashing one after another prior to initial system boot. Hope this can help you, cheers!

 

[JaymzTA]

Hmm I cant figure it out, did you reflashed /system partition or your ROM before flashing 2.56 systemless root? This is a must if you want it to work properly, otherwise some SuperSU libs kill each other if you have both version installed.

Try this, wipe only your /system partition with cache and dalvik of course. Then dirty flash ROM and then repeat systemless procedure all at once flashing one after another prior to initial system boot. Hope this can help you, cheers!

Yes, I did make sure to wipe the system partition first. I'll try this:

Full wipe
Install rom
Let it boot
Go to recovery
Wipe system
Dirty flash rom
Install chainfires boot.img
Install systemless root
Install kernel of choice
Then hopefully profit!

 

[drac0]

I just tried the latest SuperSU v2.56 still no luck. Already upgraded to 6.0 so been using the following steps with no luck.

1. Boot into TWRP
2. Flash boot.img file
3. Flash SuperSU v2.56
4. Flash blu_spark kernel

Not having any luck. Would I need to wipe and reinstall CleanCore again? Just trying to get root.

If I wanted to go back to Lollipop from my TWRP backup, am I able to just restore the backup or is there anything else that I need to do?

Of course you can always restore your backup, no further actions needed and no worries about that, just hit restore and forget it. But why go back to Lollipop, rather return to 58K where root is tested and working like a charm! Hope all this solves pretty soon, Chainfire is working on it I'm sure.

---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------

Yes, I did make sure to wipe the system partition first. I'll try this:

Full wipe
Install rom
Let it boot
Go to recovery
Wipe system
Dirty flash rom
Install chainfires boot.img
Install systemless root
Install kernel of choice
Then hopefully profit!

Make sure not to wipe your internal data!

I did similar with 58K let it boot after ROM install then figured I should have flashed all at once prior to system initial boot up. First run left me without root, but when I tried all again with all at once flashing it worked!

Btw you dont need to wipe system partition on untouched 6.0 since there is no root libs present so no need to double flash your ROM or to repeat that step.

Try your way and report back, I'm curious! Good luck!

 

[JaymzTA]

Alas, still no dice.

What I don't get is how it's working for some people, but not others.

 

[jaxbierley]

Also unable to root here

 

[luloo]

Also unable to root here

Same here, used the SuperSU v2.56 on both 58K and N and no luck. I did see the script before the first boot about installing SuperSU but it does seem like root does not seem to be working. When I load up SELinuxModeChanger it tells me that I am not rooted. Running out of ideas. Tried to reinstall both 58K and N multiple times.

Really curious as to why it works for some people and not others.

 

[aderuhya]

I wonder why, already try many way to root like above post told but still unable to root.

 

[rizqi_ir]

currently on 58N, still can't set security lock screen (pattern, PIN) even i use modified Chainfire's kernel.

 

[jouet24]

no success here too. many trys, many method but no success

 

[Mairo]

stock rom, hellscore kernel , supersu 2.52, twrp 2.8.7.1 and no problem with root. First I flashed bootloader , then radio, then boot, then recovery, then system ( all stock ). After each flash I rebooted to bootloader. Then simple reboot and waited every app updated. Then rebooted back to bootlaoder. Then I flashed modified boot.img and twrp. then under twrp I flashed supersu. And I got root.
And optional, if u want, flask custom kernel. I use hellscore.

 

[Yousie642]

I'm stuck with a boot loop sorta. It starts to boot with the Marshmallow splash animation, but then reboots into TWRP. I tried flashing BL+Radio, CC, and then letting TWRP flash SuperSU on it's own. Tried to manually flash SuperSU. I also tried the kernel, but the kernel fails on flash without any error message besides "Error flashing zip"

 

[drac0]

Also no problem here with blu_spark and 2.52 supersu. Inside twrp flashed new bootloader and radio first (coming from lollipop). Then installed system then all at once flashed Chainfires boot.img with supersu and blu_spark immediately after it. Followed blu_spark instructions for stock marshmallow flashing. Workin like a charm! Not sure why some people having so much trouble, maybe its just due to new supersu and flashing order, who knows. Keep trying everyone since its working fine. Cheers all! :good:

 

[luloo]

I'm stuck with a boot loop sorta. It starts to boot with the Marshmallow splash animation, but then reboots into TWRP. I tried flashing BL+Radio, CC, and then letting TWRP flash SuperSU on it's own. Tried to manually flash SuperSU. I also tried the kernel, but the kernel fails on flash without any error message besides "Error flashing zip"

I haven't had luck with root, but if you are flashing the zip of Chainfire's kernel that won't work. You need to extract the boot.img file and flash the img, not the zip. Give that a shot and you may not get the error message any more.

 

[aikidoka9]

Also no problem here with blu_spark and 2.52 supersu. Inside twrp flashed new bootloader and radio first (coming from lollipop). Then installed system then all at once flashed Chainfires boot.img with supersu and blu_spark immediately after it. Followed blu_spark instructions for stock marshmallow flashing. Workin like a charm! Not sure why some people having so much trouble, maybe its just due to new supersu and flashing order, who knows. Keep trying everyone since its working fine. Cheers all! :good:

Drac0,
The CleanCore is really nice, thin and quick thanks to Vomer. I'd love to use it as a Daily Driver.

Thanks for the suggestions BUT no joy for me. It seems so clear but after hours AND
on 2 different devices I'm left with functioning CleanCore MRA58K installs with no root.
I have TWRP on both so I can revert to the non Marshmallow BU.

Device 1(daily driver) 4.4.4 Nexus 5 hammerhead, root, TWRP etc.
TWRP BU CleanCore MRA58K install with ElementalX

2 (test device) Nexus 5 hammerhead TWRP, MultiROM, CM 12.1 (internal primary)
Ubuntu secondary and MRA58K secondary.
All the files are for hammerhead, current and TWRP says success to all my flashes.
I wiped prior to installs.

I have tried your suggested approach AND the suggested approach of others with no luck. . .
so the problem is probably ME, somehow.

The last attempt was with your instructions with Blu_spark. NO JOY. I got the following error
message: ERROR SuperSU Stage 3-Root user account:error
error: stderr:null. stdout:id:no such tool, exit_value:255
At my noob level the info is of no use to me. I hope that it helps others with more knowledge
than I have.

Thank you for the time you've put in. I'm sure that if it works for you it'll work for others, just not me. I'm beginning to feel like a klutz.
I guess I'll have to wait for the next Chainfire and/or CleanCore advances and pray they
make a difference. Be well, stay cool.

aikidoka9

 

[drac0]

Drac0,

The last attempt was with your instructions with Blu_spark. NO JOY. I got the following error
message: ERROR SuperSU Stage 3-Root user account:error
error: stderr:null. stdout:id:no such tool, exit_value:255
At my noob level the info is of no use to me.

aikidoka9

I'm not sure what happened at your end but did you extracted Chainsfire boot.img out of zip file? You need to flash .img file NOT the .zip one!

As I said I've followed eng_stk instructions on how to flash latest supersu with his blu_spark kernel so I'm not sure whats the procedure with other custom kernels, all I can confirm its working just fine with blu_spark. Hope this helps and hope Chainfire sorts this out with some new stable release. Till then keep trying. Cheers!

 

[Pekoltia]

whats users preferred kernel for Cleancore?

 

[drac0]

whats users preferred kernel for Cleancore?

Try blu_spark. Working like a charm! Link in my sig. Cheers! :good:

 

[Isley_]

+1 for Blu_spark.

Sent from my Nexus 5 using Tapatalk