Database Develop

Rooting the Captivate using the command line under Linux

I've tried just about every automated/one click/whatever method for rooting my spiffy new Captivate, and they all failed for one reason or another. I finally got it to work using adb & the command line. Here's how I did it. Oh, and before someone asks "Why didn't you just use Windoze?", it's because all my computers run Linux so that's not an option.
STANDARD DISCLAIMER: If you root your phone, the ceiling will collapse on your head and your family will die. No one should ever follow these instructions. In fact, I should probably be banned for even posting them.
MY SETUP:
Ubuntu 11.04 (natty)
Samsung Captivate i897, stock, KB2
AT&T
1. Download SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
I used 1.9.5, only because another poster told me he had successfully rooted his Captivate using that specific version. This may also work with the files from a newer version; I don't see why it wouldn't.
2. Extract everything
Duh.
3. Put adblinux, psneuter, busybox, su-v2, and Superuser.apk in one directory.
I don't know that it has to specifically be su-v2, but that one worked for me, so huzzah.
4. Put the phone in USB debug mode; plug it in to your computer.
Settings -> Applications -> Development (check the box for USB debugging). Linux users need no drivers.
5. Open a terminal, cd into wherever you extracted the SOC files.
6. Let's dance:
Code:
./adblinux push psneuter /data/local/tmp
./adblinux push su-v2 /data/local/tmp
./adblinux push busybox /data/local/tmp
./adblinux shell
$ cd /data/local/tmp
Make everything you just pushed over executable:
Code:
$ chmod 6755 psneuter
$ chmod 6755 su-v2
$ chmod 6755 busybox
Run the exploit:
Code:
$ /data/local/tmp/psneuter
Running psneuter successfully kicked me out of the shell, so go back. You should also notice when you re-enter the shell that your prompt has changed from "$" to "#", indicating psneuter was successful. This also means you have root privileges, at least temporarily, for the rest of your work.
Code:
./adblinux shell
# mount
"mount" should spit out something that looks like this:
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs ro,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepa ge=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
On your phone, that output might look a little different, but you're looking for the line in BOLD. In the example above, "/dev/block/stl9" is the mount point for "/system". If "mount" gives you a different mount point, then use that in the commands below. The stuff after that tells you the properties of "/system"; "ro" is the one we're concerned with. That tells us that "/system" is mounted as "read-only". We need to change that so we can move some files over.
Code:
# mount -o remount,rw /dev/block/stl9 /system
"/system" is now writable. Let's move some files over.
Code:
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin
# chmod 6755 /system/xbin/busybox
# /data/local/tmp/busybox chown 0.2000 /system/xbin/busybox
A functional copy of busybox now resides at /system/xbin, so from now on you can just call it with "busybox" instead of having to use the full path to the one we pushed over earlier.
Code:
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# chmod 6755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
IMPORTANT: Do not leave your "/system" mounted as read-write; change it back and exit the shell:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
You should be back at your basic Linux command prompt now. Install the Superuser app.
Code:
./adblinux install Superuser.apk
7. Reboot your phone
When everything loads back up, you should have root privileges. Update BusyBox from the market. If everything went according to plan, when you try to install BusyBox you should get a prompt from the Superuser app asking if you want to grant the BusyBox installer superuser privileges. If so, everything worked the way it was supposed to, and you're now a 1337 [email protected]><0r or something.
8. Troubleshooting
Mine didn't take the first time for some reason. After reboot, I installed BusyBox and Titanium Backup, both of which failed to get root privileges. I went back into the phone with adblinux, remounted /system as rw, again set the privileges for "/system/xbin/su" to 6755, then remounted /system as ro and rebooted. It took the second time, so I'm assuming I may have typed something wrong.
Another thing I was keen to try is installing the Superuser app FIRST, then running the hacks to root the phone. The phone does not need to be rooted to install Superuser, only for it to work as designed. I am curious if "SU->root->reboot" would work the first time, instead of "Root->SU->Reboot->Re-Root->Reboot", which is how it's been working now. If I happen to reinstall and try this again, I'll update. If anyone else gives it a whirl, post a comment and I'll update accordingly.
I hope this helps someone else. Please comment below with questions/criticisms/flames.

