Related
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
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
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
My HTC desire 820 keeps restarting itself as it is stuck in an endless boot loop. I have come across threads speaking of the same issue but the solutions don't seem to work on my phone.
My boot loader is locked. When i try to unlock it in fastboot mode, the device doesn't show up on the PC.
I need the boot loader unlocked so that i could push in a custom recovery mode as i cant get into the stock recovery too.
Does anybody have a solution for my kind of problem?
Also, when the phone is in fastboot usb mode, the computer makes a notification sound which indicates it recognizes the phone.
The only thing i can get into is my boot loader and which looks like this now:
***LOCKED***
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-3.17.708.3
eMMC-boot 2048 mb
Apr 12 2016, 11:49:54.0
NOTE: I never tried to install a custom ROM. This problem arose on its own for reasons unknown to me. Moreover, my phone is UNROOTED.
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
themember1993 said:
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
Click to expand...
Click to collapse
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Gibz97 said:
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
themember1993 said:
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
Click to expand...
Click to collapse
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Gibz97 said:
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
themember1993 said:
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
Click to expand...
Click to collapse
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Gibz97 said:
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Click to expand...
Click to collapse
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
themember1993 said:
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
Click to expand...
Click to collapse
Try downloading usb deview from here. Uninstall all the USB drivers, reinstall them then try again
http://downloads.tomsguide.com/USBDeview,0301-13254.html
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
dziedziol said:
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
Click to expand...
Click to collapse
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
uweork said:
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
Click to expand...
Click to collapse
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
dziedziol said:
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
Click to expand...
Click to collapse
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
RuedasLocas said:
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
Click to expand...
Click to collapse
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
You could Check if FWUL from SteadfasterX is helping You out with your Problem.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
With the Installed Salt You cann Backup your Device.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
<waiting for any device> because if windows don't recognizes the device as it should adb will never "see" it.
While on the process, pay attention to the device manager. When you get the message in cmd of <waiting for any device>, uninstall your device and make device manager search for devices.
If still shows you as the same device and adb still waiting, you might have to uninstall the device and install it manually choosing from a list. Now I don't remember how it is suppose to be detected...
During install and uninstall don't disconnect the device from the computer, and remember, use a USB2 port.
I already got that several time. Took me time but that's how I managed to fix it.
okay, guys, it is a shame for me... but I worked out what is wrong with my phone.. maybe not with my phone, but what is wrong with me.
all I needed to do to launch a fastboot was type "adb reboot bootloader" and everything is fine now.
Sorry that you had to give me so much tips and this problem turned to be my stupid mistake, but I'm glad that i won't have to install linux and play with virtual machines to repair my phone
Anyway, thanks for your kindness and will to help, greetings for everyone!
@edit: Turns out that i have one more question. I want to uninstall xposed framework. But there are many versions of uninstaller on their site. Is there any risk that i will "break" my G4 if I use the newest one? I have xposed version 87 and I don't want to do something stupid. thanks in advance.
somebody knows? if I can use the newest version of uninstaller no matter which version of xposed framework im using?