Related
I've been looking at the root folder using Astro and there are several files/folders. Can any be deleted, without causing any problem? I'm running out of space and am hoping some are just temporary files etc...
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Thanks
p.s - I am using an unrooted HTC Desire.
bradavon said:
I've been looking at the root folder using Astro and there are several files/folders. Can any be deleted, without causing any problem? I'm running out of space and am hoping some are just temporary files etc...
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Thanks
p.s - I am using an unrooted HTC Desire.
Click to expand...
Click to collapse
you cant delete them using astro, we only have write access to /system in recovery, use adb in recovery to delete them
edit, without root you cant delete anything lol
bradavon said:
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Click to expand...
Click to collapse
In addition, deleting anything from /system won't actually gain you any more space for applications anyway due to the way that the filesystems are partitioned.
Regards,
Dave
Thanks guys. I take it you mean we've got write but not modify access to the \system folder? So we can write to existing files but not delete them.
I wasn't just asking about \system though but any files/folders in the Root folder. Are there any at all, that can be safely deleted? Or are you saying you cannot delete a thing without rooting?
Not that it sounds like it will make any difference, due to partitioning.
Thanks
Ok to put it as simple as possible:
- no you cant pretty much delete a thing apart from sd without root
- we cant do anything in the system partition while the system is booted due to the nand protection
- we can modify /system while in recovery (using adb)
- when you are running out of space it is on the /data partition, which have a fixed size so deleting from /system or anything else won't help
And at last my advice to you is to go root and install a2sd easy as pie and i've never had space problems since.
Thanks for the informative reply mortenmhp
I have just rooted my 2.1 Desire, trying to remove two of the mms.apk and one other mms file in the /system folder so I can install a different mms.apk, however when I try to do it, it says I dont have the proper permissions. Its rooted, I see the Super User icon in applications.
Any suggestions?
Please read a little before asking questions. It is commonly known, that we dont have full root access on the desire yet.
Due to the nand protection you cant edit the system partition while the system is bootet. You have to use a custom recovery image either via fakeflash or installed by unrevoked. Then you can edit the system partition by using adb commands.
Edit: which i also stated quite clearly 2 posts above yours several months ago
Is A2SD better than the Android 2.2 implementation? Which as far as I can tell just moves the APK (not apps/data) to the SD Card.
Thanks.
Well it is kinda off topic here but in my opinion yes it is better. I'm running a2sd+ atm. and you can make it move /data/data as well.
In froyo there have been some complications though when remountingSD after using it as mass storage. But you can read more about that elsewhere(i would provide a link but I'm writing from my phone)
So the conclusion must be that it is down to personal preferences
Thanks because the official implementation is something of a cop out. On WM you could run the entire App/Data etc... on an SD card.
I'm hoping someone can help.
I'm rooted with Radio S-OFF and ENG S-OFF, running LeeDrOiD 2.2.2 with Kernal 2.2.7.
I am trying to edit system/etc/hosts to remove all the adblock entries, as it's causing issues with Words with Friends, also I think blocking ads just hinders the development of decent applications in the future.
I've tried editing it with Astro File Manager, but I am told I have "insufficient privillages". I then connected via USB Debuggin and ran adb remount, which shows my system partition as mounted. However I still can't edit it.
I thought S-OFF was supposed to mount the system partition for you for good.
You can use root explorer found in market and then mount system as r/w. S-off gives you the ability to mount system r/w but its not by default r/w.
Hello everyone. I see a lot of very basic android questions floating around the forums, so I figured I'd give a VERY basic rundown of the android filesystem for those who don't know. (If you're even slighty experienced, this'll seem like a "duh" thread, you should skip this. This is for new people.)
Ok, to understand android, first thing you need to understand are the basic partition structures. There are 5 android partitions.
boot
cache
recovery
system
data
Before I get into the partitions, you'll have to understand what a mount point is. When you "mount" a drive, you are making it available to the system. On linux (and by extension, android), you need to have a mount point. This is a directory somewhere that serves as a path for the mounted filesystem. So for example, let's say I wanted to mount mmcblk0p1 to a temp directory to edit it. For this example I'll create a directory /data/temp. Now you'd mount mmcblk0p1 /data/temp. When you read the contents of the directory temp under the directory data, you'll see all the info stored on mmcblk0p1. Even something as simple as a flash drive needs to be mounted under linux. If you're an ubuntu user, usually it automounts to /mnt/name of device.
Now, when you boot android, the first thing it does is boot up the linux kernel (when you see the tmobile splashscreen, that's when the kernel is loading.) Next, it loads up the ramdisk. Both of these files are on the boot partition. (When you open up a cwm zip file, you'll see boot.img in there, that's where these reside.) There are two files on the boot partition. zImage (the linux kernel), and initrd.gz (the cpio archive containing the ramdisk.)
What is the ramdisk you ask? Well, very simply, it's the place where the root file system is loaded, and where the init.rc resides. The init.rc is the android startup script (again, basic analogy). If you'd really like to learn about android and how it works, this is the first file I'd start reading.
On to the partitions:
boot - Described above, containing the zimage and initrd.gz
recovery - this is where either the stock recovery or clockwork recovery is located. This is only accessed when entering recovery mode.
cache - You guessed it, this is where some parts of android cache it's file. (Not to be confused with the dalvlik cache, that's located on the data partition.)
system - this is where the system is located. (Esentially the rom you're flashing.)
data - this is the partition where all your installed apps go, as well as the location of a couple parts of the system, like the dalvik-cache and the batterystats.bin file. (Quite a few more, just givinig examples.)
So what does all this mean to you? Well, I see a LOT of people asking about wipes before installs, or asking about flashing kernels, this is why I took the time to explain this.
When you enter cwm, and do a backup, it creates 5 .img files on your sdcard. (One for each of the partitions mentioned above.) When you flash a kernel, it only replaces the boot.img, and a couple files in the system folder. Usually these are kernel modules like the wifi module, and any other modules that aren't compiled into the system. (Although most kernel builders build cifs.ko and all that right into the kernel so the modules aren't needed.)
When you flash a rom, it will always replace the /system and /boot partitions. The rest, that depends on the rom. If you'd like to know what your rom is doing, open up the cwm zip file, and go to meta-inf/com/google/android and you'll see 2 files. Updater-script and update-binary. Updater-script will tell you what it does on install. (You'll see it mounting the partitions it needs, what it does and doesn't format, and also it does a whole bunch of simlinks.) Simlinks, or symbolic links, are either files or directories that point to somewhere else. For example, let's say you are a user who uses ext-sd. What you do is create a simlink for /data that points to the ext3 partition on your sdcard. This way, anytime the system goes to /data it writes somewhere else. Most of the simlinks created in android are more for busybox commands, but that's for another post
If you'd like to see what your mount points are, from an android terminal emulator (or of course adb, but if you are experienced with adb chances are you don't need any of this info in the first place ), type mount. (You might need to type su first, hit enter, then mount). This will list all your mount info. If you'd like to know the actual device name of the mount point, you'd look here. On ours, for example, it's:
mmcblk0p24 is /system
mmcblk0p26 is /cache
mmcblk0p25 is /data
and so on.
Ok, finally, a couple other questions I see often:
Why does my system "hotboot"?
When a system hotboots, it means that zygote has crashed. This is the virtual machine that android runs in. So if you are using your phone, and you all of a sudden go back to the boot animation (NOT the splashscreen with the kernel logo), you just hot-booted. When an application allows you to hotboot all it does is the following command from inside linux: pkill zygote (or pkill -9 zygote).
How do I calibrate my battery?
The batter calibration is a file called batterystats.bin. This is located in /data/system. When you get to 100% charge, if you delete this file, it'll start over on the battery calibration. (There are also market apps to do this for you for the squeamish.)
Other notable files:
gps.conf
Located in the /system/etc folder. This has all the gps configuration, nameservers, and things like this.
build.prop
Located in /system
A lot of device info is stored in here. For more info, google it.
Hopefully this wasn't too mashed together and confusing. I tried to follow a logical order, but I've had way too much turkey and beer today, so I'll post this and let it fly.
Have a happy thanksgiving everyone!
Good stuff, thanks OP.
Powered by the SGSII....
Very very useful for someone like me who knows a bit here a bit there but not sure of the whole picture.
Thanks!!
this should be useful for alot of noobs!
Thanks so much for this, being new to android this is incredibly useful. Bookmarking!
Sent from my SGH-T989 using xda premium
This thread should help alot of new people that just joined this forum and that are new .
Very informative, thank you.
I've recently did a factory reset, but before doing that I backed up the internal storage partition using
Code:
adb pull /dev/block/sda29
that is my partition for /data according to /cache/recovery/log generated by twrp.
Now I have this little (128GB) file inside my pc, I mounted it into a folder but entering media/0/ it say "Permission Denied" even if I access it using root user. I think is releted with android full encryption.
I tried using testdisk for finding other files and I found a bunch of random named files that testdisk fails to recover, but at least I get into the directory...
Someone can figure out how to access those files? thanks
topongo said:
I've recently did a factory reset, but before doing that I backed up the internal storage partition using
Code:
adb pull /dev/block/sda29
that is my partition for /data according to /cache/recovery/log generated by twrp.
Now I have this little (128GB) file inside my pc, I mounted it into a folder but entering media/0/ it say "Permission Denied" even if I access it using root user. I think is releted with android full encryption.
I tried using testdisk for finding other files and I found a bunch of random named files that testdisk fails to recover, but at least I get into the directory...
Someone can figure out how to access those files? thanks
Click to expand...
Click to collapse
it could be the file extension, windows will not read ext4 files unless you download a tool, linux supports it so you could try mountiong the file on linix or with ext4 app reader (you probably wont be able to modify the data)
Hello! I just rooted my Rog 6 with Magisk to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Well you must be in os12 same issue with me but in different device
senna33 said:
Hello! I just rooted my Rog 6 to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Click to expand...
Click to collapse
did you use a file explorer that supports root and try to change the permission on the file?
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
senna33 said:
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
Click to expand...
Click to collapse
i don't understand how a device is rooted if you can't modifie system files
nadejo said:
i don't understand how a device is rooted if you can't modifie system files
Click to expand...
Click to collapse
That's kinda how I feel about it. Root Checker Pro says I have root, I can run Su in a terminal and I get a popup asking for superuser rights when I use a function that requires root. I attached some screenshots from Root Checker Pro
The problem is that the partitions (system vendor and co) are only integrated as R/O and cannot be easily integrated as R/W
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
senna33 said:
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
Click to expand...
Click to collapse
ChrisFeiveel84 said:
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
Click to expand...
Click to collapse
I converted still same
Mr Hassan said:
I converted still same
Click to expand...
Click to collapse
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
ChrisFeiveel84 said:
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
Click to expand...
Click to collapse
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
If the partitions are not converted from erofs to ext4, it remains with ro because erofs cannot be mounted as rw
Mr Hassan said:
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
Click to expand...
Click to collapse
how did you try to convert the images to ext 4 without write protection?
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
There's thread available on xda but as i told useless
What u think as i said upper if device
Dev block mapper have full root
But not possible to edit system vend or anything
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
see this
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
and still i,m not able to edit these parts
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
ChrisFeiveel84 said:
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
Click to expand...
Click to collapse
Men see upper logs its converted to ext4
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
ChrisFeiveel84 said:
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
Click to expand...
Click to collapse
But in os10 os11 is possible
But don't know how to fix this os12
Is there anyway to remove write protection?