Whats the changelog?New build up in the testers section. Kernel changes mostly
Whats the changelog?New build up in the testers section. Kernel changes mostly
251de68ef67e50b23a44b081692802940a9752fc msm: flash: Use low-power flash when battery is lowWhats the changelog?
Which one?I did not yet flash anything.Which build you want us to test,just sayOf those flashed that build, need feedback regarding stability, specially gpu and otg wise
Well,I have it.Just tap the build number 7-8 times and you will have dev options from.which you can then select root options.Coming from 8.4
Just flashed 8.14 + GApp Mini --> No Root and No Developer/Advanced section in the Settings Menu to Enable / Disable Super SU
I'm flashing 8.12 now
You are welcomeLove you :*
Thanx
Wtf?!?This feature was always present in this ROM but since I installed newest weekly,options are grayed out!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
But I have question, I miss under Developer Settings the menu entry to revoke authenticated PCs...
I'm not sure if this was ever set in Slimkat builds, but make the following change in build.prop to enable secure adb:Wtf?!?This feature was always present in this ROM but since I installed newest weekly,options are grayed out!
ro.adb.secure=1
Hey there,I'm not sure if this was ever set in Slimkat builds, but make the following change in build.prop to enable secure adb:It'll be in my next build.Code:ro.adb.secure=1
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):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^^
[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
Hey there,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):Maybe you have a file manager installed that remounts partitions RW?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
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.
[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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,noatime,nobarrier,data=ordered 0 0
I just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:as u can see
is "RW" also on my other (backup-ed) version, after some restarts the mount is still "RW".Code:/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/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
Where did you download official build from?Can you provide a link,'couse I only see weekly 8.16.ThanksI just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:
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.Code:/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
That's what I meant - official weekly. Pyramid doesn't have any "stable" builds as of yet.Where did you download official build from?Can you provide a link,'couse I only see weekly 8.16.Thanks
Hey there,I just clean flashed Official 8.16 by itself (no gapps or anything else) and I'm seeing the following via adb shell:
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.Code:/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,nobarrier,data=ordered 0 0
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.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?