Permission denied though phone is rooted - Android Software Development

I am trying to get lynx text based browser working on my phone.
I extracted from the lynx.tar.gz file by using -
tar -xzvf foo.tar.gz
This works fine but when I try to run the configuration script using -
./configure
I get a permission denied error though I am logged in as root user. Can anyone help me with this?

Did you mark it executable? (chmod +x configure)
Regardless, automake, autoconf, make, gcc, etc... aren't on Android, so you won't be able to build anyway. You will need to try and setup a cross compile setup using the NDK and/or sources.

Yes I did mark it as an executable. But, no luck.
And, meanwhile I dug in deeper and read about how to get these to work on android and well it wasn't as straight forward as I thought it would be Thanks kllrnohj.

Related

problems installing anything

I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.
if yr installing through and use
Make sure phone is synced
Make sure app is in tool file I'd adk file
Make sure when at command prompt Ur in adk/tools file first
Adb remount
Adb push (app.apk) /system/(app/framework)
ok I figured out my problem but fixing it is going to be quite confusing. Looks like I would have to know a lot more than I do to fix it. Basically the adb is not reading the phone as root (or something like that). And the ro.secure is set to 1 which it should be set to 0 to be considerd root. So therefore I have to reinstall a bootimg. Ive been reading it on another forum page but i cant post it cause my account hasn't been verified yet. but it's this forum and here is the thread showthread.php?t=443041&page=2
but it's like french to me!!! If anyone can dumb this down for me I would really appreciate it lol thanks a lot you guys have been so much help in the little amount of time ive been a member to this forum. Thank you
redlinethecar said:
I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.
Click to expand...
Click to collapse
First, put your apk's in your "C:\AndroidSDK\Tools\" Folder
Second open the cmd window and do "cd C:\AndroidSDK\Tools\"
Third do "adb remount"
Fourth "adb push xxxx.apk /system/app/"
that will install them
When remounting I get error
Code:
remount failed: Operation not permitted
but I continue anyway and the
Code:
adb push HTC_IME.apk /system/app
sends the file with no problem but it doesn't install it though.
Here are steps to do if it is not already installed on your phone. However, if it is you can not install when it is already there. I'm not sure how to remove in terminal and everything I've tried it tells me read only blah, blah, blah...
I tried mount -o remount,rw /system---that is suppose to work.
1.Make sure anything you want installed is in
the root of the sdcard..(/sdcard/nameoffile.apk)
2. Download a terminal emulator from the market.
If it installs continue..If not then continue on back to the thread.
3. Open up the terminal emulator. It should ask permission from SU. >Always allow
4. Now type the following
su (hit enter)
install /sdcard/name_of_file.apk /system/app/name_of_file.apk----if it is a system app
If it is a downloaded app then use /data/app
Ok.... well I tried that way also and I get the error
Code:
install: not found
I downloaded the terminal app from the market and entered the commands as you said for ex.
Code:
install /sdcard/HTC_IME.apk /system/app/HTC_IME.apk
Thanks a lot though I wish it could have been that easy.

Guide to install LXDE on samsung galaxy s

