Database Users

cp: write error: no space left on device in system

I have been having this error message come up using the terminal. I was attempting to add the volume enhancements via Lucid's script on the hybrid JF 1.51 with the HTC apps. I have asked Lucid if he knew how to solve this, but i wanted to see if anyone else might know the solution. I have been searching on here and also on google and yahoo but I have yet to find anything. I even took out my sd card to see if that would help after restarting my phone but nothing. Did i just screw myself?

innerlight said:
I have been having this error message come up using the terminal. I was attempting to add the volume enhancements via Lucid's script on the hybrid JF 1.51 with the HTC apps. I have asked Lucid if he knew how to solve this, but i wanted to see if anyone else might know the solution. I have been searching on here and also on google and yahoo but I have yet to find anything. I even took out my sd card to see if that would help after restarting my phone but nothing. Did i just screw myself?
Click to expand...
Click to collapse
i'm not privvy to lucid's script, but..
remount /system rewrite
do a cp -f to the files you are replacing
remount /system read-only
if you still get no space left, reboot your phone, then try again.

pershoot said:
i'm not privvy to lucid's script, but..
remount /system rewrite
do a cp -f to the files you are replacing
remount /system read-only
if you still get no space left, reboot your phone, then try again.
Click to expand...
Click to collapse
forgive my ignorance but do I type this in terminal as is? Because when I do that it cannot find remount.

I think I found the problem as to why I saw that error. I went from JFs-1.51 US built to the hybrid one that cyanogen did (the JF-1.51 + HTC apps) and I think there maybe something wrong inside there. First wiped and flashed JF's one and then wiped and flashed the cyanogen one and the problem is there.

innerlight said:
forgive my ignorance but do I type this in terminal as is? Because when I do that it cannot find remount.
Click to expand...
Click to collapse
copy the three files needed for the volume increase (2 if your on JF (AudioFilter and AudioPara4)) on to the sdcard in to lets say a directory named 'audio'. make sure you have unmounted the sdcard from within your OS after you have completed the copy, and have unplugged the USB cable.
open up terminal (on your phone)
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /sdcard/audio
# mkdir BK
# cp -p /system/etc/Audio* ./BK
# cp -f AudioFilter.csv /system/etc
# cp -f AudioPara4.csv /system/etc
# cp -f AudioPara_TMUS.csv /system/etc
# mount -o ro,remount /dev/block/mtdblock3 /system
# exit
$ exit
bounce your phone.

pershoot said:
copy the three files needed for the volume increase (2 if your on JF (AudioFilter and AudioPara4)) on to the sdcard in to lets say a directory named 'audio'. make sure you have unmounted the sdcard from within your OS after you have completed the copy, and have unplugged the USB cable.
open up terminal (on your phone)
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /sdcard/audio
# mkdir BK
# cp -p /system/etc/Audio* ./BK
# cp -f AudioFilter.csv /system/etc
# cp -f AudioPara4.csv /system/etc
# cp -f AudioPara_TMUS.csv /system/etc
# mount -o ro,remount /dev/block/mtdblock3 /system
# exit
$ exit
bounce your phone.
Click to expand...
Click to collapse
Thanks for the reply. I am still getting the same error with the JF-1.51+HTC apps build. I told Cyanogen about it and hopefully he will get it sorted out because his built is faster than the regular JF build. I guess I have to decide if the added HTC apps are worth more than the sound increase.

Adding blur alarm to Fission ROM

For those of you that felt in love with the Blur Alarm and looking for a way to add it back. I have figured out the missing files beside the apk that goes in the system\app. This has been tested with sucess for Fission ROM v2.0.1.
Adding Blur alarm
system\app\BlurAlarmClock.apk
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Hope it help.

nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.

braway said:
nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.
Click to expand...
Click to collapse
What ROM are you using? I renamed the original DeskClock.apk to DeskClock.bak since I don't have a docking station. May be it has something to do with the dlauncher. I also deleted the original launcher2 and replaced it with launcherpro.apk.

Fission 2.0.2
I basically did the same with the DeskClock.apk
but added the Dock.apk from the clean verizon rom (which is basically the "stock" droid2), I guess I'm simply missing something
btw, com.motorola.dlauncher is Dock.apk
I guess something is still missing which would set the missing permission oO

got it to work...
if someone cares:
I had to manually modify the /data/system/packages.xml
it should contain something like this:
Code:
<package name="com.motorola.dlauncher" codePath="/system/app/Dock.apk" flags="1" ts="1288859615000" version="8" userId="10057">
<sigs count="1">
<cert index="1" />
</sigs>
</package>
userId and ts are probably different
change the cert index to 0 !
reboot (right after it, for example with adb reboot)
after reboot, check that your change is still in this file (should be)
put your phone into the docking station, and the blur dock should start
yay

