Hi, i want to unlock my bootloader, and i know that i must use fastboot app on my computer.
But everytime i click on fastboot.exe it's turn off after 1 second?
What I do wrong?
hurdleman said:
Hi, i want to unlock my bootloader, and i know that i must use fastboot app on my computer.
But everytime i click on fastboot.exe it's turn off after 1 second?
What I do wrong?
Click to expand...
Click to collapse
It's a command line program, so you have to open a command prompt to the directory fastboot is in
An easy way to get command prompt to the correct directory is to hold shift and right click on an empty space in the folder (make sure no files are selected), then an "open command window here" option can be selected
no offence but if you fail at loading a CLI program then maybe you should re consider unlocking your device. but if you know what your doing and this was a genuine silly mistake then feel free to unlock it.
Fma965 - Forgottencoders.co.uk
jacklebott said:
An easy way to get command prompt to the correct directory is to hold shift and right click on an empty space in the folder (make sure no files are selected), then an "open command window here" option can be selected
Click to expand...
Click to collapse
The shift - click method only works in Windows 7, I think.
But you can also open up a CMD window and use the CD command (Change directory). Type in cd and then drag and drop the folder containing the fastboot files in the CMD window and then press Enter.
Sent from my R800i using xda premium
Related
i am trying to install a boot animation, but i can't remember the sequence or how to navigate to the tools folder with my command prompt. 2 weeks ago i managed to change my splash screen, but im still kinda new with this and forgot what i did. lol. i've tried searching this forum, but nothing ive found so far helps. could someone point me in a better direction? thanks!
open command prompt either by the shift right click method or using the cmd prompt... if the shift right click method doesn't work (it doesn't for me) then just do it the long way
type:
cd android-sdk-windows
cd tools
then type the commands of what you're trying to fastboot
surrealmethod said:
open command prompt either by the shift right click method or using the cmd prompt... if the shift right click method doesn't work (it doesn't for me) then just do it the long way
type:
cd android-sdk-windows
cd tools
then type the commands of what you're trying to fastboot
Click to expand...
Click to collapse
Not quite.
Code:
cd c:\android-sdk-windows\tools
That will put you in the ADB directory, assuming you have the android-sdk-windows folder on the root of your C: drive, not inside another folder (mine downloaded inside another folder, I just pulled it out and put it so it fits the above structure). Then pass the commands.
Power user tip: Just type in "cd c:\and" and then hit Tab. It will complete the rest of the folder name, then you can hit "\t" and hit Tab again to complete the next part. Tab is an auto-complete feature. I never type path names anymore.
Hello, I've been trying to bootload my XPlay but I'm having problems with it. I've followed the directions from both mills and ashergray and got the unlock key from them as well (btw, thanks to the both of you for all the help). When I get to Step 10, where you have to run/open fastboot, it closes instantly (the cmd prompt) and I can't finish doing the unlocking of the bootload. I've tried the ubuntu boot and that didn't either. Can someone help or guide me with the problem that I'm having, Thank you for your time and have a great day.
xavy82 said:
Hello, I've been trying to bootload my XPlay but I'm having problems with it. I've followed the directions from both mills and ashergray and got the unlock key from them as well (btw, thanks to the both of you for all the help). When I get to Step 10, where you have to run/open fastboot, it closes instantly (the cmd prompt) and I can't finish doing the unlocking of the bootload. I've tried the ubuntu boot and that didn't either. Can someone help or guide me with the problem that I'm having, Thank you for your time and have a great day.
Click to expand...
Click to collapse
You have to open a windows command promt not the one inside the fastboot folder.
1. Open windows cmd promt.
2. Open fastboot folder and copy the path.
3. Go to your new cmd window and type *cd* and press space once and paste your path and hit enter (type cd is without *)
4. Connect your phone in fastbootmode, when you see a blue light on the power button type this in the cmd window:
fastboot devices (enter)
Then you should get a *list of devices* and under that a number. If there's a number your phone is detected and you can proceed with unlocking. If not you might need to setup some drivers.
5. Unlock your phone if 4 was a yes.
Hopes this helps you
Regards Dousan...
Just a few extra tips on top of dousans excellent advice.
If your using Windows Vista/7, you can hold shift, and right click on an empty space in the same folder as fastboot.exe. Choose open command prompt here. This will open a command prompt straight to the right folder.
Also you can open a command window and just drag and drop fastboot.exe into it.
Thank you guys, I will try this in the morning, I really appreciate the help and if you ever need anything, don't hesitate to ask
AndroHero said:
Just a few extra tips on top of dousans excellent advice.
If your using Windows Vista/7, you can hold shift, and right click on an empty space in the same folder as fastboot.exe. This will open a command prompt straight to the right folder.
Also you can open a command window and just drag and drop fastboot.exe into it.
Click to expand...
Click to collapse
Didn't know about the drag and drop, nice one. Ohh and I'm using the old, before the wall fell, windows xp
Regards Dousan...
Dousan said:
Didn't know about the drag and drop, nice one. Ohh and I'm using the old, before the wall fell, windows xp
Regards Dousan...
Click to expand...
Click to collapse
I don't think you can do it on XP
trying to get my command prompt up in my SDK tools folder so i can root my nexuz when i get it. but when i hold the shift key and right click i dont get the option for open command promp here? could it be blocked since im on my work computer? i also tried going
start>run cmd.
it starts off in H...
then i type
cd C:\android-sdk-windows\platform-tools
and it just goes right back to H? am i doing something wrong?
Are you on Windows 7?
If you are, go to your tools folder and right click anywhere inside the folder while holding the shift key. Select "Open command window here" from the menu.
If you're on XP, try these commands after running "cmd":
C:
cd android-sdk-windows
cd platform-tools
flakz0r said:
Are you on Windows 7?
If you are, go to your tools folder and right click anywhere inside the folder while holding the shift key. Select "Open command window here" from the menu.
If you're on XP, try these commands after running "cmd":
C:
cd android-sdk-windows
cd platform-tools
Click to expand...
Click to collapse
that worked! thanks a bunch! was trying the shift thing and didnt work... running XP so that must be why. and didnt know you had to split the folders up when moving. thanks again!
I have a LTE gnex. I am having problems getting my bootloader unlocked.
If I attempt to use fastboot commands at all I get the error 'fastboot is not recognized as an internal or external command, operable program or batch file.'
If I attempt to use adb devices while I am in fastboot it says "List of devices attached." If I use the adb devices command when my phone is turned on it lists my device like normal.
I feel like I am so close, but yet so far. Any ideas?
EDIT: I'm attempting this on XP, and I am on 4.0.2
I am no expert in these matters, but a few things come to mind:
1) have you got all the proper drivers installed?
2) in the cmd prompt, are you in the directory where fastboot.exe is located?
Have you followed this thread? I'd recommend downloading superboot, extract the contents, go into that folder, and then use: 'fastboot-windows oem unlock'. That should definitely do the trick. Good luck.
EDIT: I don't specifically know all the differences for the GSM/LTE/CDMA versions, but the above should be okay for all versions. To root, and install recovery, on CDMA versions, check out this google+ post.
EDIT2: Also, this thread may be worth looking into.
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
aldouse said:
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
Click to expand...
Click to collapse
^^^^^^This.....beat me to it LOL. This should work for ya just fine. Just make sure tour fast boot file is in the same as tour adb file. Hope ya her it man. It can def get frustrating
Sent from my Galaxy Nexus using Tapatalk
When I shift + right click I don't have any option to open a command window...well this is frustrating.
twiz0r said:
When I shift + right click I don't have any option to open a command window...well this is frustrating.
Click to expand...
Click to collapse
just open command prompt manually and then go to folder. Eg 'start' -> 'run' -> type 'cmd' and hit enter. Then cd c:\path to folder\ etc.
edit: plus, i gave you a few links to other threads. I really recommend to follow the steps described there if you haven't so far...
im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?
I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .
PhazeDelta1 said:
I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .
Click to expand...
Click to collapse
yeap i did that already i open command window and type adb reboot bootloader it gives me that msg
galaxy16 said:
im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?
Click to expand...
Click to collapse
You need to get adb working on your PC. You don't have it installed or you are using it wrong (not in the directory it is in, or it isn't set to PATH as examples).
Side note adb doesn't work in the bootloader.
use gnex toolkit in galaxy nexus android development
Open the CMD and navigate to the folder where ADB.EXE is located and like someone mentioned about adb wont work in bootloader, so instead you'll have to use "fastboot", type "fastboot /?" for help and commands.
also make sure you execute CMD as Administrator.
on the toolkit, adb file's name is different. try "adb-toolkit" instead of "adb"
so: "adb-toolkit reboot bootloader"