Database Users

ADB Push

I searched around and couldn't get a clear answer. I'm a noob at anything command prompt/terminal related.
I was screwing around with adb last night after figuring out that I can remove program .apks with the rm <com.whatever.program> command. I got a little trigger happy and removed things that I don't use, just to test it out. I made a nandroid backup before I started. The phone runs fine, but now the Market won't download anything. It just sits on the Starting download... screen.
One of the .apks I removed was GmailProvider.apk. Whether this is the problem or not, I'd like to reinstall it for practice. I can always nand restore later.
So my question is... How can I use adb push to reinstall an apk?
I tried:
Code:
adb push C:\GmailProvider.apk
adb install C:\GmailProvider.apk
adb install C:\GmailProvider.apk \system\app
And about every variation of the 3, in and out of the adb shell.
It didn't work, and I'm at a loss to do anything else. So does anyone have any suggestions?
EDIT: I think my "\" should be "/". I got this
Code:
BusyBox v1.15.2 <2009-12-02 TIME EST> multi-call binary
Usage: install [-cdDsp] [-o USER] [-g GRP] [-m MODE] [source] dest|directory
Copy files and set attributes
Options:
Then some usage stuff here.
Then I looked at the command prompt and made a face like .
Suggestions?
It might help to say that I'm using EvilEris 2.0.1, Windows 7.

Just reflash your ROM after doing a titanium backup. Easiest fix.

try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write

silverramsrt said:
try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write
Click to expand...
Click to collapse
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.

CPCookieMan said:
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.[/QUOTE
i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse

i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App

zach.xtr said:
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App
Click to expand...
Click to collapse
im running xtrom 3.0.......i just went ahead and installed the social app flash and deleted what the ones i dont uses,but thanks for the help anyways.i was looking into pushing friendstream into it but found out its only works in sprint base builds

Superuser?

Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828

It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.

I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.

Might be a dumb question, but did you do adb remount ?

I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.

I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU

I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.

It's probably not compatible with our phone yet.

Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.

I see you posted on the thread for the program itself. Hopefully someone there will have a response.

Yeah, I'm hoping to get a response to it. We will see.

The newer version 2.2.2 works.

Awesome, ill give it a shot a little later.

Tried the newer version, and I get the same issues.

How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.

I just did it through adb. I'll give that method a shot.

Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.

Galaxy-S Stalling Issue?

After having some major speed issues using Touchdown on my new Vibrant, I was directed to this thread discussing issues with the way Samsung stores app data on the phone. Apparently the app data is stored on the internal SD vs. NAND and that is considerably slower. Here are the two methods to fix:
*Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
*READ THE THREADS!*
Method 1: http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Method 2: http://android.modaco.com/content/s...ed-real-fix-for-the-stalling-lagging-problem/
Hopefully this will be helpful moving forward with the development of this phone!
Note: I have used method 1 which moved the app data from the SD space to the NAND space which significantly increased the speed of my phone, but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use. Method 2 purports to fix this limitation...
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot

Awesome, thanks for doing the parsing and putting out a procedure. Works great. No more lag.

Thanks, just tried it out on mine.

BE WARNED you will run into issues if your application data goes over 130MB. There is a better way to do this which includes a custom kernel with ext3/4 support and symlinking to the ext partition instead of the small NAND space.
Find it herehttp://android.modaco.com/content/samsung-galaxy-s-s-modaco-com/313365/updated-real-fix-for-the-stalling-lagging-problem/
I havent felt the need to perform either of these ATM. Please warn people of the consequences especially if your just telling them "Hey this will make your phone faster!" I do notice its explained in the article you linked from but not everyone will read that and then when they start having issues they will have no idea what to do. For those that completed this method you might want to revert it and go a better route. 130MB isnt enough room.

Agreed...I figured people would read the link, but you never know. Will update accordingly. THX!

I am trying test out method 1 but I keep getting stuck. I type in cp -rp /data/data /dbdata into adb but it comes back with cp: not found. Any ideas what I am doing wrong here?

Add busybox before the cp command; i.e.: busybox cp etc...

Krycek said:
Add busybox before the cp command; i.e.: busybox cp etc...
Click to expand...
Click to collapse
Thanks, figured it was something simple like that. Still new to this Android stuff after years of custom WinMo roms and hybrid Blackberry roms.

i'm a little sketchy about applying method 2...will installing a modified kernal have an effect when samsung rolls out the update for 2.2?

I concur, but that is also probably the "right" way to do it. The nice part about method 1 is it is easily reversible. I will update post 1 in a minute with how to check what your current usage is to see if you are close to the 130MB limit.

Thanks, just checked my usage and was only using 21MB thus far. I figure the 130MB limit should suit me fine until Samsung issues a fix. It looks like the European devices already have a new firmware that speeds it up quite a bit so probably won't be too much longer here in the US either.

Im not going to do either. Im going to wait for an official fix.

I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).

anomalous3 said:
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
Click to expand...
Click to collapse
i doubt it...it's the reason you need to install the modded kernal so that it recognizes the ext3 or ext4 partition. without it the partition is useless. i personally wouldnt use method 2 as there is no way to revert as of now.

Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!

I'm not infront of my PC atm, but try this.
adb mount
adb shell
su
If mount doesn't work try remount.
Let me know if this works for you, once i'm home I can double check.