Thanks bro this is a very handy guide i to use only linux and it kills me how many people say ehh just install windows it easier BLAAA is what i say great work keep it coming...

tkienzle said:
Thanks bro this is a very handy guide i to use only linux and it kills me how many people say ehh just install windows it easier BLAAA is what i say great work keep it coming...
Click to expand...
Click to collapse
I'm with you. I HATE hearing "just use Odin" or "you can buy a copy of Windoze for not much $$$!" If I wanted Windoze, I'd be using it already. If I could use Odin, I'd probably just follow the directions for that and not be asking questions about Heimdall.

+1 thanks. been running linux since 2002, wasn't looking forward to using a friends computer just to root a phone.

New Radio install Mod?

EDIT: This does work for us.. Confirmed! Screenshot page 2.
Thanks @Turge for the help with this. Great Mod!!
Turge has posted a way to change radios on the OneX+ which is still s-on. Does anyone with some dev smarts know if this procedure could be ported to the one? Thought it was interesting and wanted to share. Hopefully it helps. Turge's original thread for One X+ http://forum.xda-developers.com/showthread.php?t=2240968
Turge said:
Description:
This mod enables you to switch radios without actually flashing the radio partition (which requires S-OFF).​
How does it work?
The mod flashes the radio files to /system/mdm. On boot up, if the radio exists in this location, the radio partition will be unmounted and a symbolic link will be created from /firmware/mdm to /system/mdm.​
Boot.img Specifications:
Unsecured
init.d support
Requirements:
Unlocked bootloader
Custom boot.img with init.d support (see Downloads below)
Busybox (see Downloads below)
New AT&T (1.19.502.1) or Telus (1.20.661.1) build (Other builds have not been qualified yet)
See my thread: http://forum.xda-developers.com/showthread.php?p=40450319#post40450319
Install:
Download and flash custom boot.img with init.d support for your current build
Example:
Code:
fastboot flash boot c:\boot-1.20.661.1.img
Reboot to Recovery
Flash Busybox zip
Flash desired radio zip
Reboot
Profit
Downloads:
Custom boot.img with init.d support:
AT&T 1.19.502.1: http://www.androidfilehost.com/?fid=22909751817930309 (5MB)
Telus 1.20.661.1: http://www.androidfilehost.com/?fid=22909751817930305 (5MB)​
Busybox Install:
Busybox_Install.zip: http://www.androidfilehost.com/?fid=22909751817930298 (2MB)​
Radios:
AT&T/Telus 1.09.55.17: http://www.androidfilehost.com/?fid=22909751817930300 (19MB)
AT&T 2.14.55.01: http://www.androidfilehost.com/?fid=22909751817930299 (19MB)
Telus 2.15.55.11: http://www.androidfilehost.com/?fid=22909751817930301 (19MB)​
Click to expand...
Click to collapse

nugzo said:
Turge has posted a way to change radios on the OneX+ which is still s-off.. Does anyone with some dev smarts know if this procedure could be ported to the one? Thought it was interesting and wanted to share. Hopefully it helps.
http://forum.xda-developers.com/showthread.php?t=2240968
Click to expand...
Click to collapse
Send me the boot.img and I'll let you know..

Turge said:
Send me the boot.img and I'll let you know..
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/10203258/boot.img Thanks for quick reply. Guess i shoulda asked you first A
Are you just on the ball like that or do you get a notification when someone posts your name lol
Ahh the quote probably did it

nugzo said:
https://dl.dropboxusercontent.com/u/10203258/boot.img Thanks for quick reply. Guess i shoulda asked you first A
Are you just on the ball like that or do you get a notification when someone posts your name lol
Ahh the quote probably did it
Click to expand...
Click to collapse
Shouldn't be a problem. I can create something, but need some more info:
1. Which radio do you want to flash? Do you have a link to the firmware? Maybe the OTA? All I'm looking for is the mdm*.img file.
2. Does your boot.img have init.d support? I can update this one and add init.d support if desired.
3. If I'm repackaging the boot.img, how does it get flashed? Can it be flashed via recovery or only through fastboot?
4. Do you need a busybox installer? Busybox/init.d is required for my mod
5. Can you send me an update-binary from the META-INF folder of a working custom ROM? I don't want to download a 1GB zip just for it.
Turge

