[Q] Please solve my problem of a2sd darktremor - Android Q&A, Help & Troubleshooting

I'm using CM 7.2 latest, already done partition of sd card by minitool partition (Ext4)
when i type a2sd data in terminal emulation it shows this error message, please reply me as soon as possible what this problem is all about & how can I solve it..
$ export PATH=/data/local/bin:$PATH
$ a2sd datasd
/system/bin/a2sd: line 61: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 65: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 66: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 67: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 68: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 69: /data/dta2sd.log: Permission denied
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
grep: /init.rc: Permission denied
/system/bin/launcha2sd: line 296: /data/.lmdefault: Permission denied
/system/bin/launcha2sd: line 297: /data/.lmdefault: Permission denied
tee: /data/dta2sd.log: Permission denied
__ _____
tee: /data/dta2sd.log: Permission denied
| \ |
tee: /data/dta2sd.log: Permission denied
| | |
tee: /data/dta2sd.log: Permission denied
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 1: Check for SD Card Fix and Implement.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 4: Determine Mount Point.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 5: Set Parameter Variables.
/system/bin/launcha2sd: line 373: /data/dta2sd.log: Permission denied
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 6: Insert CyanogenMod patch.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 8: Resetting Dalvik Cache Partition
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 10: Checking for existence of command parameter
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 11: Check for a2sd help command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 12: Check for a2sd check command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 13: Display version information.
/system/bin/launcha2sd: line 538: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 14: Check for filesystem support.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 15: Mount partition.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 17: Mount Swap.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 48m
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
tee: /data/dta2sd.log: Permission denied
[ ] Launching Apps2SD Start Program with datasd
/system/bin/launcha2sd: line 820: /data/dta2sd.log: Permission denied
/system/bin/starta2sd: line 18: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD in datasd mode
/system/bin/starta2sd: line 61: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[X] No partition available. Data move not available
/system/bin/starta2sd: line 114: /data/.nodata: Permission denied
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[ ] Setting File System Ready property to 1.
/system/bin/starta2sd: line 1211: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 822: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 71: /data/dta2sd.log: Permission denied

Related

[Q] A2SD

