Official Announcements  - 
Slim7 Alpha 0.6 is now available! This build brings a slew of bug fixes, security updates, and device-specific updates.

Hammerhead (Nexus 5) and Kenzo (Xiaomi Redmi Note 3) have joined the list of devices receiving Slim7 Alpha builds!

Downloads and more detailed changelog can be found at

How to Install:

How to Report bugs:

Questions? Check the FAQ:

Don't forget to keep it Slim!
SlimRoms' website, news, downloads.
Endra Prasetya's profile photoJosue Rivera's profile photoCarlo Carnevali's profile photoPaul Sheehan Jr.'s profile photo
I see that Kenzo has been added which is good news but I can't fondc the link in the download section
Wops. We added the space, missing graphics. But kenzo users can at least access it now. Sorry! (image is incoming)

+Rachid Mohsmedi
This is one awesome Android Nougat ROM. Thank you for the OnePlus One support!!! Here WeGo maps app throws errors at startup. No big deal, but reporting nonetheless. +Dan Cartier
+Josue Rivera Thanks for the quick reply. I have the adb log, but there is a ton of irrelevant and personal data needing to be stripped out of the ADB log. I'm not comfortable posting the log. It is an easy enough problem to repro by any ROM dev on bacon. Anyway, not a deal breaker, thx! +Dan Cartier
. If it bothers you so much copy the relevant bits or delete the bits that aren't relevant and provide it to DM. Unless your using some sketchy information worst case it's an email address . Or just link it directly to DM Pm on xda or w/e.

Just because it's easily reproduce doesn't mean you shouldn't provide logs. Your saving the DM time, which we could be using for other things :p

Has anyone any idea how I'd ether delete the "addon.d" permanently (it gets recreated after i delete it with all file managers ive tried) or how to change it into a directory? Its a text file at the moment.
It's, iIrc, a folder that contains backup script. 
+Josue Rivera OK so the error I'm getting when trying to do a twrp backup saying error 255 addin.d can't be accessed because its isn't a directory, how would I fix that? I cant do a backup because of it so kinda stuck.

PS I do a lot if searching before asking questions here but couldnt find the answer.
When you flash do you format /system? 
+Josue Rivera I didn't format system but it was a total clean flash, wiping Cache, dalvak, data, system.

I guess I need to re flash and format system first?

I did come from mm though and deleted a line from the update script to get it to flash after flinnys advice to do so, maybe that could be related?
That's what they are supposed to be. Flash root get a terminal emulator and run
rm -rf /system/addon.d
See if that works? 
Getting /system/addon.d read only file, is the fine the same in all device trees? Could I try replacing it with one from gerrit?
+StuPot it's supposed to be as that's something handled in vendor/slim not device specific. Sounds to me you got a perm problem. From terminal do
cd /system
ls -l
I've now put the permissions right but it still isn't a directory, replace the file completely?
+Josue Rivera u0_a86@android:/ $ su
root@android:/ # rm rf /system/addon.d
rm: /system/addon.d: Read-only file system
1|root@android:/ # is -l
sush: is: not found
127|root@android:/ # ls -l
total 3896
drwxr-xr-x 54 root root 0 2017-01-09 10:54 acct
drwxrwx--- 6 system cache 4096 2017-01-09 10:54 cache
drwxrwx--- 3 system oem_11 4096 1970-01-01 01:00 carrier
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 2017-01-09 10:54 config
lrwxrwxrwx 1 root root 17 1970-01-01 01:00 d -> /sys/kernel/debug
drwxrwx--x 45 system system 4096 2017-01-09 10:54 data
-rw-r--r- 1 root root 1027 1970-01-01 01:00 default.prop
drwxr-xr-x 16 root root 4580 2017-01-09 10:54 dev
lrwxrwxrwx 1 root root 11 1970-01-01 01:00 etc > /system/etc
-rw-r--r- 1 root root 41921 1970-01-01 01:00 file_contexts.bin
drwxr-xr-x 6 root root 0 2017-01-09 10:54 firmware
rw-r----- 1 root root 3717 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 1316008 1970-01-01 01:00 init
-rwxr-x--- 1 root root 1148 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 679 1970-01-01 01:00 init.magisk.rc
-rwxr-x--- 1 root root 7564 1970-01-01 01:00 init.qcom.power.rc
-rwxr-x--- 1 root root 19767 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 6272 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26084 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 7564 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 8231 1970-01-01 01:00 init.slim.rc
-rwxr-x--- 1 root root 484 1970-01-01 01:00 init.supersu.rc
-rwxr-x--- 1 root root 12058 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5715 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 411 1970-01-01 01:00 init.zygote32.rc
-rwxr-x--- 1 root root 684 1970-01-01 01:00 init.zygote64_32.rc
drwxr-xr-x 3 root root 4096 2017-01-09 10:54 magisk
drwxr-xr-x 10 root system 220 2017-01-09 10:54 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxrwx--x 11 system system 4096 2016-12-19 10:42 persist
dr-xr-xr-x 469 root root 0 1970-01-01 01:00 proc
-rw-r--r- 1 root root 9942 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-12-24 15:25 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-01-01 01:00 sdcard > /storage/self/primary
-rw-r--r- 1 root root 1957 1970-01-01 01:00 seapp_contexts
rw-r--r- 1 root root 66 1970-01-01 01:00 selinux_version
rw-r--r- 1 root root 382495 1970-01-01 01:00 sepolicy
rw-r--r- 1 root root 17596 1970-01-01 01:00 service_contexts
drwxr-xr-x 5 root root 100 2017-01-09 10:54 storage
drwxr-xr-x 8 root root 4096 2016-12-26 15:46 su
dr-xr-xr-x 22 root root 0 2017-01-09 10:54 sys
drwxr-xr-x 19 root root 4096 2016-12-26 13:14 system
lrwxrwxrwx 1 root root 16 2017-01-09 10:54 tombstones > /data/tombstones
-rw-r--r- 1 root root 12564 1970-01-01 01:00 ueventd.qcom.rc
rw-r--r- 1 root root 4857 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-01-01 01:00 vendor -> /system/vendor
root@android:/ #
Haha I'm searching the terms you're using to try work it out,