We want T-Mobile radio! I want to see if a T-Mobile radio will enable penta band on AT&T or dev edition phones.
Sent from my HTC One X

ECEXCURSION said:
We want T-Mobile radio! I want to see if a T-Mobile radio will enable penta band on AT&T or dev edition phones.
Sent from my HTC One X
Click to expand...
Click to collapse
Do you have a link to the ruu?

Turge said:
Shouldn't be a problem. I can create something, but need some more info:
1. Which radio do you want to flash? Do you have a link to the firmware? Maybe the OTA? All I'm looking for is the mdm*.img file.
2. Does your boot.img have init.d support? I can update this one and add init.d support if desired.
3. If I'm repackaging the boot.img, how does it get flashed? Can it be flashed via recovery or only through fastboot?
4. Do you need a busybox installer? Busybox/init.d is required for my mod
5. Can you send me an update-binary from the META-INF folder of a working custom ROM? I don't want to download a 1GB zip just for it.
Turge
Click to expand...
Click to collapse
boot.img gets flashed through fastboot. I dont have any particular radio in mind yet, just wanted to share your MOD. I am having some LTE speed issues but not sure if international radio will work for me, Probably not. I'm in the US (AT&T) and all the custom roms and kernels are from Non-US bases. This is a unique phone, ATT and International can use the same roms finally. (unlike one x+)
Yes the kernel has init.d support. Not sure about busy box.
This is the rom i'm using atm. But If you want to test anything i can change roms to whatever you request. Here is the update_binary https://dl.dropboxusercontent.com/u/10203258/update-binary
And here is Mike1986 firmware package from the latest wwe ruu. My CID is not supported so cant flash the firmware package. I think that's everything you needed..
Well on the rom i'm using i guess kernel can flash through recovery.. this is from the rom details: "Kernels get flashed through recovery (thanks xHausx)"

Turge said:
Do you have a link to the ruu?
Click to expand...
Click to collapse
Unfortunately I couldn't find an RUU. :-/ but it seems Tachi91 is under the impression that this will not enable all bands anyway. I just thought it was worth a try.

nugzo said:
boot.img gets flashed through fastboot. I dont have any particular radio in mind yet, just wanted to share your MOD. I am having some LTE speed issues but not sure if international radio will work for me, Probably not. I'm in the US (AT&T) and all the custom roms and kernels are from Non-US bases. This is a unique phone, ATT and International can use the same roms finally. (unlike one x+)
Yes the kernel has init.d support. Not sure about busy box.
This is the rom i'm using atm. But If you want to test anything i can change roms to whatever you request. Here is the update_binary https://dl.dropboxusercontent.com/u/10203258/update-binary
And here is Mike1986 firmware package from the latest wwe ruu. My CID is not supported so cant flash the firmware package. I think that's everything you needed..
Well on the rom i'm using i guess kernel can flash through recovery.. this is from the rom details: "Kernels get flashed through recovery (thanks xHausx)"
Click to expand...
Click to collapse
Give this a shot: http://www.androidfilehost.com/?fid=22909751817930629 (23MB)
If it doesn't change the frmware version, run "adb shell busybox sh /system/etc/init.d/00firmware" and post the output.
You can also post the output of "adb shell mount"
To get rid of the mod, delete "/system/etc/init.d/00firmware" or "/system/mdm" or both.