lol, this default blur alarm app is awesome and best I have seen. I was so surprised at what it wanted me to do when I first woke up to it , lol

I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks

rkrasny said:
I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks
Click to expand...
Click to collapse
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...

braway said:
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...
Click to expand...
Click to collapse
Perfect; thanks much.

Question?
How do I add this to my phone and make it work? Do I need to use ADB and move it to the phone or what? I really liked the blur alarm a lot and would like to get that back if I can. Thanks for any help in advance.

You just need a method to transfer the files to the phone to the correct spot
ADB or root explorer can move the files
I will show the adb method below, you can substitute the adb shell, mount, cp (copy), chmod (change permissions), and rm (delete) steps with Root Explorer
ADB
Open a command prompt
cd to the directory where you have the files on your computer
Code:
adb push BlurAlarmClock.apk /sdcard/BlurAlarmClock.apk
adb push blur-res.apk /sdcard/BlurAlarmClock.apk
adb push com.motorola.blur.library.utilities.jar /sdcard/com.motorola.blur.library.utilities.jar
Then adb shell to the phone, mount system as r/w, copy the files to the system
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurAlarmClock.apk /system/app/BlurAlarmClock.apk
cp /sdcard/blur-res.apk /system/framework/blur-res.apk
cp /sdcard/com.motorola.blur.library.utilities.jar /system/framework/com.motorola.blur.library.utilities.jar
Then set the permissions on these files so they will work
Code:
chmod 644 /system/app/BlurAlarmClock.apk
chmod 644 /system/framework/blur-res.apk
chmod 644 /system/framework/com.motorola.blur.library.utilities.jar
You can then remove the files from the sdcard if you wish
Code:
rm /sdcard/BlurAlarmClock.apk
rm /sdcard/blur-res.apk
rm /sdcard/com.motorola.blur.library.utilities.jar
Now mount the system as read-only again
Code:
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
As for the Blur dock
Use the same steps above to copy the file and move it to the system
Code:
adb push Dock.apk /sdcard/Dock.apk
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Dock.apk /system/app/Dock.apk
chmod 644 /system/app/Dock.apk
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /sdcard/Dock.apk
Next pull the packages.xml file
Code:
adb pull /data/system/packages.xml
Edit packages.xml as shown in the above post
Then push back
Code:
adb push packages.xml /data/system/packages.xml
When you "install" the blur dock, you might want to remove the standard android dock
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mv /system/app/DeskClock.apk /system/app/DeskClock.bak
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Notice I just used mv (rename/move)
This is just in case I want it back later
You may need to reboot the phone when you are finished for this to work.
I never tried without rebooting so I don't know if they will work otherwise.

Why 'adb remount' failed on a Rooted neuxs one

Hi,
I have rooted my Nexus one. I can do "'adb shell and then 'su' under the shell"
But on my MacOS Desktop, when I execute 'adb remount', it still said
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Can anyone please help me resolve this?
Thank you.

[size=+4]DO *NOT* POST QUESTIONS IN THIS FORUM - only tips/info/etc.[/size]
Right at the top. Why does this have to be repeated on a daily basis?

Can you please move my thread to the right forum? I can't find a way to do it.

Anyhow, to answer you question... you "adb remount" is disabled in production releases... just rooting does not allow this.
You need a modified boot image where ro.secure=0 in default.props, instead of ro.secure=1. The ro.secure flag in the boot image indicates whether the root filesystem can be remounted as read/write... 0 indicated it can be... 1 indicated it cannot be.
If ro.secure=0, this is referred to as insecure boot.
Most custom ROMs have this by default... some rooted stock ROMs do not have this...

Will the Modified GRI40 (2.3.3 Gingerbread) ROM from this
http:// forum.xda-developers.com/showthread.php?t=968396
Does what I need? Thanks.

Or you can also use these commands to mount and unmount the system partition as writable:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,ro /dev/block/mtdblock3 /system

Thank you. That seems to be an easier solution for me.
But after I did
$ adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I go to another shell and i did
adb push sqlite3 /system
failed to copy 'sqlite3' to '/system/sqlite3': Read-only file system
$ adb push sqlite3 /system/bin
failed to copy 'sqlite3' to '/system/bin/sqlite3': Permission denied
Click to expand...
Click to collapse
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.

hap497 said:
Thank you. That seems to be an easier solution for me.
But after I did
I go to another shell and i did
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
Click to expand...
Click to collapse
Don't try to combine adb commands with shell commands.
Copy/move/push the file to your sdcard first.
Then open a root shell, mount it as rw, then copy the file from your sdcard to the directory you want.

Thanks. but I get 'failed on '/sdcard/sqlite3' - Cross-device link'
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/sqlite3 /system/
failed on '/sdcard/sqlite3' - Cross-device link
# ls -l /sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
and i have tried:
# mv /mnt/sdcard/sqlite3 /system/bin/
failed on '/mnt/sdcard/sqlite3' - Cross-device link
# ls -l /mnt/sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
I get the 'sqlite3' from SuperOneClickv1.7-ShortFuse.zip.

Wholly crap, don't use the mv command! Bad idea!!! mv does not move the data, it moves the hardlink to the data! Thank your lucky stars mv wouldn't let you do it.
Use cp instead. cp will actually copy the data to where you're going.

Thank you. But I don't have 'cp' in my adb shell.
# cp
cp: not found
# /system/bin/cp
/system/bin/cp: not found
Click to expand...
Click to collapse
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin

How do you have mv but not cp? Do you not have BusyBox installed?

No. I just need to search 'BusyBox' on Android market and install it? That is?

hap497 said:
Thank you. But I don't have 'cp' in my adb shell.
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
Click to expand...
Click to collapse
The cat command will work fine, no busybox needed: cat source_file > dest_file

efrant said:
The cat command will work fine, no busybox needed: cat source_file > dest_file
Click to expand...
Click to collapse
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
OP, Yes, BusyBox can be installed from the market.

GldRush98 said:
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
Click to expand...
Click to collapse
Really? I was unaware of that. It worked every time I used it.

efrant said:
Really? I was unaware of that. It worked every time I used it.
Click to expand...
Click to collapse
On standard Unix/Linux/etc. systems, cat works fine for binary files. It's only under DOS that cat or type shouldn't be used for binaries.

back in my ADB days.. itd say remount failed or w.e but i could still access my phone..
but i dont know.. ever since i switched to linux i stopped using ADB.. hahah

sl4a shell script help

Hi all,
I'm trying to run a shell script in sl4a but I'm running into problems. Here's what I want to do: change ADW configuration files in one click (since the app doesn't yet do it natively). There are two files that need to be changed for this to happen:
Code:
/data/data/org.adwfreak.launcher/databases/launcher.db
/data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I'm trying to delete those files and copy in new files from a stored location on the SD card but I can't get the sl4a script to run the following rm commands:
Code:
rm -rR /data/data/org.adwfreak.launcher/databases/launcher.db
rm -rR /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I use
Code:
su -c
before the rm commands to run them as root, but the error then is that the /data partition is not mounted (which I find strange since it should be rw anyway...). I've tried using
Code:
mount -o remount,rw /dev/block/userdata /data
and it looks like it runs but then it doesn't work and I can't rm the files anyway.
Am I running into a limitation of sl4a or shell scripts in sl4a? I can rm the files from the terminal, so I'm not sure what the issue is. I'm very new to this (obviously) so any tips would be helpful. Thanks!

