I was trying to install pixel experience on my mi note 7 pro using Windows 10 laptop.
# what caused problem
I unlocked bootloader and then I flashed custom recovery provided in pixel experience website instead of TWRP recovery.I wiped data and now I was not getting further steps to follow, so I started my phone it got fresh installed again. here usb connection failed. Also Now my phone was not showing pixel experience bootloader. it showed mi bootloader.
# Issue
my pc cannot recognise my phone. I dont think this is a driver issue because I was able to successfully unlock bootloader using mi unlock tool which required drivers.
Also now my phone is also not showing option of switching between USB TETHERING/ CHARGING/ MEDIA TRANSFER etc in notification panel. So my phone is also not recognising my PC.
Note: usb was working perfectly before I flashed custom recovery of pixel experience and wiped the data.
# Things I have tried:
1) different Usb cabels
2) different laptops
3) usb 2.0 & 3.0 ports
Related
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
i was trying to install a custom ROM and wiped all the partitions. I accidentally rebooted my Xiaomi redmi note 8 and now it is stuck in fastboot. i tried to flash TWRP using ADB however it shows that it is waiting for device. (I'm guessing that the USB DEBUGGING turned off). Anyone know how to fix this? Thanks in advance!
I would try possibly checking drivers on your computer, or just try a different cable. USB Debugging is not necessarily a thing in fastboot. Or, better said, there is not a toggle switch for turning on USB access. Plugging in a USB cable gives you full access to fastboot commands on the device that you're using. If that doesn't work, you might want to try checking out the Redmi Note 8 sub-forums since others might have the same issue. Try drivers and/or cable changes and share the results
Model Name: ROG 3 trncent edition( ZS661KS)
Firmware Version:WW-17.0823.2012.131
Rooted or not: yes ( was trying to root)
Frequency of Occurrence: Got<HARDBRICKED>
APP Name & APP Version (If your issue relates to the app): no app used.(magisk or anything else)
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
My rog phone 3 (tencent), which i brought about 6 months ago. I never had any issues like this.
The other day i opened my camera and suddenly the front camera was not working. I restarted the phone, did factory reset, cleared camera data, but nothing solved the issue. I thought i have to upgrade the firmware. So i downloaded the new firmware (2012.143) and connected the usb c cable with my laptop ( lenovo ideapad 320) , but it did not recognize. i tried both ports. I never had this problem before. I unlocked the bootloader, i thought it might help. I also turned on the developer option and selected FTP protocol and USB debugging. But it still didn't connect. while i was trying to enter bootloader recovery mode I accidently put the phone on EDL mode and now its bricked . The indicator light is flashing when i connect to the pc but the PC isn't recognizing the port ( i downloaded the qualcomm EDL driver on my laptop also, but the port option is not showing at all). Is it hardware problem, But the phone was charging just fine.
please help, gaming is my life
Hi there... I am struggling with my zte axon A2020G Pro running android 11. The problem is i can only connect it to my Windows 10 PC in charging mode. No fastboot or adb connection. Bootloader locked.
When trying to connect with usb cable i get the message Unown usb device. It charges only. I have tried changing cables, changing computer, Wireless adb, Rooting without PC. I have tried software upgrade/downgrade from sdcard.
I have read this problem can arise when flashing wrong uppgrade but as the booloader is locked i dont think this is the problem.
Everything else i working perfect and the phone is looing like new. Bought it from Tradera so no service support available in Sweden.
My main goal is to get it working with my PC so i can get it bootloader unlocked and transfer files.
Any ideas or suggestions?
Brief: Having issues with USB in Windows 11 and my Le2115. Right now, Windows sees the device, and adb devices returns a serial number (with debugging on); however, the phone is not seeing that it is plugged in at all. It is not charging, no transfer options, nothing.
History: So, it all starting sometime after trying to get rid of OS13 and returning to stock, I bricked my phone pretty good. Ended up using MSM and loaded an india version, went back to a Global version, lost touchscreen after updating to v12, used MSM to go back to a different rom (OS-11.2.4.4.LE25AA... don't remember the previous ones) and then updated to C65.
After rebooting to C65, I plugged by phone it that I got no response from either Windows 11 or from my phone. Swapped cables, swapped ports, rebooting both devices, uninstalled Oneplus drivers, rebooted and reinstalled them... nothing worked. Plugged in my LG V60 and Windows would see it fine. Put the phone into Recovery and tested with fastboot devices and the phone showed up fine. Reset the phone to factory... no change; Window would not need see it.
Reflashed the phone to the OS-11.2.4.4.LE25AA ROM via MSM. Booted up the first time and Windows saw the phone just fine and the phone gave me the connection type notification and began charging. Successfully tested file transfer and adb devices. Ran the first update... tested it and everything worked fine. Turned on Debugging to make sure that adb and fastboot worked... they did. Ran the C48 OTA update.
After rebooting, when I plugged in the USB-C Warp cable, Windows defects the phone as an MTP device (sm8350-mtp in device manager), but the phone did not see that it was plugged in (no charging, no notification). Turning on Default USB Configuration allows me to change it to other modes when plugging it in (File Transfer will even let me browse the phone via Explorer), and the phone will show in device manager as a Oneplus 9 G5, but the phone never indicates that it is plugged in and will not charge at all. Plugging the phone into a USB 2 or 3 port seems to do the same thing. Fastboot in recovery works fine. Turning of Default USB Configuration causes it to either detect as a generic USB Composite Device or as an MTP device (not sure how/when/what causes it to change). Charging and warp charging on a power brick works fine and it does show up in the phone.
Seems I am going in circles now and not sure how to get out of this cycle. Any suggestions would be most appreciated!
[TMO To Global] [No Dual-SIM Bug]
Requirements:- * Unlock Token * T-Mobile MSM Tool * OOS 11.2.10.10 and OOS 12 C.48 Global * Fastboot Enhance Instructions:- 1) MSM back to TMobile OOS11 and unlock bootloader through unlock token 2) Extract the payload file from...
forum.xda-developers.com
That will basically fix your problem. Just use le2115aa