Turge said:
Give this a shot: http://www.androidfilehost.com/?fid=22909751817930629 (23MB)
If it doesn't change the frmware version, run "adb shell busybox sh /system/etc/init.d/00firmware" and post the output.
You can also post the output of "adb shell mount"
To get rid of the mod, delete "/system/etc/init.d/00firmware" or "/system/mdm" or both.
Click to expand...
Click to collapse
Ok thanks so much. Just gave it a shot. Radio version did not change. Ran command adb shell busybox sh /system/etc/init.d/00firmware and got this.
Code:
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell busybox sh /system/etc/in
it.d/00firmware
sh: applet not found
And adb shell mount
Code:
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p35 /system ext4 ro,relatime,nobarrier,data=ordered 0 0
/dev/block/mmcblk0p37 /data ext4 rw,nosuid,nodev,noatime,discard,nobarrier,noaut
o_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,nosuid,nodev,noatime,nobarrier,data=ordered
0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,nosuid,nodev,noatime,nobarrier,errors=cont
inue,data=ordered 0 0
tmpfs /data/qcks tmpfs rw,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
D:\Storage\Android Stuff\ASDK\platform-tools>

2 more:
adb shell busybox sh
adb shell ls -l /system/etc/init.d
Sent from my HTC One X using Tapatalk 2

Turge said:
2 more:
adb shell busybox sh
adb shell ls -l /system/etc/init.d
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell busybox sh
sh: applet not found
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell ls -l /system/etc/init.d
-rwxrwxrwx root shell 621 2008-08-01 08:00 00firmware
-rwxrwxrwx root shell 2572 2008-08-01 08:00 01renovate
-rwxrwxrwx root shell 1878 2008-08-01 08:00 85sqlite
-rwxrwxrwx root shell 598 2008-08-01 08:00 90initdtest
-rwxrwxrwx root shell 1601 2008-08-01 08:00 99pure
-rwxrwxrwx root shell 66 2008-08-01 08:00 99sysctl
D:\Storage\Android Stuff\ASDK\platform-tools>
Edit: just realized i didnt have busybox installed. Installing now and gonna reflash mod.
Same result.

Turge said:
2 more:
adb shell busybox sh
adb shell ls -l /system/etc/init.d
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Is the busybox in the playstore the same as the one you posted in your mod thread? i had to use the one from play store because mid check failed during aroma install for the one in your thread.

Turge said:
Give this a shot: http://www.androidfilehost.com/?fid=22909751817930629 (23MB)
If it doesn't change the frmware version, run "adb shell busybox sh /system/etc/init.d/00firmware" and post the output.
You can also post the output of "adb shell mount"
To get rid of the mod, delete "/system/etc/init.d/00firmware" or "/system/mdm" or both.
Click to expand...
Click to collapse
Ok after manually pushing the busybox from your installer to xbin.. i get this when i run the busybox commands
Code:
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell busybox sh
/system/bin/sh: busybox: can't execute: Permission denied
D:\Storage\Android Stuff\ASDK\platform-tools>adb shell busybox sh /system/etc/in
it.d/00firmware
/system/bin/sh: busybox: can't execute: Permission denied

Gonna wipe everything and start from scratch.
And if it's successful am i looking for the build number to change or the baseband numbers to change?
Edit. Tried everything again and baseband nor build number changed

nugzo said:
Gonna wipe everything and start from scratch.
And if it's successful am i looking for the build number to change or the baseband numbers to change?
Click to expand...
Click to collapse
Try running adb shell and typing "su" then run the commands above without the "adb shell" part
Sent from my HTC One X using Tapatalk 2

Turge said:
Try running adb shell and typing "su" then run the commands above without the "adb shell" part
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
getting same thing. applet not found. I installed busybox from playstore. If i push your busybox to the xbin folder i get the permision denied response when running the commands.

nugzo said:
getting same thing. applet not found. I installed busybox from playstore. If i push your busybox to the xbin folder i get the permision denied response when running the commands.
Click to expand...
Click to collapse
Tell me your radio version before applying the mod. You need to find a different radio to verify if it works. Meanwhile, try this:
adb shell
$ su
# sh /system/etc/init.d/00firmware
Ignore the $ and # signs
Sent from my HTC Flyer P512 using xda app-developers app

