Develop Bugs

Which user am I logged in as ?

Hi all,
couple of questions I hope somebody can answer for me ?
1. If I connect my Hero phone to my XP PC and run adb shell and then SU so I get the # prompt, what user am I logged in as ? is it root ? I tried whoami command but it was not a recognised command.
2. What is special about the system directory, because if I try and do
#chmod 777 system
I get this error: Unable to chmod system: Read-only file system
but no problem if I do same command to the sys directory. Both sys and system have same file permissions:
drwxr-xr-x root root 2009-08-27 03:51 system
drwxr-xr-x root root 1970-01-01 01:00 sys
so what makes the system directory a Read-only file system ?
I hope this makes sense, I'm only just starting to dabble with this linux stuff.

The answer to the first question is you are indeed logged in as root, su will(...should...) log you in as root for the entire session.

with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.

kendong2 said:
with # you are root. the id command works.
/system is the "rom" part, it should not be changed and therefore is usually mounted RO. you can remount it RW with the usual mount options or adb remount. why would you want to change the permissions of the folder? i don't think it's good idea tbh, you should not mess with system files unless you know what you are doing.
Click to expand...
Click to collapse
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers

gudge said:
OK, thanks for explaining. tbh I was just seeing what I could and could not do, I will take your advice and not mess with the system files any more.
So the read only thing, is to do with mounting rather than file permissions from what you say. I think I need to read up on the subject.
Cheers
Click to expand...
Click to collapse
do whatever you like, i learned most of what i know by trial&error just be prepared to break it, never go without a backup...

Trying to change boot animation

I am using ADB to push the bootanimation.zip to /data/local but nothing is changed in the phone.
I am using Telus Raidroid fully rooted and s-off.
Any ideas?

Try /system/customise/resource/
Sent from my Desire HD using Tapatalk

