Hello-
I am trying to use the motorola bootloader unlock app (motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b[/url]). I am stuck on the following directions:
TO GET YOUR DEVICE ID
Put your device in fastboot mode.
On your computer, open a command prompt or Terminal session.
Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
Admittedly, I do not know how to use SDK tools. When I use a command prompt and navigate to the tools folder and enter the command string I get an error. If someone could guide me in the right direction to what I am doing wrong it would be greatly appreciated.
PS- I did a search and found nothing but the petition threads. And if this is in the wrong forum please move or delete.
Thanks Jason
Me tooo don't know it
Related
Hey guys! I'm a noob, I aknowledge it and I apologize for it.
I've been trying to open the bootloader on my brand new Ray by following the official Sony Ericsson guide found on their website. The problem is that I'm stuck with this step:
# Open a command window and go to the tools folder within the Android SDK folder.
# Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your phone is connected properly.
The only answer that I get from command promt is: 'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.
This leads me to thinking that there's not fastboot in the SDK-folder. Why is this? I've followed the guide to the letter, and I've checked several times that I actually did follow it to the letter. Any help guys? Please?
Found the solution after hours and hours of fighting, still not through with all the problems though.
Try flashtool, inside x10 flasher folder you will find the required fastboot and adb.exe and dll for them. Try from there.
http://forum.xda-developers.com/showthread.php?t=1034087
Try this to unlock boot loader I uses it found Easier than se site
It.sounds like a driver problem I had the same issue the link above has the.drivers needed.to sort it out
sent from my gorgeus Xperia Ray
Like many of you, my S6000F was easily rooted; but, isn't cooperating with my attempts to unlock it.
I have been following the directions posted at Lenovo Ideatab S6000 Unlock Bootloader Tutorial (not allowed to post a link on xda); but, have hit a brick wall when trying to execute the command line: fastboot-windows oem unlock
I get one of two error messages:
1) If I am at the command line, and the tablet is in normal Android, it will say: Waiting on device
2) If I have the tablet in fastboot mode, it will say: fastboot is not recognized as an external or internal command
I have ensured that
ADT was fully installed and configured
the correct adb windows and adb drivers were installed (I have tried the Google drivers provided with the guide I lined to above; and, also tried the Universal Naked Drivers)
adb can 'see' the tablet, as can Windows (in device manager with the tablet in normal and fastboot modes)
I use an administrative command prompt window
adb, fastboot and sdk are all in the same folder; and, that I open an administrative command prompt in that same folder
I have honestly spent hours trying to find relevent info via Google and Bing; and, then researching in the forums that show up in the searches. All the steps that I bulleted above are the results of what I have found, piecemeal; but, I havn't been able to find one, complete lucid guide to this issue. Any solid direction would be greatly appreciated.
Thanks, in advance!
PJ Arts
Edit 2: [SOLVED] Just needed to run it as sudo (duh). Discovered solution @ Stack Overflow article titled: "Android fastboot waiting for device".
Probably an easy fix. Haven't flashed a ROM in a while and forgot some stuff.
Problem: Accidentally deleted Google Now launcher. OS wouldn't load properly.
Action: Was able to get into settings, so I DL'ed the latest nightly build for CM13. Got it on the device successfully. Wiped the delvik, cache, system and all that, but when I tried to flash the build, I get an error:
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
Sprint CDMA variant detected!
Reboot into Bootloader Mode, connect your device to PC and from PC terminal type:
fastboot oem config fsg-id boost
and then flash the CM mod again
Click to expand...
Click to collapse
Next Action: I recently re-installed Linux Mint, so I had to re-install the ADB and Fastboot. I did so per the instructions on LifeHacker for Linux (can't link to it BC I'm a new user still on XDA).
Current Issue: I can't figure out how to open a terminal for my device. If I installed ADB and Fastboot correctly I should just be able to right-click and select 'Open Terminal here' like I did before, but for some reason (probably some terminal command I'm forgetting) my PC isn't allowing me terminal access to the device still/yet.
Other Information:
My PC does recognize my device as a USB storage device.
My old ROM did have ADB Debugging.
I still have access to Fastboot and TWRP (not bricked, thankfully).
CM13 ROM file is still in the device. So, I'm very close, but still a step away from fixing this.
I think I'm missing something simple, but I haven't done this in a while.
Thank you for your help in advance! :good::good::good:
Edit
Forgot to mention: When I connect the device and put it into Fastboot and then type in the command "fastboot oem config fsg-id boost" in my terminal, I get: <Waiting for device>. So, something is missing.
EDIT: nvm, didn't see your edit. I use linux and didn't have to install anything besides Minimal ADB & Fastboot.
Solved. :victory::good:
Just needed to run command ("fastboot oem config fsg-id boost") as sudo. Duh. :silly:
Found solution @ Stack Overflow articled titled "Android fastboot waiting for device".
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Krejdlis said:
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Click to expand...
Click to collapse
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Augustoandro said:
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Click to expand...
Click to collapse
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Krejdlis said:
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Click to expand...
Click to collapse
Have you installed adb? If yes, then proceed further.
You are in the wrong folder. The correct path should be C:\adb
Then Shift+right click
Select "Open command window here"
Hello,
C:\platform-tools-latest-windows\platform-tools>adb reboot bootloader
phone rebooting
C:\platform-tools-latest-windows\platform-tools>fastboot devices
after this command it shows nothing
can you please make a steps for ADB drivers instalation, i dont know if i made it properly.
Thanks
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
SomeoneAnonymous said:
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
Click to expand...
Click to collapse
Hi, still in progress, i trying everything but still without succes. Someone know how to easily downgrade to 5.1.1 with this phone?
Now it give me this : <waiting for any device>
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!