Database Develop

apps2sdcard removing problem

Hello, I followed this guide: http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD
It says:" Then proceed to the ADB instructions from after 'adb shell' " so I jumped those steps:
Code:
adb remount
adb shell
Why are they shown anyway if you have to jump them?
Then
Code:
rm /data/dalvik-cache
did not work so i used
Code:
rm -r /data/dalvik-cache
instead but it also did not work because the dir was busy. Any ideas?
Thank you very much.

Wait, what are you trying to do, remove the apps2sd function? If so backup the contents of your card, format it and copy the contents back. You'll be without an ext partition so the phone will have to install apps to the nand.

Yes, thanks. But Apps2SDCard will be reinstalled of course.

What? You need to be more clear on what you want to achieve.... if you dont have an EXT partition, apps2sd is disabled.

[Q] ADB "No space left on device"

Hey guys
So I am currently running 2.3.3 on my N1. I manually flashed the update from Here. I used the "Modified GRI40".
So after update, I noticed that my adfree wasn't working. Running the app, it tells me my host file is up to date. However, no ads are being blocked. Same after uninstalling and re-installing the app. So then I decided to try to copy the host file over manually using adb.
I run adb and get root prompt. Then I mount /system as rw using
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
It appears to work. So then I try copying the host file to /system/etc using
Code:
cp hosts /system/etc
Then I get the following error.
"write error: No space left on device"
But i do, over 30mb of free space.
So I don't know what the issue is. Im thinking that maybe /system isn't being mounted as RW so it is giving the error??
Any help would be much appreciated.
Thanks!

Did you check the /system free space, or /data?

Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.

codesplice said:
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
Click to expand...
Click to collapse
Well looks like somehow I don't have any space left. I went to go download a terminal application from the market but it errored saying no space left.
So now I can't even install new apps.
However, under settings->storage it says I have 28MB of free space left.
Any ideas?
Sent from my Nexus One using XDA App

Reboot, wipe Dalvik cache.
Go to Manage Applications, clear browser cache.
If it restores you some space - great, proceed with what codesplice suggested above.
If it doesn't - backup, wipe and reflash.
If no backup installed - you're out of luck.

Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts

codesplice said:
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
Well that's thing, that is why I started this thread because I was trying to use ADB to push a new hosts file but got the no space error. So I already tried that.
Sent from my Nexus One using XDA App

I was asking if you had specifically tried removing the old one and replacing it rather than just overwriting.

Oh I see what you mean. But no I have not, let me give it a shot.
**Nope didn't work. I still got the same error, no space left on device.

Have you had the opportunity to do adb shell df -h yet?

codesplice said:
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?

Brownbay said:
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Click to expand...
Click to collapse
yes, without root access to the filesystem, adb remount will fail.

So when I try adb shell df -h, I get:
"-h: No such filesystem or directory"

You don't have busybox. Try running "adb shell df", maybe it'll still give some info.

Ok when I ran adb shell df I got a listing of filesystems. /system says size 145M and used 145M. So apparently it is full.
How could that be though?

It could be that you have some bad blocks on your /system partition (you can generally only check by doing a wipe operation in recovery and then viewing the log). These bad blocks could take up space that would otherwise store your system data, and could push you over capacity.
Or you could just have some extra bloat related to that ROM. You could drive to remove some of the applications on /system that you don't have use for (the Amazon MP3 thing, for instance). I'd suggest using Titanium Backup to do this, but you can also do it by manually using the adb shell.
Alternatively, a full wipe and clean reinstall may help make sure you don't have anything left over taking up space.

I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?

decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
I've been really impressed with the Kang-o-rama ROMs. Basically prettied-up versions of Cyanogen. The latest release is a beta based on CM7, so still has a few issues. The prior release (KOR 1.1Final) is still quite solid.
And yes, a nandroid backup creates a copy of your current disk image, which can then be restored at any time to revert back to a previously-working configuration (great for when you break stuff!).

decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
Exactly Remember to wipe before restoring

Oh and that brings up another thought.
So if before I flash a new ROM, I do a Titanium Backup and then flash the ROM...
Would I then be able to restore that Titanium Backup made on the previous stock ROM to restore all my apps and user data?

[Q] How to fix wrong CHMOD permissions on /system

Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2

Try the Serendipity VII Q&A.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

