[Completed] Can't flash recovery due to low battery (Moto e) - XDA Assist

Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery

xgisse said:
Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Moto E Q&A,Help and Troubleshooting.
Are you able to charge with the device turned off?
___
v7
XDA Assist

Related

How to bring back to original recovery and rom???

I have my Moto G with clockwork mod and Cyanogenmod and I would like to bring back to stock. Any tutorial???
Thanks in advanced and sorry about my english.
return to stock moto g
[Acme] said:
I have my Moto G with clockwork mod and Cyanogenmod and I would like to bring back to stock. Any tutorial???
Thanks in advanced and sorry about my english.
Click to expand...
Click to collapse
Moto G restore
So if you brick your phone or you need to revert to stock the instructions should be:
1 - Download stock firmware
http://forum.xda-developers.com/moto...kxb21-t2805619
2 - Unzip
3 - Open Windows Command Prompt
4 - Using the cd command, change to where the unzipped firmware and mfastboot is
5 - Now enter the commands one by one as shown:
http://forum.xda-developers.com/moto...kxb21-t2805619
[Acme] said:
I have my Moto G with clockwork mod and Cyanogenmod and I would like to bring back to stock. Any tutorial???
Thanks in advanced and sorry about my english.
Click to expand...
Click to collapse
Or go here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Download and flash the zip in recovery.
Then flash stock recovery...
spiritflare said:
Moto G restore
So if you brick your phone or you need to revert to stock the instructions should be:
1 - Download stock firmware
http://forum.xda-developers.com/moto...kxb21-t2805619
2 - Unzip
3 - Open Windows Command Prompt
4 - Using the cd command, change to where the unzipped firmware and mfastboot is
5 - Now enter the commands one by one as shown:
http://forum.xda-developers.com/moto...kxb21-t2805619
Click to expand...
Click to collapse
Thank yoy very much for your reply.
Links are broken.
restore to stock
[Acme] said:
Thank yoy very much for your reply.
Links are broken.
Click to expand...
Click to collapse
Here you go:
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
---------- Post added at 03:56 PM ---------- Previous post was at 03:43 PM ----------
[Acme] said:
Thank yoy very much for your reply.
Links are broken.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Thank you very much for your reply, I try it but something was wrong.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gp
t.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.053s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.107s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.158s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bi
n
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.071s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.im
g
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.380s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.433s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery rec
overy.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.412s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.471s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260913 KB)...
OKAY [ 8.280s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.628s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257716 KB)...
OKAY [ 8.273s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.504s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (232611 KB)...
OKAY [ 7.585s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.103s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HL
OS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.658s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.746s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.033s]
finished. total time: 0.036s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.082s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.135s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.403s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 7.365s]
finished. total time: 7.368s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.040s]
finished. total time: 0.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe reboot
rebooting...
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>
[Acme] said:
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Thank you very much for your reply, I try it but something was wrong.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gp
t.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.053s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.107s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.158s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bi
n
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.071s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.im
g
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.380s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.433s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery rec
overy.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.412s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.471s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260913 KB)...
OKAY [ 8.280s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.628s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257716 KB)...
OKAY [ 8.273s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.504s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (232611 KB)...
OKAY [ 7.585s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 8.103s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HL
OS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.658s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.746s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.033s]
finished. total time: 0.036s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.082s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.135s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.403s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 7.365s]
finished. total time: 7.368s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.040s]
finished. total time: 0.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe reboot
rebooting...
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You have low battery as the error message reads. Charge and try again...
---------- Post added at 07:33 PM ---------- Previous post was at 07:31 PM ----------
skyguy126 said:
You have low battery as the error message reads. Charge and try again...
Click to expand...
Click to collapse
And at the beginning before flashing run"fastboot oem lock begin"
[Acme] said:
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Thank you very much for your reply, I try it but something was wrong.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Before you do anythimg make sure ADB can see your device
Run: adb devices
If not make sure your usb drivers are installed correct
2) make sure your battery is fully charged
3) your bootloader looks locked. Unlock it first.
Click to expand...
Click to collapse
Thank you very much for your reply, I will try it.
[Acme] said:
Thank you very much for your reply, I will try it.
Click to expand...
Click to collapse
Or when the phone is off, hold vol down and power at the same time for 5 seconds. The let go. You should be in boot loader mode.
Device is UNLOCKED. Status Code: 3
[Acme] said:
Device is UNLOCKED. Status Code: 3
Click to expand...
Click to collapse
Look at post #4
I did it! With some errors but done...
Mac-mini:users RamonML$ cd /Users/RamonML/Desktop/mfastboot-v2
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.021s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.439s]
finished. total time: 0.460s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.091s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.505s]
finished. total time: 1.596s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.113s]
finished. total time: 0.192s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.384s]
writing 'boot'...
OKAY [ 0.908s]
finished. total time: 1.292s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.389s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.292s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260913 KB)...
OKAY [ 8.703s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 9.935s]
finished. total time: 18.638s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257716 KB)...
OKAY [ 8.605s]
writing 'system'...
OKAY [ 10.844s]
finished. total time: 19.449s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (232611 KB)...
OKAY [ 7.768s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 18.881s]
finished. total time: 26.649s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.624s]
writing 'modem'...
OKAY [ 1.451s]
finished. total time: 3.075s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.023s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.052s]
finished. total time: 0.052s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.074s]
writing 'fsg'...
OKAY [ 0.088s]
finished. total time: 0.162s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase cache
erasing 'cache'...
OKAY [ 0.357s]
finished. total time: 0.357s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.621s]
finished. total time: 6.621s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.041s]
finished. total time: 0.041s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.040s]
finished. total time: 0.040s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot reboot
rebooting...
finished. total time: 0.001s
Mac-mini:mfastboot-v2 RamonML$
[Acme] said:
I did it! With some errors but done...
Mac-mini:users RamonML$ cd /Users/RamonML/Desktop/mfastboot-v2
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.021s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.439s]
finished. total time: 0.460s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.091s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.505s]
finished. total time: 1.596s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.113s]
finished. total time: 0.192s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.384s]
writing 'boot'...
OKAY [ 0.908s]
finished. total time: 1.292s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.389s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.292s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260913 KB)...
OKAY [ 8.703s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 9.935s]
finished. total time: 18.638s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257716 KB)...
OKAY [ 8.605s]
writing 'system'...
OKAY [ 10.844s]
finished. total time: 19.449s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (232611 KB)...
OKAY [ 7.768s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 18.881s]
finished. total time: 26.649s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.624s]
writing 'modem'...
OKAY [ 1.451s]
finished. total time: 3.075s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.023s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.052s]
finished. total time: 0.052s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.074s]
writing 'fsg'...
OKAY [ 0.088s]
finished. total time: 0.162s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase cache
erasing 'cache'...
OKAY [ 0.357s]
finished. total time: 0.357s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.621s]
finished. total time: 6.621s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.041s]
finished. total time: 0.041s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.040s]
finished. total time: 0.040s
Mac-mini:mfastboot-v2 RamonML$ /Users/RamonML/Desktop/mfastboot-v2/osx-fastboot reboot
rebooting...
finished. total time: 0.001s
Mac-mini:mfastboot-v2 RamonML$
Click to expand...
Click to collapse
You didn't run "fastboot oem lock begin" before flashing.
skyguy126 said:
You didn't run "fastboot oem lock begin" before flashing.
Click to expand...
Click to collapse
Yep! :angel:
When will be I do it???
[Acme] said:
Yep! :angel:
When will be I do it???
Click to expand...
Click to collapse
YOu need to run it at the beginning before flashing.

Help to relock bootloader

hi
i want to relock my phone x1032 gpe with the android 5.1 img and i got some error in the "adb"
here is my log and my phone is x1032 gpe and i was have a custom rom before that with unlock bootloader
please help me
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 2.767s]
finished. total time: 2.783s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.094s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash motoboot m
otoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.156s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.092s]
finished. total time: 1.264s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash logo logo.
bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.187s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash boot boot.
img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.452s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.905s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash recovery r
ecovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.452s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 1.232s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 9.454s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.859s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 9.578s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.656s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 9.580s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.674s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.764s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.827s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash modem NON-
HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.858s]
writing 'modem'...
OKAY [ 1.498s]
finished. total time: 3.372s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash fsg fsg.mb
n
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.589s]
finished. total time: 5.714s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.265s]
finished. total time: 0.281s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 5.023s]
finished. total time: 5.023s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>
Click to expand...
Click to collapse
any help please
I don't know, sorry!

Require some help and some advice if possible.

Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
C:\adb>fastboot oem fb_mode_set
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.172s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.319s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.172s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.687s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.891s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.664s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.883s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257278 KB)...
OKAY [ 9.982s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.097s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 10.125s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.157s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (258384 KB)...
OKAY [ 10.076s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.107s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (252313 KB)...
OKAY [ 9.973s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.004s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (254404 KB)...
OKAY [ 10.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.064s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (258060 KB)...
OKAY [ 10.114s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.161s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76857 KB)...
OKAY [ 3.038s]
writing 'modem'...
OKAY [ 2.036s]
finished. total time: 5.075s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1864 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.210s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Phatzy said:
Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
Click to expand...
Click to collapse
It looks to me like you're trying to flash a firmware that is a downgrade from what was already on the device. It's probably blocking you because it won't allow a downgrade. Flash the version that the device already had on it or flash a newer version.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Phatzy said:
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Click to expand...
Click to collapse
You may have to faatboot flash the individual .img(boot, system, cache, recovery, etc..) files by themselves.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yeah I tried that too. I just get the same errors as this.....
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
Click to expand...
Click to collapse
Phatzy said:
Yeah I tried that too. I just get the same errors as this.....
Click to expand...
Click to collapse
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
I dont think so as I cannot check due to the phone not able to get pass bootloader. I tried to use the fb_mode command but still goes back to bootloader saying filed to start.
Thanks..
Droidriven said:
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse

Bricked Pixel 2 help

Hi
Hope you are all doing great, I have limited experience from rooting my own phones, any help will be appreciated a lot.
After buying a pixel 2 (walleye/google store unlocked ) I wanted to root it like my other phones so I proceeded to unlock bootloader, temp boot twrp and installed magisk.
So far it was fine but gave me a notification that android has an internal error. So I decided to go back to stock and retry rooting. Flashed to stock was great. Set the phone up again, did not root it or anything from stock. When re-enabling the developer options & USB debugging I unfortunately locked boot loader up again.
The phone is stuck at bootloader ERROR: Slot Unbootable: Load Error, going to recovery it goes back to same.
Can't flash cos status locked, cant unlock .
Fastboot FAIL not allowed in locked state.
Download mode Error: Operation denied
Interestingly boot-slot is b, tried to change it , of course not allowed.
getvar all dump below, its what I could extract. Let me know if I can get you more info by running logging etc. that I can.
(bootloader) avb_err:0(0)
(bootloader) is_avb_critical_error:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.
(bootloader) version-main:
(bootloader) imei:
(bootloader) boot-mode:FASTBOOT
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3759
(bootloader) version-baseband:g8998-00202-1803121407
(bootloader) version-bootloader:mw8998-002.0069.00
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD49BFB000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:dtbo:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:1
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) cid:00000000
(bootloader) secure:yes
(bootloader) serialno:
(bootloader) hw-revision:MP1
(bootloader) product:walleye
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
try flashing factory image again.
munchy_cool said:
try flashing factory image again.
Click to expand...
Click to collapse
Hi munchy_cool, first things first , thank you so much for taking out time to reply
I tried flashing stock again, I rechecked if I flashed the right stock (sometimes that is a problem)
----------------------------------------------------------
Sending 'bootloader_b' (38652 KB) OKAY [ 1.055s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.075s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.007s
Sending 'radio_b' (60412 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.672s
rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.007s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: mw8998-002.0069.00
Baseband Version.....: g8998-00202-1803121407
Serial Number........: XXXXXX
--------------------------------------------
Checking product OKAY [ 0.006s]
Checking version-bootloader FAILED
Device version-bootloader is 'mw8998-002.0069.00'.
Update requires 'mw8998-002.0067.00'.
fastboot: error: requirements not met!
Press any key to exit...
--------------------------------------------------------------
Then I tried with --slot to try to change it to a , no luck.
I rechecked the radio img and the bootimage but no luck
Try deuces script instead of stock script.
Worked for me
mrorange2108 said:
Try deuces script instead of stock script.
Worked for me
Click to expand...
Click to collapse
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
--------------------------------------------------------------------
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (status read failed (Too many links))
Finished. Total time: 13.234s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.004s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.013s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.071s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.106s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.661s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.059s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.078s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_a' (404 KB) OKAY [ 0.027s]
Writing 'abl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.048s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_a' (16 KB) OKAY [ 0.016s]
Writing 'apdp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.033s
Sending 'boot_a' (32768 KB) OKAY [ 0.909s]
Writing 'boot_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.929s
Sending 'cmnlib_a' (224 KB) OKAY [ 0.015s]
Writing 'cmnlib_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.035s
Sending 'cmnlib64_a' (292 KB) OKAY [ 0.025s]
Writing 'cmnlib64_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.045s
Sending 'devcfg_a' (60 KB) OKAY [ 0.015s]
Writing 'devcfg_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.228s]
Writing 'dtbo_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.248s
Sending 'hyp_a' (256 KB) OKAY [ 0.016s]
Writing 'hyp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.036s
Sending 'keymaster_a' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.040s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_a' (60420 KB) OKAY [ 1.640s]
Writing 'modem_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.658s
Sending 'msadp_a' (16 KB) OKAY [ 0.016s]
Writing 'msadp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'pmic_a' (52 KB) OKAY [ 0.009s]
Writing 'pmic_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_a' (232 KB) OKAY [ 0.016s]
Writing 'rpm_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'tz_a' (1900 KB) OKAY [ 0.066s]
Writing 'tz_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'vendor_a' (346964 KB) OKAY [ 9.482s]
Writing 'vendor_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.503s
Sending 'xbl_a' (3720 KB) OKAY [ 0.114s]
Writing 'xbl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.136s
Flashing System A
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 16.225s]
Writing sparse 'system_a' 1/4 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 29.095s
Flashing System B
Sending sparse 'system_b' 1/2 (524284 KB) OKAY [ 16.205s]
Writing sparse 'system_b' 1/2 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 19.821s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_b' (404 KB) OKAY [ 0.026s]
Writing 'abl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.046s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_b' (16 KB) OKAY [ 0.006s]
Writing 'apdp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.026s
Sending 'boot_b' (32768 KB) OKAY [ 0.901s]
Writing 'boot_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.921s
Sending 'cmnlib_b' (224 KB) OKAY [ 0.019s]
Writing 'cmnlib_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'cmnlib64_b' (292 KB) OKAY [ 0.021s]
Writing 'cmnlib64_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
Sending 'devcfg_b' (60 KB) OKAY [ 0.011s]
Writing 'devcfg_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.030s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.233s]
Writing 'dtbo_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.252s
Sending 'hyp_b' (256 KB) OKAY [ 0.015s]
Writing 'hyp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.038s
Sending 'keymaster_b' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_b' (60420 KB) OKAY [ 1.639s]
Writing 'modem_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.659s
Sending 'msadp_b' (16 KB) OKAY [ 0.013s]
Writing 'msadp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'pmic_b' (52 KB) OKAY [ 0.010s]
Writing 'pmic_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_b' (232 KB) OKAY [ 0.017s]
Writing 'rpm_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'tz_b' (1900 KB) OKAY [ 0.063s]
Writing 'tz_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.031s
Sending 'vendor_b' (346964 KB) OKAY [ 9.583s]
Writing 'vendor_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.604s
Sending 'xbl_b' (3720 KB) OKAY [ 0.109s]
Writing 'xbl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.132s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Format Userdata[Y/N]?y
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: XXXXXXX
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4497 KB) OKAY [ 0.138s]
Writing 'userdata' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.656s
NoobHelp said:
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
Click to expand...
Click to collapse
Surely there is a way to fix this? My getvar returned nearly identical information, except that my slots were all successful.
Did you have any luck with this or know anyone that has?
Thanks,
Alex

Asus zenfone max pro m1 can't unlock bootloader

hi,
I tried to use the unlock.cmd in command promt via fastboot, half of it worked it only unlocked my frp but it said "failed: Unknown Command !". Please help, is there any other way I can unlock my bootloader? My max pro m1 won't boot and doesn't have access to recovery mode. Thanks
C:\adb>C:\adb\unlock.bat.cmd
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is user
target reported max download size of 536870912 bytes
sending 'IMAUOvZqcpug' (0 KB)...
OKAY [ 0.002s]
writing 'IMAUOvZqcpug'...
(bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.005s]
finished. total time: 0.009s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.003s
All is download
Maybe update your adb/fastboot

Categories

Resources