Database Info

problems accessing to /system using terminal (from the phone)

hi,
after latest upgrade (htc desire, open desire 2.3, busybox, app2sd), i have issues with the access to the file system on /system (via terminal emulator from the phone).
all works fine using adb, but when i try to delete or copy a file to /system (directly on phone), i have a error.
i have searched over inet, but i don't find :/
i attach a example below
Code:
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /system/etc/test
# ls
-rw-rw-rw root root 124 ul 22 13:54 test1
-rw-rw-rw root root 124 ul 22 13:54 test2
# rm test1
error deleting test1: directory not empty
# ls
-rw-rw-rw root root 124 ul 22 13:54 test2
# ls test1
test1

edit:
i have the same issue when i connect to my phone using adb (and the phone started, not in recovery mode)..
Code:
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /system/app
# cp -f /sdcard/install/nosense/system/app/Terminal.apk .
cp: can't create './Terminal.apk': Out of memory
# cp -f /sdcard/install/nosense/system/app/Terminal.apk .
cp: can't create './Terminal.apk': Out of memory
# cd /system/app
# cp -f /sdcard/install/nosense/system/app/Terminal.apk .
cp: can't create './Terminal.apk': Out of memory
# cd /system/app
# cp -f /sdcard/install/nosense/system/app/Terminal.apk .
cp: can't create './Terminal.apk': Out of memory

Hi there... are you new to the desire?
As far as I can remember, writing to /system/ outside of ADB in Recovery is not possible on the Desire - an unfortunate limitation of the current root methods which hasn't been circumvented yet.

oh! thx!
i have received my desire a few days ago.
my old phone was a nexus.
i agree! and sorry for the inconvenience

What inconvenience?
I was a little confused too when I started reading about root on the Desire, and the info is hard to find (buried in one [or a few] of the many root tutorials)...
The really interesting part, IMO, is whether this limitation causes any problems with root-apps. But there don't seem to be any other than Adfree, and there seem to be patched versions that work with the Desire now (IIRC by moving the Hosts file out of /system/ and symlinking to it)

Mac Terminal system remount syntax

I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now and tried all kinds of syntax, and now I'm here. What am I doing wrong? Thanks

Try:
mount -o remount,rw /system
The remount option automatically looks up the info for /system so you shouldn't have to bother with the details.

Hmm, I tried that thanks, and I still got 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'

Hmm, I can't think of any reason that wouldn't work but it sounds like your phone is locked down pretty tight. Do you know if others have been able to remount /system?
What version of busybox do you have? Maybe you could try updating it. There are one or two free busybox updater apps on the market, if you can use them.

Have you tried just 'adb remount'?
Does the mount command require busybox? Do you have that properly installed?

That requires adbd itself to be run in root mode (this is different from being rooted on the phone) & you could do that only on insecure boot image. mount/unmount both happen to come from the busybox package. It would be hard to contemplate that Motorola actually changed that but nothing would stop them from. You could try updating the busybox utility onboard your phone. There is nothing with your usage of the command - it would work the same way on my Nexus S

I do have Busybox in /system/xbin. Thinking that maybe the xbin directory may need to have the rewrite permissions, I changed its permissions to 777 using the chmod command in phone Terminal. I did the remount command 'mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system' in shell on the phone, and I THOUGHT I BRICKED! Haha, but it just turned off, and I rebooted to find that my button backlights were turned off...which I fixed with the brightness file.
Anyhow, I think I'll just use the chmod command because that seems to work. NeoA, I think you are right about the adbd to run in root mode, because I've seen discussions about that before.
Thanks for the feedback guys! At least I know I wasn't having syntax errors to say the least

So did it remount it as rw? The mount command was running before, just giving errors, but if it's running that should mean the permissions were ok.

try
Code:
busybox mount -o remount,rw /system

Fr4gg0r said:
try
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
"mount: can't find /system/app in /proc/mounts"
but
Code:
busybox chmod 777 /system
is good enough for me, for now

marlasinger said:
Code:
busybox chmod 777 /system
is good enough for me, for now
Click to expand...
Click to collapse
Using chmod to change permissions won't actually give you rw access to the system partition since it won't change whether it's mounted as read-only or r/w. To be able to run the chmod command, the system must already have been mounted as r/w or you would have received a "Read-only file system" error. It must have gotten mounted as read/write when the remount command caused a reboot. You can see how /system is mounted by just typing "mount" in adb shell which will list all of the mounted partitions.

