market - Nook Color Q&A, Help & Troubleshooting

I installed Honeycomb onto my sd card following instructions to the tee. I also unzipped the android sdk files onto the sd card as well. Now when it comes to opening a command prompt in that folder I am completely stupid. I go to My computer and the sd card shows up under the F: drive. How do I open a command prompt for my F drive (ie.. what do I type?)? I know it's a stupid question, but I really don't know how to do it.

Not sure why you need a command prompt on that file, but in your computer, you can go to start -> run -> then type "command" (without the quotes) to get a command prompt

Which instructions? If you're using windoze, you shoulda downloaded some files to a windoze folder, not the sd card if I remember correctly. To open a command prompt in the open windoze folder use shift-right click and select "open command window here".
Smiley

Thank you for the shift-right click. Still learning something new every day.

Related

Install non-market apps without File Manager: Possible?

Simply put is there a way to get an app onto my phone without the market or file manager?
I ask because I want to use Haykuro's G build but I cant download any apps. I do however have all the ones I use regularly backed up onto my SD card but I cant access them without a File Manager (which I cant download to use). Is there a way?
|Spike|
There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.
Unicornasaurus said:
There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.
Click to expand...
Click to collapse
How do I install thru ADB?
|Spike|
Get the android usb drivers, adb.exe and adbwinapi.dll from an Android SDK. Plug the Dream in via USB and point to the location of the drivers when it is installed. Then open your command line, navigate to whatever folder adb.exe is in and type adb install <full path to the apk>. If you run Linux hopefully you can figure it out on your own based on the steps above.
Alternately, upload all the apks you want to the internet somewhere. Check the box to enable installation from Non-market sources in the system settings, then type the full URL of the apk into the browser. The package installer will take over from there.
Here's how you do it. Assuming your G1 is rooted
1. Download the attched files, and copy them into your \system32 folder (Start > Run > %systemroot%\system32)
2. Sure your G1 is enabled for USB Debugging (Settings > Applications > Development > USB debugging) and that your G1 has the appropriate drivers installed. If not, download the USB drivers from HERE
3. Plug your G1 into your computer (Make sure you have USB 2.0 - Click here to find out how to check). When your G1 says "USB Connected" DO NOT click "Mount"..don't do anything
4a. Vista users - Follow these steps. For XP Users, skip to step 5
4b. On your computer, browse to the directory where the APK for your file is located
4c. Once located, hold SHIFT and right click on a blank area of the folder
4d. Click on "Open Command Window Here"
4e. Type "adb install nameofyourapkhere.apk" - without the quotes.
4f. It might say something like "daemon service not started" or something, but it will start it and continue. It'll then say something like 626k/1293k bla bla bla
4g. If it was successful, it will just say "Success". You can close the command window and SHAZAM! Your program will now be installed on your G1, and you can access it like any other program on your phone
5. XP Users - Follow these directions:
a) You can either go Start > Run > type CMD and press enter
OR
Windows Key + R > type CMD and press enter
Navigate to your APK file via the command prompt. For easy usage, put your APK file on your desktop. That way all you have to do is type "CD Desktop" into the command prompt
b)Type "adb install nameofyourapkhere.apk"
c)You may get a couple of messages like in the steps for Vista users
d)If all goes well, you too will get the success message
e)Enjoy your application!
Any confusions, let me know. Hope it helps, and Good Luck!
I've been using a local web server and the android browser.
untermensch:
Thats a possibility, but oddly enough, that requires a http-server
AGx-07_162:
With unicornasaurus's method above, you can install all the apk's you want... you can install apkinstaller and use that through that method, but you can just aswell install your apk's directly through it
I ran into the same problem. Here is the easiest ways to get the appinstaller on your G1. Download this file from your g1 browser or Gmail yourself this file, and download.
http://www.mediafire.com/?egy0mop2qqx

EASIEST sdk adb guide tutorial instructions

