Database Develop

Note 5 Bricked. Need Help. USB port not working.

I was trying to restore a backup via TWRP, now the Note 5 is stuck in boot screen (over 30 mins).
Can boot into TWRP and Download mode, but my PC (and 4 others running Windows 7/10, Ubuntu) do not recognize the Note 5 showing "Unknown USB Device (Device Descriptor Request Failed)" with the instance ID USB\VID_0000&PID_0002\6&d66f1f7&0&7.
I tried to modify the Android Driver with the corrupted VID & PID, tried to use adb shell etc, but can not see the phone on the PC to try Odin any other recovery process. I tired connecting an OTG flash drive, but can't get TWRP to recognize it.
I have also tried replacing the USB Charging Port of the Note 5, and the same behavior is there with the original and the new charging port chip.
Is there any way I can access the storage, or fix the PID and VID of the phone so I can try to flash firmware via Odin.
All input is greatly appreciated.

Fastboot mode not detected + MTP mode not detected

Hello,
since 2 days my MI5 is not working fine. I can plug it to the energy and charges, but when I connect it to the PC via ADB or fastboot, is not recognized, but charges.
is it possible that the usb-connector is damaged? It looks like the mobile doesn't recognize when is connected to a computer and always is on charge mode. Any ideas how can I check it?
I installed the MIUI USB Settings (https://play.google.com/store/apps/details?id=co.vincze.usbsettings&hl=es_419) and I get the message that I need to plug my mobile to the computer.
I tried with several usb - cables, and also with different computers.
I restart the mobile in fastboot mode and is not detected too, just charges.
thanks for ur help

Anyway what rom and version you're using it..?
Using original cable..?, and already check it that usb connected as MTP not just for charging in developer option..?
Did you already install all driver needed for adb and fastboot interface..i mean driver included while installing miflash tool?, also checking it under pc device manager to check that's already connect with correct driver

JJeamy said:
Anyway what rom and version you're using it..?
Using original cable..?, and already check it that usb connected as MTP not just for charging in developer option..?
Did you already install all driver needed for adb and fastboot interface..i mean driver included while installing miflash tool?, also checking it under pc device manager to check that's already connect with correct driver
Click to expand...
Click to collapse
last developer rom: MIUI 8 Global 7.1.19 | Beta
original cable + other cable.
driver installed correctly (in 3 computers) - The phone was always recognized in the 3 computers, and now is never recognized.
In pc device manager nothing is displayed.
In developer options MTP enabled.
And always is charging.
Restarting in fastboot mode, connected to computer, and also only charges, is not recognized. Is is possible that the usb-port is damaged?

ivanrsz said:
last developer rom: MIUI 8 Global 7.1.19 | Beta
original cable + other cable.
driver installed correctly (in 3 computers) - The phone was always recognized in the 3 computers, and now is never recognized.
In pc device manager nothing is displayed.
In developer options MTP enabled.
And always is charging.
Restarting in fastboot mode, connected to computer, and also only charges, is not recognized. Is is possible that the usb-port is damaged?
Click to expand...
Click to collapse
Really weird..but it's possible your usb port of your phone already broken..
Anyway how do you get using 7.1.19 beta rom..?, from updating or fresh flashing from twrp with already unlocked bootloader..?
If from twrp..how about connecting while in twrp..?, did your pc recognized it..?

JJeamy said:
Really weird..but it's possible your usb port of your phone already broken..
Anyway how do you get using 7.1.19 beta rom..?, from updating or fresh flashing from twrp with already unlocked bootloader..?
If from twrp..how about connecting while in twrp..?, did your pc recognized it..?
Click to expand...
Click to collapse
unlooking bootloader and installing twrp. after I get the updates directly from xiaomi...

ivanrsz said:
Hello,
since 2 days my MI5 is not working fine. I can plug it to the energy and charges, but when I connect it to the PC via ADB or fastboot, is not recognized, but charges.
is it possible that the usb-connector is damaged? It looks like the mobile doesn't recognize when is connected to a computer and always is on charge mode. Any ideas how can I check it?
I installed the MIUI USB Settings (https://play.google.com/store/apps/details?id=co.vincze.usbsettings&hl=es_419) and I get the message that I need to plug my mobile to the computer.
I tried with several usb - cables, and also with different computers.
I restart the mobile in fastboot mode and is not detected too, just charges.
thanks for ur help
Click to expand...
Click to collapse
Same problem here, from 3 or 4 days
Any solution to solve, please?
And neither twrp i can install

Phone not detected

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...

Recovering from bad bootloader flash

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.

device not getting detected in both adb and fastboot.

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)