[Q]How to get read-write access

I would like some tips on getting read-write access on my nexus s /system/media directory.
Im using Windows 7 x64 and i have seen a lot of tutorials but im not sure if they are for the correct model, as i noticed
"ext3"
"ext4"
Any help would be appreciated and thanked !!

XDA_Badman said:
I would like some tips on getting read-write access on my nexus s /system/media directory.
Im using Windows 7 x64 and i have seen a lot of tutorials but im not sure if they are for the correct model, as i noticed
"ext3"
"ext4"
Any help would be appreciated and thanked !!
Click to expand...
Click to collapse
Root.
You can then either remount manually:
Code:
mount -o remount,rw /dev/mtdblock3 /system
or flash an insecure boot image and then you can use adb remount.
Alternatively you can use something like Root Explorer if you want a GUI

I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #

XDA_Badman said:
I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #
Click to expand...
Click to collapse
adb shell first. It looks like you are still in the terminal based on the ~ prefix

XDA_Badman said:
I will try that , thanks alot also i tried 'Root Explorer' but it would not paste the file i needed.
EDIT!!
I tried it manually and i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # mount -o remount,rw /dev/mtdblock3 /system
mount -o remount,rw /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Invalid argument
~ #
Click to expand...
Click to collapse
adb shell first, then su. It looks like you are still in the terminal based on the ~ prefix You have root already, right?

krohnjw said:
adb shell first, then su. It looks like you are still in the terminal based on the ~ prefix You have root already, right?
Click to expand...
Click to collapse
Im sure i have root access,
1: I rooted it myself
2: I use root checker on my device
3: I was in 'adb shell' before, when i first tried it
But on 'Root Check' (on my device) it shows the following message in green colour text,
Congratulations! You have root access!
Standard su binary location:
ls:/system/bin/su: No such file or directory
Standard su binary location:
-rwsr-sr-x 1root root 26336 Aug 1
2008 /system/xbin/su
Alternate su binary location:
ls: /sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)

MODERATOR PLEASE DELETE
1: I forgot to change my root dir to /system/xbin/su
2: In root explorer i didnt see the 'Mount As' button lol

Return to stock firmware HTC ChaCha

Hi
I tried SuperOSR for a few months now, but i really want to use the camera so therefor i want to return to stock firmware.
I used this thread:
http://forum.xda-developers.com/showthread.php?t=1164468
Now the problem is, when i download stockrecovery and install it to the SDCARD and then i try to update it via CWM, it says:
Error in sdcard/stockrecovery.zip (Status 0) and then it stops, what now?

To flash stock recovery back you need to rename it to PH06img.zip.

and if you wanted to go back to stock rom alone, you dont need stock recovery. Just download the stock rom and install the RUU

If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img

Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App

zainthesnipe said:
Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
lol, yeah, I started with the Cliq, then Cliq XT, Defy, and now I'm working on CM7/SuperOSR for the Chacha, check http://forum.xda-developers.com/showthread.php?t=1291232
You got a Chacha?

