[ROM][4.4.4][WEEKLIES & STABLE] Official SlimKat (pyramid)

k1ll3r8e

Senior Member
Mar 4, 2011
724
670
123
Delmenhorst
Hey there,
1st THX for this really nice ROM!

But I have question, I miss under Developer Settings the menu entry to revoke authenticated PCs...
This is Android 4.4.4 right?
But I get no authentication dialog if I connect via Adb... Is the Adb secure build-in feature since android 4.2.2 disabled? If so, why have u excluded this feature?

For my understanding its a really big security issue.

Regards,
Sebastian

Sent from my HTC Sensation using XDA Free mobile app
 

m3mmo

Senior Member
Sep 1, 2011
550
101
0
39
Bugojno
Hey there,
1st THX for this really nice ROM!

But I have question, I miss under Developer Settings the menu entry to revoke authenticated PCs...
This is Android 4.4.4 right?
But I get no authentication dialog if I connect via Adb... Is the Adb secure build-in feature since android 4.2.2 disabled? If so, why have u excluded this feature?

For my understanding its a really big security issue.

Regards,
Sebastian

Sent from my HTC Sensation using XDA Free mobile app
Wtf?!?This feature was always present in this ROM but since I installed newest weekly,options are grayed out!

Sent from my HTC Sensation using Tapatalk
 

DJ_Uro_UE

Senior Member
Aug 7, 2008
294
55
0
Užice
I tried Slimkat yesterday, and must say that it is fastest of all kitkat roms for sensation. Only lcd density is maybe too low for my needs, but that can be changed easily. Great rom, great work!
 

LordNerevar

Senior Member
Feb 21, 2012
348
656
0
But I have question, I miss under Developer Settings the menu entry to revoke authenticated PCs...
Wtf?!?This feature was always present in this ROM but since I installed newest weekly,options are grayed out!
I'm not sure if this was ever set in Slimkat builds, but make the following change in build.prop to enable secure adb:
Code:
ro.adb.secure=1
It'll be in my next build.
 

k1ll3r8e

Senior Member
Mar 4, 2011
724
670
123
Delmenhorst
I'm not sure if this was ever set in Slimkat builds, but make the following change in build.prop to enable secure adb:
Code:
ro.adb.secure=1
It'll be in my next build.
Hey there,
THX for the fast response! :)

It worked! So also THX for that hint! ;)

Here a few things i found out:
1. GPU stability (for me) is 100% OK, no crashes/freezes or something else
2. Security issue, "/", "/system", "/data" is always mounted as "RW" better u mount it by default "RO" coz if something get "SU" access it can modify system-files/folders or even wipe the complete phone^^

All other is working fine so far, really great work!

PS: I love the "The Real Dark Slim" :D it's great!

Regards,
Sebastian
 
Last edited:

LordNerevar

Senior Member
Feb 21, 2012
348
656
0
2. Security issue, "/", "/system", "/data" is always mounted as "RW" better u mount it by default "RO" coz if something get "SU" access it can modify system-files/folders or even wipe the complete phone^^
You're welcome. I'm on my unofficial build so maybe that's the difference, but / and /system are RO (snipped output to highlight mentioned partitions):
Code:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,noauto_da_alloc,stripe=64,data=ordered 0 0
Maybe you have a file manager installed that remounts partitions RW?

P.S. /data has to be RW as all apps (user and system) write to it.
P.P.S. Once an app has SU, it can do just about anything it wants (including remounting partitions RW). Never give SU to an app you don't trust completely.
 

k1ll3r8e

Senior Member
Mar 4, 2011
724
670
123
Delmenhorst
You're welcome. I'm on my unofficial build so maybe that's the difference, but / and /system are RO (snipped output to highlight mentioned partitions):
Code:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,noauto_da_alloc,stripe=64,data=ordered 0 0
Maybe you have a file manager installed that remounts partitions RW?

P.S. /data has to be RW as all apps (user and system) write to it.
P.P.S. Once an app has SU, it can do just about anything it wants (including remounting partitions RW). Never give SU to an app you don't trust completely.
Hey there,

i just re-flashed this build here is my shell output:

Code:
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/radio /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/adsp /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/devlog /devlog ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,noatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,stripe=64,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,noauto_da_alloc,stripe=64,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.entwicklerx.macedefence-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
as u can see
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,noatime,nobarrier,data=ordered 0 0
is "RW" also on my other (backup-ed) version, after some restarts the mount is still "RW".

About the file-manager, i have currently no installed. Only the one which is shipped with the build, but this one i have not started until now. I explore my device via my "self made" explorer it uses adb and shell commands. So there is also no remount on my side.

*INFO*
Before i flashed this ROM i formatted all partitions except my sd-card.

Hope this helps :)

Regards,
Sebastian
 

LordNerevar

Senior Member
Feb 21, 2012
348
656
0
as u can see
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,noatime,nobarrier,data=ordered 0 0
is "RW" also on my other (backup-ed) version, after some restarts the mount is still "RW".
I just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
So, either it got fixed in 8.16 or it would appear there is an app you have installed and given SU rights or possibly put in priv-app that is changing /system to RW which I agree is very unsafe.
 
  • Like
Reactions: k1ll3r8e

m3mmo

Senior Member
Sep 1, 2011
550
101
0
39
Bugojno
I just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
So, either it got fixed in 8.16 or it would appear there is an app you have installed and given SU rights or possibly put in priv-app that is changing /system to RW which I agree is very unsafe.
Where did you download official build from?Can you provide a link,'couse I only see weekly 8.16.Thanks

Sent from my HTC Sensation using Tapatalk
 

k1ll3r8e

Senior Member
Mar 4, 2011
724
670
123
Delmenhorst
I just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
So, either it got fixed in 8.16 or it would appear there is an app you have installed and given SU rights or possibly put in priv-app that is changing /system to RW which I agree is very unsafe.
Hey there,

thank u for testing it also! - I also downloaded it again and re-flashed it now all seems be right!
(But i dun understand why this happens... Coz i also only installed the ROM it self and gapps minimal, after that i started the device and configured my G-Axx. Then i got an "playstore-service" update and installed the missing google apps (Maps, Earth, Notes, etc.))

Could it be that there was any cached data (from my old ROM) on any partition i can't format except cache,system,data?

Regards,
Sebastian
 

LordNerevar

Senior Member
Feb 21, 2012
348
656
0
Hey there,
Could it be that there was any cached data (from my old ROM) on any partition i can't format except cache,system,data?
Not impossible, but very unlikely. I'd definitely keep an eye on it and check your bugreport logs if you see it change to RW again. Maybe there will be something noted in there.
 
Last edited: