Develop Bugs

Trying to unlock the bootloader

I get through all the steps, adb setup recognizes my device is connected. When i try to unlock the bootloader <fastboot oem unlock> command line locks up at <waiting for device>.
can someone advise?
Verizon if that matters

What happens when you type in "fastboot devices"

Nothing happens. Tried it both before and after typing in adb reboot bootloader

You sure your pc is detecting the phone when it is in fastboot mode? To me it seems like your computer isn't detecting the phone or the drivers didn't get installed properly.

<deleted>
answered my own question

I had the same issue. Assuming you're using Windows, you need to find where the latest Samsung drivers for the GN were copied to when you installed them (you have installed them, right?) The next time you plug in your phone, it will probably ask you to setup a new device. Tell it you will install the drivers from a location you choose, navigate to the folder where the drivers are, let it install them, restart if it asks, and then try the process over.
FWIW, I used the directions and links from this tutorial and eventually got it working. They include alternate drivers here in case the one from samsung.com doesn't work.

im having the SAME PROBLEM AND HAVE TRIED TWO DIFFERENT COMPUTERS.TRING ADB METHOD

What's the ADB method? Why don't you just just hold the volume up, volume down and power to get into fastboot mode? When you plug it in, windows should see a new device that needs drivers. You need to make sure the drivers are installed before fastboot will work.

i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device

robitron929 said:
i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device
Click to expand...
Click to collapse
Is it saying that it couldn't install the drivers for Android 1.0 or something like that? What step are you at? Which tutorial are you using?
Read the driver installation part of this tutorial.
http://forum.xda-developers.com/showthread.php?t=1392310

i got it. it was this
TO GET DRIVER WORKING IN BOOTLOADER YOU MIGHT HAVE TO DO THIS, THIS TOOK ME FOREVER TO FIND!!!!!!!!!!!
I TAKE NO CREDIT!
READ CAREFULLY
THANKS TO KELLEX FROM DROIDLIFE
Tips:
-We know that many of you are running into a “waiting for device” issue when apply the fastboot oem unlock command. This is a driver issue and one that a reader has a suggestion for:
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

Trouble with Fastboot

I just can't seem to get fastboot to see the phone...
I have a Z00AD2 with 2.19.40.22 software. USB Debugging is turned on. ADB sees the phone, both from my Ubuntu host system, and from a Windows 8.1 virtual machine. When I use "fastboot device" I just get "<waiting for device>" and when I run scripts/batch files (such as the one-click root) it hangs as well.
I'm assuming there's something very simple, and probably obvious, that I'm missing - but after 8hrs of messing with it yesterday, I'm a little fried.
Appreciate any thoughts!

This morning I installed a new Windows8.1 VM, installed the Intel drivers and adb/fastboot from the sticky page in the general forum. During adb/fastboot install, should I use the drivers provided if I've already installed the Intel version? I think I've tried both ways at this point... Plug the phone in, and it is recognized in adb. Fastboot displays "waiting for device".
I tried the one-click root batch file, and when running CheckBeforeAction.bat my phone restarts into fastboot mode, with the android opened-up on its back, and the batch file continues to "make sure 'asus android bootloader interface' installed on your computer successfully" (I'm not sure it is? I don't see any reference to it anywhere...).
If I proceed further I get the "if you see '123456789 ... fastboot' then you are ready to root" message - where is that supposed to display? On the phone's screen? Finally I hit a key and the batch file says it's rebooting my phone, and it gets stuck on <waiting for device>
Again, I'm sure I'm missing something simple; but I just can't figure what step(s) I'm missing.

Solved the problem, at least in terms of running fastboot on my virtual machine... I had only set up one device filter in VirtualBox, for the phone when it was in it's normal state. When in fastboot mode it uses a different driver, and thus needed a second device filter set up - once I did that, everything went smoothly as far as adb and fastboot functionality go. Having trouble now with flashing twrp...

Windows 10 ADB, Fastboot and USB Drivers

Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?

diji1 said:
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
Click to expand...
Click to collapse
Do a search on how to install unsigned drivers on windows 10, that should fix your problem

Cheers that fixed it although using BCEDIT didn't I had to use the restart method.

diji1 said:
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
Click to expand...
Click to collapse
Cool
Now don't forget to backup your TA partition before unlocking your bootloader...
Happy rooting

Cannot install USB drivers for Razer phone on Win10

Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!

Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL

Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)