[Solutions] OTA update not insatalling stuck at Red triangle - One (M7) Q&A, Help & Troubleshooting

Many user at XDA everyday asking this same Question again and again.
Our phone not updating after getting OTA update.
Symptoms
Phone reboots to recovery but stuck at red triangle
Requirements
>>Stock recovery ( custom recovery TWRP/CWM can't flash OTA )
>>Stock system unmodified (custom kernel modifies system files so if you flashed custom kernel you need original files to restore)
>> Data/preload Apps ***Most Important*** according to phone software version (different CID contaions diffrent apps) when we unlock bootloader it delets data partition so data/preload apps also when OTA check OS integrity it also check data/preload apps with their md5/sha-1 match.
{How to Do}
1. 1st we need flash stock recovery (if you already have, skip this point ) you can flash it via Fastboot or Flash Image GUI App
fastboot flash recovery recovery_name.zip
Link for stock recovery
you can extract stock recovery from firmware zip here
2. Stuck at Red Triangle
means stuck at OS verification stage. You have to do 2 things
verify data/preload apps
verify system
extract OTA updater-script (open with Notepad++) from OTA (Meta-inf/com/google/android/updater-script) match apk file to OS.
Getting missing files - find these apks according to your system software version Like This or fastboot getvar all
Where to find apps
Previous OTA
Guru ROM Reset
Nandriod Backup
Anyone uploaded over internet
Find a HTC One m7 same version backup apps with ES File Explorer
Restore files using Root Explorer
rename apps according to updater-script copy to phone storage copy to data/preload REBOOT.
Most apps
calculator, flashlight, Htcringtonetrimmer, HtcSoundrecorder, 7digital, soundhound, Twitter_client.apk + more
Tools
Notepad++
MD5 & SHA-1 check
If this process is boring Lengthy to you, use RUU, Guru reset rom to get stock & then flash OTA.

Don't want download OTA again or use PC downloaded OTA
Don't want download OTA again or use PC downloaded OTA
copy ota file to PC.
start downloading OTA at phone over wifi again
stop wifi at 1% ( don't cancel OTA dialog )
match file name phone storage/download/ota file to PC file rename it.
copy PC file to phone/download overwrite existing file.
resume wifi it will show download complete Start Installing.....

The correct way to flash recovery is
fastboot flash recovery nameOFrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Don't skip the last 2 steps !!

Related

Noob Guide to Manual update to 4.4.2

Am sorry if am Making this Guide in the Wrong section..
NOTE:
AM not responsible for any data lose or Result in brick etc..
.
Do Charge your device 100%
Have a Copy of Stock image to revert back to stock if something goes wrong, or a nandroid backup...
Steps To follow for Rooted users:
Use Nexus Tool kit to flash Stock Kernel and Recovery... ( you will lose your Root cos of this )
Download and extract Stock Factory image of 4.4 and edit flash-all.bat ( Remove "-w" and save it )
Copy the Extracted files into Fastbood Folder
Now Boot your device into Bootloader ( adb reboot-bootloader )
Now execute Flash-all.bat
Your device will be flashed back to stock without wiping your data or user files... Settings Apps will be intact.
Once device boots up, Reboot into Recovery Mode ( Stock Recovery )
Use Volume button to select "apply update from ADB"
Now Open Fastboot and type in " adb sideload xxxx.zip " ( xxxx denotes your 4.4.2 or 4.4.1 file name ) ( type without " " )
Once done wipe cache and reboot...
You are now on Android 4.4.2
Download links:
Nexus 4 Stock 4.4
Update from 4.4 to 4.4.2
Update:
Am Attaching flash-all.bat modified here,
users who are not able to edit flash-all.bat, can download the attachment and replace it with stock flash-all.bat

[Troubleshooting Q] Can't take OTA

I received a notification to download and install the OTA on my GSM Dev Edition Moto X. I'm rooted with stock 4.4.2 installed and xposed. I disabled xposed. Then tried to install the firmware. My phone rebooted into recovery (TWRP 2.6.3.1) and then the install failed. I look at the terminal and I saw the assert failed that was checking the model type (it was checking some values in the build.prop for "ghost") I checked the build prop, and the values were correct. I can't figure out why it's failing.
[Q] Would it be safe to download the zip currently available, extract the contents, delete the assert, and re-archive, and then flash this one instead?
(Follow-up question) If this is safe, I saw on 7zip there are many options to re-zip a file. At first I chose no compression, but then I tried normal compression and that ended up with a zip that was the same size as the original. Should I just follow a guide on how to create a flashable file?
rsromano said:
I received a notification to download and install the OTA on my GSM Dev Edition Moto X. I'm rooted with stock 4.4.2 installed and xposed. I disabled xposed. Then tried to install the firmware. My phone rebooted into recovery (TWRP 2.6.3.1) and then the install failed. I look at the terminal and I saw the assert failed that was checking the model type (it was checking some values in the build.prop for "ghost") I checked the build prop, and the values were correct. I can't figure out why it's failing.
[Q] Would it be safe to download the zip currently available, extract the contents, delete the assert, and re-archive, and then flash this one instead?
(Follow-up question) If this is safe, I saw on 7zip there are many options to re-zip a file. At first I chose no compression, but then I tried normal compression and that ended up with a zip that was the same size as the original. Should I just follow a guide on how to create a flashable file?
Click to expand...
Click to collapse
Your problem is highlighted in red. All of the guides tell you that you have to flash the stock recovery back in order to accept the OTA. Download the official SBF for your carrier here: http://sbf.droid-developers.org/phone.php?device=0
Now extract the file. You only need 1 file -- recovery.img
Put it in the same folder that has "mfastboot".
Boot the phone into bootloader mode, then type:
mfastboot flash recovery recovery.img
Now you -should- be able to accept the OTA assuming you haven't made further modifications to the system.
When you have successfully updated, you can now flash TWRP back.
Good Luck
I tried downloading stock, but through a different method, and still ran into an error. I will try your method tonight.
Do you have a link to a guide? I was looking and couldn't find one this weekend.
Sent from my XT1053 using Tapatalk
http://mark.cdmaforums.com/MotoX-OTA.html pretty much covers what you need to take an OTA on the X (and most Motos). The same info is scatter throughout the thread talking about the GSM 4.4.3 update.
to flash stock recovery, see the Requirements section, then Option 2 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Before you flash stock recovery, visit this post -> http://forum.xda-developers.com/showpost.php?p=24267797&postcount=1 and download the attached Xposed-Disabler-Recovery.zip, and place it on the emulated SD Card of your X.
Boot into Recovery and install update from SD. Pick the Xposed-Disabler-Recovery.zip, then the flash stock recovery and take the OTA update.

How to flash OTA Zip manually?

How can i flash a OTA Zip manually?
I tried it with CWM but get the eror Message "/system/build.prop": No such file or directory
no way Jose!
the OTA Zip is ONLY for the normal recovery.. not work in Custom recovery like CWM or TWRP ...
flash a stock ROM to works..
greetings..
:good:
mario93 said:
How can i flash a OTA Zip manually?
I tried it with CWM but get the eror Message "/system/build.prop": No such file or directory
Click to expand...
Click to collapse
You must do it from a clean system without root (in theory) and the recovery of stock
so you must prepares a clean install with RSD lite and from there you have the zip ota, you must place it on the external SD and reboot into bootloader mode and choose to enter recovery, once in the recovery you must install zip from external sd
ota file has specific restrictions in origin (compilation of your operating system) to destination are upgrading so ota files will verify that you are in the point of origin of the operating system for which it was designed that update.
see here one example
http://forum.xda-developers.com/razr-i/general/kk-brazil-retail-tested-t2917886

[GUIDE] Downgrade Zenfone 2 Laser to any official firmware

I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
(!less_than_int(1457089250, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Mar 4 19:00:50 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
Click to expand...
Click to collapse
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold "volume down Up" button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Successfully downgraded to 1.16.40.763 from 1.17.40.1234 without root
Thanks!
sziraqui said:
I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Click to expand...
Click to collapse
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
ThanveerAliSayed said:
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
Click to expand...
Click to collapse
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
sziraqui said:
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
Click to expand...
Click to collapse
I got a 412 mb ota update some days before. I downloaded it. Apply it for proceed. Then it start checking system as usual phone restarted. But update did not happened. Instead this same error show up. Then i can only reboot system. Got an update failed message.since that when i check for updates iam not even getting any. May be it will be solved by a factory reset .but even if i get an ota. The update wont proceed .because the recovery wont allow me to do that
And also that wipe cache partition also results the same error .so without solving this error i cant update to the latest MM too :/ .
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
where can i find the recovery file in Stock rom
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Thanks for the Information, Can you please help to find the recovery file in Stock rom.
Click to expand...
Click to collapse
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
I see only boot.img file , i didn't find any recovery.img file, in case if you have already done this probably yes then please share us the steps to get recovery from Stock rom.
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
Click to expand...
Click to collapse
I cant find any recovery.img in the firmware zip. :/
Can you detaily explain that fastboot method as it is for flashing the lolipop recovery for downgrading to 1.13.
Iam a beginner in android. This is my first android phone.
murat124 said:
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
Click to expand...
Click to collapse
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
ThanveerAliSayed said:
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Click to expand...
Click to collapse
Thank you.
Can ZE551KL use the recovery.img from ZE550KL? My ZE551KL has the extra 1700(AWS) band.
Please where are you guys downloading your stock rom from?
The stock zip is NOT flash-able like a custom ROM .zip. That's not how it works. If the Roms you have are custom recovery flash-able, they are not the OEM rom, they have been modified.
All the Roms I have come with a recovery.img file...
Then again if I have to explain how to use fast boot to flash the recovery, there is a good chance you shouldn't be messing around with fast boot.......
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
murat124 said:
thank you.
Can ze551kl use the recovery.img from ze550kl? My ze551kl has the extra 1700(aws) band.
Click to expand...
Click to collapse
no it cannot. Do not try it
Weird ..... I can find recovery.img
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
ThanveerAliSayed said:
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
Click to expand...
Click to collapse
You don't need to unlock bootloader for flashing stock recovery that you downloaded from the above mega drive.
To flash the recovery.img (or any .img) You need to have Adb and fastboot files in your pc as well as Asus Zenfone drivers installed
All info and downloads for adb and fastboot can be found here
Search and download Asus ZenFone 2 laser drivers.
Once you have your pc setup with these tools,
With Administrator priveleges, locate the folder where adb.exe and fastboot.exe files are present. Hold down shift key and right click on that folder and select "open command window here". Then reboot your phone to fastboot mode [power off, hold vol up +power, release power when logo appears]
Connect your device to pc.
Type the following command on cmd
Code:
fastboot devices
Output should be something like this
Code:
FCAHSJSJJAKAK fastboot
This command will check if your device is connected or not
If output is blank, device is not being detected.
To flash recovery.img, copy the recovery.img file to the same folder where fastboot.exe exists and then type
Code:
fastboot flash recovery recovery.img
Output is easy to understand, if it says [OKAY] then flashing succeeded
Tried downgrading ze551kl by fastboot erase system then installing .zip from Asus website (via sdcard). All of the Asus updates except the earliest fail with 'fota return code 403'.
1.14.40.550 installs ok but then boots (gets as far as displaying the wallpaper), gives an error message in german (looks like 'android media process stopped') and goes into boot loop. Anyone seen this before?
Also, any way to build a recovery.img from the Asus update files?
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Leftrand said:
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Click to expand...
Click to collapse
I think OP needs a small correction to enter into FASTBOOT you need to press volume up and power instead of volume down and power buttons
---------- Post added at 05:45 PM ---------- Previous post was at 05:38 PM ----------

Backup data from fastboot on Pixel 4XL

Hi, I am stuck in a bootloop with my pixel 4XL and can only access fastboot/adb. I want to pull my photos from the device before wiping it to factory settings but cannot figure out a way to do it. My bootloader is unlocked so figured it was possible somehow.
I cannot access files under sdcard using abd and changing the recovery image doesn't seem to work (I tried TWRP) using fastboot flash recovery, I get this error:
Writing 'recovery' FAILED (remote: 'No such file or directory')
I am guessing TWRP doesn't work because of Android 10
Have I got any options to try and backup my data?
TWRP doesn't work on devices that had Android 10 pre-installed due to a new partition scheme.
I would try dirty flashing a Google stock image of your current build. It should undo any kernel or Magisk changes for booting purposes.
Google images: https://developers.google.com/android/images#coral
Platform Tools: https://developer.android.com/studio/releases/platform-tools.html
Extract the image ZIP somewhere, extract platform-tools into that same folder. (fastboot/adb, the .bat file and the 2nd image-coral*.zip should all be in the same folder)
Edit the "flash-all.bat" file, line 23 should look like this: "fastboot update image-coral-qq2a.200405.005.zip" (remove the '-w' or your photos/data will be wiped!)
Make sure fastboot devices sees the phone, run the .bat and mostly ignore your phone screen until the .bat says it's done.
Dirty flashing may corrupt your face data which might later require a full factory reset. Normally you would delete the face data before dirty flashing.

Categories

Resources