Database Users

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.

How do I get adb shell to work in recovery after root?

I rooted following the 10 minute root video, however forgot to remove a lot of those junk system apps, like CityID. I cannot get back into SU while in recovery, no matter what I do. How do I get back into the shell in recovery so I can remove all the bloatware?

I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?

areghas said:
I can get the error message:
- exec '/system/bin/sh' failed: No such file or directory
however i cannot seem to get back into the shell where I can access SU and remove the bloatware, anyone have any ideas on what im missing?
Click to expand...
Click to collapse
I'm in the exact same boat as you. I don't know where to go from here.

run update.zip and let it fail again then you caN adb shell su

hmm doesnt seem to work for me

in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.

i had to run do the hole process over again to get su so i could remove cityid after root.
i used the 1.bat file as in the utube video for noobs.

ejlax said:
in order to get the back to adb shell in recovery, you have to go through the whole root process again. Then once you have snuck in the payload-update.zip and it has successfully installed it, you are able to do adb shell.
Click to expand...
Click to collapse
not cool lol, took me 3 hours to get the things to work with my sd card haha not worth it.

that is the only way
They are correct, you must do it all again, but look for a PNY 4gig class 4 sd. I tried hundreds of times over a 3 day period to do it and it worked first time and every time with this card.

when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.

qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
There is also another terminal app in the market for 1.99, listed as being for that purpose, so, has anyone tried it?
I don't have anything else I want to delete at the moment, since I got rid of cityid at the recovery adb prompt.
Click to expand...
Click to collapse
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.

qwho said:
when I run terminal emulator in the OS on the phone, and type su, the super user app grants it permission. Would we be able to delete system apps from there?
Click to expand...
Click to collapse
E30kid said:
The nand is locked down when you are in the main OS, so no, it would not work. You would need to do the re-root to gain access to /system/ as recovery is the only place where we are able to access it right now.
Click to expand...
Click to collapse
I can get su access while in the OS. No problem on that. And I tried to delete teeter.apk, but got the "read only" message. So, I mounted it as read-write with
Code:
/system/bin/mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
that went fine too, but when I tried to delete teeter.apk, i got "rm failed, directory not empty"... but I'm not trying to delete a directory...
I guess the "nand is locked" and that's why, but... "the nand is locked" doesn't mean much to me, as I have no clue what that means

x10a Baseband Version?

Solved. Thanks!

Anyone wanna help? -.-

xGary said:
So I did some modding (unfortunately) to the framework-res.apk file and it worked the first time and a few other times but then I changed something and now when I turn on the phone it freezes at the "Sony Ericsson" screen before the logo. What do I do?
I tried pushing the backup framework file but it says "failed to copy framework-res.apk to /sdcard/framework-res.apk: Permission denied
however, when I use adb devices, it does show my device as being attached.
So what can I do now?
Edit
I was also able to pull files...
Also tried manually putting the framework-res.apk in the sdcard and then using adb to copy it to the framework folder. Doesnt work. Saids that the directory cannot be open for read. I guess the device cant read the SD card until it boots up
Also, if you are replying, please stay on the thread. I will probably comment back ASAP
Click to expand...
Click to collapse
Hey... are you sure that you've got your phone rooted? I mean sure pulling files work irrespective if you are rooted or not, but in order to replace files under the /system filesystem you've gotta have root and remount it as read/write.

Happen to me too, for the exact same reason. I had to reformat the phone... I simply re-rooted the damn phone.

cp /system/bin/sh /system/bin/rootsh
chmod 6755 /system/bin/rootsh
Try using this script before trying to push your framework back on

Well it was rooted and I already flashed it and re rooted it. However, I have three questions
1) Should I update from the v24 to 26?
2) I have a x10a, after running step 3 my phone still says its an x10i with baseband version of 1.1.28
3) And those apps that were supposed to be installed in step 2 didnt go so well. I could install them manually with ADB right?

[q] adb remount wont work on vibrant

So i rooted my vibrant with the hopes of removing some of the bloatware. i rooted with the one click root method, loaded clockwork recovery, i know i am rooted but every time i try adb remount i get remount failed: no such file or directory.
so i tried going into clockwork recovery in the partition menu and mounting system there and trying adb remount and got remount failed: operation not permited. i ran adb root and got root can not run on factory builds (or something close to that)
in adb shell ive tried mounting every which way i can think of and nothing works.
ive searched all over and havent been able to find a fix, please help

root explorer didnt work either
also i tried deleting the system apps with root explorer and it would mount either

adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how

cojonesx said:
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
Click to expand...
Click to collapse
like i said in my post, i tried shell and couldnt get it to mount. maybe i did it wrong

semi-success: delayed update to 6.3 and preserved root

This did not go exactly as I had planned but it ended up ok anyway and I learned some.
I am using a rooted stock rom. First, my idea was to prevent the auto update to 6.3. Second, I wanted to see if it was possible to somehow preserve root so that I wouldn't have to re-root after the update, because I am not really thrilled by the idea of installing a new boot loader and so on; I would prefer to make the minimum modifications necessary to do what I need.
The first goal appeared to be well-served by using droidwall. I used whitelist mode and blocked everything that I couldn't tell had an obvious need to access the net. I posted more detail here. From the time the update started going out until today when I had time to actually try my update, I did not receive the update automatically. So that appeared to work.
Next, my idea was to simply make a copy of /system/xbin/su to a place that wouldn't get overwritten by the update.
# mkdir /data/lunchmeat
# cat /system/xbin/su > /data/lunchmeat/salami
# chmod 6755 /data/lunchmeat/salami
The idea being that since it's still setuid root, I'd be able to execute it and become root after the update. (I just picked a silly name in case something looked for su and blew it away).
So, I turned off wifi, disabled droidwall, manually updated (copied the updates into kindleupdates and so on) and after it rebooted, I opened the terminal app and tried to execute my salami binary. I got permission denied, and the superuser app said that superuser permission was denied on the terminal app. Hmmm....
Couldn't figure out why it was behaving that way so I thought I'd try adb root, and whadya know, I had a root shell.
remounted /system read-write, copied su back into /system/xbin, renamed /system/bin/check_rooted to /system/bin/check_rootedx, created an empty executable /system/bin/check_rooted, and rebooted...
...and everything is (rooted) as it was before. I re-enabled droidwall. google play seems to be working.
Why did 'adb root' work for me after the update? That might be a good question to answer, since it could make the re-rooting process much simpler for people! 2 or 3 commands and you're done.
edit: ohhhhh, stupid me! /data is mounted nosuid. / seems to get blown away on every reboot, so even if I remount it read/write and put su there, it gets lost.
And, also, I just remembered that I did what jcase said in this post which is what allowed me to keep adb root working.
So, so far this idea is going nowhere.