Phone: Xiaomi Mi 5s.
Custom rom: Pixel Experience.
Bootloader: unlocked.
Custom recovery: NO.
ROOT: NO.
Developer mode: enabled.
USB debugging: enabled.
[problem]
Everything worked fine until 3-4 weeks after installing rom.
USB charging: Tried 3 different cables and 4-6 different power supplies. It looks like the cable doesn't matter. Of all power supplies, the phone is charged only from [IET002048 - Lighting 8 pin, 1000 mA, 5 Bt].
USB connection to PC: no connection
USB Preferences not showing up on phone. In config they turned gray.
Default USB configuration set to File Transfer.
Looks like i tried everything but i hope i am wrong. I've also tried to find a way to root phone (so i can install custom recovery), or install custom recovery without root. But seems like it is impossible.
It is possible that this is due to the fact that Piexel Expirience is Pixel Phone based and Pixel Phone sometimes have problems with connecting to PC.
I hope somebody can help me. If you need any more information - tell me.
P.S. I am not a native speaker of English.
Related
Help! I have 2 Mi Max Hydrogen devices.
Device 1: Mine running Lineage OS
Device 2: My wife's running with MIUI Global 7.3.11.0 which is having problem. Just stock when purchased.
Device 2 cant connect to any PC! I have tried different cables but still not working. device 1 can connect. The Device 2 can use OTG flash drives perfectly, i can access the files and copy paste so the micro USB port seems OK right?
I have tried the EDL method but computers(i have several) doesn't seem to respond to this device, it seems nothing is being plugged.
I don't want to make this post too long, so my question is, is my wife's Mi Max USB port have hardware problem? Is there a way to flash ROM or even just root for this device without connecting to PC?
Btw, warranty no more
Anyone? Is my Mi Max have hardware problem?
I have tried to update the OS using the default MIUI updater but it always fails, (cannot verify rom), have tried different ROMs using this method but still same error.
If you will convince me that my device have hardware problem, then i will have peace of mind! Knowing that I lost the only option to flash ROMS.
Otherwise, hope someone could point me to some solution as i would like to update/change the ROM of this device.
Thank you in advance for your kind assistance!
Have you tried an usb adapter to transfer files?
Sent from my MI MAX using XDA-Developers Legacy app
mongoload said:
Help! I have 2 Mi Max Hydrogen devices.
Device 1: Mine running Lineage OS
Device 2: My wife's running with MIUI Global 7.3.11.0 which is having problem. Just stock when purchased.
Device 2 cant connect to any PC! I have tried different cables but still not working. device 1 can connect. The Device 2 can use OTG flash drives perfectly, i can access the files and copy paste so the micro USB port seems OK right?
I have tried the EDL method but computers(i have several) doesn't seem to respond to this device, it seems nothing is being plugged.
I don't want to make this post too long, so my question is, is my wife's Mi Max USB port have hardware problem? Is there a way to flash ROM or even just root for this device without connecting to PC?
Btw, warranty no more
Click to expand...
Click to collapse
I don't think it's a hardware problem as OTG uses all usual +one ground wire on USB so if it's working all is. It's probably bad modified ROM by resellers & a ancient one.
Did you try to cut the man In the middle & update directly from the phone? Like this:
http://en.miui.com/a-232.html
It's basically a side load from a internal SD card method.
Naturaly you can download it directly to the phone and put into according required directory (no need for a PC at all). It's pretty much simple as it can get. Please be certain that you Download PROPER version of ROM for your device exact model!
http://en.miui.com/download-302.html
I recommend at least for now that you stick to the global stable ROM.
I hope that it works out like this for you & do me a favour & leave absolutely bad review to that reseller on Amazon.
Best regards.
Edit:
Actuality to make a process even more easy you can from Updater app chose download update option that should automatically start download of appropriate latest ROM versions (stable global) for a device & directly to the appropriate folder.
Hello everybody.... I write because I'm facing a problem that's causing lot of headhache:
I have this Samsung A3 (SM-A320FL) with broken screen, no USB debug, no root and stock recovery and I need to retrieve data from it.
I tried almost everything:
- programs like Dr.Fone, but the model wasn't supported
- connect the smartphone to the pc, but I can't confirm the mtp connection from the first
- used a USB otg splitter, one port filled with a mouse and another connected directly to the pc, but the smartphone wasn't even seen
I was thinking to flash a custom recovery to use adb, but:
I don't even know what version of Android is installed, nor firmware and I think that encryption was automatically turned on, so unless someone of you has a solution, the best for now is to repair the screen.
The situation is interesting but honestly I didn't see as many solutions...
Sent from my Pixel 2 using Tapatalk
I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?
DangerIsGo said:
I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?
Click to expand...
Click to collapse
Have you tried toggling USB debugging a few times to see if it connects?
Badger50 said:
Have you tried toggling USB debugging a few times to see if it connects?
Click to expand...
Click to collapse
Yes.
Same thing happened to me. First it randomly rebooted and then hung on the "G" splash screen. I couldn't get it to boot at all. It wouldn't show up on windows 8 or 10 (it did on Sept patch) it would charge, but no adb. Had to factory reset in recovery and it booted, but still no USB connection. Went through diagnosis with Google tech support and they are replacing it under warranty.
Not really the same thing here but, my phone suddenly stopped being recognized by my windows 10 laptop even tried several different cables. Also what further made it evident that something must be wrong with the USB-C port when I used the dongle adapter for wired headphones nothing at all, no sound nothing but it charges just fine. I just contacted Google yesterday for a standard RMA and sent if off for a replacement. I love Google's devices but kind of sad I'll be on my 2nd replacement here now, oh well least I get another replacement right?
I've been having issues with my USB-C port as well. I've actually kinda chilled on flashing because of that. I'm worried it's gonna bite me in the ass.
So I ended up talking with Google and I just went for a replacement device. Not ideal but not much more I could do!
Pixel 2 XL updated to.Android 11 recently here in UK.
Now I cannot connect to DJI Mavic Pro or my PC
No USB pop up on status bar saying USB Connected
Yes Dev options enabled and using proper cables (have 2)
My Question is it possible to Downgrade fully to
Android 9 or 10
If so what do i need, links?
Thanks
In the networking section of Dev options is "Default USB Configuration." When I set that to "File Transfer/Android Auto" I was able to connect to my PC. I sometimes have to disable then re-enable ADB to get it to connect. I haven't got a Mavic to test, but hopefully that will help some, at least with the computer.
Yeah tried that with no success
Was working fine with 9 and 10 version
Tried hard reset and safe mode still same
What you mean disable/enable ADB
So looking for how to downgrade if possible
EwOkie said:
Pixel 2 XL updated to.Android 11 recently here in UK.
Now I cannot connect to DJI Mavic Pro or my PC
No USB pop up on status bar saying USB Connected
Yes Dev options enabled and using proper cables (have 2)
My Question is it possible to Downgrade fully to
Android 9 or 10
If so what do i need, links?
Thanks
Click to expand...
Click to collapse
I'm pretty sure the only way to downgrade is to wipe your device though, so make sure you have a backup first. You can downgrade by flashing the Google Factory Images.
There's also an online flashing tool from Google here: https://flash.android.com/
When my device is cranky, sometimes I can revoke USB debugging authorisations, then turn USB debugging (ADB) off and back on. This seems to reset the PC connection and let's it communicate properly, even if I'm only looking to transfer files.
Otherwise, you'll want to flash the factory image as MrBrady suggested.
Today I tried to transfer some files from my Pixel to my PC.
After plugging in different cables into different PCs and Ports I only could get my phone to load.
There was no way to change it to transfer mode...
Windows didn't recognize the phone at all.
In the developer options it is already set to data transfer / Android Auto.
I am using the latest December (October) patch.
My final goal was to backup my data and install a different ROM now after there are no more official updates.
Anyone has an idea how to get my phone connected to a PC again? In the past it was working well - but I don't know how long it isn't working anymore.
PS: I already cleaned to USB port of my Pixel.
Thanks a lot!
I just bought a used Pixel 2 XL and have the same problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery.
It's got to be a software problem on the phone. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.