Related
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.
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
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )
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
I have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help
I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.
http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help
When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.
ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.
djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^
It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.
The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working
Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom