Database Users

I got the device into fastboot mode

You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"

epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
need use QPST (http://forum.xda-developers.com/showthread.php?t=2588608&page=5)
but this way not completed until the end of

I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?

epicfailol said:
I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?
Click to expand...
Click to collapse
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.

GSLEON3 said:
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.
Click to expand...
Click to collapse
I used getvar, and it worked fine (but most the of parameters don't), boot and idme don't work because it's locked, and oem unlock doesn't exist. But what your saying is that I shouldn't even be able to do any of this?

i look at the picture and the kindle is not hdx.
i've searching for fastboot cable on ebay but didn't found, the cable only work for kindle HD
so for there is no fix for bricked kindle fire hdx

You can turn HDX into fastboot mode by "adb reboot bootloader" if device is alive.
But you can not flash anything anyway - error "flash not allowed for locked hw".
Fastboot cable perfect fit to HDX too. But it turn device in Qloader for QPST.

epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
Try "fastboot -i 0x1949 yourcommandhere"

ADB doesn't see the phone in fastboot mode (although windows sees it)

Hello,
I'm trying to flash a TWRP, but for some reason the phone doesn't show up any more in adb when in fastboot mode (at the bottom of the phone screen it tells me to connect a USB cable). It was showing fine until yesterday. I have tried several different USB ports. The cable is definitely working (in fact plugging and unplugging it causes Windows to notice and make a sound, and also it works fine in ADB when the phone is booted up.
The only thing that I can think that happened since I had last connected to it in fastboot mode (to unlock the bootloader) is that I connected my PC to a couple other phones (Galaxy S3 and Nexus 5) using them in MTP mode. I have reinstalled Google and universal drivers several times, deleted the device from device manager, etc etc. No good.
Any ideas?

We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode

Simer03 said:
We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode
Click to expand...
Click to collapse
Arghhhh :-|
that was it, I was using adb devices. Thanks! (I feel dumb now)

Bricked Oneplus 2 Not Connecting To PC

- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop

I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable

Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?

foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable

evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week

fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.

evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken

Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc

ADB Disconnects when phone is in bootloader

So I'm trying to install TWRP through ADB, but every time i reboot my phone into bootloader, adb disconnects and my computer does not recognize it. This problem only recently started. I am on the official version of Nougat. Does anyone else have this problem and know a solution? Thanks!

asadabbas95 said:
So I'm trying to install TWRP through ADB, but every time i reboot my phone into bootloader, adb disconnects and my computer does not recognize it. This problem only recently started. I am on the official version of Nougat. Does anyone else have this problem and know a solution? Thanks!
Click to expand...
Click to collapse
ADB is only supposed to work while the phone is loaded into the OS or in sideload mode. In bootloader mode, only fastboot will work.
So the correct command to flash the recovery would be:
Code:
fastboot flash recovery recovery-name.img
Example:
Code:
fastboot flash recovery twrp-3.0.2-1-angler.img

DJBhardwaj said:
ADB is only supposed to work while the phone is loaded into the OS or in sideload mode. In bootloader mode, only fastboot will work.
So the correct command to flash the recovery would be:
Code:
fastboot flash recovery recovery-name.img
Example:
Code:
fastboot flash recovery twrp-3.0.2-1-angler.img
Click to expand...
Click to collapse
sorry my mistake, I meant fastboot. The problem I'm having is that i cannot even enter these commands. It disconnects as soon as it goes into bootloader mode.

asadabbas95 said:
sorry my mistake, I meant fastboot. The problem I'm having is that i cannot even enter these commands. It disconnects as soon as it goes into bootloader mode.
Click to expand...
Click to collapse
Uninstall and then reinstall the drivers by connecting the device. Also, try switching ports.

as weird as it may be, try changing the cable also
I was getting fastboot errors when flashing recovery few days ago, and just by curiosity,I tried with another cable.. it worked with no errors
one more thing.. if you send an adb command to reboot in bootloader, then you have to physically unplug your phone from the computer and plug it back again
only after that, fastboot devices command will show your phone in fastboot mode

ciocu said:
as weird as it may be, try changing the cable also
I was getting fastboot errors when flashing recovery few days ago, and just by curiosity,I tried with another cable.. it worked with no errors
one more thing.. if you send an adb command to reboot in bootloader, then you have to physically unplug your phone from the computer and plug it back again
only after that, fastboot devices command will show your phone in fastboot mode
Click to expand...
Click to collapse
I tried all of this but it still doesn't work. It was working just a few weeks back when i installed nougat, but now it doesn't work. It's so strange. Any other suggestions?

asadabbas95 said:
I tried all of this but it still doesn't work. It was working just a few weeks back when i installed nougat, but now it doesn't work. It's so strange. Any other suggestions?
Click to expand...
Click to collapse
Does charging work fine? And did you try using a different computer? Try charging the phone with that cord that you're using. (even though it's really short, see if it charges steadily)

TnT_ said:
Does charging work fine? And did you try using a different computer? Try charging the phone with that cord that you're using. (even though it's really short, see if it charges steadily)
Click to expand...
Click to collapse
Any other suggestions?

sharmilasingh said:
Any other suggestions?
Click to expand...
Click to collapse
Try updating adb drivers. and make sure you're using data transfer cable, there are many charging cables out there.. those will not read your phone in transfer mode, I've faced this, solved by purchasing new data cable.
Sent from my angler using XDA Labs

ADB cannot detect after reboot to bootloader menu

ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.

Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.

wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.

Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.