So 3 days of trying to install ubuntu on chroot and a little knowledge of linux and terminal, i was rather surprised to log into it and there i was, faced with an LXDE interface.
I want to thank coralic, burningbroccoli, lifehacker, josh_axeY and backfireNL for supplying the information i needed to make this possible.
So a brief overview of whats going to be done. First we will need to root our galaxy s in order to access terminal. An ubuntu image will be created and used in chroot environment by mounting (loading) it. Finally a vnc server will be setup and will be logged in using androidVNC.
So for the guide i suppose!
Guide:
First your going to need to root your phone. This is to access terminal and enter the commands required. This is taken from backfireNl's easy way to root your phone.
1. Download: 2.1 Update .zip
2. Put update.zip to root of /sdcard (not /sdcard/sd) (not on the physical SD card but the Internal SD card/Phone Memory)
3. Turn off phone
4. Hold down volume up + home button + power (tip: release the power button for half a second when you see the samsung logo)
5. Phone will reboot into recovery mode
6. Wait until you see the Recovery Screen and then release the buttons
7. With the volume down key go to the option: "apply: /sdcard/update.zip"
8. Press the home button
9. Phone will start updating
10. Phone reboots... and there you go! your phone is rooted!
So that wasnt too hard was it? Although once you have done this, you will need to download a couple of programs from the market. Goto market and download the following programs:
-Busybox
-Terminal Emulator
-androidVNC
Ensure all of these are installed as this is what you shall need in order to successfully run LXDE on your phone.
Next is the image for the install! i will post up an image file for download although for the sake of people wanting the whole info on how-to here it is.
1) login on your ubuntu machine and fire up terminal.
2) login as the super user by entering "sudo su"
3) you will be required to enter your su password, enter this and you will be logged in as root
4) In terminal enter "apt-get install rootstock"
5) One this package is all installed, enter the following code into the computer terminal:
sudo rootstock -f localhost --login ubuntu --password ubuntu --imagesize 1G --notarball --dist lucid --seed ssh,tightvncserver,lxde,expect
6)The image will be stored in the home folder. The image will need to be a .img file or it wont work. So extract the file if necessesary and rename the file so it reads "ubuntu.img"
7)Now you will need to put the ubuntu.img on the phone. The directory which it needs to be installed into is "/sdcard/ubuntu/"
8) All done for this step!
Ok so you have everything setup and ready to do the fun part! so lets get everything mounted and configured!
1)Open up terminal emulator on your phone
2)enter "su". this logs you in as superuser
3)I found you will need to make the following directories in order to work, so in terminal emulator enter:
mkdir /data/local/mnt
mkdir /data/local/mnt/proc
mkdir /data/local/mnt/dev
mkdir /data/local/mnt/dev/pts
4)enter "cd sdcard" then "cd ubuntu"
5)You will then be in the folder with the image. Type into terminal:
export HOME=/root
export USER=root
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
busybox mount -t ext3 ubuntu.img /data/local/mnt
busybox mount -t proc proc /data/local/mnt/proc
busybox mount -t devpts devpts /data/local/mnt/dev/pts
busybox chroot /data/local/mnt /bin/bash
/etc/init.d/ssh start
6) Although it doesnt seem it, your now into your distro!
Okay so your into your distro but it looks all horrid and "text based". wouldnt it be lovely to see a proper desktop? so lets go!
1) enter into terminal "apt-get install x11vnc" this installs x11vnc to your phone. This may take a while depending on how your connected to the net
2) once x11vnc is installed, type "x11vnc -storepasswd" and enter a password. It will ask to verify the password so enter it again, then enter "y" to setup a password for it
3) first enter "vncserver" to initiate the server on your distro. For some reason without this, androidVNC will start to connect then crash
4)finally enter "x11vnc -usepw -find"
now your x11vnc is setup using a password hooray! last step in this guide and you will be away in no time! So is everyone ready?
1)hit the button on the bottom to return to the desktop but keep terminal emulator running
2)goto androidVNC and enter the following:
Nickname: root
Password: (whatever password you setup in x11vnc)
address: localhost
Port: 5900
color format can be anything, i set it to 4 bpp and use local mouse pointer
3)Simply click "connect" and viola! welcome to your impressive lxde environment!
This has been done before although i tried to do every step, base it around the phone as much as possible so no connecting to the computer.
any questions or problems i will try my best to help you guys, and thanks for the guys who helped me on this voyage.
i will write a bash script soon to try and incorporate as much of the manual typing in as possible
good luck!
Things which need to be done:
Upload image: Completed! - http://www.megaupload.com/?d=H55O5UEM
Bash script for terminal emulator: Completed, needs to be uploaded
Bash script for setup process of terminal emulator: Not completed
Startup script for image: Not completed
Youtube video: Not completed
Include internet browser and x11vnc in image file: Not completed
If anyone has any recommendations on how to make the process easier please let me know and i will try my best
Good to see the info consolidated into one post!
Cheers for the shoutout.
no probs your information helped me soo much, i just thought it would be good for someone to goto a post and go "oh yeah thats how to do it" instead of going to loadsa websites
i will try it very soon, thank you.
awesome!
When will you post your img file? I'll have a try.
I have no ubuntu installed, I'm using ArchLinux.
okay ive written a bash script to automate most of the process although there are a few things i could tweak before im fully happy
i have also posted a youtube video to demonstrate how easy it is! the first post will be updated with the link.
people ask me the reason for doing this and i have 2 replies:
1)to show the true potential of this phone (and working in a phone shop it really works)
2)for development purposes. Things like this are the next step in unlocking the true potential of the phone
lijgame: Im just uploading it now for you
Good work, will give it a try. And what about any browser ? Like firefox ?
hi.
okay so this is installing ubuntu into a chrooted environment and vnc'ing to it.
does anyone know if it is possible to blow away android and install pure debian on it? does anyone know of a hardware list on the sbc in this thing and what sort of support one might need to hack in to get a such a thing to work?
I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
In terms of installing a clean debian would need more than just a straightforward port. You would be looking at making an environment which supports the arm architecture, porting all of the drivers over, creating an option to support telephony, messages and gps too. If you wanted a debian environment it would probably be best to either run it like how the n900 does or getting a distro of it which is specifically made towards mobiles and modifying it.
Although you have an extremely good point there! Tell you what, once ive got everything running on here i will have a look and see what i can do in terms of atleast getting a debian shell running or a limo version
.kiz said:
I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
Click to expand...
Click to collapse
Just create zip/tar-ball of img file and it will become around 300MB. Then you can upload it on multiupload (or megaupload/rapidshare/mediafire).
I just created that image too and will be testing on my Galaxy S soon, so if its working for me then I will upload my image too.
Thanks for your good work
haha i shouldve really thought about compressing the file really
this will be a pre-image im just working on getting a better image with optimization, x11vnc and firefox
okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started
Tnx for the credit!
Ubuntu image is uploaded and ready to go, im currently working on a better image so when ive finished that, it shall be released.
Also i have recently installed an internet browser and it is functioning properly. I will post screenshots soon
.kiz said:
okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started
Click to expand...
Click to collapse
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists
Try creating a second loop device with: mknod /dev/loop2 b 7 0
fslateef said:
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists
Click to expand...
Click to collapse
im guessing because the image is corrupt, your unable to mount it.
I have just uploaded my bash script making it easier to mount each time.
bash script: http://www.megaupload.com/?d=CEU6R5J4
Image file: http://www.megaupload.com/?d=H55O5UEM
ensure you have made the directories explained in my first post.
pop the hsetup.sh file inside /sdcard/ubuntu (along with your image)
then fire up terminal emulator and type:
su
cd sdcard
cd ubuntu
sh hsetup.sh
This mounts everything for you and logs you into LXDE, all you need to do after is type in:
/etc/init.d/ssh start
vncserver
x11vnc -find
Then log in using androidVNC
i will attempt to upload the file to another location and i will test the image file to ensure its not a compression error
i apologise, ive just looked at the zip file and it is corrupt.
just compressing a new one and i will upload it
.kiz said:
im guessing because the image is corrupt, your unable to mount it.
Click to expand...
Click to collapse
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....
fslateef said:
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....
Click to expand...
Click to collapse
I found the problem. As mentioned by ArminC, I found that there isn't any loop device node in my mobile hence I created one and its mounted
Great ... Now going ahead .....