adlx.xda said:
(if some1 could mirror it, I can't seem to access any file sharing from here)
Click to expand...
Click to collapse
Up on http://alex.swtesting.ro/downloads/ or http://swtesting.ro/alex/downloads/ for unlimited time.

when i type mount sdcard,adb show me this:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
whats wrong?
and its all of this comands:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: permission denied

ok, sorry about that, my mistake
Try that:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img

all of my phone:
C:\Users\Pasha\Desktop\adb\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#
file not found but i placed recovery.img into root of my sdcard!

From your post you're missing a / in "mount /sdcard".

not found again..
$ su
su
# mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#

The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs

Justphemy said:
flash_image: not found
[/COLOR]
Click to expand...
Click to collapse
Damn it! I thought CWM had flash_image...

help
pongzor said:
The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs
Click to expand...
Click to collapse
Could you write step by step how to back to stock revocery or show which file should I download, please

That should be a useful guide I agree

Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
flash_image is a small utility to be used on the device that allows you to re-write system partitions with image files. If you don't have it, it can be found here: http://cyanogen-files.carneeki.net/flash_image.zip (Unzip it)
You will need to install flash_image on the device, this requires the use of the SDK. So if you do not have the SDK installed, do it now.
Then go to the tools directory in the SDK,
Code:
example: cd c:\android-sdk-windows\tools
or
Code:
example: cd ~/android-sdk-linux/tools
At this point you will need to use your command line or terminal on your PC to access ADB, if you do not know how to use ADB and it is causing you to unsuccessfully perform these actions please read one of the many guides on ADB, also if the device is not recognized, you may need to uninstall HTC sync and install the ADB USB drivers in the SDK after downloading them from the setup program. (You will also need to turn on USB debugging on the device, in Settings/Applications/Development)
From command prompt or terminal:
Copy flash_image to the sdcard on the device
Code:
adb push flash_image /sdcard/
To use flash_image to flash a recovery image called recovery.img in the root of your sd card
Code:
adb shell
su [/CODE]
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
Code:
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I hope it works for you. It did for me.

adlx.xda said:
If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Hi !
When i write su and press enter it's says permission denied
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
C:\Fastboot>adb shell
$ mount -o remount, exect /dev/block//vold/179:1 /sdcard
mount -o remount, exect /dev/block//vold/179:1 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ ./flash_image recovery /sd/card/recovery.img
./flash_image recovery /sd/card/recovery.img
./flash_image: not found
$ ./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip: not found
$ ./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip: permission denied
Anybody a little help ...

[ Tutorial ] How to Install Debian Linux on Your Samsung Galaxy Fit

This is a Tutorial to install Ubuntu/Debian in any Android mobile.​
* Installing Ubuntu or Debian Linux does not format your Android OS or change anything to your phone.
The Operating Systems run over the underlying Android OS which continues to function as normal
Choosing your Linux OS:
There are few things you must be aware of before installing Ubuntu/Debian on youe Android Phone
Ubuntu does not support earlier ARM CPUs like the ones used in the Motorola Cliq. Samsung Galaxy Fit (ARMv6), Samsung Galaxy Y, etc.
( Reason behind this is , Your Android OS Kernel must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it. )
You need at least an ARMv7 CPU like the kind found in the Motorola Droid, Samsung Galaxy S,HTC EVO 3D, Sony Experia Play, etc. most newer phones (Hummingbird, Snapdragon, Tegra2, etc.).So you can Install Ubuntu if you have ARMv7 or newer Processor.
If you have ARMV6 or any other moderate Processor don't be sad, because Debian supports the CPU on practically all Android devices, so if you prefer Debian, or you can't run Ubuntu, choose the Debian download link.
* If you're not sure what CPU your device has, look up your device on http://pdadb.net/, click the link under CPU, and read the line for "Supported Instruction Set(s)".
e.g. : My Phone which is a " Samsung Galaxy Fit" uses ARMV6 Instruction Sets.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Pre-Requirements:
Hardware Required:
an Android Phone
SD Card with more than 2GB of free Space
Android root environment:
Most important! Your Android device should be “rooted” because you need root access to run Ubuntu/Debian off your Android. If your device is not rooted you have to root your device.
Linux Operating System:
Download suitable OS from the following Link:
Ubuntu 11.04 (Natty Narwhal)
linux.ubuntu-natty.tar.bz2 Ubuntu 11.04 (Natty)
Ubuntu 11.10 Oneiric Ocelot
linux.ubuntu-oneiric.tar.bz2 Ubuntu 11.10 (Oneiric)
Debian 6.0 Squeeze
linux.debian-squeeze.tar.bz2 Debian 6.0 (Squeeze)
Click to expand...
Click to collapse
Applications Required:
BusyBox Installer
A terminal emulator like Better Terminal Emulator ( Recommended ) or Terminal Emulator.
Optional Apllications:
androidVNC
Or
ConnectBot
Click to expand...
Click to collapse
Procedure ----------------------------------------------->
Step 1:
(Mount the SD card on your computer.)
Extract the .tar.bz2 file you downloaded to your SD card. You should now have a folder named "linux" on the root of your card.
(Unmount the SD card.)
Open Busybox Installer, and install Busybox.
Open Better Terminal Emulator, and install Better Terminal Emulator.
Click to expand...
Click to collapse
Step 2:
Open your terminal emulator. (If using ConnectBot, connect to 'local', not 'ssh'.)
Run the following commands:
Code:
[B]su[/B]
( If Prompt for Superuser Request then allow )
Code:
cd /sdcard/linux
sh install.sh
If you don't see any errors, Linux is now installed.
Click to expand...
Click to collapse
Step 3:
Open your terminal emulator.
To start a chroot session
Code:
su
linux
To start the SSH server
Code:
su
linux ssh
You can then use ConnectBot (SSH: [email protected]) on your device, or any SSH client to connect to your device. See Login Information, below.
Click to expand...
Click to collapse
To start a VNC session
( Firest you need androidVNC to be installed , then type the following in terminal )
Click to expand...
Click to collapse
Code:
su
linux vnc
The first time you run VNC, it will prompt you to create a VNC password.
You can then use androidVNC (host: localhost port: 5901), or any VNC client to connect to your device.
Configure The VNC App as follows:
Note: The default desktop environment is icewm. If you wish to replace it, for example, with LXDE:
Run the following as root in Linux:
Code:
apt-get autoremove icewm- lxde+
Secure your Log in Password:
Please remember to change these passwords if you are planning on using the SSH server. Malicious people can do Very Bad things to your device if you don't.
There are two accounts included in the images:
root
Password:cheesecake
user
Password:dessert
Click to expand...
Click to collapse
After a successful connection to host you will be able to use Ubuntu / Debian in graphical interface just like in your PC ! It will keep your Android OS as it is and just run in the upper layer over it
These are some of the screen shots taken from my Samsung Galaxy Fit!
Click to expand...
Click to collapse
Linux vs Linux Terminal Emulator :
Terminal Emulator only Emulates Linux terminal, but after Linux Installation you can get full features; more than just the limited commands which runs on Android shell rather than Linux Shell.
Please Leave your Feedback and Queries below. Thank You
​

Verry Good
I'll test it now. Thanks for the tutorial

Did a long time ago...
even i managed to install Backtrack 5..
anyway nice post...
there is app call BotBrew...try it...

vs4vijay said:
Did a long time ago...
even i managed to install Backtrack 5..
anyway nice post...
there is app call BotBrew...try it...
Click to expand...
Click to collapse
Nice app Bro
Its very hard to get low end devices to perform flawlessly.
but who cares as long as u can work around it

great thanks

screenshots please.

Linux won't install
I love this forum. Over the last couple months I've been reading the forums and learning how to root my phone and install custom ROMs. For the last 10 years I've been using Linux on my computers and netbooks. I like Android because it's a mobile version of Linux, but I would like to get a full version of Linux running on my phone. I followed this thread many times with and cannot get Linux to install. I'll try to give the details:
I am running a rooted Samsung Galaxy S 4G T959V running the Valhalla-Black edition ROM (Gingerbread). I installed Busybox V1.20.0 and Busybox Installer V1.20 without uninstalling either. I have Android Terminal Emulator installed with su privileges. I keep getting the same mount error with all the 3 linux images shown on this thread. Here is what I got (the first error has to do with mount):
****************************************************************************************************************************************************
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
cp: can't create '/system/bin/fsrw': File exists
Unable to chmod /system/bin/fsrw: Read-only file system
cp: can't create '/system/bin/linux': File exists
Unable to chmod /system/bin/linux: Read-only file system
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
*********************************************************************************************************************************
What am I missing here?
Marty

LinuxHippy said:
I love this forum. Over the last couple months I've been reading the forums and learning how to root my phone and install custom ROMs. For the last 10 years I've been using Linux on my computers and netbooks. I like Android because it's a mobile version of Linux, but I would like to get a full version of Linux running on my phone. I followed this thread many times with and cannot get Linux to install. I'll try to give the details:
I am running a rooted Samsung Galaxy S 4G T959V running the Valhalla-Black edition ROM (Gingerbread). I installed Busybox V1.20.0 and Busybox Installer V1.20 without uninstalling either. I have Android Terminal Emulator installed with su privileges. I keep getting the same mount error with all the 3 linux images shown on this thread. Here is what I got (the first error has to do with mount):
****************************************************************************************************************************************************
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
cp: can't create '/system/bin/fsrw': File exists
Unable to chmod /system/bin/fsrw: Read-only file system
*********************************************************************************************************************************
What am I missing here?
Marty
Click to expand...
Click to collapse
I guess mount command in install.sh didnt work
Maybe you can edit it. to correct one, may be this or may be not
Code:
echo "Remounting /system rw ..."
#busybox mount -o remount,rw /system
sh $kit/scripts/fsrw

zcop said:
I guess mount command in install.sh didnt work
Maybe you can edit it. to correct one, may be this or may be not
Code:
echo "Remounting /system rw ..."
#busybox mount -o remount,rw /system
sh $kit/scripts/fsrw
Click to expand...
Click to collapse
I placed these lines in install.sh and deleted the 3 original lines that looked similar to it. I still got messages about mount, but these are a bit different:
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished

Full install.sh
Code:
sdcard=$(readlink -f /sdcard)
kit=$sdcard/linux
img=$kit/linux.img
mnt=/data/local/mnt
export bin=/system/bin
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=screen
export HOME=/root
echo "Remounting /system rw ..."
[COLOR="Red"]#Mount command
busybox mount -o remount,rw /system
#This script just mount system. We mount it above so we dont need it again.You can see [B]fsrw[/B] with notepad....
#sh $kit/scripts/fsrw[/COLOR]
echo "Installing scripts in $bin ..."
cd $kit/scripts
for file in *; do
cp $file $bin
chmod 755 $bin/$file
done
cd - > /dev/null
echo "Mounting the Linux image ..."
#mount the image
$bin/linux mount
echo "Customizing the image ..."
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
#echo "Setting localhost on /etc/hosts "
#echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo " Installing root-scripts ..."
#install custom root-scripts in $mnt/root/scripts
if [ ! -d $mnt/root/scripts ]; then
mkdir $mnt/root/scripts
fi
chmod 755 $mnt/root/scripts
cp $kit/root-scripts/* $mnt/root/scripts
chmod 755 $mnt/root/scripts/*
echo "Install finished"
Try it again and let see what happen

same thing:
Remounting /system rw ...
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished

so install.sh working. Now problem is in /script/linux
edit
Code:
mount -o dev,remount $sdcard
to
Code:
busybox mount -o dev,remount [COLOR="Red"]$sdcard[/COLOR]
it not work change $sdcard to /mnt/sdcard

zcop said:
so install.sh working. Now problem is in /script/linux
edit
Code:
mount -o dev,remount $sdcard
to
Code:
busybox mount -o dev,remount [COLOR="Red"]$sdcard[/COLOR]
it not work change $sdcard to /mnt/sdcard
Click to expand...
Click to collapse
It got a little further this time by adding this to /sdcard/linux/scripts/linux:
busybox mount -o dev,remount
this is what happened:
# sh install.sh
Remounting /system rw ...
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Mounting: Loopback mount ...
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished

hey guys.
Thanx to the author of this forum on debian on android. I had the same problem you see in the error logs above. the problem is between regular "mount" command and busybox "mount". you need to use the busybox mount. so I added the word busybox infront of every mount word in the script. eg. busybox mount -o , rw /system remount. the alternative is to delete the mount found on /system/bin so that the terminal will use the busybox one automatically on /system/xbin.

nice tutorial

Good article but...
I have some issues about installing it.I tried it with XXKPI 2.3.4 on my Fit but it only caused my phone to give me bunch of error codes on the terminal and my phone started to not dedecting sdcard and sometimes it doesnt mount on computer.I have SdCard issues.I have edited all the mount codes in fsrw,linux and install.sh (by typing a busybox like busybox mount -o)but still have problems.I have installed XXKPI in 4 Part inst. with Odin and wiped the device before and after the installation and after the Odin inst. i rooted it with UnlockRoot v 2.2.1 so it is rooted.Done a binary update on SU and installed BusyBox 1.9.3 because newer versions are incompatible with my phone.This is my last terminal session(all included)
Code:
$ su
# cd /sdcard/linux
# sh install.sh
Remounting /system rw ...
mount: mounting /dev/stl12 on rfs failed: No such file or directory
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Mounting: Loopback mount ...
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: mounting /dev on /data/local/mnt/dev failed: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting /sys on /data/local/mnt/sys failed: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: mounting /mnt/sdcard on /data/local/mnt/media/sdcard failed: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
#
So what can i do about it?I want to install Debian 6.0 so much and i am getting impatient about it.
Any help would be appreciated.
Sorry for my English if i have mistakes.

R: [ Tutorial ] How to Install Debian Linux on Your Samsung Galaxy Fit
Is possible install aircrack-ng airodump-ng and airmon-ng on ubuntu...
Sent from my GT-5670 using xda premium

can't install inside debian
I managed to install debian and in terminal mode, i cannot install anything, i get the error about "ldconfig" when installing xterm
dpkg: warning: 'ldconfig' not fount in PATH or not executable
the same with 'start-stop-daemon'
can you help me? i wish to install a terminal like xterm inside debian and some other app
Regards,

Works
Thanks
I was able to install this on my galaxy fit very smooth. Like your tutorials

Dwi Aulia Rahman Putra said:
screenshots please.
Click to expand...
Click to collapse
Screens have been given