Hey guys,
I had a few questions about sideloading off market apps, that i couldn't find answers to. Thanks for your consideration.
If i understand correctly, you can only sideload apps on my unrooted samsung captivate by using a connection to a computer, right?
I know about the sideload wonder machine and i have used it successfully.
I know i could download the android sdk, and use the adb push command.
Is there a way to edit the no_market_app value in the settings db file only using my un-rooted phone?
Or can i use terminal emulator or a combination of both to somehow install an off market app?
I was just trying to think of ways to avoid having to conncect to a computer to install an app. I was on the road with a friend, and i had an off market app i wanted to give him, but he also has att(which blocks sideloading of off market apps), so i didn't even try. But wouldn't it be awesome if i could send the apps to his phone through bluetooth or email, then install it on his phone without rooting his phone? Maybe a temporary root of some sort would work? Isn't that how swc works?
Anyways, once i've played enough with my stock phone, i'll beg for more and i'll eventually root, and i'll probably end up playing with the sdk too. Thanks again guys!
To Root or Not To Root... or Perhaps Just A Temp Root...
There are a few quick fix temp root apps floating around. It really depends on you model and build if they work correctly or not.
You could, as you mentioned, push from a cmd promt in adb, install from the cmd promt in adb to the device - or - pull from the device itself using a shell or terminal.
Unfortunately, I currently don't know of a direct way that you would be able to access, let alone edit the system.db file to make a permanent modification without at least being under a temp root.
Peace-
Related
Is it possible to root within the phone using a terminal emulator as long as all the files are where they need to be in the sd card?
I tried but I'm stuck at the step "cd_sqlite_stmt_journals" it just says permission denied
Do you have to have it hooked up to the pc with adb even if the files are already on the SD card?
I ask because last night the OTA update forced it's way into my phone while I was sleeping and I lost root, I'm not home so I don't have the transfer cable with me
I think you are trying to root without ADB correct or connecting to your PC? If so use this step by step directions to be able to root without ADB. I believe it does require a separate file you may need. Hope this helps!
http://www.youtube.com/watch?v=HwNP5a5ULPs
I did it all from the phone - using the instructions here with success - and then it updated and I still have root... so I am not promising anything other than I rooted with the original OS and then upgraded OTA with no impact to my root or phone in general.
http://www.droidforums.net/forum/droid-x-hacks/62450-how-root-without-using-adb.html
Hope this helps, and looking forward to having the ability to eliminiate the Blur interface and go AOSP (I also have a EVO and think that interface with Sense rules compared, but AOSP is better than that Blur crap in my opinion...)
Is it possible to do this?
how can i run script commands without having to connect my phone to a laptop computer?
I have root explorer app installed, if someone knows how to do it with that app please give me a simple tutorial.
also, i found this other app on the android market called "ScriptMe" by gilsken.
the app has no reviews, but the description doesnt say how to use it to execute scripts.
in case any of you haven't noticed, yes I am a newbie when it comes rooting phones, any help is appreciated, let me know, thanks.
Do you want to use adb natively on the phone or just general scripts? You can run commands and scripts by installing a terminal from the market, I think Better Terminal Emulator Pro is the best. I think you can run most adb commands from the terminal but I'm not sure if they all work. I mean, push and pull don't seem like they'd work without somewhere to transfer files to, but maybe they push and pull to the sdcard or something. I'm really kinda clueless when it comes to adb because I've only used it to root the phone and use standard terminal tools for everything else.
I think I tried ScriptMe. You have to put the script on the sdcard, select it with the app, tap "execute" then it says "script ran". I'm not sure how that's useful. The only scripting app I've found useful is GScript, but there is another called "Scripter" which stores the scripts so you can select them from a list to execute them. Kinda like a no frills GScript.
Yeah just use the terminal app. It comes loaded on cyanogen and most ROMs out of the box.
Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike
Download and install "SuperUser" from the Android market
OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.
id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App
fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.
fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.
Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.
Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.
OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.
I hope this post can be of use to someone. My workplace is running Lotus Notes (sigh) and IBM recently released an update to their Traveler server which supports Activesync sychronizaton of mail, contacts, calendar and directory on Android, Iphone, etc.
The only problem is AT&T blocks Sideloading. Yes a simple root can fix the issue but that is not a true solution for every Captivate for our users. I figured out a relatively easy method of getting around this limitation.
First you need the following:
Rooted Captivate (to obtain the .apk files necessary) Only needed once, I would upload the necessary files but IBM won't like that very much.
Computer with Captivate drivers and Android SDK
The Lotus Traveler setup requires two installs which makes the process more tricky than simply doing an adb install lotusinstaller.apk, so we need a few more steps.
1. On your PC download the Lotusinstaller.apk file from your traveler server and copy it to you sdk\tools folder.
2. Plug your rooted Captivate phone into you computer with debugging mode on and use adb to issue the following command "adb install lotusinstaller.apk"
3. Open the installer application on your phone and enter the required server and authentication information for your system and click next. (this will create the server setting on the phone and download the lotustraveler.apk file to your rooted phone.) I can't remember the exact location so simply do an adb shell then "su" to gain super user rights and then do a find -name LotusTraveler.apk (or *.apk and find the lotustraveler.apk)
4. copy this file to your computer. One easy way would be to adb pull LotusTraveler.apk c:\location of sdk\tools\
Now that you have both the lotusinstaller.apk and lotustraveler.apk you will not need the rooted captivate for future phone setups.
5. Now to setup a stock Captivate. Enable usb debugging
6. adb install lotusinstaller.apk
7. launch the installer and enter the appropriate settings on the phone and click next. It will attempt to download the lotustraveler.apk and then give you an error about not being able to install applications that aren't from the market. Ignore that and close the installer.
8. now issues abd install lotustraveler.apk on your pc
You're done. The installer setup the initial server settings and the lotustraveler did the rest.
To setup more phones begin from step 5 from now on
***Disclaimer***
I wrote this up simply from memory so I'm sorry if this is not 100% accurate with the commands etc.
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
thats exactly my first thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Clienterror said:
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'll try the wonder machine first. thanks for that tip.
Your suggestion won't work as stated in my walkthrough. The initial apk downloads another apk to your phone somewhere in the system directory. Once you have both apk files it's a simple "adb install lotusinstaller.apk" then "adb install Lotustraveler.apk"
wonder machine causes the issue of not being able to install the second apk file as stated in my last post. It can replace adb install after you have both apk files on your computer.
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Ziuck said:
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Click to expand...
Click to collapse
just do
find -name LotusTraveler.apk
it will show you where the apk is located
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
psbear532 said:
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
Click to expand...
Click to collapse
Use adb
Code:
adb install myapp.apk
ros87 said:
Use adb
Code:
adb install myapp.apk
Click to expand...
Click to collapse
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
psbear532,
You can use a file explorer program (astro, es explorer, etc), and choose the apk on sd and install it. Just remember to use nookcolortools and de-select and re-select the non-market app box.
I guess it would be easier - I haven't had luck with adb so far...
psbear532 said:
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
Click to expand...
Click to collapse
Assuming you've successfully rooted your NST:
1: Enable wifi on your NST and make a note of the IP address assigned to it.
2: Tell adb to connect to that IP
Code:
adb connect 10.0.0.2
That's it, if adb was able to connect you can now adb push or adb install all you want
---------- Post added at 01:41 AM ---------- Previous post was at 01:39 AM ----------
apeine said:
psbear532,
I guess it would be easier - I haven't had luck with adb so far...
Click to expand...
Click to collapse
Why?, apart from having to download and install the Android SDK, using adb should be straightforward unless you're trying to get it to connect to the NST trough usb.
Ros87,
Maybe that was my mistake. I've always tried using USB :S
apeine said:
Ros87,
Maybe that was my mistake. I've always tried using USB :S
Click to expand...
Click to collapse
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Thank you both so much! Ros87 I got it to work over wifi which I think is even better since now I don't even have to deal with the wire. apeine I didn't try your method since adb worked, but thanks for your time anyway.
ros87 said:
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Click to expand...
Click to collapse
So why don't you install linux on a separate partition?
How does one do this without an SD card? I will be getting one soon, but for now, can I just create a temporary folder on the home directory and install it from there? Does it automatically install to the apps directory?
Thanks!
EDIT: I just figured out how much you can browse with the computer. So...
The simplest method is to just copy the apps to an SD card, insert the card,browse to the .apk location,tap on the .apk file, you will be prompted with an screen asking if you want to proceed to install or just use the adb over wifi method as explained above
I use and app names Airdroid. It allows you to install apps remotely from your computer via wifi.
I have an "apk" folder in my UbuntuOne account, Dropbox should work too.
then i have the app for the service installed.
it works fine for me