I flash rom combination successed. When i use adb shell mkdir/data/vendor/.... Error permission denie.
Please help. Thanks!
Related
I use this tutorial and have got till I have to tipe in emulator -
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 but all I get is error of=/dev/block/mmcblk0p18/dev/block/mmcblk0p18: cannot open for write: Permission denied. Any ideas why?
Hi,
I tried to load a rom.zip file on to sdcard using adb push . It returned a permission denied error.
I did not see the file in the sdcard so I know the file not loaded.
Other adb command work just fine.
What did I do wrong ?
Thanks for your help
Boot into recovery before issuing your adb commands.
soupmagnet said:
Boot into recovery before issuing your adb commands.
Click to expand...
Click to collapse
Thanks. It works.
Can I do the same using TWRP ? what function of Twrp will do the same as adb push ?
Thanks
You can "Mount" your sdcard to USB.
Hi,
my M9 is s-off and rooted + TWRP. So i want to profit from the build.prop for the Cam. So I try to add the lines on my build.prop with root explorer, but I cant r/w /system . And if I uninstall System-Apps like facebook/g+ for HTC Sense and the stock fonts with systemapp remover and reboot, they still there and are not removed.
Try flashing the newest beta super su in twrp
do net helped
*$M3RT$* said:
do net helped
Click to expand...
Click to collapse
Using twrp 2864?
2.48? This is supposedly the only one that gives write access on m9.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Yes trwp 2.8.6.4 and SuperSU v2.48B. But same issues
You relocked didnt you
I need to relock??
No you don't need to relock. He was asking if you relocked.
I do not relocked it, but set it to "locked" with scotty1223' guide
Code:
E:\adb>adb shell
[email protected]_himauhl:/ $ su
su
[email protected]_himauhl:/ # mount -o rw
mount: Read-only file sys
255|[email protected]_himauhl:/ #
*$M3RT$* said:
I do not relocked it, but set it to "locked" with scotty1223' guide
Code:
E:\adb>adb shell
[email protected]_himauhl:/ $ su
su
[email protected]_himauhl:/ # mount -o rw
mount: Read-only file sys
255|[email protected]_himauhl:/ #
Click to expand...
Click to collapse
You need to unlock your bootloader again then
ok, when I have write permisson, can I lock it again? Or change it back to read-only?
bootloader unlocked:
Code:
E:\adb>adb remount
remount of system failed: Permission denied
remount failed
*$M3RT$* said:
ok, when I have write permisson, can I lock it again? Or change it back to read-only?
bootloader unlocked:
Code:
E:\adb>adb remount
remount of system failed: Permission denied
remount failed
Click to expand...
Click to collapse
Everytime you want to write to system you will need to unlock again, you may as well leave it unlocked until whatever time you decide to move on to the next device... or use a custom kernel, presumably that is where it is set.
With stock kernel locked means system stays R only for whatever reason, even with a custom ROM or previously modified system... small perk of .17 iirc.
Trying to install openvpn, installer fails, have resorted to trying to install it manually, unzipping apk and taking openvpn-2.1.1-static-xbin asset, copying that to system\xbins , but when I try and run it I get the error
error: only position independent executables (PIE) are supported.
Can anyone help with how to fix this?
Loading the OpenVPN settings says all prerequisites are there, but launching any configs (PIA OpenVPN's) produces this error in the log.
Many thanks
Andy
andywuk said:
Trying to install openvpn, installer fails, have resorted to trying to install it manually, unzipping apk and taking openvpn-2.1.1-static-xbin asset, copying that to system\xbins , but when I try and run it I get the error
error: only position independent executables (PIE) are supported.
Can anyone help with how to fix this?
Loading the OpenVPN settings says all prerequisites are there, but launching any configs (PIA OpenVPN's) produces this error in the log.
Many thanks
Andy
Click to expand...
Click to collapse
Check permissions
Enviado desde mi A0001 mediante Tapatalk
andywuk said:
error: only position independent executables (PIE) are supported.
Click to expand...
Click to collapse
Whatever you are trying to run is too old. It needs to be updated for Lollipop. Lollipop started enforcing that all binaries be compiled with PIE.
Thanks for that rbox, it seems it was an old binary, found a newer one on thread
http://forum.xda-developers.com/spr...nvpn-binary-lollipop-s5-t3086672#post64696367
took that, installed manually
adb shell
su
mount -o remount rw /system
cp /sdcard/openvpn /system/xbin/
rm /sdcard/openvpn
chmod 755 /system/xbin/openvpn
mount -o remount ro /system
and it seems to be running now, just an issue with my vpn config left.
andywuk said:
Thanks for that rbox, it seems it was an old binary, found a newer one on thread
http://forum.xda-developers.com/spr...nvpn-binary-lollipop-s5-t3086672#post64696367
took that, installed manually
adb shell
su
mount -o remount rw /system
cp /sdcard/openvpn /system/xbin/
rm /sdcard/openvpn
chmod 755 /system/xbin/openvpn
mount -o remount ro /system
and it seems to be running now, just an issue with my vpn config left.
Click to expand...
Click to collapse
Did you end up being successful in configuring openvpn? I have performed exactly the same steps and cannot get it to work. Cheers
I was following this thread http://en.miui.com/thread-183258-1-1.html for resizing system partition. ADB worked fine when phone was switched on and "adb shell" command worked fine. But when I rebooted into recovery mode and typed the same command I got this "/sbin/sh: su: not found" error. I tried to mount /system in recovery mode but in vain.
Please guide!
Thanks!
make sure u have rooted
boot into twrp
umount data cache and system and also disable mtp
use twrp filemanager go to system/bin chmod to 755 and copy parted to system/bin
now u can try adb shell