Namit1994 said:
Tell me your radio version before applying the mod. You need to find a different radio to verify if it works. Meanwhile, try this:
adb shell
$ su
# sh /system/etc/init.d/00firmware
Ignore the $ and # signs
Sent from my HTC Flyer P512 using xda app-developers app
Click to expand...
Click to collapse
My radio should be different, ATT radio 4A 14.3250.13_10.33.1150.01L
[email protected]/# /system/etc/init.d/00firmware
/system/etc/init.d/00firmware
00firmware
**VENOM: mdmFolder: /system/mdm
**VENOM: Flag File: /system/mdm/radiover.cfg
**VENOM: Mounting /system/mdm to /firmware/mdm
[email protected]/#

nugzo said:
My radio should be different, ATT radio 4A 14.3250.13_10.33.1150.01L
[email protected]/# /system/etc/init.d/00firmware
/system/etc/init.d/00firmware
00firmware
**VENOM: mdmFolder: /system/mdm
**VENOM: Flag File: /system/mdm/radiover.cfg
**VENOM: Mounting /system/mdm to /firmware/mdm
[email protected]/#
Click to expand...
Click to collapse
Looks like the script ran but but the radio from Turge's package is also 4A 14.3250.13 (same as your AT&T). We cannot be sure if it worked because the radio is the same version anway. We need to mount an older radio with a different number.
---------- Post added at 11:53 PM ---------- Previous post was at 11:43 PM ----------
Turge said:
Do you have a link to the ruu?
Click to expand...
Click to collapse
Turge, it seems your package uses the same radio that nugzo's device already has. Would you mind creating a new package from an older radio with a different version number?
This is the link to the RUU with a different radio version (4A.13.3231.20 instead of 4A.14.3250.13):
http://www.androidfiles.org/ruu/sec...0_10.30.1131.05_release_309365_signed_2_4.exe

Permission Denied writing to SDcard

When copying files to say /sdcard/Download on my pc it just freezes
When using adb it says permission denied
If i delete the folder or files inside the folder they vanish from view on my pc, but when I replug in my phone they appear again
When using adb shell to try and remove the folder i get this
Code:
127|[email protected]:/sdcard # rmdir Download
rmdir Download
rmdir failed for Download, Directory not empty
255|[email protected]:/sdcard # rm -rf Download
rm -rf Download
rm failed for Download, Permission denied
255|[email protected]:/sdcard #
Code:
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=
1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,gr
oup_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,use
r_id=1023,group_id=1023,default_permissions,allow_other 0 0
anyone know whats up?
Edit: Its only the download folder, all other folders and new ones I create work fine. But I want to remove the contents of download because it has a few roms in it taking up space
Edit2: I just wiped internal storage in TWRP and that fixed it. Still confused why this would happen though.

Yes you are not using the correct file designation - use the search option this has been asked a few dozen times in the past

[q] [help]couldn't install in usb storage or sd card

I tried to install an app from PlayStore and got an error message: COULDN'T INSTALL IN USB STORAGE OR SD CARD.
After logcat I found these Errors:
Error creating imagefile(Read-only file system)
ASEC imagefile creation failed(Read-only file system)
Failed to create container smdl2tmp1
How do I fix this problem. Please help me.
I forgot to mention my device details, it's I9070 running CM-11 by TeamCanjica. I do not have an external SD card.
The error occured when i tried to install this app: https://play.google.com/store/apps/details?id=com.wordsmobile.soccerkicks
It also happens with some other apps.
PS:Since the logcat showed read only error I remounted asec with 0777 permissions and then i was able to install the app,
but the app vanished after a restart. I think it's because asec by default is mounted as tmpfs type filesystem. I don't know how to proceed now.

This happened to me too one time, resolved with wipe data/factory reset
Inviato dal mio GT-I9070

Tesla-MADAL93 said:
This happened to me too one time, resolved with wipe data/factory reset
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
Thanks for the info, but i would prefer to not lose my data or spend time backing it up.
I am looking for an alternate way to fix this.
I forgot to mention my device details, it's I9070 running CM-11 by TeamCanjica.
PS:Since the logcat showed read only error I remounted asec with 0777 permissions and then i was able to install the app,
but the app vanished after a restart. I think it's because asec by default is mounted as tmpfs type filesystem. I don't know how to proceed now.