texasagent said:
Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2
Click to expand...
Click to collapse
Using adb (and your phone in recovery, with the /system partition mounted):
adb root
adb shell
chmod 777 /system
exit
adb reboot
Hopefully that should get you there.

Thanks jmtheiss. That allowed me to get back in to change the permissions, however it still won't get past recovery mode after each reboot. Its strange that even after mounting /system, it doesn't contain a directory called 'app' anymore (or any subdirectories for that matter), just a handful of files. Looks like I have bigger issues.
Guess it's back to reloading the ROM again...
Thanks for your help!!
TexasAgent

Please post in the right sections. Should have been in Q&A

[Q] "no external storage" on KitKat ROMs [Mint]

Hey guys,
I think I'm getting crazy, I tried so many things now, but somehow the internal sdcard is not working on Xperia T with KitKat ROM.
Problem:
When I open the camera app is crashes instantly. Other camera apps say they need an external storage. The gallery says "no external storage"
In the filebrowser I see a lost+found folder but can't open it or do anything (write/read).
In adb shell with su I don't even have the permission to create a folder:
Code:
255|[email protected]:/ # mkdir /storage/sdcard0/test
mkdir /storage/sdcard0/test
mkdir failed for /storage/sdcard0/test, Permission denied
I tried CM12 M10-M12, an OmniRom and AOKP build. (all KitKat based)
I'm using TWRP 2.7.1.0 first, now 2.8.0.1 (2.8.1.0 does not seem to start). I wipe everything in recovery except the external micro sd card with the ZIPs. Then install the ROM and I tried with and without GAPPs. The boot.img is flashed via fastboot.
I tried erasing partitions via fastboot.
I flased CM10.2 (JB) and I could take a photo.
I have 2 Xperia T (Mint) with unlocked bootloader here to test and I don't get it working. But my sister has one too and I installed her CM11 a few month ago and she doesn't have any problems.
WTF am I doing wrong?

Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0

WhiteNeo said:
Try to enter the following in terminal:
Click to expand...
Click to collapse
It works :good: Thank you so much
It seems that it works as long as I don't wipe sdcard. Does this mean TWRP is wiping/formating the partition wrong?

qubbey said:
It works :good: Thank you so much
It seems that it works as long as I don't wipe sdcard. Does this mean TWRP is wiping/formating the partition wrong?
Click to expand...
Click to collapse
The wiping is correct, the problem is that Sony has decided for some reason to use a different user/group than the one used by default in Android (and most other phones, as far as I know). Given that Android (Linux) is a user/group/permission driven OS, if any of these don't correspond to the action performed, there will be no access.
If you format the sdcard from a custom ROM or recovery, it will use user/group 1023 (media_rw), but the kernel is set to use user 2800, therefore you will lose RW access.
This can be easily fixed by modding the kernel to use the "proper" permissions, or simply correct the user/group with a CHOWN command.

Is this common knowledge? I didn't find a thing when I was searching for a solution. But I guess it happened to lot of people.

qubbey said:
Is this common knowledge? I didn't find a thing when I was searching for a solution. But I guess it happened to lot of people.
Click to expand...
Click to collapse
It is definitely not common knowledge, but anyone compiling a kernel and having tinkered with formatting would have noticed this, as did @updateing a few months back and was actually the one who confirmed this to me a few months back when I was modding kernels to get Folder Mount to work.
It just takes a bit of troubleshooting to come to this conclusion, but since it's being asked so many times lately, someone should make it a sticky.

WhiteNeo said:
Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
Hi, I'm having the same problem. After putting in the above, it says: Operation NOT permitted.
What is going wrong?

*-MaCK-* said:
Hi, I'm having the same problem. After putting in the above, it says: Operation NOT permitted.
What is going wrong?
Click to expand...
Click to collapse
You might try running the command without the "-R" first, so you're able to access sdcard0 at all.
If this fails as well, try replacing /mn7/media_rw/sdcard0 with /storage/sdcard0

WhiteNeo said:
You might try running the command without the "-R" first, so you're able to access sdcard0 at all.
If this fails as well, try replacing /mn7/media_rw/sdcard0 with /storage/sdcard0
Click to expand...
Click to collapse
I'd be surprised if that works, given that the proper user/group for /storage/sdcard0 is "root:sdcard_rw", as it is set by default, and not "2800".
@*-MaCK-*:
Did you type in the "su" command first, on it's own?
Are you in fact rooted?
Does your storage have the proper file system format (ext4)?
You can check the file system format by running the command:
Code:
mount

