Hi.
I tried to use the Emacs app from Google play store to see if I could see and edit various settings (as I sometimes do in classical unix when nothing else helps), but apparently the "dired" command is not working. I get the message "Listing directory failed, but 'access file ' worked". Is this due to the fact that I do not have superuser rights? Is it possible to give the emacs app su rights?
(As you can see, I do not know much about Android.)
Olof47 said:
Hi.
I tried to use the Emacs app from Google play store to see if I could see and edit various settings (as I sometimes do in classical unix when nothing else helps), but apparently the "dired" command is not working. I get the message "Listing directory failed, but 'access file ' worked". Is this due to the fact that I do not have superuser rights? Is it possible to give the emacs app su rights?
Click to expand...
Click to collapse
The original question still remains unanswered, but I just realized that for me there is a very simple workaround (which I should have realized much earlier):
Since I use NativeSD the whole system is on the SD-card, and nothing prevents me from putting the SD-card into a card reader, and mounting it on a unix computer (in my case Kubuntu). This way I can mount both the FAT-partition and the Ext4-partition, and modify whatever I want.
This is one of the reasons why I like NativeSD: I have the original boot loader and the original Windows Mobile 6.5 in DRAM in my HD2, and no matter how many errors I do when I try to install NaviteSD roms on the SD card I do not brick the phone, as long as I do not touch DRAM. And I find the NativeSD roms surpisingly fast.
Related
I keep getting the "not sufficient space" error when i try to install Handcent SMS from the market. I do have 30MB free tho ... any ideas why?
What rom you on?
Have you tried to install other apps since you got this error message?
ROM: Villain 5.2
installing / uninstalling other apps causes no problems
nevermind. removed everything via adb shell.
the last update attempt seems to have caused some troubles.
thanks for the quick reply anyway!!
just FYI: as I noticed in logcat trace output:
It seems that the underlying problem for this widely noticed problem simply were wrong filesystem permissions on the "lib" directory within the data directory of applications.
This prevented the installer from deleting/updating the *.so file(s). And it seems that the installer is so dumb to show a "not enough space" error every time it cannot write to the filesystem (even if it cannot write because of missing permissions).
The problem affected only applications which include native shared libraries (*.so files) which are placed in this "lib" directory (like "Handcent SMS", "Better Terminal Emulator Pro", "aTilt 3D Labyrinth", ..)
interesting ... i'm gonna check that the next i have similar issues
Seems my problem started after install of Terminal Emulator. Now Handcent fails to install and I have no idea how to fix it, removing via adb shell is not in my vocabulary. Can someone clue me in on this as I am use to Hancent and like the way it operates.
Thanks!
Thought I'd post in this thread save starting a new one. I am having the same problems. I can install other apps but not handcent, the error is same as above not enough space.
Can someone please post instruction on how to fix this via adb ? (for a layman)
I have looked at the other posts concerning this and looked in the /data dir' and searched via astro for any related "handcent" entries but cannot find any and I still have the problem. Please help.
Many Thanks
androcheck said:
just FYI: as I noticed in logcat trace output:
It seems that the underlying problem for this widely noticed problem simply were wrong filesystem permissions on the "lib" directory within the data directory of applications.
This prevented the installer from deleting/updating the *.so file(s). And it seems that the installer is so dumb to show a "not enough space" error every time it cannot write to the filesystem (even if it cannot write because of missing permissions).
The problem affected only applications which include native shared libraries (*.so files) which are placed in this "lib" directory (like "Handcent SMS", "Better Terminal Emulator Pro", "aTilt 3D Labyrinth", ..)
Click to expand...
Click to collapse
Can you/someone give advice on how to perform this fix because I'm having this problem and this seems to be the only fix. It's not working but I don't think I'm doing it right.
Hi!
Could anyone help steer me towards a solution please?
Or tell me if its impossible (and why).
I am trying to put together a script of some kind which I can use to do a basic rebuild of my Archos 70 after I have done a Full Reinitialization. I like to mess around installing all sorts of stuff, but when done, it's nice to reset and go
back to a clean machine.
As it's not rooted (yet?) I generally rebuild manually which takes ages.
Although a relative newbie at Android/Linux, I have worked with scripting
on mainframes and in the Windoze arena for many years.
The scripting requirement is quite simple, namely to install packages one by one from the SD card. Also to copy back Bookmarks, launcher setting etc
I am happy to work in any language which will work, but to date have just been trying with .SL (Bash?) scripts which run quite happily from within the SL4A environment or according to my theory, should work also from Android natively.
I envisage the script residing on the SD card and when invoked installing my launcher, Dolphin Browser, various other apps and games, then copying back the settings which I have saved (also by script) before the Initialisation.
Trouble is, I can find no simple samples which help. When I try, I can 'cp' stuff about and echo messages etc, but when I try to install, I don't really know where to start. I have tried just the name of the app package
'/sdcard/sdcard/packagename.apk', it replies 'permission denied' and if I try 'sudo package.apk', it says 'not found'.
I am assuming that the 'permission denied' is a good sign because it understands what I'm trying to do at least. But if I am allowed to do it myself, then surely my script should be allowed to do it?
I am quite happy messing around myself. But if anyone has any pointers
(sample scripts, which language/environment to use, etc.) I would be most grateful.
Sorry if this is covered elsewhere. I have searched but was unable to find much which helped. I am continuing the search!
Thanks in anticipation!
1. All normal installed Apps are installed in /data/app as the apk
2. Local/private data comes into /data/data/name.of.the.package
Both directories are ony accessible with root.
Hell again,
Thanks for your reply fzelle, but I'm not sure as to whether I may have explained it properly.
I am running 'Quick System Info' which is great, and it has a function to backup all the installed apps to a directory you can get at without root access. From there I have copied them onto the SD card.
I am not just trying to copy them into the working directory.
If I click on an app, it lets me install it without any problem.
I am trying to automate that part of the process, and I need the name of the software which does the installation, and how to actually give it the parameters for it to do the install. Although a Linux newbie, I don't really understand why, if I am allowed to install apps myself,
a script that I run should not be allowed to install them also?
Anyone got any ideas please?
Oops! - Sorry for that unfortunate typo at the beginning of my last post. Please read as 'Hello'!
No, i didn't understand you wrong.
You want to automate the installation of your std programs, and that normaly doesn't only include the apk but also the private Data.
And if you manually want to install this, you need root to be able to write in /data/data
If you just want to Backup/Install the apps, use appSaver from the market.
That has allready everything you need, and doesn't need root.
fzelle said:
1. All normal installed Apps are installed in /data/app as the apk
2. Local/private data comes into /data/data/name.of.the.package
Both directories are ony accessible with root.
Click to expand...
Click to collapse
Not entirely true.
I have some SSH tunnels set up on my rooted phone that use keys and a shell script to launch them, all set up with Better Terminal Emulator. The key and script files are located under /data/data/com.magicandroidapps.bettertempro/home. I wanted to use the same keys and script on my A70, so I copied the files from my phone to the same directory on my A70 using the terminal command line. Although you can't browse to the app folders under /data/data/, there is some ability to copy stuff into them. I guess the trick is knowing what and to where.
I've not used appsaver, but Astro will also let you back up and reinstall your apps all at once.
I installed Z4 mod and ran it and it says my g-tab is rooted. I have read that custom ROMS are pre-rooted. In my limited linux experience - being root gives you total control over the machine. I ran Terminal Emulator and cd / to get me to the top of the file structure. I tried to mkdir test and I was denied because the file system is read only. Next I went into the system folder because a lot of stuff in there looks familiar. I again tried mkdir test and was denied because the file system is read only. It would seem that to be root I would need a password and Z4 didn't offer to give me one or let me set it. Thinking further, I wonder if the file system is mounted for read only and that is why I can't create a new directory. When I am running the rom (Vegan) I can write there (understanding that I am writing to the sdcard that is mounted - presumably with RW access. So, what is all this rooting talk about then? What is the purpose of being root if you still do not have access to the file system?
You need Superuser.apk, as well. Think of Superuser as similar to Windows UAC, and rooting as making yourself an administrator. Even though you have root (admin) access, UAC (Supeuser.apk) still needs to let you through.
You also need "root aware" apps. Perfect example is Titanium Backup and that's usually my "litmus test" for verifying if I really have root or not on a device.
yup, in my limited rooting experience (droid1 and gtablet), after the process, there was always a new icon in the app tray entitled "superuser". i didnt have to install it separately, it showed up after the rooting process. if you don't have the superuser app, im betting the root process was unsuccessful.
my memory tells me i had some problems with z4root rooting my tablet, and i had to do it a few times before it actually worked. that was back in december tho, so i dont know if the current version of z4 is different than the one i used, and if so, if kinks were worked out...
so yeah, i probably helped none.
I always though z4root and Superuser were kind of a package deal.
I use them on my Cowon D3, as Cowon completely locks down their recovery process. boo to that.
rodzero,
With z4root you install it first. Then, you install a file manager program like "Root
Explorer" and when it comes up you click to "Allow" it. After that, you can go in
through Root Explorer and create and change R/O to R/W as needed. Same same
with Titanium Backup, once you have "allowed" it you can do what you need
to with the program.
Rev
More Investigation.
Thanks for the fast responses! I do have Superuser installed and it pops up from time to time when an app wants su access. Using terminal emulator, I worked my way into and what do I find but su! I ran su and got was granted su rights in the terminal. I felt pretty smug so I headed into the etc folder thinking I would make a simple change to the hosts file just to see if I could do it. I'm used to using nano in Ubuntu but no nano here. I tried vi (which I really don't know how to use) and I got some strange display but I don't think it was an editor. So, for the sake of closing the loop - if I wanted to edit the hosts file and add a new host - how would I do it. The Terminal Emulator now seems to be in the list to be granted su whenever I type it in. I know how to move around the file system. What kind of text editor would I invoke to actually alter the file? OK.... I went and downloaded TED and worked my way back to the hosts file, added a line but TED doesn't have su rights to save the file. So it looks like su exists but I don't see how to run an app in su mode except for terminal where I can invoke it by a text command. What's the missing piece to get TED to ask for su access?
Just a guess, but TED need to ask for elevation of privileges. It's probably an app issue.
hi. i can't believe i'm the first person to ask this but i've searched as best i can through these forums, and on google, and cannot find a definitive answer. there are lots of pages giving high level descriptions of rooting a phone like "gives admin access", "allows access to the root filesystem", etc. but, when you root a phone, what actually happens ? does it simply make the "su" binary available so that apps can call it to access the root user ? eg. i've got a samsung galaxy s2, if i install an insecure kernel, then add su to /system/xbin, and then reinstall a stock kernel, is that technically a rooted phone ? this is actually what i did on my phone, although i installed superuser and busybox from the market after adding su. i am aware that there are various threads in the sgs2 forums on how to root, i'm just using my phone as an example, i'm just trying to understand generically what is meant when someone says a phone has been rooted. cheers.
Full control over your system
Ability to alter system files. You can replace many parts of the "Android Core" with this including:
Themes
Core apps (maps, calendar, clock etc)
Recovery image
Bootloader
Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
Boot images
Add linux binaries
Run special apps that need more control over the system
SuperUser (lets you approve or deny the use of root access to any program)
Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
<there are more but I cannot think of any right now>
Backup your system
You can make a folder on your sdcard and backup all of your .apk files to your sdcard (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
Relocate your (browser/maps/market) cache to your /sdcard
Relocate your installed applications to your /sdcard
Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Copied and pasted from google... it is your friend.
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Carrot Cruncher said:
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Click to expand...
Click to collapse
Unrooted phone is like logging on as user in a computer. By rooting you have "administrative" rights, just like using sudo command in Ubuntu. Some binaries which are important in gaining administrative rights are installed in the phone.
sent from my nokia 3210
If you come from Windows, you're familiar with the Administrator account. A user that can do everything on the system, as opposed to other users than only have limited privileges. In Linux, that account is called "root". That's all there is to it. It's a user that can do everything on the system.
@Panos_dm: Actually, it's *not* like using sudo. Sudo gives elevated privileges to your existing user account, whereas "root" is a whole separate account.
Nope, sudo actually switches users
i'm a linux user and have been a linux admin in the past so understand the difference between su and sudo. sorry to sound pedantic but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
It opens your phone to a whole new array of possibilities.
Sent from my HTC Sensation 4G using xda premium
Carrot Cruncher said:
but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
Click to expand...
Click to collapse
In a gist? The "su" binary and the Superuser.apk app get installed. Sometimes doing so requires exploiting a vulnerability via a trigger. Rageagainstthecage is a common trigger. I once had a link that explained what exactly rageagainstthecage does, but I don't have it anymore.
If you really want to know all the details, here's the script I used to root my Defy: http://pastebin.com/G3m9v4FQ
Hmm, I see the script contains a link to the explanation of what rageagainstthecage does. Cool.
many thanks for confirming my understanding of the process.
**EDIT** Was seaching for a while couldn't find what I was looking for, pressed back button and posted this in what I thought was just a general troubleshooting forum. Sorry about that please move this question to the correct location. Thank you.
I've looked everywhere for the answer, only answers I could find were for ICS (I have gingerbread 2.3.4), where for non-low-end systems or weren't compatible with low-end systems (at least ones with YAFFS, I don't know if I have that or not though).
How do I move the cache folder to SD card without Emulator? (I believe I have a YAFFS device according to this post: http://forum.xda-developers.com/showthread.php?t=633246 {Since it is a "low-end" device - Kyocera Milano C5120} )
I've found a couple tutorials on how to do this, one doesn't work since my termial emulator wants to say "Failed" on the first command line "umonut /cache" my phone is rooted and I could move stuff around and delete it with Link2sd and RootAppDelete while using "Root File Manager" to give myself permissions.
The other tutorial was here:
rojanu
.wordpress.
com/2011/11/30/
moving-android-cache-to-sd-card/
It tells me to use umount /cache but it says the same thing my computer says when I try to run shell commands on it, "Failed" but all my other root apps work just fine, its just that for some reason I can't use the terminal. (I had to use Poot to Root, since all the commands though the terminal kept saing "Failed".
Would like to just be able to install stuff without having to constantly manipulate internal memory all the time.
With all that information basically my question is: How do I move the cache folder to SD card on a low-end device (Kyrocera milano C5120) running gingerbread 2.3.4 without a Terminal Emulator?
~Rooted Kyocera Milano C5120
Zelious said:
**EDIT** Was seaching for a while couldn't find what I was looking for, pressed back button and posted this in what I thought was just a general troubleshooting forum. Sorry about that please move this question to the correct location. Thank you.
I've looked everywhere for the answer, only answers I could find were for ICS (I have gingerbread 2.3.4), where for non-low-end systems or weren't compatible with low-end systems (at least ones with YAFFS, I don't know if I have that or not though).
How do I move the cache folder to SD card without Emulator? (I believe I have a YAFFS device according to this post: http://forum.xda-developers.com/showthread.php?t=633246 {Since it is a "low-end" device - Kyocera Milano C5120} )
I've found a couple tutorials on how to do this, one doesn't work since my termial emulator wants to say "Failed" on the first command line "umonut /cache" my phone is rooted and I could move stuff around and delete it with Link2sd and RootAppDelete while using "Root File Manager" to give myself permissions.
The other tutorial was here:
rojanu
.wordpress.
com/2011/11/30/
moving-android-cache-to-sd-card/
It tells me to use umount /cache but it says the same thing my computer says when I try to run shell commands on it, "Failed" but all my other root apps work just fine, its just that for some reason I can't use the terminal. (I had to use Poot to Root, since all the commands though the terminal kept saing "Failed".
Would like to just be able to install stuff without having to constantly manipulate internal memory all the time.
With all that information basically my question is: How do I move the cache folder to SD card on a low-end device (Kyrocera milano C5120) running gingerbread 2.3.4 without a Terminal Emulator?
~Rooted Kyocera Milano C5120
Click to expand...
Click to collapse
Have you tried using something like root browser lite and just long press click move and place wherever you want?