[KERNEL] adb "cannot run as root in production builds" fix

Discovering "adb shell" gave joy, experiencing the shell as minimal bash with awful line handling (backspace and command recall) gave annoyance, experiencing "adb root" refusing access gave frustration.
After some tracking, it turns out that adbd behaviour is determined by the property "ro.debuggable" which is set during system init. The initial value is located in the file "/default.prop". In JP6 it is set to 0 resulting is adbd refusing access. However, set to 1, "adbd root" will give the much better response of "restarting adbd as root".
Once set, the property value cannot be changed. To get this fixed you need to change the contents of the file default.prop which is located in the initial ramdisk image.
Optionally, you can put a replacement shell in /sbin of in ramdisk image so that when connected "exec bash" will make things more relaxing. I attached the version I am using, which is statically linked with ncurses/readline.
There is also a simple patch to unlock adbd if you dislike opening and rebuilding the ramdisk image. However, you do need binoffset which is located in the scripts directory of the linux source tree.
Code:
ofs=`scripts/binoffset initramfs.cpio \`echo -n 'debuggable=0' | od -t u1 -An\` 2>/dev/null`
echo 'debuggable=1' | dd bs=1 seek=$ofs conv=notrunc of=initramfs.cpio
Thanks...any help though?
Hi....thanks for the fix....could you point me to a decent howto on editting the initial ramdisk?
Thanks
M
it doesn't sound simple
i will try to figure that one out ...
Dear Hexabit,
I know it's an old topic.
But do you know how can I use this Fix on a windows 7?
tried searching for binoffset software/script..couldn't find anything
I have a Flytouch 3 tablet, rooted(Z4) with terminal emulator and root explorer.
is there a way to use you bash.rar to unlock adb access?
thanks for the help
doekoe87 said:
Dear Hexabit,
I know it's an old topic.
But do you know how can I use this Fix on a windows 7?
tried searching for binoffset software/script..couldn't find anything
I have a Flytouch 3 tablet, rooted(Z4) with terminal emulator and root explorer.
is there a way to use you bash.rar to unlock adb access?
thanks for the help
Click to expand...
Click to collapse
you have to split the kernel, then decompile the ramdisk and edit default.prop and change ro.debuggable to 1, then recompile and flash
confuse but giving me a clue
I use unpackbootimg in my ubuntu pc.
The adb root works not properly after set debuggable=1.
When I saw your thread that told the adbd should be unlocked too, then I replace the adbd with a unlocked one. It works!
Thanks for your help.
I am sorry but I don't understand how to use the file.
teoking said:
I use unpackbootimg in my ubuntu pc.
The adb root works not properly after set debuggable=1.
When I saw your thread that told the adbd should be unlocked too, then I replace the adbd with a unlocked one. It works!
Thanks for your help.
Click to expand...
Click to collapse
Hi,
I can upload nothing to my root catalog of my phone.
So how could I use the adbd file in this case?
Phone is rooted but I have a problem with adb root command like subject of this topic is.
Can u help me with the process because I kept the file in /sbin but still it's not working.
Active system
Sent from my SM-G900T3 using Tapatalk

