Database Develop

How to push files using busy box in the terminal emulator

Hello folks, i have a quick question... i have cyan mod 4.1.99 installed on my phone which im sure comes equipped with busybox. I am trying to find the commands that i would type into terminal emulator to push .apk files without having to use adb.. my pc went up and all i have is my g1 phone now. Is it possible to do what adb does like install, push, and pull files through terminal emulator and busybox? If so what are the commands, or is there a thread with a list of commands? Thanks in advance

to install an app
busybox install <path to apk>
there may be an arguement im missing.....but it should still work (if you put in a random argument or do -h or -help, it should give you the lists. i dont remember what they are though)
for moving files, use the mv and cp commands (mv = move, cp = copy paste)
ie
cp /sdcard/app/heroled.apk /system/sd/app
Click to expand...
Click to collapse

Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system

Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system

bbbblack said:
Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system
Click to expand...
Click to collapse
its block, not black
that should mount as rw

SuperD latest changing physical layout

I ve noticed that many people have posted having problems with keyboard layouts after flashing a rom. I have a German G1 which was rooted to Cyanogens 4.2.14.1 before, and I never had problems keeping the phone in English but retaining the German keyboard (I ve gotten use to it).
But after flashing Super D just now (which is AWESOME), my keyboard has defaulted back to the U.S keyboard, which is really annoying.
Anyone know exactly why this problem didnt exist in Cyanogens rom and why it does exist with SuperD? Also, Im assuming this is something I have to live with, as I couldnt find an easy fix for it? I really just want the German keyboard back.
Any help would really be appreciated.

1.SuperD isnt Cyanogen
2.Most Likely in the scripts that have to do with the keyboard.
Hope that didnt sound rude but yeah =/ You would probably have to change something in the system/usr directory.

I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.

kugelfish said:
I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.
Click to expand...
Click to collapse
This is exactly what I tried, but after the "dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin" command in terminal, I get an error that says:
"cannot open for write: Read-only file system"
Not sure what Im doing wrong. I unzipped the file, put it on sd card, and entered in the commands.
I heard this method works for everyone, but for some reason I get this error when i try it.

Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system

kugelfish said:
Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system
Click to expand...
Click to collapse
Still no luck. I double checked, and its typed correctly. I tried swapping this command:
mount -o remount,rw /dev/block/mtdblock3 /system
for this one:
mount -o rw,remount /dev/block/mtdblock3 /system (found in another thread)
but it still didnt work. After I tried using the "mount -o rw,remount /dev/block/mtdblock3 /system" command that I found in the other thread, I didnt get the error, and thought this may have fixed the keyboard. But when I rebooted, the keyboard was still wrong.

Sorry dude, that's all I got. All I can say is, it works for me.
Maybe this'll help?
http://www.handy-faq.de/forum/htc_d...ogle_g1_qwertz_tastatur_wiederherstellen.html

try: mount -o rw,remount yaffs2 /system

bubonik said:
try: mount -o rw,remount yaffs2 /system
Click to expand...
Click to collapse
It worked!!! Thanks to everybody for all there help. It was this one command line that made all the difference!
So nice to have a keyboard again where all the keys actually display what they are supposed to. It was driving me crazy.
Thanks again guys

[Q] Hello there have some problems with moving system files

Hi i moved some files from system/app into the sd card to get some space so i could use the metamorph app but i didnt work so i was going to move back the files from the sd card to system/app but now they wont move there anyone know a soloution how to do this?
thanks in advance

system is readonly
you must do an
adb shell
mount /dev/block/mtdblock3 /system
then you can fool around with your system apps

mount /dev/block/mtdblock3 /system || I wrote that but it says
"mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy"
i rooted my phone yesterday quite knew to android and i have no clue what to do

You are doing that in recovery mode right?

I tried in ClockworkMod Recovery v2.5.0.1 but it says Device or resource busy :/ have no clue.

