How to solve "Permission denied" following partition identification command? - OnePlus 2 Q&A, Help & Troubleshooting

Hi all,
I tried to identify partitions on the device (userdata, vendor, system, etc.)
Device: Oneplus2 (unrooted).
After
Code:
adb shell
ls -l /dev/block/by-name
It returns
Code:
/dev/block/by-name: Permission denied
I also tried
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The same result followed.
So
1. How to solve this "permission denied" problem?
2. Would it nevertheless be possible identify partitions on an unrooted device?
Thanks in advance.
Cheers,
Wen

Related

Root and android-wifi-tether

Hi!
Short and simple:
I've used this guide to 'root' my HTC magic.
Concerning the guide, my phone is root'ed.
Output of adb shell id
Code:
uid=0(root) gid=0(root)
Now I want to use android-wifi-tether, but the app tells me I ain't got root.
Am I missing something?
Thanks for help,
xenator
xenator said:
Hi!
Short and simple:
I've used this guide to 'root' my HTC magic.
Concerning the guide, my phone is root'ed.
Output of adb shell id
Code:
uid=0(root) gid=0(root)
Now I want to use android-wifi-tether, but the app tells me I ain't got root.
Am I missing something?
Thanks for help,
xenator
Click to expand...
Click to collapse
Does the su-binary exist /system/bin/su?
You could type something like: "ls /system/bin/su" to check that.
If this binary does not exist execute following commands:
adb shell
cd /system/bin
cat sh > su
chmod 4755 su
... try again ...
Code:
# cat sh > su
cat sh > su
cannot create su: read-only file system
Seems like I've to re-mount with 'rw'?
I'm a linux guy, but I don't want to break anything on the phone
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Did the job.
Now it seems that my kernel is missing 'netfilter'.
How do I get a kernel with that option compiled?
And again I could help myself
See here.
Thanks for the help so far!
xenator
android-wifi-tether works just fine, but I'm not able to use my "normal" WLAN anymore.
Anytime I try to activate WLAN in the settings it says "WLAN could not be started".
Anyone can help?

How do I backup /persist/ and /data/system/ ?

Hello,
I got my G2 connected to adb and have access to shell commands with root access. However, I have problems backing up those two folders /persist/rct and /data/system/.
When I issue
Code:
adb shell cp /persist /mnt/sdcard/download
I get an error:
Code:
WARNING: generic atexit() called from legacy shared library.
cp: omitting directory '/persist'
I'm issuing the wrong command?
Any help greatly appreciated.
Thanks

Error during root attempt —*Mount: Operation not permitted

Hey Everyone,
I'm attempting to root my VS980 (software version: VS98011A) on OS X via Terminal.
I am able to the following successfully:
View my device with the command ./adb devices
Push required files supplied by TheCubed's post
I cannot successfully execute the command below. It returns the error "mount: operation not permitted"
Code:
./adb shell "mount -o remount,rw /system
Am I missing a step that is causing an error? Do I need to use Loki Bootloader bypass first?
Occupying space for updates and hopeful solution for other mac users.
UPDATES:
Some more tinkering shows that SU cannot be found in /system/bin/sh —*Am I safe to push su to this location? Will this aid in achieving root?

Dumpsys command not working?

Hey all,
Recently I found out that the dumpsys command isn't working anymore. I can't delete the battery stats with command: dumpsys batterystats--reset. I'm getting an unknown error. I'm on 7.1.2 may patch with magisk installed. The command still works on my n5 running darkrom 7.1.2 with may patch and magisk installed. Any clue how to fix this?
Thanks in advance!
This is the exact error in the terminal:
angler:/ $ su
angler:/ # dumpsys batterystats --reset
Error dumping service info: (Unknown error -2147483646) batterystatsangler:/ #
swa100 said:
This is the exact error in the terminal:
angler:/ $ su
angler:/ # dumpsys batterystats --reset
Error dumping service info: (Unknown error -2147483646) batterystatsangler:/ #
Click to expand...
Click to collapse
Hi I have the same exact issue. Have you managed to find the root cause and fix?

[A/B Partition issue] Changing apn settings in LOS 17 does not persist after reboot

My phone has not been able to receive calls because the default APN settings from LOS are just wrong. I updated the file (/system/product/etc/apns-conf.xml) in recovery, but after a reboot, the file is back to what it was before I changed it.
I am using LOS recovery if that helps. How do I change that one file to have it persist across reboots?
Thanks
Problem solved!
Had to mount the "/" partition to be writable using the command:
Bash:
adb shell su -c 'mount -o remount,rw /'
Then after making changes, I first pushed the file to internal storage:
Bash:
adb push ./apns-conf.xml /sdcard/Documents/apns-conf.xml
Then finally I copied it to the proper location:
Bash:
adb shell su -c 'cp sdcard/Documents/file.xml /system/product/etc/apns-conf.xml'
Hope that helps someone

Categories

Resources