Pixel experience version is PixelExperience_vayu-12.0-20220128-2345-OFFICIAL, I don't know why but after installing pe mobile network on my phone stopped working. I have tried to reboot my phone, but it did not help. I don't know much about custom ROMs, Any ideas?
What about reaching recovery or fastboot mode?
Related
I recently installed the MIUI 10 Global Beta. Since then, none of my computers or operating systems detect the device in fastboot mode.
In Linux, no device file is created under /dev.
Trying to flash anything results in errors. I'm not even able to flash TWRP through fastboot. My bootloader has been unlocked.
Has anyone else come across this issue? Does anyone know any fixes?
EDIT
Turns out, this issue is also present in some other recent Xiaomi devices. Works fine with USB 2.0, the problem occurs when using USB 3.0.
This is the first time I've heard this problem.
But I assume that you installed the new system via TWRP, so why didn't you reinstall TWRP immediately before the first start?
Did you tickled usb debugging modus in developer options?
I recently managed to royally screw up installing Havok OS on my OP7 Pro.
I managed to get OOS installed and everything appears to be working.
However, when I was about to give it another crack, I rebooted into fastboot and the device is showing as "msmnile" and it's not detected by my computer.
Seems to me as though the fastboot ROM is FUBARd... Any ideas how to reflash it?
Install the adb for OnePlus that's automatically pops up when you connect your USB to the PC. Your phone might not show up but this drivers will. You can do it in fastboot mode or adb mode. If not go and search for OnePlus drivers
I had the same issue once. If twrp is still working you can try flashing a stock rom. Everything is in it to fox this. Then wipe system data en cache etc and flash your prevered custom rom.
Otherwise it could be a driver issue. Win 10 doesnt support everything without good drivers and there is even een issue with use of some Usb3 ports VS Usb2. Just try some ports and some drivers on diverend machines.
Last stage is a full factor recovery with
quallcomm download mode. Then every thing Will. Be wiped and you need to unlock boadloader etc again.
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.
Hey everyone.
I have a bizzare problem?
I have no computer connection when in recovery mode with my Poco?
It happened after I logged out of my miaccount following youtube flash instructions in an online guide.
At first I thought avast on the PC had removed my android drivers. Or that it was the TWRP (3.4.0-15-surya-mauronofrio). i uninstalled avast an replaced it with IObit an reinstalled Xiaomi android drivers.
The cell has windows access when booted an transfer option is chosen on the Poco.
I cannot get windows access for transferring files when in recovery?
does anyone know how I can restore my recovery mode windows access so i can transfer files an see what I'm doing?
Ive never had this happen before. I will never log out of Miui before flahing a custom recovery ever again thats for sure.
Wierd?
Bryceicle1971 said:
Hey everyone.
I have a bizzare problem?
I have no computer connection when in recovery mode with my Poco?
It happened after I logged out of my miaccount following youtube flash instructions in an online guide.
At first I thought avast on the PC had removed my android drivers. Or that it was the TWRP (3.4.0-15-surya-mauronofrio). i uninstalled avast an replaced it with IObit an reinstalled Xiaomi android drivers.
The cell has windows access when booted an transfer option is chosen on the Poco.
I cannot get windows access for transferring files when in recovery?
does anyone know how I can restore my recovery mode windows access so i can transfer files an see what I'm doing?
Ive never had this happen before. I will never log out of Miui before flahing a custom recovery ever again thats for sure.
Wierd?
Click to expand...
Click to collapse
check if you have Enable MTP switched ON in Ofox or TWRP, if not turn it on, should help
or reflash Ofox again and reboot recovery and see if that helps
jeryll said:
check if you have Enable MTP switched ON in Ofox or TWRP, if not turn it on, should help
or reflash Ofox again and reboot recovery and see if that helps
Click to expand...
Click to collapse
Yeah I tried that. It was a simple issue. The owner of the laptop recently got a gaming rig with windows 10. An Acer. An I was using her gaming laptop. A HP. She is logged into windows on both computers. During the night windows got a bit stupid an installed adb drivers as system that were Acer drivers on both computers. Hense no adb connect in fastboot was possible on the HP. She remembered her HP update driver password an activated her HP account. I have removed the Acer android drivers but cannot install any. Hoping to using HP driver install to remedy this.
What a nightmare lol.
I am currently on Pixel Experience 10 official beta with twrp an ANX camera. Luckily I had some ROMs on my SD card lol. I was in the middle of formatting data with no Rom installed when I discovered it.
Always have a relaible easy to flash Rom.
I thought I was soft bricked. Very scary
it could be easy if the available recoveries support adb sideload or adb push so you can transfer files to /sdcard
I have never tried side load. Maybe I should learn. An if you want a terrific anx camera inbuilt then switch to Pixel Experience Beta Android 10. I don't know as much about photography as you. I just know I suck at it lol. Same procedure an Evox 5.2. flash 12.0.3.0 firmware then PE then format data. Bang. Everything works I've tested so far unlike Evox 5.2. Similar experience but not a power Rom. Strong an steady. Antutus in the 282-287k range. Mind you after nearly bricking my Poco last night for safety I made data an Cache ext4 an not f2fs.
Probably why it's a little slower.
Xiaomi Poco X3 (surya) - Pixel Experience
Xiaomi Poco X3 (surya) - Pixel Experience
download.pixelexperience.org
Bryceicle1971 said:
Xiaomi Poco X3 (surya) - Pixel Experience
Xiaomi Poco X3 (surya) - Pixel Experience
download.pixelexperience.org
Click to expand...
Click to collapse
What if I use A11 instead of A10 of PE?
Hello everybody, I have a Mi note 10 pro (CC pro) it is a global version, so initially I installed TWRP and start using .eu rom. everything was ok. in one opportunity I make a mistake and installed the Chinese rom so I repeated the process of installing TWRP and again everything was ok. the last month I saw in the playstore an app for miui update I tried it, but it was for Chinese roms again, I didn't realize and installed the Chinese rom, once it was installed TWRP disappeared I tried to repeat the same process of installing TWRP and flash a global rom, the surprise was that once it was with the Chinese rom it was impossible (still now) to connect the mobile in fastboot mode it was working fine with my computer previously to the Chinese rom, I tried updating drivers nothing change, I tried another mobile in my computer it works fine, I tested in another computer and nothing no one recognizes my mobile while it is on fastboot mode ( in adb it works fine) once I go to fastbook it desapear from device manager and lost the connection with the computer, I tried it even in ubuntu and nothing at all.
Finally I could go back to the global rom using EDL flash with an authorized account, but still, fastboot mode is not working at all.
I would like to go back to the custom rom but It is impossible because I can't connect the mobile with the computer in fastboot mode. ( tried even using an otg cable with another mobile and nothing works)