Hello,
I've got a problem when trying to load fastboot that I haven't been able to find a solution for here. I'm hoping someone else has run into this and can help. My phone (H811) seems to freeze upon entering fastboot mode. I have...
Flashed 20i using TWRP
Enabled OEM Unlock and Debugging
Uninstalled and Reinstalled drivers in every imaginable configuration over the past two days
Flashed (and completely wiped internal storage) the 20i KDZ
Continued to muck around with drivers
Everything is fine when connecting to my PC, ADB has no issues. I run into trouble when rebooting (via ADB) and the phone freezes. The power button is unresponsive and I have to pull the battery to exit fastboot. My device manager shows -something- is connected after entering fastboot, but so far I haven't been able to find a working driver for that.
Thanks
Related
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Revolution_09 said:
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Click to expand...
Click to collapse
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
alray said:
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
Click to expand...
Click to collapse
Thank you! Everything else went smoothly and I've flashed 5.1 now.
Hello, I've a stock rooted moto g 2014 edition.
Today my phone started rebooting randomly. Half an hour ago it would restart after unlocking my device. Now it can't even get past the bootloader unlocked screen.
I've gone into fastboot and tried getting into recovery but it just reboots again after showing the TWRP splash.
I can't execute any commands through fastboot itself either, Minimal ADB and fastboot doesn't recognize the device.
Flash mode says battery low and asks me to connect the usb cable, but it already is and windows is prompting me "unknown usb device" even after the automatic fastboot driver install.
I haven't messed with any system files in a looong time.
Please help me, thanks.
EDIT: I had to get the drivers from the website, then all I had to do was erase userdata from fastboot.
Case solved =]
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.
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.