Hi, right after 3 days I installed April 2020 security update on my pixel 3 XL, my phone's screen turns black and i can't unlock my phone. So i reboot my phone then it enter fastboot mode and it displayed "failed to load/verify boot images". I try using the Volume keys to scroll until Recovery Mode but it's still going to fastboot mode. The start, recovery mode, and rescue mode options all just go back to the fastboot menu with "failed to load/verify boot images".
I had try leave my phone on the fastboot mode screen until it die and plugging it back while holding the power button. Then it still just go back to the fastboot menu with "failed to load/verify boot images". I also try plug my phone into a different charger and USB-C cable but still the same problem appear.
Any help guys, what should i do ? Thank you very much.
What happens in bootloader when you type fastboot reboot fastboot?
Just download the android 10 factory image latest and google platform tools in that same page and unzip the image and copy those contents to platform tools and then using cmd prompt CD to platform tools and make sure fastboot can detect your device and then type flash-all and it should be back to factory condition.
Related
Hi all,
After I've installed color os 2.1.1 from sniper-joe I cannot back into my recovery.
The phone can boot on OS and in fastboot but not into recovery.
My phone still boot loop as long I press volume down. When I release the button I'm in fastboot.
Model x9006
I try to remove SD and SIM : same
I've installed different TWMP and CWM : same
I've got some issue with 2.1.1 and want to go back to 2.0.8 but cannot
Mine has too after installing the official Lollipop, any help? Lollipop was buggy for me so I'd like to unbrick my Oppo.
So plug in phone AFTER booting into Fastboot mode (power+volume up) then open a command window by pushing shift and right clicking anywhere that the platform-tools folder is and then type fastboot devices and hit enter and then type fastboot oem unlock and hit enter and then fastboot flash recovery recovery.img or whatever the name of your rcovery is then just power+volume down and boot into the recovery. It helped me!
droidiam said:
Mine has too after installing the official Lollipop, any help? Lollipop was buggy for me so I'd like to unbrick my Oppo.
So plug in phone AFTER booting into Fastboot mode (power+volume up) then open a command window by pushing shift and right clicking anywhere that the platform-tools folder is and then type fastboot devices and hit enter and then type fastboot oem unlock and hit enter and then fastboot flash recovery recovery.img or whatever the name of your rcovery is then just power+volume down and boot into the recovery. It helped me!
Click to expand...
Click to collapse
You need one of these recoveries if you own a R63419 LCD (newer find 7 have this model) - For me the first was OK :
forum.xda-developers.com
/find-7/find7-development/x9076-r63419-lcd-recoveries-t3049886
Hello guys,
After doing oem unlock with fastboot ,i've tried to flash TWRP recovery but after the comand i cannot acess recovery, it just reboots. Tried several recovery images and read alot of toturials but with no sucess!! Win10 64bits computer here.
Thanks,
NightSource
Nightsource said:
Hello guys,
After doing oem unlock with fastboot ,i've tried to flash TWRP recovery but after the comand i cannot acess recovery, it just reboots. Tried several recovery images and read alot of toturials but with no sucess!! Win10 64bits computer here.
Thanks,
NightSource
Click to expand...
Click to collapse
Did you hold the volume down button + power button to get to recovery mode manually right after flashing?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
If you have successfully unlocked the bootloader, you'll get a bootloader unlocked warning every time you boot. On the warning screen, click either of the volume buttons and you'll be redirected to a bootup menu. From there, you can select "boot to recovery" using the volume rocker and power button.
Alternatively, enable "advanced reboot" in developer options and reboot to recovery from the main OS power menu.
If these don't work, reflash TWRP using fastboot. Make sure that you're using at least version 3.0.3-1, best to use 3.0.4-1.
Tried manually reboot into recovery but it just reboots,
I can sucessfully unlock as i have the warning on boot, but there if i go to the menu and press for recovery it just reboots, tried several tipes of recovery TWRP imgs
Any help greatly wanted
Download this version of TWRP (jcadduono's 4.0.3-1). Rename the file to something like twrp.img.
1) Make sure adb/fastboot is working on your computer (if you've already unlocked the bootloader, then I am assuming it is).
2) Put your phone into fastboot mode and connect it to your computer. Open a command prompt where you can access fastboot.
3) Put the twrp.img file to the same folder where you opened your command prompt.
3) Enter
Code:
fastboot devices
in fastboot and make sure your phone shows up with its serial number.
4) Enter
Code:
fastboot erase recovery
to erase your current recovery
5) Enter
Code:
fastboot flash recovery [B]twrp.img[/B]
, where twrp.img is whatever you named your twrp file.
6) Enter
Code:
fastboot reboot
to reboot into your main system. You can either reboot then use advanced startup to enter recovery, or press a volume button at the bootloader warning page to boot directly to recovery.
Anova's Origin said:
Download this version of TWRP (jcadduono's 4.0.3-1). Rename the file to something like twrp.img.
1) Make sure adb/fastboot is working on your computer (if you've already unlocked the bootloader, then I am assuming it is).
2) Put your phone into fastboot mode and connect it to your computer. Open a command prompt where you can access fastboot.
3) Put the twrp.img file to the same folder where you opened your command prompt.
3) Enter
Code:
fastboot devices
in fastboot and make sure your phone shows up with its serial number.
4) Enter
Code:
fastboot erase recovery
to erase your current recovery
5) Enter
Code:
fastboot flash recovery [B]twrp.img[/B]
, where twrp.img is whatever you named your twrp file.
6) Enter
Code:
fastboot reboot
to reboot into your main system. You can either reboot then use advanced startup to enter recovery, or press a volume button at the bootloader warning page to boot directly to recovery.
Click to expand...
Click to collapse
Sometimes it helps to use fastboot to boot the image directly after you flash it. This ensures you get into recovery since it loads it off your computer.
It should then work normally afterwards
Sent from my ONEPLUS A3000 using Tapatalk
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
gogobaba said:
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
Click to expand...
Click to collapse
Search for FWUL from Steadfasterx.
download-> flash->connect-> open Comannd-> type "fastboot flash recovery recovery.img" or "fastboot reboot system"
Which command are you using for installing TWRP in ADB?
I got a brand new AT&T's Moto Z2 force XT1789-04 (updated to Oreo using an AT&T SIM) and got it SIM unlocked through unlockstone.com's service. After the unlock, I found the following problems:
(1) After every reboot, the device first goes to the fastboot interface (Android man down with box open, just like the figure below but shows "Start" on top right instead ), and I have to press power button to continue a normal boot.
https://www.hardreset.info/media/re...fd1b9659973ee877f48/motorola-moto-z2-play.jpg
(2) In fastboot, If I choose "recovery mode" using volume down/up and press power button, it will go back to the fastboot interface with "start". In another word, I can't see menu of recovery mode, such as "wipe data/factory reset", "Apply update from ADB" and so on.
(3) In addition, the model number has been changed from XT1789-04 to XT1601, but it shouldn't matter according to discussions of other unlockstone's users.
My first questions is, can anyone help me to explain the reason and possible fix to those issues? Would a flash of official AT&T's firmware (such as, NASH_ATT_OCX27.109-47_subsidy-ATT_regulatory-DEFAULT_CFC.xml) be able to fix it?
I understand AT&T locked the bootloader, but it is still possible to flash the firmware, according to:
"With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes." (see, https://forum.xda-developers.com/z2-force/help/updating-att-ota-issues-help-sideloading-t3864514)
So, I gave it an try on my Mac (I also tried on Windows 10, see below):
(1) install moto device manager (MDM Intaller_2.2.9.dmg) downloaded from moto
(2) install 15 second adb and fastboot installer (adb-setup-1.4.3.zip) from XDA
(3) copy files unzipped from (2) to a working folder, copy the firmware as an update.zip file to the same working folder
(4) turn on the device, open developer's options, turn on USB debugging
(5) connect the device to the MAC, choose "USB for file transfer" mode
(6) open a terminal and type the following commands
$ adb devices
List of devices attached
ZG224AGZPZ device
$ adb reboot recovery
Both work fine.
(7) Now the device is in fastboot's "START" mode, not "recovery mode". Since I cannot Select "Apply Update from ADB" from the device, the following command certainly failed:
$ adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
My second question is, can any help me how I can flash the device if the above methods doesn't work?
By the way, I also tried several methods on Windows 10:
(1) Similar to the above method, install moto device manager/or install moto USB driver, install 15 second adb and fastboot, open a CMD window, but "adb devices" couldn't find the device.
(2) Use Lenovo Moto Smart Assistant to "rescue" the device. However, since the device's model number has been changed from XT1789-04 to XT1601, it couldn't go through.
Any suggestions? Many thanks!
Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.
Great! The first problem (automatically paused at fastboot interface) is fixed! Thanks a lot!
This is what I did:
(1)
$ adb reboot recovery
$ fastboot devices
$ fastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.008s
(2) fastboot reboot or reboot the device manually, it will be brought a fresh start asking for account setting and so on.
In this step, the device got stuck at AT&T's Logo and "Checking for update", but can be solved by manual reboot.
(3) Soft reset works (Setting-->System-->Reset) and will show an "Erasing" screen during reboot.
Then a new but famous problem comes up: When use power+volume down to enter fastboot mode and then use volume key to enter "recovery mode", it shows a down Android robot with red exclamation mark + "no command" other then a menu of options.
There are multiple methods available online. What works for me is:
"it worked when pressing power button for 3 seconds then preesing volume up and released both together"
Then select reboot the system.
It can't remove the Android+Red exclamation+no command screen under the recovery mode but at least provides a method to access it.
However, I have to try it a couple of times before it can show me the recovery menu. I don't know why.
According to this (https://forum.xda-developers.com/z2-force/help/z2-force-booting-to-blank-screen-t3808222), this problem might be able to be fixed by "You should flash it back to stock.".
41rw4lk said:
Sounds like you have fastboot mode set on, most likely didn't clear from update.
In fastboot enter 'fastboot oem fb_mode_clear' w/o quotes then 'fastboot reboot' and you should boot normally.
When you flash an update, you do it from fastboot, not recovery. When you sideload, you do it from recovery.
Click to expand...
Click to collapse
I'm not sure what issue you're having. What you're describing is normal. In Nougat whenever you rebooted to recovery it went to recovery, in Oreo whenever you reboot to recovery you hit a post screen. When you see the android with 'no command' just hold power and tap vol_up, that will bring up the recovery menu like normal. That's the way it is.
XT1789-04 won't boot
Ok, here's my story. I have the very same problem here with the very same phone. Moto Z2 Force XT1789-04 from AT&T. Sim unlocked with same method as they unlocked yours. Converted to XT1601. Can't use Moto Assistant as it will find the mismatch.
Tried the fastboot commands shown here but looks like my problem goes deeper. I'm stuck on a black page that says "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device...."
Looks like they flashed a custom file or something and of course the boolotader is not unlocked and can't be. What are my chances of fixing it here?
I was starting the process of installing a LinageOS ROM on a new or practically new Pixel 3 XL. I completed the stage where I installed the LineageOS recovery image using flashboot mode. When I got to the ROM install part I found I was in fastboot mode and no matter what I try I am only able to go to a blank screen or back to fastboot mode. I have made several attempts to get out using "flash reboot" or "flash continue" and one other I found in a forum. Nothing has worked. I am able to change the menu and get Start, Reboot Bootloader, Recovery Mode, Bar Code, and Power off. None of these options get me out. Anyone know a way out of this situation? Thanks
Try
Code:
fastboot devices
fastboot reboot
jwoegerbauer said:
Try
Code:
fastboot devices
fastboot reboot
Click to expand...
Click to collapse
jwoegerbauer said:
Try
Code:
fastboot devices
fastboot reboot
Click to expand...
Click to collapse
Thanks for the quick response. I have tried those commands. Unfortunately it did not get me out of fastboot mode