AndroHero said:
Try /system/customise/resource/
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Make sure you mount the location as well (from command prompt in windows, or equivalent) - type what's in bold-type:
C:\SDK\Tools> adb shell
# mount /data/local
(screen will then print: )
mount /data/local
# ls /data/local <~this will list what is stored in this location.
(or, if it's supposed to be system/cust... as above poster said)
# mount /system/customise/resource
mount /system/customise/resource
If neither works, try using ES File Explorer. Change it's settings to "view system files", then look around in the folders until you find the bootrecovery.zip & where it's been placed. Not 100% sure but I was under impression you need to mount /filelocation to copy the bootanimation.zip to that location.

Rubixious said:
Make sure you mount the location as well (from command prompt in windows, or equivalent) - type what's in bold-type:
C:\SDK\Tools> adb shell
# mount /data/local
(screen will then print: )
mount /data/local
# ls /data/local <~this will list what is stored in this location.
(or, if it's supposed to be system/cust... as above poster said)
# mount /system/customise/resource
mount /system/customise/resource
If neither works, try using ES File Explorer. Change it's settings to "view system files", then look around in the folders until you find the bootrecovery.zip & where it's been placed. Not 100% sure but I was under impression you need to mount /filelocation to copy the bootanimation.zip to that location.
Click to expand...
Click to collapse
Thanks I'll try that later when I get home! Nothing I read mentioned having to mount anything...but I also never got any errors in ADB when pushing the file.

The file was successully pushed as per EF File Manager to /data/local/

You don't always have to use "push" to get the file into /data/local
Free apps like "Android Mate" can also let you copy files into the root of your phone. The terminal apps also allow you to copy the bootanimation.zip
cp /sdcard/bootanimation.zip /data/local

after the 1 click root - not able to mount some directories in root explorer?

I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?

sedric1 said:
I used the post to install the one click root for the samsung epic 4g (sprint), and it appears to have worked. However - after entering root explorer, only some of the directories allow me to edit files. I click the remount as r/w button but nothing happens. Any thoughts?
Click to expand...
Click to collapse
Are you sure you granted root permissions to root explorer when it first ran? Run the superuser app from the app drawer and see if root explorer is on the list of apps that are allowed root permission.
I just tried v2.17.2 and it works fine. I tried changing the permissions on /system/xbin/busybox, it said filesystem mounted ro, then I press the mount rw button and redid the permission change, this time it worked no problem.

Thanks for your response-
yes, when i ran root explorer it asked if i wanted to grant superuser and i said yes. some folders allow it to remount, but - say the /system/bin folder - it doesnt allow it at all.

for further background, i used the automated instructions here for my root:
http://forum.xda-developers.com/showthread.php?t=1342728
i did option A like 5 times and also did option C (as i have EK02).
When opening root explorer it tells me that i have super user permissions. one thing to note- if i go to /system/xbin, i do not see a busybox directory. is there something else i should be installing?
in fact, i cant mount anything under the system directory or sub directories, but above that, i was able to change to r/w mode. i could also mount the /vendor directory right beside the /system directory...

If you were able to remount "/" as r/w then the problem isn't with root. That is basicly an "I'm a little bit pregnant situation" Either you are or you aren't.
Now if you weren't able to get root in the first place, then I'd look at the root.
As to busybox, there is no directory. There should be a file /system/xbin/busybox Also there should be a bunch of symlinks from various apps it supports to busybox.

I see - yea i did validate that busybox is not allowing for a mount or any type of change on that file/directory including busybox but the file is present. any suggestions on what else may be locking down this system directory?

I don't know if root file explorer is implemented it's own concept of ro/rw to protect you from making mistakes or it is using the system facilities. If it is using the system facilities, then once you remount /system as rw, then everything under /system is automatically rw. It is all the same partition.
I would try it from "adb shell" (do not type $ or # symbols)
Code:
$ su
# mount -o remount,rw /system /system
# cd /system/xbin
# chmod 755 busybox
If it lets you do that with no errors, then you have remounted /system/xbin as rw and the problem is with root file explorer. For that, you'd have to check with them or someone more well-versed in why that might be failing.

i appreciate your help
I went off googling the adb stuff/installed it and java's jdk stuff. then figured out how to run that adb shell stuff and validated that it worked (permissions were changed in places that this app didnt allow). knowing that the problem is actually with root explorer helps a ton.. as I just assumed it was working

[Q] Need help deleting a directory

So here's the thing i've been exploring the possibilities of USBHost and decided to try an usb stick so i installed Paragon https://play.google.com/store/apps/details?id=com.paragon.mounter
It took me a while to get the hang of things. At first my usbstick was formatted in fat32. I specified in paragon i would like the default mount point to be USBStorage instead of /paragonNTFS. I made a small typo at first and named the folder usbStorage
now here comes the problem.
for some reason the app created 2 subfolders called sdb1 and sdb2 and i cannot remove them
Things i've tried:
cyanogenmod file manager in root access mode
-- delete directory > "This operation needs elevated permissions. Try switching to root access mode" (translated from dutch so wording may be a bit off
-- modifying permissions of folders > denied > changing permissions failed. for security reasons some filesystems, such as on sdcards do not allow changing permissions
Same problem for Astro file manager
Same problem when attaching the tablet to computer. parent directory (and sub dirs) get "removed" in windows but when checking the file system on the tablet, the opposite is true and the directories is still present
and now it's starting to piss me off. I want that folder "usbStorage" and it's subfolders "sdb1" and "sdb2" removed. so my guess is it'll have to be done by terminal commands but my terminal experience is ZERO.
in preperation of you guys helping me installed https://play.google.com/store/apps/details?id=jackpal.androidterm the same one used in cyanogenmod roms. I tried a bit of tinkering myself but prob doing something wrong
what i've tried (in sequence, --ok behind the command means it was succesfully executed)
su --ok
cd sdcard --ok
*rm -rf /usbStorage >> *rm: not found
rm -rf /usbstorage --ok, but folder was still present
rm -rf usbstorage --rm failed for usbStorage, Directory not empty
cd usbStorage --ok
rm -rf sdb1 --ok, rm failed for sdb1, Permission denied
at that point i gave up. I hope you guys can help me out
I do have paragon configured properly now and my USBstick in NTFS is getting recognised. Upon mounting of the usbstick, it now creates a folder called "USBStorage" where the contents of the usb stick is properly displayed.
so where are those android terminal / linux masters to help me out
only thing i can add is that when opening paragon with the stick attached but unmounted i do see a line above it /dev/block/sda1 but that doesn't seem to affect mounting in the specified directory

Bump, anyone? I want and need this folder removed
Verstuurd vanaf mijn Nexus 7 met Tapatalk

From my understanding of your post.
You are rooted and using cyanogenmod?
Did you try going into the app information and clear data?
In the app drawer hold the app and then drag it to App Info
Clear data.
Did that solve it? If not continue below.
Make sure you don't have the USB stick mounted and or plugged in.
Then go into terminal and type
su
Then type.
mount
The mount command shows all listed mount points. If you don't see the usbStorage or whatever mounted.
Then type.
busybox rm -rf usbStorage
Or whatever the main directory is...
For example directory is at.
/sdcard/usbStorage
cd /sdcard
rm -rf usbStorage
Let me know how you make out.
Sent from my Galaxy Nexus using xda app-developers app

nope, my phone is running CM 10.2 (not relevant to the question) this is the nexus section and its my nexus 7 2013 running stock rom but rooted yes that needs the folders removed.
The folders i need to delete according to the Nexus 7 mount main mount path SD content
main path: /storage/emulated/0 or /storage/emulated/legacy (both are the same according according to ParagonNTFS as a folder the mount path /sdcard/USBStorage = /storage/emulated/0/USBStorage or /storage/emulated/legacy/USBStorage
important lines?
/dev/fuse /storage/emulated/0/ fuse rw,nosuid,nodev,realtime, user_id=1023, default_permissions,allow_other 0 0
/def/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatimeuser,user_id=1023, group_id=1023,default_permissions,allow_other 0 0
folders to delete are
/storage/emulated/0/usbStorage
/storage/emulated/0/usbStorage/sdb1 <= can select these just fine
/storage/emulated/0/usbStorage/sdb2
/storage/emulated/0/ParagonNTFS <= simply selecting this folder prompts CM manager "this operation needs elevated priviledges. Try switching to rootmodus, even when the CM filemanager already is in root mode
so i went
Opening terminal
su
cd sdcard (command ok)
cd usbStorage (commando ok)
busybox rm -rf sdb1
rm: can't remove 'sdb1': permission denied
Then i tried
cd /sdcard
rm -rf usbStorage
rm failed for usbStorage, Directory not empty
cd usbStorage
rm -rf sdb1
rm failed for sdb1, Permisison denied
busybox rm -rf sdb1
rm: can't remove 'sdb1': Permision denied
According to Cyanogen mod file manager:
Filesysteminfo:
Status: rw
linkpath?: /storage/emulated/0
Device: /dev/fuse
Type: fuse
Options: rw,nosuid,nodev,relatime,user_id=1023,default_permissions,allow_other
Dump / Pass: 0 / 0
even with the app ParagonNTFS uninstalled it doesnt work

hmm
try
close the app ParoganNTFS and uninstall it.
then try to delete those directories.
Also when you type
mount
does it show any of the directories you are trying to delete as mounted?
if it is try
umount /sdcard/usbStorage/sdb1
rm -rf /sdcard/usbStorage/sda1

were you able to delete the dir?
I had the same problems under very similar circumstances. Stickmount rather than paragon. The only way I could delete the dir was to boot into recovery (team win recovery project v2.7.1.1) and delete it with TWRP's terminal command. Something in the OS apparently locks on to the mount and simply will not let it go ever. It has to be done before android starts. It's very annoying. I am beginning to really be disgusted with many of the decisions google is making with regard to android. Why do they hate sdcard expansion so much? its absurd.
---------- Post added at 04:22 AM ---------- Previous post was at 04:17 AM ----------
Oh and by the way, even though the OS latched on to that folder as if its very existence depended on it, I was never able to even see the files on the USB memory stick with any file explorer. Worked just fine in kit kat and before. In some ways lollipop really sucks.

[Q] Deleting system file in terminal causes reboot

Hello all,
I'm trying to delete a system file using the Android terminal (as my end goal is to put it in a run shell task in Tasker) and it either reboots my phone or just doesn't delete.
Long story short, I'm using the Weak Sauce root method, but I do not have S-Off as I like how easy it is to undo the Weak Sauce root alone. This means, of course, I don't have immediate RW access to system. So here's what I've done:
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p46 /system
# busybox rm -f /system/media/audio/ui/camera_click.ogg
# mount -o ro,remount -t yaffs2 /dev/block/mmcblk0p46 /system
When I do the first and last commands alone, the system mounts as RW and RO correctly, confirmed with # mount|grep system. But that middle command is the problem. Sometimes nothing will happen, other times my phone will reboot. I've also tried adding the following before the rm command with no success:
Code:
# chmod 777 /system/media/audio/ui/camera_click.ogg
I AM able to delete the file manually through ES File Explorer when mounted RW. But it comes back after I restart my phone, hence why I want this command to be used in Tasker.
What am I doing wrong?
PS: as for the "why" of deleting the shutter sound file, I take screenshots sometimes and the sound drives me nuts. I've tried removing the ogg file from the camera apk, but that didn't work after a reboot. I also tried replacing the ogg file with a silent one, but no success there either as the real one reloads itself when I restart.

Delete the file in recovery using TWRP
Sent from my HTC One_M8 using Tapatalk

SmiLey497 said:
Delete the file in recovery using TWRP
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'm trying to do it from the terminal so I can eventually put it into Tasker. I can delete it successfully with ES File Explorer, so no need for recovery. I just need some way to get it to work through the terminal.

If the file is coming back then you don't have proper write access to system and the file isn't actually being deleted which Is why it appears to come back.
Try using root explorer instead or do it through TWRP. Make system RW then just move or rename the file rather than delete it. If you have proper write access it will stick.

heather1209 said:
I'm trying to do it from the terminal so I can eventually put it into Tasker. I can delete it successfully with ES File Explorer, so no need for recovery. I just need some way to get it to work through the terminal.
Click to expand...
Click to collapse
It comes back when you reboot. Your system is not writable you need to S-OFF. get system RW kernel, or delete through recovery.

SmiLey497 said:
It comes back when you reboot. Your system is not writable you need to S-OFF. get system RW kernel, or delete through recovery.
Click to expand...
Click to collapse
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.

heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2701816

heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
[KERNEL] [June 20] [Sense] [GPE] ElementalX 0.19 I think that'll work on stock Sense system.

heather1209 said:
Ah, that makes sense. What's the system RW kernel you mentioned? I'm not familiar with that.
Click to expand...
Click to collapse
He means flash a kernel that has write access to system enabled.

SmiLey497 said:
http://forum.xda-developers.com/showthread.php?t=2701816
Click to expand...
Click to collapse
Or yeah, the MOD can work too :good: