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

R800i Issues with USB Driver and Bootloader!

Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283

If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.

Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.

PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!

Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.

jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!

I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.

jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:

Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (

You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).

Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!

Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.

i tryed this and its not wanting to work (

Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.

i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul

I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.

thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (

This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.

Thanks for the support guys i managed to solve the issue!

^^^^ Glad i could help
Sent from my GT-I9300

[Q] Rooting Problem

I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
I got search in the thread and come across
ckpv5 said:
"waiting for device" usually means the usb bootloader driver is not installed.
Connect your device in fastboot mode. Open your device manager, manually update driver for that "android 1.0".
Attached here both driver for 32bit & 64bit. Use the one that suit to your PC.
Click to expand...
Click to collapse
I download the driver and follow instructions here
ckpv5 said:
I'm also on Windows 7 64bit.
What you need to try is, hopefully what I remember is correct ...
be on fastboot usb
open device manager, on the "android 1.0" :
update driver software
browse my computer for driver software
let me pick from a list of device drivers on my computer
android usb device
next
have disk
browse to the driver you downloaded (browse up to *.inf)
it will detect as my htc
next
ignore any error
the usb bootloader driver will be installed
EDIT : Tested.. the above step is correct.
Click to expand...
Click to collapse
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.

when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers

intrepid9 said:
I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.
Click to expand...
Click to collapse
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/

jaredl45600 said:
when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers
Click to expand...
Click to collapse
I do see fastboot usb
ckpv5 said:
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/
Click to expand...
Click to collapse
Thanks. It works!

OP3 stucks on "Waiting for Device"

Hi,
I try to flash my OP3.
I did first the UNLOCK, that worked with the CMD (Running Windows 10).
My device is Unlocked.
But when I wanna try fastboot flash recovery recovery.img
Or I type then it says waiting for device...
and when i typ: fastboot devices
then if gives nothing.
Yes, I did the OEM unlock in developers options en USB debugging is on.
HELP!

HELP!

Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.

peterk-1 said:
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
Click to expand...
Click to collapse
Yes, I did that.
But not working...
Over WiFi it's working, but not with USB.

Oke, ADB is working, but only when the device in ON.
When I does the device in Fastboot.
Than it doesn't work!

HELP!

Oke, I fix it.
Did it in an VM with Windows 7.
Bye.

YourTheBest said:
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
Click to expand...
Click to collapse
I'm also stuck with this, could briefly tell me how you set up a VM with window's 7 please? I tried with Ubuntu but no luck installing the adb and fastboot? Stuck with no recovery so please help

First Tick OEM unlock and enable usb debugging. And install latest driver

Ajshal said:
First Tick OEM unlock and enable usb debugging. And install latest driver
Click to expand...
Click to collapse
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing

How did you install the driver? do you have windows 8 or above?

daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
I have same pblm on my LG K10 dude

therightperson_630 said:
How did you install the driver? do you have windows 8 or above?
Click to expand...
Click to collapse
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10

daviss101 said:
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
Click to expand...
Click to collapse
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3

therightperson_630 said:
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
Click to expand...
Click to collapse
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck

daviss101 said:
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
Click to expand...
Click to collapse
go to device manager and manually uninstall kedacom driver and install minimal adb/fastboot from the link I posted, they'll install the driver automatically

daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.

YourTheBest said:
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
Click to expand...
Click to collapse
How do I get a free version of windows 7 without downloading a cracked ISO?