I have learned alot from this site so i figured i'd give something back. these are the the two easiest methods i have found for setting up the android debug bridge. one for windows and one for linux... these instructions should work for any version of windows.
first make sure you download the latest sdk by going to android.com and clicking on developers.
windows:
after you have download the sdk, unzip it to your desktop. rename it to sdk. cut the UNzipped folder on the desktop that you just renamed by right clicking and hitting "cut" then go to start>my computer>c: and paste the folder here. now go into the new "sdk" folder and right click on the "tools" folder and click "send to" then choose "desktop (as shortcut)" you should now have a shortcut on the desktop called "tools-shortcut"
now for the easy part: hold shift and right click on tools-shorcut, holding shift adds the option "open command window here" to the context menu that comes up so click on that. now just make sure your phone is connected to the computer and on ur phone debugging is enabled (menu>applications>development>debugging). on ur command window that came up you should see a black box with white text and the cmd should be c:\sdk\tools> just type "adb devices" and you should see your phone under "list of devices attached" if you do see it you should be able to start running adb commands
adb pull "/location to file or folder on phone" -(the pulled folder or file will be in the tools folder we created earlier which you can still access by clicking on the tools-shortcut on your desktop)
adb push "name of file or folder to be placed on the phone sdcard" -(make sure the file or folder you wish to place on the phone has been placed in the "tools" folder on the computer, again its the same folder the "tools-shortcut" opens up)
hint and examples: i have found a good way to back up and reinstall all ur apps using just adb push and pull. just experimenting and playing around with it i have found you can accomplish installing with just knowing these commands above... if you plan to data wipe and flash a new rom but you don't want to go through the tedious task of reinstalling and you have a rooted android phone then you may use this method to backup/reinstall ALL of your apps. plus this will give you good practice using adb.
backup example:
adb pull /data/app .... let it finish
adb pull /data/app-private ...let it finish
now you should have ALL of ur apps in ur tools folder on ur computer! in the tools folder, create a new folder and name it what u want, i named mine APPS4EVO because i have an evo and and epic and some apps don't work for both so i keep them seperate. cut and paste all of ur apps and put them into your newly made folder. now back to the adb window
restore example:
adb push /APPS4EVO /data/app/
this will push all of your apps in your backed up folder you made earlier to the folder where apps go when they are installed and if you wait 1-10 minutes depending on how many apps you have you should be able to see them on ur phone as if you had installed them one by one. also notice the space between /APPS4EVO and /data/app/ the space seperates the folder from inside ur tools folder you wish to install and the location you wish to put them on ur phone. please be aware that you do not need to type c:\sdk\tools\APPS4EVO because the command window is already being ran in the tools folder, so the location would just be /APPS4EVO in my case.
adb shell -opens up the terminal shell to run commands specifically for the phone, while in the shell you cannot run other "adb xxxxx" commands, you will have to exit the shell by typing "exit"
OPTIONAL: i marked this as optional bc with the above it is not necessary... i have never done this and my adb works great but i have seen it often in other tutorials around the web.... i believe its only necessary on windows 7 and maybe vista. go to start then right click on "my computer" and click on "properties" then in the left pane click on "advanced system settings" then in the window that pops up click on "environment varables" button, in the next window that pops up, under "system variables" scroll down to the "path" variable and double click it. in the "variable value" box do NOT erase anything but add ";c:\sdk\tools" (without quotations). then click ok on all the windows cuz ur done.
thats all for windows.
linux (ubuntu)
extract the sdk to your home/name/ folder and rename it to sdk. now right click on the folder and go to permissions and make sure (run as executable) is checked, now go into the folder and do the same permission change to the tools directory.
now you should be able to run adb commands in the terminal when your phone is connected. same as in windows except your commands will be preceded by your tools folder location....
FOR EXAMPLE:
/home/jay/sdk/tools/adb devices
/home/jay/sdk/tools/adb push xxxx xxx
/home/jay/sdk/tools/adb pull xxxx
EXTRA:
if your having troubles connecting ur phone to ur computer over usb, even after installing drivers, like i sometimes have with my epic, you can download "wireless adb" from the market which i found to be surprisingly easy to use, just like if u were connected by usb, except under adb devices you will show up as your gateway address not ur device name but trust it still works the same.
good luck everyone, i hope this post isn't redundant and i really hope i help someone out there just starting! adb is confusing at first.

[Q] Error: adb is not recogzined as an internal or external command

Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Has winxp, tmobile GT
I had this same exact problem, but I was just able to get it working. First, this website is helped a lot:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Also, make sure you download the Java SDK package from the link given on that website.
Second, when the website says to "Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool" open command prompt and enter this code:
cd (enter the path to where the android SDK was installed), for example:
cd C:\android\android-sdk-windows\platform-tools
Notice how I entered "platform-tools" instead of just "tools" because this is the folder where the adb file is download with the android SDK. After you do this, you should then be able to apply adb codes (make sure the screen on your tab is on because you will have to accept superuser prompts, therefore your tab needs to be rooted).
Every time you open command prompt, you will have to enter:
cd thentheplacewheretheandroidSDKisinstalled
as stated above before you are able to enter adb commands.
Hope this helps!
@caveman999 is giving good advice. Working in the command window is weird to those who did not use old pc-dos environment.
You have to be in the tools directory or you have to edit your PATH in windows so you can use adb from any prompt.
thnaks for both of you guys i installed the java jdk and also specified the path in environment variables but still error message!
I could only get adb to work error-free when I was in the same directory as adb.exe program. Just change directories cd..(enter) etc until you are in that directory.
tabing said:
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Click to expand...
Click to collapse
I had the same error, until I downloaded and placed the .adb files accordingly.
Source: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
"UPDATE: If it says adb not found or something similar, download the ADB files and extract them into the Tools folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back)."
download adb files from here: http://www.megaupload.com/?d=RTEY0Q97
The important thing is to put the files really under the "tools" folder.
When you check out above Source I am sure your problem will be solved
Thank you all problem solved
tabing said:
Thank you all problem solved
Click to expand...
Click to collapse
Glad to here it. Why not hit a few thanks buttons?!

Problems with adb not working!!! Fixed

Originally Posted by Spin Dr Wolf
Gah. I can't get adb running, i keep getting the message below whenever i try any adb command.
" 'adb' is not recognised as an internal or external command, operable program or batch file. "
I have no idea where its going wrong though, i have the USD drivers installed got the SDK kit unzipped on the drive too, using the commands in the right place. Anyone got any ideas ?
I'm using Vista sadly if that makes any difference ?
HI! I understand you reading this part:
Section 3: Running ADB from Command Prompt
Running Command Prompt:
Windows XP: Select Start or Tap the Windows Key on your Keyboard, select "Run" and type "CMD" then hit "Enter".
Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-x.x_rx\tools "x = version you are using"
The Value is WRONG!!! It has changed. It should be C:\android-sdk-windows-x.x_rx\platform-tools\
Dont forget to x10christian

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

Categories

Resources