Already tried that. I have a Nexus One and adb remount works on that but for this phone it says 'remount failed: No such file or directory'

Digitalthug said:
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
Click to expand...
Click to collapse
You might have already tried this, but make sure the phone is unlocked (at home screen) when you run the su command from your workstation... superuser will then prompt and you can allow it to run.
I've noticed that if the screen is locked it won't prompt and just give the permission denied message.
Sent from my Vibrant (with lag fix and loving it)

just did method 1 and the difference is incredible. as far as method 2 goes, will custom roms have this ability from the get go or do we need the official samsung update?

I just want to confirm that this fix works for the US version of the Galaxy S (Samsung Vibrant) right?

G2 Rooting Problem

Hey all,
I would like to know, what I might have done wrong in the rooting process. I used
This Tutorial hxxp://g2hacks.com/g2-hacks/how-to-root-g2-phone/
I made it to step #18 and was stopped by this error:
Code:
/data/local/tmp/root: data/local/tmp/busybox: not found
/data/local/tmp/root: data/local/tmp/busybox: not found
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Ideas?
Thanks,
Danny

Here is a screenshot of what I pushed to the phone:
hxxp://i.imgur.com/No1id.jpg

You have a typo in your push command for busybox (you renamed it to root instead, which then got overwritten when you pushed root). Just push busybox again.

How do I back out and enter that push command again?
What would I type?
I'm a total novice.

On your comp, just type the command again:
Code:
adb push G2TempRoot/busybox /data/local/tmp/busybox
Then on your phone, in Terminal, just run the root command again:
Code:
/data/local/tmp/root
It should complete this time.

I made a mess. Check it:
hxxp://i.imgur.com/y3NRW.jpg

You are still in the adb shell (basically creates a terminal on your phone that you can interact with on your computer).
Type "exit" to leave the shell. This will return you to the regular command prompt (instead of the $). Then try the push command again.

So now the phone terminal gives me this:
Code:
/data/local/tmp/busybox: permission denied

Oh sorry, forgot you needed to set permissions on the file. Run this command again from your computer:
Code:
adb shell chmod 0755 /data/local/tmp/*
Then it should all work fine.

The errors are getting shorter
Now I get this:
Code:
mkdir failed for /system/xbin, File exists

This error doesn't matter (it's really more of a warning in this case) and is actually expected.
You should actually be rooted if you didn't see anything else.

AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?

Danny.B said:
AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?
Click to expand...
Click to collapse
Congrats! And there are a few threads about this that you can read through (just search for them). If you like HTC Sense (the interface HTC adds to a lot of their phones---basically lots nice visuals and extra polish to things), you can try Virtuous. If you like the stock look that the G2 comes with, there is a stock DEODEX rom out there. By de-odexing the rom, you can do things like customize the framework (e.g., customize the status bar icons/colors or add a battery percentage to it). Lots of people here (myself included), use CyanogenMod. It's close to stock but with lots of tweaks/extras (it's based on the Android Open Source Project or AOSP). It's also nice because it has frequent updates and constant development (they recently started pushing test builds that are based on Gingerbread---the new Android update only available on Nexus S).
Now that you are rooted though, it's easy enough to install Rom Manager and test them all out. Be sure to create a backup first as well.

ROM Manager installed. I'm backed up.
Thanks again for your help.

i cant flash the engineering hboot keep getting error md5sum : not found Verification of hboot-eng.img failed i re-download the files, re-extracted them to my SD card, and ran the flash_hboot script 3x still nothing plz help but im rooted and backed up

Did not want to create a new thread so I'm posting it here.
First off, I haven't tried rooting any of my phones previously so I'm obviously making a mistake somewhere.Hope someone here can help me out.
I installed visionary+ r14 but it just blacked out the screen with a heading.I've read elsewhere that it has all to do with the new firmware updates.My update for the DZ seems to be country a specific one and came out a couple of weeks back.
Anyway,
I tried this visionary method a few times but the phone just hung and I had to go to the homescreen and uninstall Visionary and reboot to get the phone to run smoothly again.
Then I read another way of rooting the thing and it took me here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
After a couple of tries I was able to push the files to the DZ but got stuck at this command:
adb shell chmod 0755 /data/local/tmp/*
The error it gives me is:
Unable to chmod /data/local/tmp/sqlite3: operation not permitted
Strange thing is, yesterday at the same point it gave me the same error but it was 'busybox' instead of sqlite3 and right before that it was something else.Which should mean that those earlier commands were run successfully by the terminal.
P.S. Debugging mode is on.Visionary is uninstalled. followed all the steps mentioned in the guide.

Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.

mohitanfield said:
Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.
Click to expand...
Click to collapse
It looks like you are trying to root a DZ with a firmeware version >= 1.72.
If yes to have to downgrade it to 1.34 first.
See either the instructions here: http://forum.xda-developers.com/showthread.php?t=905261 or the more comprehensive at http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
But if your CID is other then the ones stated in the the first thread you need a goldcard to downgrade first, which is also described in the first thread.
have fun - Guhl

Thanks a lot for your reply and as is the case, my phones CID is HTC_38 which does not seem to be downgradable without a gold card.
I read the procedure and although its well explained, it will take a bit of time.
Will try it sometime soon hopefully, although I wish someone would just make a simple rooting app for the newer versions!

It took us month without sleep to create the existing rooting tools. So I do not see any simple rooting tools on the horizon

- 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.