Here is my full script currently:
Code:
#!
kill android.process.acore
kill org.adwfreak.launcher
busybox rm -R /data/data/org.adwfreak.launcher/databases/*
busybox rm -R /data/data/org.adwfreak.launcher/files/*
busybox rm -R /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw_ex_launcher.db /sdcard/ADW/Honeycomb/adw_ex_launcher.db
cp /sdcard/adw_ex_settings.xml /sdcard/ADW/Honeycomb/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /sdcard/adw_ex_launcher.db
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /data/data/org.adwfreak.launcher/databases/launcher.db
chmod 664 /data/data/org.adwfreak.launcher/databases/launcher.db
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /sdcard/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
chmod 664 /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
exit
When I test the rm commands in the sl4a shell, they don't remove the files even when the /data partition is mounted. I've tried all that I know. Help please!
Sent from my DROIDX

I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.

Thanks for the response.
I'm trying to change ADW configuration with one click. I'm going to use Tasker to create a widget that, when clicked, runs a script. That script will:
1. delete the current ADW configuration files (launcher.db and adw_ex_preferences.xml)
2. copy the target configuration files to the proper places (and set permissions, owner, group)
3. restart ADW so that the configuration is loaded
OR
3. open the ADW settings page so that I can click "restore desktop" and "restore preferences" and have the configuration loaded in an almost-one-click solution.
The script in the 2nd post is my best effort at that. I have tried the busybox part of the script, but I don't believe it makes a difference. I will try again, though, and report back.
As far as chown and chgrp goes, I'll add in what I think that should be and post that back later, too.

Fr4gg0r said:
I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.
Click to expand...
Click to collapse
Progress update: Success! More or less.
I realized I wouldn't need to remove the files since the ones I was copying in would just overwrite them anyway, so that cleared up that issue.
I did add chown and chgrp (a piece of information I'm sure I'll find useful in the future) so I'm sure that helped. Making sure to get the group and owner right PER YOUR OWN SETUP was key. When I changed ROMs I had to redo it... so check properties with Root Explorer or whatever.
I revised my script a little to add the background wall paper, too.
The true key, however, was using Lua in SL4A and using the 'sush' script in this post here:
http://code.google.com/p/android-scripting/issues/detail?id=184 (comment #9). That allowed me to run my script in the 'sush' format and do what I wanted.
I also had to add a line to kill the launcher process (android.process.acore) so it would restart itself.
I now have a one-click solution to changing between two ADW desktop configurations/settings!
I've attached my script if anyone would like it. Just get SL4A, the Lua interpreter, and put the pieces together! (Use a custom shortcut on the desktop and not a widget and the desktop setup will be preserved; widgets aren't supported in any method...)

Help with installing a theme! Kinda urgent...

Im hoping to get some help to get a theme installed on my phone.
It is rooted successfully, busybox is installed successfully also.
Im trying to put the Minimal Matte theme on my phone, but no success. Actually, I managed to make my Contacts disappear...
So, I would greatly appreciate help! I don't know why the adb commands are not working that are given here:
Code:
adb shell mount -o remount,rw /dev/block/stl16 /system
adb push Contacts.apk /system/app/
adb push DialerTabActivity.apk /system/app/
adb push Settings.apk /system/app/
adb push framework-res.apk /system/framework/
adb push twframework-res.apk /system/framework/
If I try it like that, the mounting does not work cuz it says "not permitted". So then I try like this and I get this. So it is not working. How do I fix this and how do I get the theme into my phone? Thank you for help,
Here's what I tried:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# push Contacts.apk /system/app/
push Contacts.apk /system/app/
push: not found
#

Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?

Please note that your phone must be rooted! Your phone is rooted right?

barqers said:
Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?
Click to expand...
Click to collapse
Let me try this...
Im very new to all this, so I'd like to learn the tricks manually so I have a better understanding.
barqers said:
Please note that your phone must be rooted! Your phone is rooted right?
Click to expand...
Click to collapse
As stated in the first post, it is rooted and busybox is installed. Now..let me try your tips. I will report back.

Hmm..still facing the "permission denied" with these commands:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied

Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life

barqers said:
Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life
Click to expand...
Click to collapse
Tried this, but it seems I have to reboot since it did not work.
It does not let me use "adb shell mount -o remount,rw /dev/block/stl9 /system" when I try it. Only when I do the "su" first and then try that...
Now let me try again after reboot.

Still no dice...
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied

Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.

barqers said:
Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.
Click to expand...
Click to collapse
Well, when I go and click the superuser app and all, I can see stuff happening there. Also, it has asked for permission before for adb when I first used it and I gave it. Now it appears on the list there...so it seems to be working correctly, no? And I did it with the superoneclick and it ran through it smoothly as ever. Now let me try if adb is being fussy.

Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...

PolarSoul said:
Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...
Click to expand...
Click to collapse
ADB is being truly fussy! Do you have root explorer? Here is my best guess for you. Move the Contacts.apk to the /system/app/ folder manually with Root Explorer, then follow this guide to give the app root permissions:
http://francoforr.blogspot.com/2010/12/cant-reinstall-apks-easy-fix.html

Have to go find Root Explorer.

PolarSoul said:
Have to go find Root Explorer.
Click to expand...
Click to collapse
Root explorer is a paid app. But maybe ES File Manager or Astro File Manager will give you root capabilities too!

I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.

PolarSoul said:
I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.
Click to expand...
Click to collapse
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/

barqers said:
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/
Click to expand...
Click to collapse
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.

PolarSoul said:
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.
Click to expand...
Click to collapse
No problem~! Haha, yes we do But I think Finland is far from Canada!
I'm hoping it works for you!

It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?

PolarSoul said:
It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?
Click to expand...
Click to collapse
If you check settings -> SD card and storage. How much memory does it say you have? If you have less then 10mb either move some apps to the sd card or uninstall some!