Pixel 6: Trying to unlock bootloader and flash factory images. ADB works, but in Fastboot mode the phone is NOT recognized.
Enabled USB debugging. Installed the Latest SDK ADP platform from Google's website.
Adb devices and ADB reboot bootloader works. The phone reboots fine into bootloader.
As soon as the phone goes into bootloader mode -- Fastboot does NOT show any devices.
Fastboot devices -- No results
Fastboot flashing unlock -- " Waiting for Device"
Tried - different USB cables. Different USB Port. Different PCs as well. But fastboot is not working.
It's driving me crazy. Already spend half a day on this. Any help will be MUCH appreciated. Thanks!
This worked. Installed drivers for Pixel 6: https://en.usb-driver.net/google-pixel-6/
Rebooted and fastboot worked. Thanks everyone.
Thanks for the lead. I couldn't solve my problem with those files at that link. But did with this: https://adb.clockworkmod.com/
I'm on Windows 11 Pro x64. ADB commands working. But when I reboot to fastboot and type the command "fastboot flashing unlock" it shows "waiting for device" and then get all commands listed. Don't know how to solve?
refedit said:
I'm on Windows 11 Pro x64. ADB commands working. But when I reboot to fastboot and type the command "fastboot flashing unlock" it shows "waiting for device" and then get all commands listed. Don't know how to solve?
Click to expand...
Click to collapse
Do you have the latest drivers installed? https://developer.android.com/studio/run/win-usb
I'm on Linux Mint with latest platform tools and no problems here. Unlocked the bootloader right away
Edmontonchef said:
I'm on Linux Mint with latest platform tools and no problems here. Unlocked the bootloader right away
Click to expand...
Click to collapse
Maybe I have to do it on Linux also
refedit said:
I'm on Windows 11 Pro x64. ADB commands working. But when I reboot to fastboot and type the command "fastboot flashing unlock" it shows "waiting for device" and then get all commands listed. Don't know how to solve?
Click to expand...
Click to collapse
You need to install the Google drivers as well, this site has it linked and many other sites do too.
Whilst I had my Pixel 6 I tried to uninstall some system apps using ADB but never managed to get the list using these commands,
adb devices,
adb shell
su
Then these commands.
adb shell pm list packages -s
or
adb shell pm list packages
Error message " not found" or "not accessible"
I'm coming from an Android 9 setup. Is the command different in A12?
Well. Unlocking worked. Had to uninstall and install drivers couple times.
Dmverity didn't work. Last resource, had to use Linux. Worked straight forward
iamjimmy said:
Pixel 6: Trying to unlock bootloader and flash factory images. ADB works, but in Fastboot mode the phone is NOT recognized.
Enabled USB debugging. Installed the Latest SDK ADP platform from Google's website.
Adb devices and ADB reboot bootloader works. The phone reboots fine into bootloader.
As soon as the phone goes into bootloader mode -- Fastboot does NOT show any devices.
Fastboot devices -- No results
Fastboot flashing unlock -- " Waiting for Device"
Tried - different USB cables. Different USB Port. Different PCs as well. But fastboot is not working.
It's driving me crazy. Already spend half a day on this. Any help will be MUCH appreciated. Thanks!
Click to expand...
Click to collapse
Try Google pixel 6 drivers from Google that's what I did
Aulgreg38 said:
Try Google pixel 6 drivers from Google that's what I did
Click to expand...
Click to collapse
That is exactly what worked for me as well. Thanks.
T
iamjimmy said:
That is exactly what worked for me as well. Thanks.
Click to expand...
Click to collapse
That's great
adb and drivers seem to work fine for me while the device is on. Once I run adb reboot recovery, I get nothing. No notice it's reconnected, no devices with adb devices
kevp75 said:
adb and drivers seem to work fine for me while the device is on. Once I run adb reboot recovery, I get nothing. No notice it's reconnected, no devices with adb devices
Click to expand...
Click to collapse
Yes, I've tried different devices, different USB cables, uninstalled reinstalled the drivers multiple times. Unfortunately, I do not have a linux box handy to test on
interesting. adb reboot sideload worked
I got this same issue. I'm unable to get anything either. I have installed the drivers multiple times from multiple places and still nothing. I'm lost on this one big time.
Mod edit - translated by https://translate.google.com/?hl=de:
I changed the network cable and it's back to normal
**************************
我换了网线又恢复正常了
xxxxgrizz said:
Mod edit - translated by https://translate.google.com/?hl=de:
I changed the network cable and it's back to normal
**************************
我换了网线又恢复正常了
Click to expand...
Click to collapse
@xxxxgrizz
As courtesy, I've translated your above posts. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Chinese posts. Thanks for your cooperation!
Spoiler: Rule No. 4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Regards
Oswald Boelcke
Senior Moderator
Related
Hi,
I'm trying to unlock my Huawei Ascend Y300 but I'm stuck in fastboot.
I followed this guide: (not allowed to post outside links but you can find the guide by looking for "Free Huawei bootloader unlock tutorial"), but got my unlock code sent from Huawei by mail since the dc-unlocker tool didn't work as well (probably the same problem as with fastboot).
When the phone is turned on I can see it with "adb devices" but once I'm in fastboot mode (pink screen) no device can be found with "fastboot devices".
When the phone is in fastboot mode and being plugged into the computer it is recognized by Windows.
I tried two kinds of Huawei Drivers: "Huawei_U8680_U8730_U8800_U8860" and "Huawei_Android_driver" (for the last one: see the guide stated above). I also tried three different computers.
I'm using Windows 7 64bit if that helps.
Edit:
Same problem in Ubuntu, found in "adb devices" but not in fastboot mode.
Any idea anyone?
Thanks,
Patrick
Anybody?
SirBelial said:
Anybody?
Click to expand...
Click to collapse
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Maurice5813 said:
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Click to expand...
Click to collapse
SirBelial said:
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Click to expand...
Click to collapse
does you phone have a bootloader?
Maurice5813 said:
does you phone have a bootloader?
Click to expand...
Click to collapse
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
SirBelial said:
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
Click to expand...
Click to collapse
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Maurice5813 said:
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Click to expand...
Click to collapse
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
SirBelial said:
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
Click to expand...
Click to collapse
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Maurice5813 said:
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Click to expand...
Click to collapse
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Enable USB Debugging
SirBelial said:
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Click to expand...
Click to collapse
I encountered this but then started the phone and enabled USB debugging and it then found the phone.
did u get this going? im having exactly the same issue. cannot get the phone detected in fastboot, either in Linux or windows
I had the same issue. Took my hours, different Systems, Cables... Try the following:
Code:
adb reboot-bootloader
.
Hope this helps! Your phone should stay at the Huawei Logo (no pink screen!)
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
Q&A for [DEV] Bootloader unlock procedure and software
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV] Bootloader unlock procedure and software. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No unlock partition on KFSOWI
I tried to flash the unlock image on my KFSOWI.
This is the result:
target reported max download size of 1005584384 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.006s]
writing 'unlock'...
FAILED (remote: partition does not exist)
finished. total time: 0.011s
I know this is the HDX forum - but perhaps you can help me out nevertheless
About Windows
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
pablo1036 said:
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
Click to expand...
Click to collapse
Yes
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
murso74 said:
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
Click to expand...
Click to collapse
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
i actually did get it working... removed the device from the manager, unplugged and plugged it back it (showed up as fastboot device with the exclamation point) manually added the driver, using existing windows drivers, and used the adb driver for the fastboot driver.
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
I successfully unlocked my bootloader from Win 8.1 x64 using the method outlined here but not without some challenges. Like others I could not get my device to communicate at the fastboot prompt. Adb worked fine. Assuming it was driver related I deleted everything (included hidden devices), rebooted both devices multiple times and tried various adb/fastboot driver combinations and connection sequences. Nothing. My device knew when the USB cable was connected as evidenced by the 'ready' prompt but was otherwise unresponsive. Even tried a fastboot cable which of course didn't work. Then I tried rebooting into TWRP using power+volume-up+volume-down (three button salute) and from there rebooted the bootloader. Bingo! Everything has worked since. I restarted from TWRP many times as well via adb reboot. Hard to believe the three button salute did the trick but have no other explanation at this time. Maybe Murphy got distracted. Maybe I just got lucky.
murso74 said:
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
Click to expand...
Click to collapse
As you probably discovered deleting the entry under "Android Devices" (can retain the driver) and then replugging your fully booted device restores the MTP driver and associated explorer mapping.
Hopefully this post will help others.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
Gonna try this. got ubuntu on a usb. now got to find the linux commands.
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
holeshot77 said:
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
Click to expand...
Click to collapse
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
jeryll said:
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
Click to expand...
Click to collapse
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
holeshot77 said:
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
Click to expand...
Click to collapse
Yes, go for it! I suppose you have all prerequisites done and you have your signed unlock img ready, then all you need is working fastboot... :good: :highfive:
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
davekaz said:
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
Click to expand...
Click to collapse
If you are doing this in windows try open cmd, make sure you have working fastboot, then type
Code:
fastboot -i 0x1949 flash unlock
open explorer, find location of your xxxxxxxxxxx.unlock file and drag and drop it to cmd, then it should look like this
Code:
fastboot -i 0x1949 flash unlock path_to_your_xxxxxxxxxxx.unlock
then press enter and it should unlock (if the error is based on non defined path to your xxxxxxxxxxx.unlock file)
Working now I must of not spaced it correctly... I tried it again and unlocked ..green is beautiful
Sent from my Kindle Fire HDX using Tapatalk
syntax error
hey guys, i got a stupid syntax error... im doing everything exactly as it says in this thread http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
any way this is what i get:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\FBI>C:\Python27\python.exe
Python 2.7.9 (default, Dec 10 2014, 12:24:55) [MSC v.1500 32 bit (Intel)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>> cuberhdx.py 0x*********
File "<stdin>", line 1
cuberhdx.py 0x*********
^
SyntaxError: invalid syntax
>>>
Click to expand...
Click to collapse
iv tried uppercase, lowercase, moving periods around, and various other things, but still no cigar. any help is appreciated
I think the syntax error is that the script is looking for your devices codes. Try the easy scripts from the regular dev section if you are on Windows. They are much simpler.
Sent from my KFTHWI using Tapatalk
It seems the driver is not installed properly.
How can I update the driver so that windows can recognize the phone on fastboot mode?
I have tried drivers from following 2 links,
https://mega.nz/#!XqAR3QbQ!BMg_NMelPhJPXRTA8y96yGJVnCg4IUgHDVzQmco83cI
and
https://androidfilehost.com/?fid=962187416754460440
I have also tried all 3 options
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
But none of these worked.
Can anyone tell me how do you make it work?
thanks!
llaalways said:
It seems the driver is not installed properly.
How can I update the driver so that windows can recognize the phone on fastboot mode?
I have tried drivers from following 2 links,
https://mega.nz/#!XqAR3QbQ!BMg_NMelPhJPXRTA8y96yGJVnCg4IUgHDVzQmco83cI
and
https://androidfilehost.com/?fid=962187416754460440
I have also tried all 3 options
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
But none of these worked.
Can anyone tell me how do you make it work?
thanks!
Click to expand...
Click to collapse
Have you tried it with Windows 7?
I have tried boot windows 7 and 10.
llaalways said:
I have tried boot windows 7 and 10.
Click to expand...
Click to collapse
I was having this same trouble. I posted an answer on a different thread yesterday.
Was just that I needed to update my adb and fastboot exe files.
https://forum.xda-developers.com/showpost.php?p=79640181&postcount=196
mrmazak said:
I was having this same trouble. I posted an answer on a different thread yesterday.
Was just that I needed to update my adb and fastboot exe files.
https://forum.xda-developers.com/showpost.php?p=79640181&postcount=196
Click to expand...
Click to collapse
I think where a lot of people get hung up is they type "adb devices" after going into bootloader. They should be typing "fastboot devices".
my problem solved by laptop with unbuntu
you are right. update adb and fastboot worked.
mrmazak said:
I was having this same trouble. I posted an answer on a different thread yesterday.
Was just that I needed to update my adb and fastboot exe files.
https://forum.xda-developers.com/showpost.php?p=79640181&postcount=196
Click to expand...
Click to collapse
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!