Hi guys,
I've got a real head-scratcher over here. I followed every guide to a T, but I can't get my computer to detect my device in fastboot.
I installed the Xperia companion. I tried to manually install the Google USB drivers, and the sony OEM drivers. Still, no matter what, when I enter, what is supposedly fastboot, it never shows up. When the phone is on ADB devices shows it just fine. I am at a total loss!
To enter fastboot, I am shutting down the phone, pressing the volume up button, and plugging it in, then I get a black screen and a blue LED, which supposedly is correct? I've personally never seen anything like this before. Device manager does detect it as an unknown Android device, however, if I try to apply any drivers to it Windows simply informs me I already have the latest ones installed.
Thanks
SOLUTION: It was a driver issue after all. Windows 10 would not detect any drivers, nor let me install any drivers manually from files, however, it did let me select built-in drivers from my computer. YMMV, but If you are running into this issue try this:
1) Put your phone into bootloader mode.
2) Open device manager.
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4) Click the "Browse my computer" option.
5) Click "Let me pick."
Note: There are several categories here, I suggest you try them all: portable devices, android devices, and in my case, Samsung devices. In one of the categories, you will find Google listed as a manufacturer.
6) In one of the categories, you will find Google listed as a manufacturer (in my case it was under the "Samsung Devices" category).
7) Select Google and then select the newest fastboot driver listed (in my case it was dated 2016), and install that driver.
8) Go back to PowerShell and run "fastboot devices." With a little luck, it will work!
Previous steps:
Edit: I had the thought of trying
Code:
adb reboot fastboot
and that got me into fastbootd, and then my PC detected it, however, the phone did not accept the unlock command.
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I rebooted into the bootloader from here, got the same black screen, blue LED as above, and my phone is still not detected by fastboot.
Make sure you open cmd window in fastboot folder...i hope this is help
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
mehdi_s82 said:
Sony fastboot mode is different I think. It was odd to me but doesn't show anything on screen when I went to fastboot to flash US firmware
Click to expand...
Click to collapse
I live in Boston and got the the XQ-AT51 (despite the fact that B&H was originally selling the 52... so in a few months I'm going to have to flip this phone ), do I have to reflash a stock firmware before I can unlock the bootloader? I do have it from XperiFirm.
Edit: This was dumb of me as you can't flash anything onto the phone unless the bootloader is already unlocked.
Edit: I don't want to double post, but I managed to solve the problem, and added the solution to the OP.
THANK YOU VERY MUCH FOR THIS GUIDE. I was struggling for hours on end with the "Unable to open fastboot HAL" error message, but followed the steps outlined in your guide a little differently than you, since I'm on windows 7. I believe that the root cause of my issue was that I actually used the down volume button instead of the volume up, believing that it was weird for the screen to show nothing except for the blue notification LED.
Here is what I did just in case for people who might encounter the same issue in the future. Be warned though that I'm not an english native so the options won't be accurately translated but I'll try to do my best nonetheless.
1) Put your phone into bootloader mode (volume UP + power button, not down.) Don't be afraid if nothing shows up, it's actually normal
2) Open device manager
3) Right-click the device called "Android" with the yellow question mark, and select "update driver."
4)ISelect "Look for drivers on my computer (manual install option)
5)Select "Choose from a list of drivers installed on this computer"
6)Scroll down through the manufacturers and such until you find "sony sa0200"
7)Install it
Normally everything should be working fine with fastboot. What a relief
I have a similar problem, but my device manager does not show any android device from the bootloader. I've tried multiple cables and everything works fine in adb mode.
EDIT: Nevermind. It ended up being multiple bad cables. They all worked in ADB/booted but not in Fastboot/bootloader. Tried one more it it worked completely
I have same issue with my Poco X3 Pro, the device working fine and is recognized as ADB composite when i'm under MIUI, but when i launch the device in fastboot mode, the ADB composite disappear and a generic "android" device appear and i'm not able to install any drivers, no qualcomm, no xiami, no generic google usb, nothing.
Following the tips above, nothing work. I'm under windows 7.
Any tips?
Thx everyone for pointing me to the right direction. Flashing latest twrp was the final step. Recovery is back to now .
Related
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Jordan Miles said:
After installing the "15 seconds adb installer", I shift clicked the folder with my twrp file, "twrp-3.0.2-0-tbltetmo.img" to open the command prompt and type in "adb reboot bootloader" , causing my screen to go into boot loader mode. [ e.g. image ] ]So far, everything is going well, according to this guide.. However, the problem is the next step. Once in boot loader mode, i type in "fastboot flash recovery twrp-3.0.2-0-tbltetmo.img" . Instead of masses of text appearing, I instead receive the message: "Waiting for device." To be honest, I think my problem lies in the fact that before i went into boot loader mode, my phone was detected by my pc, but after it shifts to boot loader mode, it stops being detected, this causing the "waiting for device" message. However, even though I know the cause, I can't find any means to fix it after searching for hours. Also, yes, I enabled allow unknown sources and usb debugging. I've also went to T-Mobile's website to install their usb driver.
Click to expand...
Click to collapse
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
SiNJiN76 said:
Possibly the cable. Not sure if the USB drivers you got from T-Mobile's website are the same as the one that TEKHD posted in his Tutorial thread for rooting...but I use those and with my original cable. (sometimes with my Xbox One charge cable) Hope that helps.
I know that if I use a a cheap or thin cable, I get problems.
Click to expand...
Click to collapse
Thanks for your reply. I gave up using the usb cable method to connect to adb. Instead, I just flashed it with Odin, which works (strangely, even though my device still didn't appear under "Computer")
So I have literally tried every single method I have come across and I have seen a few people having the same issue i have.. adb devices see's my phone adb reboot bootloader works and puts me into fastboot mode, how ever thats where everything stops working.. this is a fresh install of windows, fresh driver installs and everything is up to date adb/fastboot wise..
as soon as i type fastboot oem unlock it says waiting for any device and stops never finding the phone..
any help solving this issue would be great.. and the one click method wont work on my phone either
I was dying on this last night but finally figured it out. ADB worked fine, but Fastboot said "waiting for device". I would suggest downloading USBDview if you don't already have it.
Boot your phone into Fastboot and connect to computer.
Check USBDeview for driver that doesn't have a green light next to it.
Open Device Manager and find that device
Right click and update driver and Let me Pick from list
Look for Fastboot and install it
Two seconds later, your bootloader will be unlocked.
brg7562 said:
I was dying on this last night but finally figured it out. ADB worked fine, but Fastboot said "waiting for device". I would suggest downloading USBDview if you don't already have it.
Boot your phone into Fastboot and connect to computer.
Check USBDeview for driver that doesn't have a green light next to it.
Open Device Manager and find that device
Right click and update driver and Let me Pick from list
Look for Fastboot and install it
Two seconds later, your bootloader will be unlocked.
Click to expand...
Click to collapse
When you say "Look for Fastboot" where is this driver that I can choose?
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.
OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.
hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards