Related
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
dbc00per said:
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
Click to expand...
Click to collapse
This would be better suited for Q&A that being said post the commands you are issuing and the errors you are getting. This would help someone trying to help you. Good luck
Try posting in clear concise sentences and it will help as well. Your post is like reading a teenagers tantrum and it's hard to follow.
From what I gathered, you can't get ADB to work, even though you're attempting to run it from a command prompt but the command prompt immediately closes from some unknown commands. That makes no sense.
From your computer, in windows, browse to the Android SDK folder.
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
With your phone connected via USB and debugging mode enabled type:
adb remount
and press enter.
What do you get?
First off...wrong section, this belongs in Q&A
Anyways...
1) Go to Settings -> Applications -> Development -> Enable USB debugging
2) Make sure HTC Sync is installed. Link
3) Right-click My Computer and go into Device Manager (while your phone is plugged in), if you see any yellow flags or unknown devices, remove them.
Now unplug your phone and plug it back in.
4) Place the sdk folder on your C:\ and run command prompt in Administrator mode.
Type "cd " (don't forget the trailing space), do not hit enter yet.
Now try to physically drag the tools folder into the prompt window, it will type text for you.
Hit enter.
5) Type adb and it should work.
If it doesn't work, well, you're going to need to give us more details...especially since if you follow what I wrote above correctly there is no reason it shouldn't work.
Sirchuk said:
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
Click to expand...
Click to collapse
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Neotelos_com said:
Does that work in XP?
Click to expand...
Click to collapse
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Neotelos_com said:
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Click to expand...
Click to collapse
Only works in vista and win 7
gx1400 said:
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Click to expand...
Click to collapse
Yeah like I said "workstation", I don't call any of my personal machines "workstations".
Also, I'd hope I know command line well considering I just gave advice on how to run adb through it.
thank you I've just gathered more information here than searching for days
Anywhere else.
Ive tried the black prince video, the unlockr method and the original xda perm root guide and my G2 will not perm root. Seriously need some help.
do you have adb and sdk installed?
>
no such thing!
its just smarter than you (;
lol
it is funny that you mention the black prince video, because that is what i used. im not sure, but i followed that video exactly and got it my first try. just watch the video very carefully, and follow EVERYTHING that he does and it should work. if not, then i am really not sure. obviously, you just need "S-off"
Are you using Visionary ? I would suggest the rage method, IMHO it's a lot more reliable and you can see if anything goes wrong because you're using individual commands.
i know its possible because I rooted my friends G2 just days before I got mine. I don't have adb, to be honest as soon as i see that it takes more than just installing a program on my pc, i flee, and its not because im new to android or rooting or anything like that, i just don't have a whole lot of spare time. And i DO have S-OFF. Like ill do everything in the blackprince video, then after I'm done I'll got and test the root by typing SU in terminal, and it says permission denied. Or for any of the other methods, same thing.
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
adamtheindien said:
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
Click to expand...
Click to collapse
Download HTC Sync from the HTC website (look in the downloads section), and install that on your PC. That'll give you all the USB drivers you need.
Download the Android SDK from http://developer.android.com/sdk/index.html and install it on your PC. Be sure to read the guide on installing it at http://developer.android.com/sdk/installing.html
Plug your phone in to your PC using the original HTC cable (do not use a third-party cable for this) and type "adb devices" at your PC's command prompt, and tell us if it can see your phone. It should show up your phone's serial number (don't tell us exactly what that is, this is a public forum), but if there's an error then we need to sort that first.
Edit - partially prompted by this request, I've started an "adb for Noobs" guide (very much a work-in-progress) at http://forum.xda-developers.com/showthread.php?t=865685
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
http://www.youtube.com/watch?v=A1SOSXwkc_8
adamtheindien said:
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
Click to expand...
Click to collapse
when you type adb devices does it recognize your device?
Super easy way.... http://forum.xda-developers.com/showthread.php?t=834228 just copy paste the codes.
Your phone might be s-off, but not allowing you to do any su commands. Mine was, but I just installed rom manager and it flashed clockwork recover no problem, then I flashed cyanogen and everything was good. Go into hboot and just make sure it says s-off, then do the rom manager bit. Try it and see if it works.
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
yeah, but i cant use rom manager since i dont have super user permissions. do i just temp root then try to install a rom? that seems sketchy. haha.
Earlier you said that you have S-OFF. If this is the case, then just open up Market and download Superuser by ChainsDD. Then you should be good to go.
adamtheindien said:
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
Click to expand...
Click to collapse
When you type "adb" on your PC, Windows needs to know where to find the "adb" program to run it. So you either need to specifically add the directory containing adb to your Windows PATH variable (which you can do in the environmental variables section, which will be in different places on different operating systems - on XP you need to right-click on My Computer, then select Properties, then Advanced, then the "Environmental Variables" button) - or you need to cd to where adb is stored under where you installed the Android SDK, and run it from that folder.
pretend youre explaining this to a five year old...
ok, which operating system do you have on your PC ?
Where did you install the Android SDK, i.e. which folder on the PC did you put it in ?
never mind guys, did what that dude said and just installed a rom with temp root and im all good now. thanks for everyones help though, sorry for my lack of knowledge in adb and what not.
Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!
You have the Motorola v4.9 USB charging drivers installed?
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.
bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.
Ah, Mac, I'm of no use to you then.
Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App
I've been wanting to set up adb for a while, but just don't know how to do it. There are numerous guides, and each say different things generally. Things that hold me back from setting up are:
1) does it make a difference what guide I use if I'm already a root user? *Cause I am.
2) when I run cmd as administrator, I get C:\Windows\system32 instead of just C:\
3) I don't know whether my computer is 32 bit or 64 bit.
4) Which are the right files I need in order to do this?
Could someone please point me in the right direction? My computer runs windows vista.
Just put the sdk on your c drive and rename the sdk folder to android-sdk-windows
Now don't run cmd as administrator, just type this in standard command prompt.
cd c:/android-sdk-windows/tools
and you should be able to use adb. Make sure debugging is checked in settings on your phone. You will find it in manage apps/development.
If that doesn't work maybe this will help.
http://forum.xda-developers.com/showthread.php?t=694250
http://forum.xda-developers.com/showthread.php?t=879701
Sent from my PC36100
Also make sure that your tools folder has the adb.exe file in it or you are going to get a
"adb shell not recognized as an internal or external batch command" took me about 20 minutes of.retyping adb shell to figure it out haha..
The reason i say that is because if you have a fresh dl of SDK within the last.couple of weeks then the adb.exe file has been moved and is no longer in your tools folder.
As for the command prompt. Open cmd then type
Cd/
Will take you straight to your C: directory if your not sure where to go from there type "dir" then cd to whatever folder your sdk is in
or type "cd(space).." like "cd .." Then do it again however many times you need to until it backs you all the way down to the c:
Click start and right click on computer then click properties, it will tell you there if your 64 or 32 bit.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks guys for the help. Sorry, but I'm not sure where to get the sdk, is this it: http://developer.android.com/sdk/index.html ?
Also, what drivers do I need to install on my phone?
guih said:
Thanks guys for the help. Sorry, but I'm not sure where to get the sdk, is this it: http://developer.android.com/sdk/index.html ?
Also, what drivers do I need to install on my phone?
Click to expand...
Click to collapse
If you check that first link I posted above it has everything you're about to ask lol. Go to control panel on ur comp, navigate to system, and it will tell you if your machine is 32 or 64bit.
And yes that's the sdk. I'd download the first zip in the post and extract it to your c drive.
Sent from my PC36100
Moving adb to the /tools folder from /platform-tools will will Bork some other features of the sdk.
lol sorry man what threw me off is the "installing drivers" thing. Ok, do I also need to download that installer file as well or do I just take the sdk and extract it to the C drive? I'm sorry for these noob questions, I just don't want to mess up anything.
Don't worry about the questions. That's what we're here for. Yes, extract it to your C: drive. Adb is located in the platform-tools folder.
Sent from my Gin and Tonic using XDA App
guih said:
lol sorry man what threw me off is the "installing drivers" thing. Ok, do I also need to download that installer file as well or do I just take the sdk and extract it to the C drive? I'm sorry for these noob questions, I just don't want to mess up anything.
Click to expand...
Click to collapse
Its cool were just trying not to confuse you as much, maybe a video will help...or not lol
http://www.youtube.com/watch?v=y6K1XLmafPc&feature=youtube_gdata_player
Sent from my PC36100
I have a tools folder and a platform folder.. I'm guessing I use the tools folder?
guih said:
I've been wanting to set up adb for a while, but just don't know how to do it. There are numerous guides, and each say different things generally. Things that hold me back from setting up are:
1) does it make a difference what guide I use if I'm already a root user? *Cause I am.
2) when I run cmd as administrator, I get C:\Windows\system32 instead of just C:\
3) I don't know whether my computer is 32 bit or 64 bit.
4) Which are the right files I need in order to do this?
Could someone please point me in the right direction? My computer runs windows vista.
Click to expand...
Click to collapse
1). It doesn't really matter what guide you use, just as long as they give you correct directions.
2) Press the windows key (between Ctrl & Alt) and type "cmd" then press enter. Then once you're in command prompt, just type "CD\"
3) Right click "My Computer" then go to properties. Look for system type, and it'll tell you whether you're 32-bit or 64-bit. I believe most people have 32-bit.
4) All you need is this file.
guih said:
I have a tools folder and a platform folder.. I'm guessing I use the tools folder?
Click to expand...
Click to collapse
No, run the SDK Manager to get the platform-tools folder.
EDIT:
The SDK Manager is located in the folder that you extracted and probably renamed. For instance, mine is located here C:\AndroidSDK\SDK Manager.exe (If you can't locate it, let me know).
After you run the SDK Manager you only need the Android SDK platform-tools, revision 5 package
(Sorry about the double post)
dirkyd3rk said:
Its cool were just trying not to confuse you as much, maybe a video will help...or not lol
http://www.youtube.com/watch?v=y6K1XLmafPc&feature=youtube_gdata_player
Sent from my PC36100
Click to expand...
Click to collapse
so far this video is helping me incredibly! lol
guih said:
so far this video is helping me incredibly! lol
Click to expand...
Click to collapse
WOW! I must've looked over that post. That's a good video. Well, good luck.
I'm waiting for the platform-tools to download... in the video the guys moves all that is in platform-tools into his tools folder. Should I do that, though someone mentioned it could bork something?
guih said:
I'm waiting for the platform-tools to download... in the video the guys moves all that is in platform-tools into his tools folder. Should I do that, though someone mentioned it could bork something?
Click to expand...
Click to collapse
Follow the video young Jedi.....
Sent from my PC36100
oh my god...IT WORKS. THANK YOU EVERYONE SO MUCH FOR EVERYTHING!
guih said:
oh my god...IT WORKS. THANK YOU EVERYONE SO MUCH FOR EVERYTHING!
Click to expand...
Click to collapse
You're welcome. Congrats. Have fun! LOL
guih said:
oh my god...IT WORKS. THANK YOU EVERYONE SO MUCH FOR EVERYTHING!
Click to expand...
Click to collapse
No problem man. May the force be with you......lol
Sent from my PC36100
guih said:
...Should I do that, though someone mentioned it could bork something?
Click to expand...
Click to collapse
If adb is the only tool you are going to use in the SDK you don't have to worry about it. If you do ever use another tool and you get an error about adb not present in the /platform-tools folder you can always just move it back.
What are the odds of hard-bricking the Nexus 7 while rooting and istalling a custom kernel? And if it bricks, is there a way to fix it?
I ask this because I want to root it, but I'm really worried.
Also, how can you fix a soft brick?
I think you should really care of these questions if you somehow corrupt both bootloader and recovery. I don't really know, but bootloader isn't a thing that is modified during rooting or changing kernel. Just carefully read the thread about rooting programs, follow the instructions and everything should be ok. The most potentially harmful thing that can be done is corrupting the recovery. It can be solved if you have a computer with adb and drivers installed. Just a sшmple command and recovery is reflashed. Unlocking the bootloader is a kind of thing that doesn't really change anything so you couldn't boot or something. It just clears the storage and changes something deep inside. Flashing ROMS/Kernels is a kind of coping files and if something goes wrong you can always reflash it from recovery or with adb or some app from the rooting kit. And also you can always flash everything stock. Just read and think of what you're doing. Good luck.
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
LittleConfucy said:
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
Click to expand...
Click to collapse
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
rtfpessoa said:
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
Click to expand...
Click to collapse
So, what do I have to do?! Sorry, I'm a complete noob xD
LittleConfucy said:
So, what do I have to do?! Sorry, I'm a complete noob xD
Click to expand...
Click to collapse
Just run:
sudo fastboot oem unlock
rtfpessoa said:
Just run:
sudo fastboot oem unlock
Click to expand...
Click to collapse
It doesn't recognize sudo as a command
LittleConfucy said:
It doesn't recognize sudo as a command
Click to expand...
Click to collapse
Are you on windows?
If yes, are you on bootloader mode?
If not:
1-Power off
2-Power On + Vol. Down
Then you execute "fastboot oem unlock"
If it doesn't work try to use any of the auto tools that you can find all over XDA forums
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Do you have any idea where can I see the drivers that were installed on the computer?
Slavon-93 said:
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Click to expand...
Click to collapse
So I have to copy the file, paste it in the same directory, without deleting the previous file, and change its name?
Need help...
After I rooted, I opened BusyBox and it said:
"There was a problem opening a shell with root acces. This is either being caused by superuser/supersu or by a device that is inproperly rooted."
I downloaded root checker, and it says that it's not proprly rooted