Hello!
I install Lineage OS 18.1 on my OP7 PRO, i don't like it and try to reinstall OOS. I messed up and wipe everything and now i'm stuck on fastboot mode, recovery mode doesn't work, adb is not recognized by PC. I don't now what to do, is my first time doing this and destroy everything.
I got here because of these:
1.
2.
This is a clip with the phone:
When I connect the phone via usb to the pc, it appears like this in Device Manager
And in MSMTool, it doesn't appear.
when i drag the fastboot.exe file on cmd and type devices, like in the first tutorial, it appears like this
I was able to reinstall Lineage OS using "TOOL ALL IN ONE". Now, how can I go back to OOS 11, or even 10? MSMTool still doesn't detect my phone.
Related
Left my phone to charge, found it in fastboot mode. When I try to reboot it, no matter what key combination I use, it reboots in fastboot mode. The problem is that the phone is not detected at all over USB. I tried to connect it to both Linux and Windows computers and plugging and unplugging the phone is simply not detected. Any ideas on how to proceed?
I only have a 24-hour period of experience with this phone, but it's strange that it wen't into fastboot during charging.
I will try to point out the main procedures I had to follow after my wife's Mi8 SE freezed after updating with recovery from MIUI 9 (from 2018) to MIUI11 (2020). I had to use platform tools for MacOs to use fastboot commands (mainly fastboot flash recovery to install a new recovery with English language; installed this: https://forum.xda-developers.com/mi-8-se/development/recovery-sky-hawk-recovery-project-2-1-t4051645).
Even after installing this recovery in fastboot mode on a MacOS computer, I had to flash a fastboot firmware downloaded from the Xiaomi Mi8 SE firmware site, only provided for Chinese only firmwares. Had to install the MiFlash and the Qualcomm driver provided for the phone by Xiaomi in a Windows computer, in order to flash the Chinese ROM using MiFlash. After several tries, discovered that I could not let the phone start with the Chinese ROM otherwise, after installing a Global ROM the phone, went back to fastboot... After flashing the Chinese ROM, installed the previously referred recovery in MacOS using the necessary command and afterwards booted into recovery mode (power and volume +), mounted the internal storage, and copied the Global ROM to the phone. Still in recovery mode wiped Cache and Dalvik cache, and installed the Global ROM. After doing this, the phone started correctly with MIUI 11.
I just want to let you know this, in MiFlash I used the mode "Install and delete all". Don't know if this works flashing in mode "Install and keep user data", if you need to maintain your data in the phone.
Hope this helps (I lost our solving my problem).
SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.
SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.
Hello you all,
So, today I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11). When I did, i got an error asking for a pin code, because my last rom encrypted the phone, so I did a Format in TWRP, I got an error saying the data unable to mount, after that I try to use ADB, when I boot into bootload the phone dont apears in my PC.. So now all I have left is a functioning TWRP recovery, an unlocked bootloader, the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the phone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I did was to try an OTG adapter, not a flashdrive but noting. Do I need a Flashdrive with OTG?
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
synced21 said:
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
Click to expand...
Click to collapse
Try a different cable.
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
i ordered a new one. anyway this is the original cable which was in the pixel box.
i got it had to plug it in and out in recvory mode.... **** this device
Hey, dear community,
First of all: I'm using Linux. The Version of Fastboot is 33.0.3p1-android-tools. The device I thought I'm experienced enough to install Lineage OS on is the Asus Zenfone 8. Yes, I asked google - for hours. And I think I am really ****ed now.
Cause the Smartphone (Asus Zenfone 8) was not cheap. And it does not boot anymore. I don't get in Recovery mode anymore. And I'm not able to connect via Fastboot anymore.
But let's start at the beginning.
I was pissed, cause my smartphone forced me to use google. Even if I skipped the Google-Part in the setup, it forced me to agree to send Google information. And I read it. They (quote: may) send Google **a lot** of data. Data I don't want to share - and I don't need to share IMHO! I didn't like to use such a intransparent Device anyway - but this convinced me to try this thing named LineageOS.
I thought about myself I am not a bloody beginner. I mean, I use Linux as my daily driver - for years. And my phone (Asus Zenfone 8) was in the list of supported devices - so I had to try it. I thought if I just install these tools, adb and fastboot, and do these things in the wiki carefully, step by step, what could happen?
And it worked. It worked to unlock device, to connect via adb, to connect via fastboot. It worked to flash the vendor_boot image, It worked to flash the recovery image. But then, just before I wanted to start with the "Installing LineageOS"-part, and therefore boot into recovery mode - it didn't work. I was stuck in the bootloader. I am. still.
There are the options "START", "Restart bootloader", "Recovery mode" and "Power off". No matter what I try to enter, the device restarts (at least it looks like) - It shows "Powered by android", and then the bootmenu again. And again. And again.
When fastboot was still connected, I tried to flash the images again. I even tried to boot directly into the recovery image using `fastboot boot image.img`. But it did not work. And then, the device even stopped showing up when I ran `fastboot devices` - it disconnected.
"Power off" is the only option, wich still appears to work (when not plugged in).
What should I do? Is it even still possible to do something? Please help me.
PS: It would be nice if you tell me, wether the tools or guides you recommend to me work on Linux, in a Windows VM or only Windows Bare Metal. I will do everything to bring my phone back, but it safes a lot of time, not to try using a tool in Windows VM if it only works bare metal anyway.
May be this thread could help you
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Schaukelstuhl said:
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Click to expand...
Click to collapse
I had the same problem. Only bootloader with no device showing with "fastboot devices".
Luckily I tried another cable. An Apple USB C cable behind a hub (screen) got fastboot working. Then I flashed android 13 beta.
And I am sure the other cable worked before with ADB and fastboot.
Try other cables and USB ports... Good luck!