UNiQ!0 said:
Thanks for the info, but i would prefer to not lose my data or spend time backing it up.
I am looking for an alternate way to fix this.
I forgot to mention my device details, it's I9070 running CM-11 by TeamCanjica.
PS:Since the logcat showed read only error I remounted asec with 0777 permissions and then i was able to install the app,
but the app vanished after a restart. I think it's because asec by default is mounted as tmpfs type filesystem. I don't know how to proceed now.
Click to expand...
Click to collapse
.android_secure folder is linked to ASEC, you can make an init.d script to remount it as 0777 at every boot
Code:
#!/system/bin/sh
#
mount -o remount,rw /mnt/asec
chmod 0777 /mnt/asec
Save it as 05asecrw for example, apply 0755 permission and owner 0 group 2000

Tesla-MADAL93 said:
.android_secure folder is linked to ASEC, you can make an init.d script to remount it as 0777 at every boot
Code:
#!/system/bin/sh
#
mount -o remount,rw /mnt/asec
chmod 0777 /mnt/asec
Save it as 05asecrw for example, apply 0755 permission and owner 0 group 2000
Click to expand...
Click to collapse
Tried it. Didn't work.
chmod 0777 /mnt/asec didn't change asec's mode to 777.
/mnt/asec is mounted by deafult (by init.rc) as tmpfs filesystem with mode=0755 and gid=1000

UNiQ!0 said:
Tried it. Didn't work.
chmod 0777 /mnt/asec didn't change asec's mode to 777.
/mnt/asec is mounted by deafult (by init.rc) as tmpfs filesystem with mode=0755 and gid=1000
Click to expand...
Click to collapse
When android boots yes, once booted you can change its permission, maybe you can do something with Smanager or Tasker/Automagic

Can someone fix my ****ing ZIP for me?

No matter what I do, it won't flash. Magisk will flash it but it does not function and creates two directories under /Magisk, Magisk-SSH? and Magisk-SSH??, and in TWRP it produces a new error no matter what I do. Even leaving the config.sh and module.prop completly alone and only adding the files to the directory the ****ing zip wont flash.
Download link

Pls upload to another site man,,can't download the file because of adfly..
Sent from my 2014813 using Tapatalk

try changing the permission to 755 instead of 777 for the binaries on your config.sh ... and zip it on sub folder of your module, dont do it on the root folder ... it wont be flashed that way bcoz wrong root folder. attached some ss for how to zip it.
Code:
set_perm $MODPATH/system/bin/scp 0 2000 0755 u:object_r:zygote_exec:s0
set_perm <filename> <owner> <group> <permission> <contexts> (default: u:object_r:system_file:s0)
or
set_perm_recursive $MODPATH/system/bin 0 0 0755 0755
set_perm_recursive <dirname> <owner> <group> <dirpermission> <filepermission> <contexts> (default: u:object_r:system_file:s0)
hope that help :good:

adewisman said:
try changing the permission to 755 instead of 777 for the binaries on your config.sh ... and zip it on sub folder of your module, dont do it on the root folder ... it wont be flashed that way bcoz wrong root folder. attached some ss for how to zip it.
Code:
set_perm $MODPATH/system/bin/scp 0 2000 0755 u:object_r:zygote_exec:s0
set_perm <filename> <owner> <group> <permission> <contexts> (default: u:object_r:system_file:s0)
or
set_perm_recursive $MODPATH/system/bin 0 0 0755 0755
set_perm_recursive <dirname> <owner> <group> <dirpermission> <filepermission> <contexts> (default: u:object_r:system_file:s0)
hope that help :good:
Click to expand...
Click to collapse
I dropped the project because the binaries don't work anyway. I placed them into /Magisk manually (basically doing the zip's job manually) along with the module.prop but calling them produces various errors. I cross-compiled them for ARM64 so they are the correct architecture.