- exec '/system/bin/sh' failed: No such file or directory (2) -

I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
rydinsmoothx said:
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
Click to expand...
Click to collapse
Not gonna happen unless you can get into recovery or have the special usb cable to throw your device into fastboot (search the unbricking thread for more information on that). If you get lucky and can fix it + revert to stock, I would not install cm7 again until doing so is more noob friendly and forgiving.
The issues people are having with installing cm7 and severely screwing up their kindle are pretty epidemic due to the issues with recovery for those that don't prepare ahead of time for the possibility of disaster. The maintainer should really either close it out for now to the public or make the disclaimer much larger.
I have the same error. This is end. Only Factory Cable can help you but even with this cable I'm not sure what you can restore it.
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
rydinsmoothx said:
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
Click to expand...
Click to collapse
Operate how? Also, please don't double post in 2 threads.
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
rydinsmoothx said:
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
Click to expand...
Click to collapse
Could be a bit more explicit. Boots as in "yay, i see a logo and can't use my device beyond a paperweight that displays the cm7 logo" or boots as in "yay, i can use my device like normal and it's not bricked or malfunctioning"
Anyways, if you actually have root privileges and can mount system in read/write, get the sh binary out of the CM7 download by unzipping it or whatever and copy it over, making sure to match the owner/group and permissions that the other things in the /system/bin directory have. Since I'm guessing you're not command line savvy, I recommend doing this in root explorer or buying it if you do not have it.
Also, many of us do not own kindles and a larger % are also not running cm7 on their kindle so saying "i ran some random script that I won't say what it does and where I found it" does not help your situation either as far as getting a helpful answer.
Can you type ADB DEVICES at your command line and get a device? What about fastboot? Can you get devices to show there while at the command line?If yes, I am sure you can flash the CWM recovery to get ADB, then follow the steps to get back to stock...Dont blame me though if it doesnt work
I got the script script from someone in the cm7 thread, its supposed to opitimize the ram usage thus making the rom more smooth. He said it worked for him so I gave it a shot. I think it unrooted my kindle because I can't gain root access with root explorer. My devices shows up in adb devices but since I can't use adb shell I can't enable the fast boot.

Terminal Screw up

Well.. I heard about Updating Ubuntu, and I've decided to go ahead and take a shot at it. and So one of the requirements for installing ubuntu is that you need to install Busybox. I downloaded an app to install busybox for me. I believe it was called BusyBox Installer. During the install.. (To install the actual busy box) It froze.. So i had to terminate the app.. so then I went back into the Application and tried installing again, it worked. but when I opened up the terminal To try and execute commands, some wouldn't work. Like "ls" wouldn't give me any result. After that, I went on the internet and Tried searching for this error, I was told to reset the path variable. I do not know how to do that and so I was given this command to execute:
Code:
export PATH=/usr/bin:/usr/sbin:/usr/local/bin:/usr/X11/bin
Tried that, and it wouldn't work for me. So I'm out of options. Is there anything I can do to fix this problem? It would be greatly appreciated. Thanks
I have an Nexus S, With ICS (4.0.3) Rooted. I am using the Android SDK to run each of my commands.
Edit:
Apparently my path environment variable is changed. all commands are executed in /system/bin/sh/ I'm assuming that I need to remove the /sh/ out of the path environment variable.

Categories

Resources