I'm using CM 7.2 latest, already done partition of sd card by minitool partition (Ext4)
when i type a2sd data in terminal emulation it shows this error message, please reply me as soon as possible what this problem is all about & how can I solve it..
$ export PATH=/data/local/bin:$PATH
$ a2sd datasd
/system/bin/a2sd: line 61: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 65: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 66: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 67: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 68: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 69: /data/dta2sd.log: Permission denied
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
grep: /init.rc: Permission denied
/system/bin/launcha2sd: line 296: /data/.lmdefault: Permission denied
/system/bin/launcha2sd: line 297: /data/.lmdefault: Permission denied
tee: /data/dta2sd.log: Permission denied
__ _____
tee: /data/dta2sd.log: Permission denied
| \ |
tee: /data/dta2sd.log: Permission denied
| | |
tee: /data/dta2sd.log: Permission denied
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 1: Check for SD Card Fix and Implement.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 4: Determine Mount Point.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 5: Set Parameter Variables.
/system/bin/launcha2sd: line 373: /data/dta2sd.log: Permission denied
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 6: Insert CyanogenMod patch.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 8: Resetting Dalvik Cache Partition
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 10: Checking for existence of command parameter
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 11: Check for a2sd help command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 12: Check for a2sd check command
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 13: Display version information.
/system/bin/launcha2sd: line 538: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 14: Check for filesystem support.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 15: Mount partition.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 17: Mount Swap.
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 48m
tee: /data/dta2sd.log: Permission denied
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
tee: /data/dta2sd.log: Permission denied
[ ] Launching Apps2SD Start Program with datasd
/system/bin/launcha2sd: line 820: /data/dta2sd.log: Permission denied
/system/bin/starta2sd: line 18: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD in datasd mode
/system/bin/starta2sd: line 61: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[X] No partition available. Data move not available
/system/bin/starta2sd: line 114: /data/.nodata: Permission denied
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[ ] Setting File System Ready property to 1.
/system/bin/starta2sd: line 1211: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 822: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 71: /data/dta2sd.log: Permission denied
Did you use the command as su or not?
It should be:
Code:
$su [ENTER]
#a2sd data [ENTER]
That's exactly how it will look in terminal. Obviously don't type the dollar or pound signs and [ENTER] just means hit enter.
Edit: Just noticed the '$' in your command there. You need to run the 'a2sd data' command as su. So follow the steps I typed above and you should be as happy as a monkey with a fresh pile of poo.
Thank for your help....
Dear thank you very very much for your help,
I'm beginner so please guide me some more, I just want to transfer my apps in SD card by using a2sd that's it. I've already partitioned my SD card from fat32 to EXT4 by using "mini tools partition wizard" now I'm having FAT32 partition & EXT4 partition in my sdcard.
I can't see EXT4 partition in my samsung galaxy gio but only can see FAT32(showing 1.2 GB) but rest of 600 MB for EXT4 is not been shown.
AFTER USING YOUR INSTRUCTIONS, I GOT THIS MESSAGE...
$ export PATH=/data/local/bin:$PATH
$ su
# a2sd data
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[-] Checkpoint 13: Display version information.
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a
[-] Checkpoint 14: Check for filesystem support.
[-] Checkpoint 15: Mount partition.
[-] Checkpoint 16: Reset Dalvik if Flag File is present.
[-] Checkpoint 17: Mount Swap.
[-] Checkpoint 18: Display Heap Size.
[ ] Heap Size set to: 48m
[-] Checkpoint 19: Check for start parameter and launch start2sd if needed.
[ ] Launching Apps2SD Start Program with data
[ ] Starting Darktremor Apps2SD in data mode
[X] Invalid command: data
[ ] Setting File System Ready property to 1.
#
now tell me what should I do to transfer my apps to SD card EXT4 partition that is hidden even I have tried titanium backup, still can't see my 600 MB
Well your apps data is on the ext partition.
Now try this command:
Code:
$ su [ENTER]
# /system/bin/a2sd reinstall [ENTER]
Your phone should reboot.
Now go back into terminal and type in this:
Code:
$ su [ENTER]
# /system/bin/a2sd cachesd [ENTER]
Again your phone will reboot. You should have a lot more space on your phones internal memory now. You're done.
If you want to check all this and have a GIU to control it with use THIS app.
One thing you'll notice is that it still looks like the apps are on in the internal memory - they're not. You can check that using Titanium Backup or that app I linked you too. You'll notice the internal memory has a lot more free space and the ext partition should be listed.
Waoooo!!!!!
Thank you very very much for your halp....
now I'm having free memory in internal memory, before reading your this comment I watch a video "how to partition sd card" so I partitioned my SDCARD again (don't know CWM partitioned it in EXT3 or EXT4 format as far I know EXT4 is fast) by using Clockworkrecovery to 500MB & there was also an option of SWAP partiton (didn't any idea what it's about) & I partitioned it to 64MB..
after that I got your message, did what you say & it has done well, now a2sdgui showing that apps are in SD card & delvik cache is in sd card as well
but dear tell me one more thing I've check by titanium backup the "google app" like google mail, youtube etc... are still in SD CARD I though this a2sd will transfer all these apps to SD Card's EXT partition??
By the way thank you very very much indeed for helping me
You're welcome!
For those apps go into settings>applications. There should be a tab at the top that will list what apps are on the sdcard. Click on that and check find those apps, make sure they're not check marked or selected. If they are, simply unselect them and they will be moved to the 'internal' memory (your phone thinks the ext partition is part of the internal memory basically). There are 2 types of a2sd, Google's version and the one you're using. They work very differently and those couple apps you mentioned are using Google's version.
Hopefully that helps. PM me if you have any other questions or just post them in this thread.
now I got some idea when you said (your phone think it's internal memory)
thumbs up for you & definitely if there will be any problem, i'll PM you within no time
Thanks for making me happy

Unpacking and repacking .cpio

I can unpack the ramdisk-recovery.cpio with the ubuntu's archive manager.
But how to repack them ??
Plz help me guys
Sent from my Xperia Mini using xda app-developers app
Try this:
Code:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
I don't want to pack it as cpio.gz
Only .cpio
Sent from my Xperia Mini using xda app-developers app
Got it
Make the .cpio.gz using above command
And then gzip -d ramdisk.cpio.gz
Mods place close the thread
Sent from my Xperia Mini using xda app-developers app
What can I do if I'm getting this error? :crying:
Code:
cpio: /data: Cannot mkdir: Permission denied
cpio: /default.prop: Cannot open: Permission denied
cpio: /dev: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /init: Cannot open: Permission denied
cpio: /init.cm.rc: Cannot open: Permission denied
cpio: /init.goldfish.rc: Cannot open: Permission denied
cpio: /init.huawei.rc: Cannot open: Permission denied
cpio: /init.huawei.usb.rc: Cannot open: Permission denied
cpio: /init.qcom.sh: Cannot open: Permission denied
cpio: /init.rc: Cannot open: Permission denied
cpio: /init.trace.rc: Cannot open: Permission denied
cpio: /init.usb.rc: Cannot open: Permission denied
cpio: /proc: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /sbin: Cannot change mode to rwxr-x---: Operation not permitted
cpio: /sbin/adbd: Cannot open: Permission denied
cpio: ../init: Cannot symlink to `/sbin/ueventd': Permission denied
cpio: ../init: Cannot symlink to `/sbin/watchdogd': Permission denied
cpio: /sys: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /system: Cannot mkdir: Permission denied
cpio: /ueventd.goldfish.rc: Cannot open: Permission denied
cpio: /ueventd.huawei.rc: Cannot open: Permission denied
cpio: /ueventd.rc: Cannot open: Permission denied
Mlopik said:
What can I do if I'm getting this error? :crying:
Code:
cpio: /data: Cannot mkdir: Permission denied
cpio: /default.prop: Cannot open: Permission denied
cpio: /dev: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /init: Cannot open: Permission denied
cpio: /init.cm.rc: Cannot open: Permission denied
cpio: /init.goldfish.rc: Cannot open: Permission denied
cpio: /init.huawei.rc: Cannot open: Permission denied
cpio: /init.huawei.usb.rc: Cannot open: Permission denied
cpio: /init.qcom.sh: Cannot open: Permission denied
cpio: /init.rc: Cannot open: Permission denied
cpio: /init.trace.rc: Cannot open: Permission denied
cpio: /init.usb.rc: Cannot open: Permission denied
cpio: /proc: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /sbin: Cannot change mode to rwxr-x---: Operation not permitted
cpio: /sbin/adbd: Cannot open: Permission denied
cpio: ../init: Cannot symlink to `/sbin/ueventd': Permission denied
cpio: ../init: Cannot symlink to `/sbin/watchdogd': Permission denied
cpio: /sys: Cannot change mode to rwxr-xr-x: Operation not permitted
cpio: /system: Cannot mkdir: Permission denied
cpio: /ueventd.goldfish.rc: Cannot open: Permission denied
cpio: /ueventd.huawei.rc: Cannot open: Permission denied
cpio: /ueventd.rc: Cannot open: Permission denied
Click to expand...
Click to collapse
You need to do this on a filesystem that supports symlinks (eg: FAT32 won't work, but NTFS and ext2/3/4 are okay)
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
singh_dd93 said:
I don't want to pack it as cpio.gz
Only .cpio
Sent from my Xperia Mini using xda app-developers app
Click to expand...
Click to collapse
Just do
Code:
find . | cpio -o > ramdisk.cpio
You need to do this on a filesystem that supports symlinks (eg: FAT32 won't work, but NTFS and ext2/3/4 are okay)
Click to expand...
Click to collapse
A really good point! I was stuck for a day and you let me go, man!

[Q] permission problem on 6 files in extract-files.sh

Running extract-files.sh to get proprietary files. All is good apart from the following files
failed to copy '/system/etc/firmware/wcnss.b00' to '../../../vendor/Samsung/express/proprietary/wcnss.b00': Permission denied
failed to copy '/system/etc/firmware/wcnss.b01' to '../../../vendor/Samsung/express/proprietary/wcnss.b01': Permission denied
failed to copy '/system/etc/firmware/wcnss.b02' to '../../../vendor/Samsung/express/proprietary/wcnss.b02': Permission denied
failed to copy '/system/etc/firmware/wcnss.b04' to '../../../vendor/Samsung/express/proprietary/wcnss.b04': Permission denied
failed to copy '/system/etc/firmware/wcnss.b05' to '../../../vendor/Samsung/express/proprietary/wcnss.b05': Permission denied
failed to copy '/system/etc/firmware/wcnss.mdt' to '../../../vendor/Samsung/express/proprietary/wcnss.mdt': Permission denied
Tried running the script as root - no difference. Using Rom Lite Toolbox and the Root Browser they are listed as rwxrwxrwx 0777
Tried running CHMOD -R 777 across the directory and an individual file. Get told it is a read only.
Any ideas?
Bazzan

selinux denies busybox although selinux is set to permissive?!

Device-info:
Phone: Sony Xperia Z1
Model number: C6903
Android version: 5.1.1
Build Number: 14.6.A.1.236
Rooted and BusyBox installed (Play Store Version!!!)
I have formatted an SD-Card to an ext4-filesystem and put another Linux on it.
After mounting the filesystem and files without problems I want to execute:
Code:
chroot /data/local/mnt /bin/bash
with /data/local/mnt is the Linux root-folder.
Execute the line above leads to the message:
Code:
chroot: can't execute '/bin/bash': Permission denied
I have checked the permission of /bin/bash and also of /data/local/mnt and remounted nearly every path which are related to that folder with exec and rw permission. So maybe you know some special rights-associated files or folders I forgot, but I think the problem is something else...
After readed that some of the Linux-on-Android project-users had some trouble with executing the init.sh because of selinux I set it to permissive:
Code:
setenforce 0
and checked it:
Code:
[email protected]:/ # getenforce
Permissive
(Of course) chroot does not work. So I checked the message buffer of the kernel for selinux-avc-deny-messages and BINGO:
Code:
[email protected]:/ # dmesg | grep denied
...
<36>[58575.652383] type=1400 audit(1470337082.042:10188): avc: denied { read } for pid=18553 comm="busybox" name="mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric"
<36>[58575.653740] type=1400 audit(1470337082.042:10189): avc: denied { open } for pid=18553 comm="busybox" name="mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric"
<36>[58575.655002] type=1400 audit(1470337082.042:10190): avc: denied { ioctl } for pid=18553 comm="busybox" path="/dev/block/mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric"
These are just 3. You can have some more if you want! So 1. QUESTION:
Why does selinux denies something when getenforce returns Permissive???
But I thought first that could be fixed anyway by allowing all these denied permissions with:
Code:
supolicy --live "allow source_class target_class permission_class permission"
FOR EXAMPLE:
Code:
supolicy --live "allow ric rootfs file execute_no_trans"
which returns:
Code:
Patching policy ...
-allow:ric:rootfs:file:execute_no_trans=ok
- Success
Well (of course) it did not work AND I get a denied message for the exact same case for a bunch of cases.
So 2. QUESTION:
Why does allowing policies not change policies to be allowed???
(Of course) I am not 100% sure if the denial of executing chroot is related to selinux and it would be very easy to find it out if I could just set it to permissive.... So 3. QUESTION:
How to solve this problem?
Well (Of course) I could take a hammer smash my device... I think that works well.
I appreciate your Help!

Unable to delete old TWRP backup as root

Hi
Code:
[email protected]_mecdug:/storage/emulated/0/TWRP # ls -las
total 12
-rw-rw---- root sdcard_rw 956 2017-12-30 14:59 .twrps
drwxrwx--x root sdcard_rw 2017-12-28 16:17 2015-04-12--20-30-48_LRX22G_release-keys
drwxrwx--x root sdcard_rw 2017-12-30 14:23 BACKUPS
m -rf 2015-04-12--20-30-48_LRX22G_release-keys/ <
rm: data.ext4.win.md5: Permission denied
rm: system.ext4.win.md5: Permission denied
rm: boot.emmc.win: Permission denied
rm: data.info: Permission denied
rm: boot.emmc.win.md5: Permission denied
rm: recovery.log: Permission denied
rm: data.ext4.win: Permission denied
rm: system.ext4.win: Permission denied
rm: system.info: Permission denied
1|[email protected]_mecdug:/storage/emulated/0/TWRP # lsattr
lsattr: reading ./BACKUPS: Inappropriate ioctl for device
lsattr: reading ./2015-04-12--20-30-48_LRX22G_release-keys: Inappropriate ioctl for device
WTF?
Try
sudo m -rf 2015-04-12--20-30-48_LRX22G_release-keys/
Or may be these files is locked by other process

Categories

Resources