Develop Bugs

[Q] ADB Remount

Alright, since i had a couple of problems with adb remount, i decided to do some research.
I'm running the latest OTA (2.10.405.2) rooted with Unrevoked 3.21, using Clockwork Recovery Mod 2.5.0.7.
Now once i go to the adb shell and type adb remount, i get the following error: (do mind, this is fully booted, i dont know if a remount is possible while booted?)
adb devices
List of devices attached
BLA12345 device
adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Ive read something about figuring out if adb recognizes your device as root, so i tried doing this with getprop ro.secure
It returned the following:
adb shell
$ getprop ro.secure
getprop ro.secure
1
Click to expand...
Click to collapse
This means adb does not recognize my device as root, so i booted into recovery, went to adb again and did the same. This time it returned:
adb devices
List of devices attached
BLA12345 recovery
adb shell
~# getprop ro.secure
getprop ro.secure
/sbin/sh: getprop: not found
Click to expand...
Click to collapse
Now, i can always mount the /system partition manually by going into clockworkmod recovery, but i'd like to be able to use adb remount aswell. Does anyone know what's going on and how to fix this
Thanks in advance!

Up.
10 chars

for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w

AndroHero said:
for starters we cant mount /system as r/w while booted... as it stands we dont even need to use the remount command, as we only have r/w access to system whilst in recovery, if you just use the mount /system command, it will automatically be mounted as r/w
Click to expand...
Click to collapse
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?

Lunatic2 said:
Aaah alright, i get the picture now! Seems they have released S-OFF today tho, time to start using remount?
Click to expand...
Click to collapse
i only just noticed that after i replied to your post happy days

[Q] Root gn gsm 4.0.4

Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.

You can root using this toolkit http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile

Mojochief said:
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
Click to expand...
Click to collapse
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
EDIT: All that file does, is copy su and Superuser.apk to your device and set the appropriate permissions.

You can root using this toolkit http://forum.xda-developers.com/show....php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Thanks I'll try it, but I'm actually not a big fan of one click thingies where you don't know what you're doing.

Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
Click to expand...
Click to collapse
Thank you I really prefer that over toolkits!

Mojochief said:
Thank you I really prefer that over toolkits!
Click to expand...
Click to collapse
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.

This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
Click to expand...
Click to collapse
Just tried it and it worked just fine
And thank you for the explanation!
So actually you could do it w/out booting cwm just with fastboot+adb right?

Mojochief said:
[snip]
So actually you could do it w/out booting cwm just with fastboot+adb right?
Click to expand...
Click to collapse
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.

No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
Click to expand...
Click to collapse
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.

Mojochief said:
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Click to expand...
Click to collapse
Yes, you can use another insecure boot image, but it needs to be a 4.0.4 compatible kernel. Older ones won't work.
Sent from my Galaxy Nexus using Tapatalk

Mount /system rw using terminal.

I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.

cmlusco said:
I have been trying for hours now to remount the /system partition rw using terminal emulator with no luck. I can do it just fine using root explorer, but thats not what im after. Im trying to make it so that system is mounted rw on boot. But every command i have known to work in the past, and every one i found thru googling has not worked. The command finishes with no errors, but /system is still ro. I even went as far as to unpack the boot img and change /system to be rw on mount. But again when i boot up /system is still ro. Its like something is protecting it or remounting it ro again. By editing the boot.img i was able to mount the root directory (/) rw on boot, but doing the same edit to the /system mount point seems to have no effect. Anyone know what im missing here? I am s-off, unlocked, i have an insecure boot.img, i have root, i dont know how much more insecure my phone could be. If root explorer and other apps are able to do it, there has to be a way to do it thru a shell.
Click to expand...
Click to collapse
Try this:
Create an executable script - like this one:
Code:
#!/system/bin/sh
# Make system rw
chmod 666 /system;
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/system");
Save it in your storage location as systemmount (or whatever).
Open terminal, type su.
Type:cd /sdcard/
Type: systemmount
Exit and see if that works. I have not tested it.

Thanks but no luck
Code:
exec /system/bin/sh '/storage/emulated/legacy/Download/scripts/00remount'
/Download/scripts/00remount' <
Unable to chmod /system: Read-only file system
/storage/emulated/legacy/Download/scripts/00remount[4]: syntax error: '"ext4",' unexpected

Put the mount first before chmod. Delete ext4 and emmc
Sent from my Lunar Ecliptic One.

Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.

cmlusco said:
Thanks, but i figured it out. It turns out the command i had used in the first place was correct. (mount -o remount,rw /system). After i ran the command i would check with root explorer to see if it worked, and it always showed it did not. But when you check it the correct way, the way i shoukd have been in the first place, by typing 'mount' in terminal it shows it did indeed get remounted rw. So its an issue with root explorer, not with the command i was using.
Incidently if you do the command 'mount' without su permission, it shows sysyem as ro, but if you do it under an su prompt it shows it as rw.
Click to expand...
Click to collapse
Nice work.
Sent from my Lunar Ecliptic One.

[Q] NO Root when installing TWRP to T989

I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.

Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 2.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2014-06-29 14:30 su -> /system/xbin/su
Analysis: File: su is a symbolic link pointing to another file: /system/xbin/su
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 348160 2014-06-29 14:30 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn

Wrong forum, US variants have their own fora. Your thread belongs here, I've asked mods to move it. Sit tight until they do.

Karetus said:
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Click to expand...
Click to collapse
You need to download the su zip and flash it in recovery.

Lokke9191 said:
You need to download the su zip and flash it in recovery.
Click to expand...
Click to collapse
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.

KJ said:
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
Click to expand...
Click to collapse
Would you happen to have a link available? Or will any version do the trick?

Karetus said:
Would you happen to have a link available? Or will any version do the trick?
Click to expand...
Click to collapse
You should not use any version. Use the one I attached.

help me please I cannot modify system files despite having root

i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?

lg_g3_d855 said:
i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
Click to expand...
Click to collapse
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.

User699 said:
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
Click to expand...
Click to collapse
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.

lg_g3_d855 said:
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
Click to expand...
Click to collapse
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.

User699 said:
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
Click to expand...
Click to collapse
yes I'm root, output is file system is read only despite adb commands

lg_g3_d855 said:
yes I'm root, output is file system is read only despite adb commands
Click to expand...
Click to collapse
Well, I'm sorry then... I can't help.
Good luck!