ClockworkMod has a nice green menu on screen from where you can see (partitions menu) which partitions are already mounter and which are not.
You can also do adb shell and run "mount" in it to see which partitions are mounted and in what way. ClockworkMod has /etc/fstab so you can mount system just by running "mount /system". If system is already mounted, you can cd to /system/app and try "touch test". If you get permission denied then your system is mounted read-only otherwise you will see test file in /system/app if you run "ls".

I did adb shell and did run "mount" and it says /dev/block/mtdblock3/ on /system type yaffs2 <ro>
I downloaded a app called root explore and the main reason for that was so i could move some files from system/app so i could get some free space so i could use metamorph that was my plan and i moved some files i have eard you could move that wouldnt harm anything but it wasnt enough free space, so my plan was to move back the files i had moved into the sd card some went great but i have like 4 files that i cant bks it says "You cannot paste here because the file system is read-only" is there any other way to push those file into the system/app again? have tried the things u wrote up.
And im not a very pro of theese things i started with this yesterday so excuse me for being stupid!

This:
/dev/block/mtdblock3/ on /system type yaffs2 <ro>
...means that system is mounted read-only (mind that "ro" at the end).
Try running "mount -o remount,rw /system". If it doesn't help run "cat /etc/fstab" and post here the output. You need to be in recovery mode while doing this of course!

did "mount -o remount,rw /system" and it said mount: can't find /system in /proc/mounts
and the other one said
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw

used my brain a little now and in the recovery settings i did mount the /system in the menu and now i tried to write cd /system/app and now in the cmd it is like this "/system/app #" anything useful?

Sure... as I already told you try to run "touch /system/app/test". This command shoud make empty test file in /system/app. If you get permission denied then you have read-only system. If it suceede, then your /system is writable and you can see all the contents of /system/app by runing "ls".

I wrote that and it wrote the same
"touch /system/app/test"
no permmission denied then it may have worked?

i checked and there is a testfile in /system/app now

I think i got it to work now thanks man for all your help!

[Q] Mounting /system partition under adb shell

Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers

masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
try: adb shell mount -o remount,rw system

Code:
adb remount
It should do the trick too

gromez said:
Code:
adb remount
It should do the trick too
Click to expand...
Click to collapse
lol, that's shorter indeed

adb remount will only remount an existing mount, it won't create one.
It's not clear what the OP wants.
You don't need rw to deodex a ROM because you certainly don't want to write to system whilst you're doing it.
Also, I thought the stock ROM was deodexed?
To mount system in recovery, which will give you rw access and allow you to pull the files you need you just type:
Code:
mount /system
or
Code:
adb shell mount /system
Because system is included in /proc/mtd

to all: the answer is:
mount -o rw,remount /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse

masi0 said:
to all: the answer is:
Click to expand...
Click to collapse
Hello
in my case, what it worked:
mount -o rw,remount /system

Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app

Micronuub said:
Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I already reported it

In my case except adb nothing is working as i cannot access system folder.
In my case except adb nothing is working as i cannot access system folder.
Can anyone suggest me what to do or what i should do as no flash tool or anything other option is working except adb.
also $ SU is not working please help me its driving crazy.
TheSSJ said:
I already reported it
Click to expand...
Click to collapse

Here's a solution
masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.

helllpppp
rktcool said:
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.
Click to expand...
Click to collapse
i used an app ldc dpi modder n its bricked with black screen n im on cm10 now it want to change chmod to 644 for my lww but i dont know how to do that please help me with step by step guide im new to this things

this worked for me:
mount -o rw,remount /system

[Q] R/W mount

I have a rooted Nexus 7 running the Eclipse custom ROM. Somehow, I cannot mount file system for R/W using "mount/system (rw/ro)" app nor using ADB method. I'm not getting any error from the mount/remount, but I still read only file warnings. I don't have any problem getting the R/W right on Nexus phone using the same way I described. I'll appreciate your help.

Code:
$ su
# mount -o remount, rw /system
???

korockinout13 said:
Code:
$ su
# mount -o remount, rw /system
???
Click to expand...
Click to collapse
I have no problem executing commands you listed, but read only.