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)
Related
I have adb and fastboot set up on my laptop, I just recently put Ubuntu back on here and just finished setting up my sdk and such a couple hours ago. I know its set up fine because adb works and I am getting fastboot output from my terminal, but its not reading my device. if I just type fastboot, the help will come up, and when i prompt for devices I get nothing, I have tried three different cables. Any ideas? fastboot tends to be unreliable for me in the past more so than adb. I just don't know what I can do now.. I am on the NS4G 4.0.4 leak and I'm trying to flash CWM and root so I really need fastboot
You are in the bootloader right?
Phone Off --> Vol. Up + Power simultaneously --> "fastboot devices"
yeah I am. I did it on my other NS4G on windows just yesterday and had no problem with it but I hate booting into windows unless I have to. Just trying to get it working on ubuntu
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"
- 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
After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
sujan smash said:
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
zgfg said:
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
Click to expand...
Click to collapse
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
sujan smash said:
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
Click to expand...
Click to collapse
Everything looks correctly set but you could still try another PC and USB cable
zgfg said:
Everything looks correctly set but you could still try another PC and USB cable
Click to expand...
Click to collapse
Well i did that too, tried it on my laptop too no luck there also,
As ive mentioned in the first thread ,
It is detecting redmi note 10 in fastboot mode on the same pc with same cable and everything, but not redmi k20, so its not abt PC drivers its something to do with my phone
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
zgfg said:
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
Click to expand...
Click to collapse
Yep it sucks, Thanks Anyways