I'm guessing this is what you meant
u0_a86@android:/ $ su
root@android:/ # ls l in /system
ls: in: No such file or directory
total 848
-rwxr-xr-x 1 root root 171292 2008-12-31 23:00 addon.d
drwxr-xr-x 37 root root 4096 2016-12-26 13:14 app
drwxr-xr-x 2 root shell 8192 2008-12-31 23:00 bin
-rw-r--r- 1 root root 5546 2008-12-31 23:00 build.prop
drwxr-xr-x 16 root root 4096 2016-12-26 13:14 etc
drwxr-xr-x 2 root root 4096 2008-12-31 23:00 fake-libs
drwxr-xr-x 2 root root 4096 2008-12-31 23:00 fake-libs64
drwxr-xr-x 2 root root 8192 2008-12-31 23:00 fonts
drwxr-xr-x 2 root root 4096 2016-12-26 13:14 framework
drwxr-xr-x 6 root root 8192 2008-12-31 23:00 lib
drwxr-xr-x 5 root root 8192 2016-12-26 13:14 lib64
drwx------ 2 root root 4096 1970-01-01 01:00 lost+found
drwxr-xr-x 3 root root 4096 2008-12-31 23:00 media
drwxr-xr-x 55 root root 4096 2016-12-26 13:14 priv-app
rw-r--r- 1 root root 171292 2008-12-31 23:00 recovery-from-boot.bak
drwxr-xr-x 3 root root 4096 2008-12-31 23:00 tts
drwxr-xr-x 8 root root 4096 2008-12-31 23:00 usr
drwxr-xr-x 7 root shell 4096 2008-12-31 23:00 vendor
drwxr-xr-x 2 root shell 4096 2008-12-31 23:00 xbin
1|root@android:/ #
+StuPot for the sake of removing the derped folder do the following
cd /system
chmod 777 addon.d
rm -rf addon.d
See if you get the same error. You shouldn't as 777 is r w x for owner, group and others 
+Josue Rivera The permissions do change to 777 but the phone reboots when I delete it with solid explorer and the file is still there.

I may be best just accepting I can't backup without a new install.
+StuPot grab a log while it happens? I'm curious to see what the hell is breaking. But I agree with you, odds are you will need to wipe everything (maybe even sdcard) duno. This is strange.
+Josue Rivera I ended up doing a full wipe and restoring an old slim6 backup, I'll likely reflash the test build later today or tomorrow so I'll see if it happens again and post results here.

It might be worth adding the slim6 addon.d file doesn't seem to be a directory either, I'll update when I've played a bit.
Bullhead 7.1.1 links are non-existent..? I thought it got added a couple of weeks back?
Ok... I managed to get the links through Safari browser. They don't seem to appear on Chrome though. Bizarre. Excited to get Slim back on my phones. I miss the SlimBean/Kat days. Back when ROM innovation was a thing. I look forward to seeing what you guys do.
+Josue Rivera After a fresh install of slim7 the twrp backup worked fine without the addon.d error, the cause is a mystery but feel free to delete our conversation for tidiness.

+Josue Rivera I too have been facing the "missing native libraries" issue that +Paul Sheehan Jr. has reported since Alpha 0.4. I've reported this along with logs at that time. Please try to fix them. :)
Mirror download please.. Yur server only 10kbps, ."
How can we get Android Pay to work? Currently, I cannot add a credit card. 
I started getting random reboots today and not sure how to repro or capture logs. Any suggestions?
Add a comment...