Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...
Related
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either
stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks
Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works
I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app
I messed up my phone a while ago by trying to update to 4.4 while being S-off. Due to several things I ended up with a phone that stays in a bootloop. I can still get to the Fastboot Menu, but even when I try to go into Recovery the phone boots and for a fraction of a second I can see the Clockworkmod Logo before the devices reboots again (so I assume I messed up Clockworkmod as well).
So I tried to sideload Clockworkmod via USB but ADB doesn't seem to recognize the phone in Windows 8. I installed the official HTC package, but the device doesn't show up when I use 'adb devices', so I can't sideload anything (phone was connected to a USB 2.0 port on the rear panel). I tried the same thing on my MacBook Retina with Windows 7 on Bootcamp, same problem. I read there might be problems with USB3 but my MacBook doesn't have USB2 ports any more. I havent tried getting into my phone in OSX or Linux yet since I couldn't find a decent guide, I only know a few basics with the Unix terminal.
Can anyone give me any tip how to get my phone to work again? I also have a USB OTG Adapter, maybe that helps?
Here is a video of my phone with the Clockworkmod Logo bootcycle (can't post links yet so please copy-paste it).
youtu.be/TjG50x7EcUw
cecay said:
I messed up my phone a while ago by trying to update to 4.4 while being S-off. Due to several things I ended up with a phone that stays in a bootloop. I can still get to the Fastboot Menu, but even when I try to go into Recovery the phone boots and for a fraction of a second I can see the Clockworkmod Logo before the devices reboots again (so I assume I messed up Clockworkmod as well).
So I tried to sideload Clockworkmod via USB but ADB doesn't seem to recognize the phone in Windows 8. I installed the official HTC package, but the device doesn't show up when I use 'adb devices', so I can't sideload anything (phone was connected to a USB 2.0 port on the rear panel). I tried the same thing on my MacBook Retina with Windows 7 on Bootcamp, same problem. I read there might be problems with USB3 but my MacBook doesn't have USB2 ports any more. I havent tried getting into my phone in OSX or Linux yet since I couldn't find a decent guide, I only know a few basics with the Unix terminal.
Can anyone give me any tip how to get my phone to work again? I also have a USB OTG Adapter, maybe that helps?
Click to expand...
Click to collapse
adb doesn't work in the bootloader .. never has
Post results of fastboot getvar all minus you SN and IMEI
Download TWRP 2.6.3.3 > http://techerrata.com/browse/twrp2/m7
flash it (unless you have a sprint or Verizon phone Then STOP)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
your bootloop should be gone now boot to recovery and adb should work fine again
I have an XZ1C that I seemed to have damaged the bootloader during a flashing operation.
I have a working OS and can reboot the device with adb without problems via an "adb reboot bootloader" call.
When the device comes back, I'm unable to install the device drivers since the USB IDs are different than are supported from the regular XZ1C driver. My device is reporting as VID 0FCE PID 0DDE. This still seems like an Xperia IDE, but the ID is not supported from the regular Xperia driver.
Does anyone have any ideas how I can reflash the proper bootloader, or have pointers to a specific driver that might work given the odd mode that I've managed to mangle my XZ1C into?
Much thanks!
I didn't understand, what you mean with I can reboot the device via adb....
From my personal view : if the bootloader is broken, no connection via adb could be possible, no fastboot is possible and so on....
Maybe I'm wrong?
If the device is available, is the USB debugging in the Dev menu and OEM unlock enabled? Could you accept the fingerprint?
The VID/PID combo of 0FCE:0DDE is the fastboot device identifier.
If you're trying to get to flash mode, the procedure is to:
- Disconnect the phone from USB.
- Power off the phone.
- Hold the Vol-Down button.
- While holding Vol-Down, connect the phone to your computer via USB.
This will activate flash mode with a VID/PID of 0FCE:B00B.
You can tell the difference between the two by the color of the notification LED.
Fastboot mode has a blue notification LED, while the flash mode color is green.
Not sure I understand fully what you mean but if you're running windows, change the driver manually to Android ADB device once it's plugged in. Windows should recognize fastboot mode at that point you can flash a new boot image.
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
VoltaGe86 said:
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
Click to expand...
Click to collapse
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Sony make.belive said:
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Click to expand...
Click to collapse
Sorry I think I've explained incorrectly. Those are the drivers I've installed, the problem is it only works once.
The second time I reboot the phone into Fastboot mode it doesn't display in device manager. Looking at USBDeview absolutely nothing shows up. Changing USB ports and the cable have no effect, however if I plug the phone into an old USB 2 hub I have then plug that into the computer it will display again in the device manager.
I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.
Sparkenstein said:
I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.
Click to expand...
Click to collapse
Hey man, I know this might sound dumb, but have tried using a different PC ??, I have been in a situation like this and trying using a different pc actually was successful
> Have you tried different PC
Yes. My first suspicion was USB3.0 Ports. So I tried a different PC as well. Unfortunately couldn't find a PC with USB 2.0 ports but yeah another PC didn't work as well (Note mine worked for past 4 years just fine)