Question about ADB - myTouch 3G, Magic General

I am currently running CM 4.2.2. on MT3G and I have been reading/hearing a lot about adb. Is it required to do something you can't do otherwise? Also, I downloaded the adbwin.zip wrapper and when i do "adb devices" my phone shows up as connected and I can browse through the file system and stuff. Does that mean that adb is working fine?
I tried installing an apk named test.apk that was in the main folder of the sd card by doing "install /sdcard/test.apk" but it didn't work.
Any help?

ADB isn't required, but it sure does make doing some stuff easier.
Refer to that guide if you want to setup ADB, it'll show you some commands for ADB also. Hope that helps
http://forum.xda-developers.com/showthread.php?t=532719

Related

ADB Problem with HTC Magic Vodafone

Hello, I install the android SDK correctly and install all correct drivers, all correct files from the google repository, and reading on unlockr, you need to type CMD and enter a few commands, the final one being ADB devices, which is meant to bring up your device serial/id but doesnt show nothing for me, i deleted all drivers with a program, and it re-installs them, I put the phone into debug mode too, but whatever i try, i cant root my magic (32B), please help!!!!
i have followed every single guide but cant blooming root my phone!!!
HELP!!!!!!!!
Install the HTC Sync software first. If this connects correctly and recognizes your phone, then the ADB will find it too. I use it as a test, whether the drivers are installed correctly or not.
To start the ADB, you have to navigate to the folder where the SDK was extracted using the CMD Prompt, and then into /tools. There you type ADB and the command you want to execute.
done that mate, going to /tools and then adb devices and its meant to say a device serial, but on mine it shows nothing
As far as I know, you have to have a recovery installed to access adb.
Write "fastboot devices" while in /tools to see if the drivers are OK. When you install a recovery, adb should be accessible.

New guy rooting vibrant

Hay, my name's Nick, been reading the posts for a while, decided to join. Iv'e been wanting to root my T-mobile vibrant so i can get a more streamlined ROM will less features to make the ones i use go smoother and faster and get the full potential out of the device. I rooted it no problem with one click root, installed clockwork rom manager, and titanium backup, installed clockwork recovery (i love the clockwork orange icons by the way) put the latest "insanity 0.6.7.zip" in the root of the internal SD, and hit the "install rom" option on the rom manager and selected the .zip, and it made my phone go into the standard recovery mode, no option to install any .zip files. So i opened the rom manager and manually put it into CWM recovery so i could manually install the rom. It looked like it was going to work, but then it sent my phone back to the recovery screen with white text that said "install update.zip" so i did what it said, and it sent my phone into a boot loop. I can get into recovery mode, but when ever i try to recover my backup or access any files it says "no files found, operation canceled" or something like that. It also fails to mount via USB. I can get it to go to download mode but have not tried odin yet, because im on a mac (working on getting bootcamp working now to run windows)
Odin seems like my only option now right? anyone have any idea ware I went wrong? it must have been the incorrect update.zip file right?
I dont think u flashed a vibrant rom
Just mount your internal sd from clockwork and copy over a vibrant rom, and flash
Sent from my SGH-T959 using XDA Premium App
have any idea why it wont let me mount my sd card? that makes me worried it wont connect to a Pc in download mode but i haven't had the opportunity to try that yet.
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
when it booted up it went to my normal "vibrant" screen, then to an unfamiliar "galaxy s 19000" screen. Im assuming there is a difference between galaxy s and vibrant right?
jRi0T68 said:
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
Click to expand...
Click to collapse
tried that, when i try to to install zip from sdcard it says "no files found"
i assume it's looking for files on the internal and not the external right? so i tried mounting the external sd card from the mounts and storage menu, and i got an error message that said "E:INFO is WRONError mounting SDEXT !"
In recovery, do you see any folders when you click install from zip, or is that when you get an error message?
If you see folders, can you navigate to external_sd?
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
amandadam said:
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
Click to expand...
Click to collapse
That's useful for me as well.!
shreddintyres said:
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
Click to expand...
Click to collapse
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
niik000 said:
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
Click to expand...
Click to collapse
Never rename rom zips to update.zip leave it at bionix.zip and flash through clockwork mod recovery.
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
niik000 said:
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
Click to expand...
Click to collapse
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
i ran the SDK and AVd manager and installed the rest of the SDK packages, then found the ADB file and drug it into the terminal, that gave me the list of commands. I plugged in the phone and tried "adb devices" and it said "command not found" tried quitting and restarting terminal a few times and still nothing
shreddintyres said:
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
Click to expand...
Click to collapse
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
niik000 said:
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
Click to expand...
Click to collapse
thats a security feature within linux it wont show what you are typing but rest assured its registering keystrokes, and you dont drag and drop to terminal
assuming the androidsdk is in your home directory you would type
cd /home/username/android-sdk/platform-tools
then ./adb devices (this is just a check to make sure your phone is being recognized)
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
niik000 said:
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
Click to expand...
Click to collapse
ok so you are doing this from mac then? i apologize as i have no experience messing with android using a mac, id imagine itd be much like linux although terminal commands may be different. If i were you id google using adb commands in mac os and see what you can find, personally i use windows normally and am only just learning how to work linux

ADBWireless

I've seen a few posts mentioned how easy using adbWireless app, instead of using USB. However, I've tried and never work. I don't now why people saying it's easy or simple to use, based on different of definition of "easy"
On the NC side, it asked to "adb connect 192.168.xx.yyyy:5555"
I typed that on the Command Prompt on PC running W7, always get "adb is not recognized as an internal or external command, operable program or patch file."
Am I missing something here?
Thought I must need to get the SDK installed, I follow this link:
http://www.androidcentral.com/sdk-driver-root-oh-my
In that instructions of Step 1, the author said "Unzip the download with your favorite archiving tool and drag the folder you extracted into your Workspace. Don't open the folder, just drag the whole thing over. That's it. The Android SDK is now installed."
Is that true? That's it? no need to run any executable file? just drag the folder over and SDK suddenly get installed somehow? Really?
Any input is welcomed.
Ended up installing both SDK and usb driver.
Using adbWireless, cannot connect to it then suddenly it does, don't even know why or what I have done.
I'm start thinking the culprit is my laptop.
"adb devices" always returns with no devices regardless using adbWireless or USB cable.
Gotta tried on different computer.
Sounds like you need to CD to your tools folder in the sdk.
Sent from my LG Optimus V using Tapatalk
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
votinh said:
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
Click to expand...
Click to collapse
If you use adb connect ###.###.###.### (you only need ": port" if you change from default of 5555) then issue adb devices it should list the nook with its ip address as the device id after it is connected.
One thing to be aware of with adb wireless... if the nook is rebooted with it enabled... you will have to cycle adb wireless for it to work.
I actually tried to connect both with and without xx:5555

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.

Can't sideload onto NSTG

Firstly i rooted with GlowNooter, but the market wasn't working, so I figured might as well go with tinynooter as I don't any other gapps.
I've successfully rooted with tinynooter now, but I'm not sure how I can sideload applications. I have them copied onto the sd card, but how do i navigate to the sd card? The supermanager that's included isn't working
And amazon appstore doesn't work for me since I'm outside of the USA.
What's the easiest way to get a file manager installed (or is there one somewhere im unaware of) ?
What you need to do is set up ADB on your computer - ADB = Android Debug Bridge, and you can use it to install apk files to rooted devices.
ADB wireless, included in glownooter and tinynoot, lets you issue ADB commands to your device over the wireless connection, eliminating one hassle that many folks have - getting ADB running over USB. I think but don't remember for sure that you need to have the "allow non-market apps" tickbox ticked in the Nook Color tools for this to work.
The command to install an app via adb is just
adb install appname.apk
(that assumes that you are running the command from the same directory that you have the APK sitting in on your computer.)
To install files that you already have copied to your device, you can do:
adb connect x.y.a.b
where x.y.a.b is your wifi IP address
then (with tinynoot; glownoot users don't need this step, I don't think)
su
then
cd /sdcard
pm install appname.apk
(pm is the android package manger, which you are running directly in this case.)
How do you install ADB?
written guide:
http://forum.xda-developers.com/showthread.php?t=879701
video guide:
http://www.xda-developers.com/xda-tv-2/pro-tip-number-4-installing-applications-using-adb-xda-tv/
Thanks a dozen, I was just reading up on that, and i managed to get it to work

Categories

Resources