Antiga Prime said:
I'd be surprised if that works, given that the proper user/group for /storage/sdcard0 is "root:sdcard_rw", as it is set by default, and not "2800".
@*-MaCK-*:
Did you type in the "su" command first, on it's own?
Are you in fact rooted?
Does your storage have the proper file system format (ext4)?
You can check the file system format by running the command:
Code:
mount
Click to expand...
Click to collapse
Yes, I'm rooted. And yes, I've typed in the "su"command first.
I think that my storage doesn't have the right format. I think it was vfat?
But now things have changed. After flashing a stock rom, there is only a ejected sdcar0 left. Before i could enter the sdcard0 via device/mnt..... Now, their is no mnt map, and esfile explorer doesn't show anything. It says: "SD card ejected"
It doesn't matter if the data is lost, but i realy like to have access again too the sdcard0 drive!

*-MaCK-* said:
Yes, I'm rooted. And yes, I've typed in the "su"command first.
I think that my storage doesn't have the right format. I think it was vfat?
But now things have changed. After flashing a stock rom, there is only a ejected sdcar0 left. Before i could enter the sdcard0 via device/mnt..... Now, their is no mnt map, and esfile explorer doesn't show anything. It says: "SD card ejected"
It doesn't matter if the data is lost, but i realy like to have access again too the sdcard0 drive!
Click to expand...
Click to collapse
:laugh: It seems like I have fixed it. I managed to install the latest version of TWRP and fixed the format of the sdcard to ext4.
It is formatted and working. Very happy.
After reboot the sdcard0 was visible again. Though, I could not write too it. So I put in the next in the Terminal:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
After this, averything was normal again!
Thanx you all!:good::good::good::good:

WhiteNeo said:
Try to enter the following in terminal:
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
i have th same problem i write this code but it tell me busybox not found

[Q] Problem SDCARD0 Permisions On Ofical CM12.1 Xperia T Mint

Hi have this CM installed on my Xperia T:
12.20150616-nightly-mint
It works fine but APPS cant write to Internal Memory (SDACRD0), the camera doesn't works, whatsapp cant save images.... ect ect.
Is a Know Issue, to solve it i tried to change permisions via ADB, with this commands:
adb.exe wait-for-device
adb.exe root
adb.exe wait-for-device
adb.exe shell chown -R 2800 /mnt/media_rw/sdcard0
adb.exe shell chgrp -R 2800 /mnt/media_rw/sdcard0
I tried the same on a phone terminal as a root. the message is "operation not permited".
Pelase help

LanderXX said:
Hi have this CM installed on my Xperia T:
12.20150616-nightly-mint
It works fine but APPS cant write to Internal Memory (SDACRD0), the camera doesn't works, whatsapp cant save images.... ect ect.
Is a Know Issue, to solve it i tried to change permisions via ADB, with this commands:
adb.exe wait-for-device
adb.exe root
adb.exe wait-for-device
adb.exe shell chown -R 2800 /mnt/media_rw/sdcard0
adb.exe shell chgrp -R 2800 /mnt/media_rw/sdcard0
I tried the same on a phone terminal as a root. the message is "operation not permited".
Pelase help
Click to expand...
Click to collapse
I had the same problem with it. You should backup everything from your internal sdcard and reformat it from inside Android -> Settings -> Storage and the problem is fixed. After that copy your backup back into your phone. The problem seems to be on how the internal memory is mounted.. I experimented and actually made a shell script that worked on CM 12 to remount the internal memory after booting but stopped working on CM12.1 and had to reformat. I don't know if there's another way.

SOLVED!
captita said:
I had the same problem with it. You should backup everything from your internal sdcard and reformat it from inside Android -> Settings -> Storage and the problem is fixed. After that copy your backup back into your phone. The problem seems to be on how the internal memory is mounted.. I experimented and actually made a shell script that worked on CM 12 to remount the internal memory after booting but stopped working on CM12.1 and had to reformat. I don't know if there's another way.
Click to expand...
Click to collapse
IT WORKS!!!!!!!!!
I backup all internall storage to My computer, I Erased Internal Storage trought settings, I copied all my backup to Internal Storage, and NOW CM 12.1 works FINE!!!!!!!! Camera Works, and whatsapp can save images and videos.
MANY MANY MANY THANKS!!!