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

Search This thread

luloo

Member
Jun 5, 2013
29
1
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

Senior Member
Apr 3, 2011
133
30
OnePlus 3T
OnePlus 7 Pro
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

Senior Member
Dec 31, 2010
538
368
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!
 
  • Like
Reactions: JaymzTA

JaymzTA

Senior Member
Apr 3, 2011
133
30
OnePlus 3T
OnePlus 7 Pro
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

Senior Member
Dec 31, 2010
538
368
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! :p

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!
 
Last edited:

luloo

Member
Jun 5, 2013
29
1
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.
 
  • Like
Reactions: jcjan

rizqi_ir

Senior Member
Nov 19, 2014
83
23
currently on 58N, still can't set security lock screen (pattern, PIN) even i use modified Chainfire's kernel.
 

Mairo

Senior Member
Feb 28, 2013
558
139
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

Senior Member
Dec 3, 2010
138
10
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"
 
  • Like
Reactions: josito_theDH

drac0

Senior Member
Dec 31, 2010
538
368
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:
 
  • Like
Reactions: aikidoka9

luloo

Member
Jun 5, 2013
29
1
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

Member
May 27, 2012
17
2
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 :confused:
 

drac0

Senior Member
Dec 31, 2010
538
368
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 :confused:

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!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 691
    Welcome to my new project - CleanCore

    CleanCore is a rom series focused on a clean and lean version of the latest stock android builds.

    Features:

    - Always sourced from stock factory images w/ stock kernel
    - Trimmed out Gapps & useless bloat

    Trimmings:

    Videos
    YouTube
    Books
    Chrome
    CloudPrint2
    Drive
    EditorsDocs
    EditorsSheets
    EditorsSlides
    FitnessPrebuilt
    GoogleEars
    GoogleEarth
    GoogleHindiIME
    GooglePinyinIME
    KoreanIME
    Maps
    Music2
    Newsstand
    Photos
    PlusOne
    PrebuiltGmail
    PrebuiltKeep
    PrebuiltNewsWeather
    Street

    Donations:



    Files (flashable):

    Flash Order:
    Flash Bootloader & Radio -> Flash CleanCore -> Flash Modified kernel (if needed) -> Flash SuperSU or SuperSU Beta

    6.0.x:

    MRA58K Radio+Bootloader.zip
    CleanCore N5
    MRA58K Modified Kernel by Chainfire

    5.1.x:

    - LMY48M: https://www.androidfilehost.com/?w=files&flid=37013

    - LMY48I: https://www.androidfilehost.com/?fid=24052804347801140
    - LMY48B: http://forum.xda-developers.com/showthread.php?p=60882024#post60882024
    - LMY48B Radio & Bootloader: https://www.androidfilehost.com/?fid=23991606952608490
    - LMY47I CleanCore: http://forum.xda-developers.com/showpost.php?p=59698354&postcount=8061
    - LMY47D Radio & Bootloader: https://www.androidfilehost.com/?fid=95916177934540588 zip by asim0
    - LMY47D CleanCore: http://forum.xda-developers.com/showpost.php?p=59638725&postcount=8042
    - LMY47D Stock: http://forum.xda-developers.com/showpost.php?p=59391346&postcount=7987


    5.0.x:

    - LRX22C: http://forum.xda-developers.com/showpost.php?p=57613996&postcount=7893
    - LRX22C Radio: https://www.androidfilehost.com/?fid=95864024717066668
    - LRX21O: http://forum.xda-developers.com/showpost.php?p=56948124&postcount=7803
    - LRX21O Radio: https://www.androidfilehost.com/?fid=95784891001609833
    - SuperSU: http://download.chainfire.eu/supersu
    - Lollipop Sounds: https://www.androidfilehost.com/?fid=95784891001615212

    Archive:

    L Developer Previews:
    - Stock ROM (LPX13D): http://forum.xda-developers.com/showpost.php?p=56112246&postcount=5498
    - Art and VM tweaks: https://www.androidfilehost.com/?fid=95747613655048592 (Credit: @sykopompus)
    - Radio Only (LPX13D): https://www.androidfilehost.com/?fid=95747613655047015
    - Modified Kernel (allows root): by Chainfire or by sykopompos
    - PIE Security Check Patch: http://forum.xda-developers.com/showpost.php?p=56123703&postcount=13
    - LPX13D IMG Files: https://www.androidfilehost.com/?w=files&flid=20081
    - Stock ROM (LPV81C): http://www.androidfilehost.com/?fid=23610159112651697
    - Stock ROM (LPV79): http://www.androidfilehost.com/?fid=23501681358553483 (credits to Tasssadar for his install script)
    - Radio: http://www.androidfilehost.com/?fid=23501681358553376


    Other Files:

    - N6 /system/app/ & /system/priv-app/ dump: https://www.androidfilehost.com/?fid=95747613655048224
    - Busybox: https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&
    - Bootanimation (flashable): http://www63.zippyshare.com/v/84100724/file.html
    - Modified Kernel: http://www.androidfilehost.com/?fid=23501681358553514
    - TWRP: http://techerrata.com/browse/twrp2/hammerhead


    Google IMG files (manual installation):

    LPX13D
    - Full L Package: http://storage.googleapis.com/androiddevelopers/finalpreview/hammerhead-lpx13d-preview-f7596f51.tgz

    LPV81C
    - Full L Package: https://developers.google.com/fit/preview#flash_your_nexus_5_or_nexus_7
    - Note: The new Android L build didn't come with a new radio (same as LPV79)

    LPV79:
    - Full L Package: http://www.androidfilehost.com/?fid=23501681358553290
    - Stock "L" Radio: http://www.androidfilehost.com/?fid=23501681358553294
    - Stock "L" Boot (kernel): http://www.androidfilehost.com/?fid=23501681358553305
    - Stock "L" Bootloader: http://www.androidfilehost.com/?fid=23501681358553296
    - Stock "L" Recovery: http://www.androidfilehost.com/?fid=23501681358553307
    - Stock "L" Userdata: http://www.androidfilehost.com/?fid=23501681358553346
    - System partition dump: http://www.androidfilehost.com/?fid=23501681358553357

    Report Bugs:

    G+ Community: https://plus.google.com/communities/101985907812750684586
    Report Issues: https://code.google.com/p/android-developer-preview/

    Instructions:

    A clean install is highly recommended when coming from v4.x to "L"
    DOES NOT wipe your SD card.

    via flashable file:

    - Boot into recovery (TWRP/CWM)
    - Un-mount /system in TWRP/CWM
    - Wipe: system, data, dalvik and cache
    - Flash ROM (be patient - takes a while)
    - Flash SuperSU (optional)
    - Flash radio (optional)
    - Reboot (first boot takes a while)

    MultiROM users can follow this method.

    via fastboot (manual installation):

    SYSTEM PREP (skip if you already have fastboot/adb setup):

    Let's setup ADB and fastboot

    Windows:

    - Automated: http://forum.xda-developers.com/showthread.php?t=2588979 (follow the steps in the software)

    - Manual Method:

    Download this file and extract the folder called "adb" to your C: drive. Your path should look like this:

    Code:
    C:\adb\

    You will need to open a command prompt window using this method:

    Code:
    - Go to the C:\adb\ folder 
    - hold down SHIFT key and RIGHT-CLICK 
    - select "Open command window here".

    In order to use ADB & Fastboot from anywhere - use the following steps to setup windows environment variables:

    Navigate to & click on Start > Right-Click on Computer > click on Advance System Settings >
    Click on Environment Variables (under the advanced tab) > Click on New (User Variables) >
    Variables Name: ADB (Or anything you want) Variables Value: ;C:\adb (this is the Path of my adb.exe file)

    gUw4I5m.png


    Mac & Linux:

    Install ADB & fastboot using: this file

    1. Extract the downloaded zip to your desktop
    2. Open Terminal and type in:

    Code:
    su
    cd Desktop/Android/ (note: Android is the directory extracted from zip file)

    3. Now type

    Code:
    ./ADB-Install-Mac.sh

    Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/

    ----
    Now that you're setup, let's do the flashing:

    Boot into TWRP to wipe cache, dalvik, data (not internal storage/SD) and system.

    Reboot to bootloader and flash the following:

    • fastboot flash bootloader <insert bootloader img name>
    • fastboot reboot-bootloader
    • fastboot flash radio <insert radio img name>
    • fastboot reboot-bootloader
    • fastboot flash system system.img
    • fastboot flash boot boot.img // OR // fastboot flash boot <insert name of unecrypt boot.img>
    • fastboot flash cache cache.img
    • fastboot reboot

    After you finish the above - reboot in to recovery (TWRP/CWM) and factory reset - then reboot

    -------

    FAQ

    Check out this comprehensive HELP INDEX which will help answer your questions.

    Got "No SDCard" error?
    This is because 4.4.x seems to point to: storage/emulated/0 & L points to: data/media/0

    Solution:

    - Mount system in TWRP/CWM
    - Wipe system, dalvik, data, cache
    - Unmount system
    - Install ROM
    - Factory reset
    - Reboot
    - Go back to recovery & flash SuperSU (link above).
    - Reboot

    Still not resolved? try:

    Open terminal and type
    su
    restorecon -FR /data/media/0

    or type

    su
    restorecon -r /data/media/0/*

    Still not resolved? back everything up and flash the userdata.img (erases your SD card)

    Does Titanium Backup work?
    Titanium backup and other similar apps do not work 100% on L... as expected.

    How do I restore my user apps?
    You can restore your apps using this method:

    - While on a 4.4.x rom, go into TB > batch actions > recovery > 'create update.zip...' > select user apps
    - Install L > flash the update.zip
    - Done!

    I get a "failed" error when flashing ROM
    You did not unmount system or it got re-mounted automatically. Reboot your recovery > unmount system > flash ROM

    SMS/MMS not working?
    SMS & MMS is related to your APN and not the ROM. Check that.

    Can I flash this over my 4.4.x rom?
    Yes, but do a clean install

    OMG x app is not working?
    That's expected - a lot of apps need to be updated to be compatible with L

    OMG xPosed is not working?
    No, it's not compatible with ART which is the default runtime on L

    Can I flash a custom kernel?
    Yes, thanks to @eng.stk

    Disclaimer & Copyrights:

    I test everything before I share - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.

    Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.

    Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.

    Let's do this! :)
    162
    LPX13D: https://www.androidfilehost.com/?fid=95747613655047401

    I have noticed a few sites and a few users here "re-brand" my zips to pass as their own - pls have some courtesy and link to this thread instead... If you see one - please report it

    If you would like to support my work donate to me via:



    Keep in touch:
    3hawHKs.png
    VomerTweets

    Thank you :)

    special thanks to:
    @ben1066 @Tzfardaya @SanTos0250 @sykopompos

    for helping me with test cases :good: :good:
    79
    Dual Boot Custom ROM With Android L Preview

    Why would you want to use MultiBoot with the Android L preview?
    Because this is only a preview release and probably should not be your daily driver. By dual booting, you can still have your normal daily driver ROM as well as being able to test Android L on the side whenever you want without having to sacrifice anything, be it data or time. It's just a more convenient and efficient way to go about the situation, in my opinion.

    How to dual boot a custom ROM with the new Android L preview:
    You'll want to go to the Play Store on your main ROM and download this app: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=en

    1. Open the MultiROM Manager app and under "Install/Update" make sure "MultiROM v26" and the recovery are both checked (recovery is required anyways.) If you already have a custom kernel of your choosing installed I would leave the kernel alone, otherwise go ahead and check the kernel box and choose the appropriate version you are running.

    2. Next, tap "Install" and then let it download and reboot. Then, make sure you have the Android L preview Stock ROM zip from this thread downloaded. Put it somewhere on your phone internal storage... let's say the "Download" folder. Reboot into the new MultiROM TWRP recovery, tap "Advanced", tap "MultiROM" (bottom right), tap "Add ROM", (top right), keep ROM type set to Android, don't share kernel, install to internal memory (only one option anyways), tap "Next", choose "ZIP file" for the ROM source, navigate to the Android L preview zip you downloaded from this thread (I chose the "Download" folder), select it and then swipe to confirm.

    3. Let it finish installing, and then once you reboot the next time you will be presented with a new MultiROM boot up screen with a short count down timer. Tap the screen to cancel the auto booting of your primary ROM. If all went well you should see two ROM's listed... your main ROM as well as the new Android L preview. Simply tap the Android L preview ROM in the list, hit "Boot" (lower right corner), wait for about 5 to 10 mins for it to boot up for the first time (boot time seems to vary, but it shouldn't be bootlooping though. Just be patient), and then you're all set! It kind of sounds like a lot, but in reality it's pretty quick to do once you've done it a time or two.

    How to enable root on the Android L preview ROM using MultiBoot:
    Root is not working very well at the moment on L since it's an early preview release and not a final product. Please keep this in mind. Rooting L at this point in time would only be used for testing purposes.

    First off, you need to grab the SuperSU zip under the "Main files" part of the thread found here: http://forum.xda-developers.com/google-nexus-5/development/rom-n5-l-developer-preview-t2796003 and put it on your phone internal storage somewhere you will remember. Boot into recovery, tap "Advanced", tap "MultiROM", tap "List ROMs", tap the Android L preview ROM, tap "Flash ZIP", now locate the SuperSU zip you downloaded from the thread and tap it then swipe to install it, and now you're done! Reboot the system back into the Android L preview and you'll have SuperSU installed.

    If you have any specific problems related to MultiBoot let me know! I'd be happy to help out when and where I can. Thanks all!
    49
    I read at the last days in all L threads and in any thread many times the same problems.

    There are different groups of users

    Group 1

    = people read the threads, understand what is written, follow the instructions step by step, understand what they do ~ result, minimal or no issues.

    Group 2

    - people read a little bit, most to find the download link, flashing, have isuses but don't understand all (no problem), start asking in the thread and most time issues are after some time solved.

    Last but not least

    Group 3

    - first question before do anything " where is the download link, how is battery" . After some flames download link found,
    Download, flashing, knowing what they download, no, why? It's in the download link listet, let's go. Knowing what they download? Yes, difference between kernel and Rom, Rom File is bigger and download takes more time.
    After flashing = let's go in the thread, asking what i have downloaded, what to do, what is fastboot, device starts faster? Great, DOWNLOAD LINK!!!???

    I can write now a unending text but maybe the one or other think about it.


    = read the FAQ and more important, understand what you read. If you don't understand, your welcome to ask, there are many people who can help but, only when you understand the help it makes sense.


    What i want to say, 70=80% off the Postings with again and again the same question / answer crap Would not be necessary with a little initiative and i am 100% sure, we all would feel better then.


    Guys with true problems become faster help, guys who helping must not write the same every day again.


    Maybe the one or other is thinking about it before my posting in a few minutes ends in the Nirvana.

    Thanks to all who read it, understand and think about it and thanks to all other.

    Best Regards
    48
    not flashable yet - working on that as we speak!

    I am uploading/posting all original files as I go so people have some mirrors too :cowboy: