My phone is running perfectly fine. But after updating my phone last week officially, my PC doesn't recognize the phone in Fastboot. I'm trying to flash a custom recovery and root it, but in CMD, when I type fastboot devices, nothing comes up.
I am in the Fastboot mode when I try to do this. My phone was rooted earlier too with no issues. Also, in the Fastboot mode, The Bootloader version and the baseband version is blank. I tried different ports and a different cable along with a different PC, nothing seems to help.
Any suggestions?
Hi, did you ever get an answer?
I am having this exact same problem as well. Computer isn't recognizing the device as a fastboot device, I can't even run the fastboot boot recovery.img command to get into recovery.
I was able to get it to recognize my phone in fastboot mode by following the directions in this post: https://forum.xda-developers.com/t/...nize-device-but-adb-can.4040635/post-84052027
Though I never was able to root or install TWRP, this did allow my computer to recognize the phone in fastboot mode.
Related
Managed to flash TrickDroid and now I need to flash the boot.img, but there are two obstacles. The first being that 'adb devices' returns with nothing and fastboot just keeps showing '< waiting for device >'. I was thinking either flash it on my device rather than on the computer or some way that enables my phone to be recgonised.
thecyancow said:
Managed to flash TrickDroid and now I need to flash the boot.img, but there are two obstacles. The first being that 'adb devices' returns with nothing and fastboot just keeps showing '< waiting for device >'. I was thinking either flash it on my device rather than on the computer or some way that enables my phone to be recgonised.
Click to expand...
Click to collapse
Have you rebooted your device into bootloader (ie the white screen) and selected fastboot? When your in the bootloader adb shouldnt work but fastboot should. And you can run a fastboot devices to be sure as well.
Check if u have the appropriate drivers installed
Yeah, it was in bootloader and tried recovery aswell and had the right drivers. Formatted the sdcard from the pc and managed to get it working again.
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
joeyism said:
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
Click to expand...
Click to collapse
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Renosh said:
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yea I was trying to flash it, but I read from http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that another trick is to do
Code:
fastboot boot <path/name of the recovery twrp img>
So I thought I'd try it. But now my computer can't even detect my phone :/ Would there be a reason why my phone no longer communicates with my computer?
Hey folks,
i have a problem with my shieldtablet. The fastboot doesn't work properly. I cannot load anything via "fastboot flash blablabla.img". Minimal ADB and Fastboot just shows "waiting for device" and if i check the devices via "fastboot devices" is just shows nothing but the normal command prompt.
Then i did a mistake and flashed the twrp 3 version with an older one, so i am unable to enter the recovery-mode. If i chose Recovery Mode via bootloader (or if i restart the tablet into recovery mode) it has a short bootloop and then after some trials it starts normal into Blisspop.
How could i flash this without the fastboot? Is there any trick i could use?
The tablet is unlocked. I had several custom-roms installed. Currently Blisspop 6.4 without playstore.
That looks like your PC is not seeing your tablet. Boot into fastboot mode, connect it to your PC and look in Windows device manager for the device.
Thanks a lot! ADB worked fine on Win10. Last time I flashed the recovery was on my old Win7-System. It seems, that the Upgrade deleted just the fastboot drivers.
One last question: is it normal, that if i chose the fastboot protocoll entry on the bootloader, that it restarts the bootloader?
Yes, that's normal. The menu entry is redundant because when you see it you are in fastboot mode already.
Hey,
so, three days ago my Mi4i suddenly turned itself off during the night.
I couldn´t turn it back on, it was stuck on the Cyanogenmod-Logo and wouldn`t go any further.
I couldn´t even enter recovery mode. The only thing I could do was enter Fastboot.
And now Im stuck there.
Tried recovery via Mi PC Suite- it recognised the phone, started recovery, said "finished", but the phone is still in Fastboot.
Same for Mi Flash tool.
Doesn´t matter which ROM i try to flash, I´m still in Fastboot.
Any ideas what I can still try? Or is the phone completely bricked and I need a new one?
Try rebooting by connecting the phone with USB and in CMD running fastboot reboot.
May I know why MIUI did u try flashing on your phone?
If it was Developer ROM. I suggest you to try Global Stable ROMs, This usually fixes everything.
Good luck mate!
Regards,
Sharan
Unfortunately, I did try all that.
Do fastboot commands work? Does your device show up in
fastboot devices?
If yes, Try booting into a recovery using fastboot boot recovery.img
If commands don't work even after you've drivers properly installed(i.e. your PC's fastboot works for other phones), Then I have no idea.
Hello, today I finally received my one plus 6. Been loving the device so far
I was on my way to Chuck a custom recovery and rom unlocked the bootloader no drama
I then hit a Plato of fastboot coming up with no command error as in fastboot isn't working in cmd I have researched heaps about it and I can not find a single thing. I tried to reinstall drivers and all that, and yes I'm running cmd in the fastboot files, only adb seems to be working but I can no longer use fastboot on my PC.
Has anyone come across this error, it seems to be that after installing the one plus drivers it stopped working correctly and fastboot commands no longer register in fastboot...
My phone is detected in fastboot mode so it's not the drivers. What could be causing this, is it the computer at fault?