I followed this guide https://forum.xda-developers.com/mo...e-restore-moto-e-2015-stock-firmware-t3044936
only these last commands fail! How can I solve?
C:\Users\aulaz\Downloads\XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0..
ubsidy-DEFAULT_CFC.xml>mfastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\aulaz\Downloads\XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0..
ubsidy-DEFAULT_CFC.xml>mfastboot oem config carrier vzw
...
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\aulaz\Downloads\XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0..
ubsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.012s
Click to expand...
Click to collapse
Related
well i went to fastboot and erased everything
now it wont boot..
i know it shouldnt boot.. but it wont BOOT.. like turn on.. not even the red light on bootup.. am i ****ed?
also connecting to pc says qhsusb_dload drivers installing but doesnt find any drivers..
C:\adb>fastboot erase system
erasing 'system'...
OKAY [ 3.531s]
finished. total time: 3.531s
C:\adb>fastboot erase adsp
erasing 'adsp'...
OKAY [ 0.861s]
finished. total time: 0.861s
C:\adb>fastboot erase boot
erasing 'boot'...
OKAY [ 0.643s]
finished. total time: 0.643s
C:\adb>fastboot erase dzdata
erasing 'dzdata'...
OKAY [ 1.908s]
finished. total time: 1.908s
C:\adb>fastboot erase radio
erasing 'radio'...
OKAY [ 0.682s]
finished. total time: 0.683s
C:\adb>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.089s]
finished. total time: 1.089s
C:\adb>fastboot erase rcdata
erasing 'rcdata'...
FAILED (remote: partition is not allowed to be erased!)
finished. total time: 0.002s
C:\adb>fastboot erase rpm
erasing 'rpm'...
OKAY [ 0.190s]
finished. total time: 0.190s
C:\adb>fastboot erase sbl1
erasing 'sbl1'...
OKAY [ 0.833s]
finished. total time: 0.833s
C:\adb>fastboot erase sbl2
erasing 'sbl2'...
OKAY [ 0.188s]
finished. total time: 0.188s
C:\adb>fastboot erase sbl3
erasing 'sbl3'...
OKAY [ 0.884s]
finished. total time: 0.884s
C:\adb>fastboot erase tz
erasing 'tz'...
OKAY [ 0.311s]
finished. total time: 0.311s
C:\adb>fastboot erase rcdata
erasing 'rcdata'...
FAILED (remote: partition is not allowed to be erased!)
finished. total time: 0.003s
C:\adb>fastboot erase spcustom
erasing 'spcustom'...
OKAY [ 0.171s]
finished. total time: 0.171s
C:\adb>fastboot erase pg2fs
erasing 'pg2fs'...
OKAY [ 1.741s]
finished. total time: 1.741s
fahadj2003 said:
well i went to fastboot and erased everything
now it wont boot..
i know it shouldnt boot.. but it wont BOOT.. like turn on.. not even the red light on bootup.. am i ****ed?
also connecting to pc says qhsusb_dload drivers installing but doesnt find any drivers..
C:\adb>fastboot erase system
erasing 'system'...
OKAY [ 3.531s]
finished. total time: 3.531s
C:\adb>fastboot erase adsp
erasing 'adsp'...
OKAY [ 0.861s]
finished. total time: 0.861s
C:\adb>fastboot erase boot
erasing 'boot'...
OKAY [ 0.643s]
finished. total time: 0.643s
C:\adb>fastboot erase dzdata
erasing 'dzdata'...
OKAY [ 1.908s]
finished. total time: 1.908s
C:\adb>fastboot erase radio
erasing 'radio'...
OKAY [ 0.682s]
finished. total time: 0.683s
C:\adb>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.089s]
finished. total time: 1.089s
C:\adb>fastboot erase rcdata
erasing 'rcdata'...
FAILED (remote: partition is not allowed to be erased!)
finished. total time: 0.002s
C:\adb>fastboot erase rpm
erasing 'rpm'...
OKAY [ 0.190s]
finished. total time: 0.190s
C:\adb>fastboot erase sbl1
erasing 'sbl1'...
OKAY [ 0.833s]
finished. total time: 0.833s
C:\adb>fastboot erase sbl2
erasing 'sbl2'...
OKAY [ 0.188s]
finished. total time: 0.188s
C:\adb>fastboot erase sbl3
erasing 'sbl3'...
OKAY [ 0.884s]
finished. total time: 0.884s
C:\adb>fastboot erase tz
erasing 'tz'...
OKAY [ 0.311s]
finished. total time: 0.311s
C:\adb>fastboot erase rcdata
erasing 'rcdata'...
FAILED (remote: partition is not allowed to be erased!)
finished. total time: 0.003s
C:\adb>fastboot erase spcustom
erasing 'spcustom'...
OKAY [ 0.171s]
finished. total time: 0.171s
C:\adb>fastboot erase pg2fs
erasing 'pg2fs'...
OKAY [ 1.741s]
finished. total time: 1.741s
Click to expand...
Click to collapse
according to this you should still be ok... you didnt try ad reinstall a copy of hboot... so you should be able to bot to that to use a full ruu to fix the rest
wloftus said:
according to this you should still be ok... you didnt try ad reinstall a copy of hboot... so you should be able to bot to that to use a full ruu to fix the rest
Click to expand...
Click to collapse
i cant
wont boot at all..
connecting to pc gives qhsusb_dload drivers which i got..
apparently im in downgrade state..
got 2 apps named qpst and odin.. dunno what they do..
man.. im freakin out :S
its a gsm phone and i wont be back in my home country for another 2 months..
C:\android-tools>fastboot devices
014FDCF003009004 fastboot
C:\android-tools>fastboot oem unlock\
...
FAILED (remote: unsupported command)
finished. total time: 0.003s
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
Nothing wrong with you, these commands are just not supported by Huawei bootloader (fastboot)
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
MarioGirotti said:
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
Click to expand...
Click to collapse
Yup, sucks big time, especially when trying to develop something
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
^ maybe the green text saying "unlocked" is a hint
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
I will check this evening when I am back from work also this command
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
MarioGirotti said:
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
Click to expand...
Click to collapse
by the way, on this phone it's...
Code:
fastboot oem get-bootinfo
EDIT: IGNORE ME! You already said that in the OP
Yesterday, I was using my phone (Moto E XT1022) and suddenly it got turned off automatically..
When I tried Switching it on,it got stuck on boot logo...
Tried resetting cache/data from recovery mode but it gives the following error
E:Can't mount / cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/platform/msm_sdcc.1/y-name/misc
(No such file or directory)
Click to expand...
Click to collapse
Also tried flashing 4.4.4 Kitkat stock firmware but it doesn't let me flash..Error:
Code:
C:\androide>mfastboot.exe oem lock begin
...
(bootloader) Device is already locked!
OKAY [ 0.023s]
finished. total time: 0.024s
C:\androide>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.488s
C:\androide>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.119s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 6.740s
C:\androide>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.075s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.085s
C:\androide>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.537s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 6.182s
C:\androide>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.208s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (254408 KB)...
OKAY [ 11.958s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.784s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (245298 KB)...
OKAY [ 11.531s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 19.975s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (193465 KB)...
OKAY [ 9.065s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 26.199s
C:\androide>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 2.197s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 7.217s
C:\androide>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.017s
C:\androide>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.020s
C:\androide>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (857 KB)...
OKAY [ 0.120s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.139s
C:\androide>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.016s
C:\androide>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.016s
C:\androide>
Tried unlocking bootloader....
Output:
Code:
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure! FAILED
(remote failure) finished.
total time: 10.440s
Please help me..If I need to flash any other stock firmware,please help me with a link with complete steps...
Thanks in Advance
What OS version were you running before?
The 4.4.4 error suggests you were trying to downgrade.
Tapped from My Moto X
neo.ank said:
What OS version were you running before?
The 4.4.4 error suggests you were trying to downgrade.
Tapped from My Moto X
Click to expand...
Click to collapse
I was running 5.0.2 but the phone turned off automatically...Didn't find any firmware other than 4.4.4 online..
Same thing happn into my moto e, my is xt 1025 and was running 5.02 too.
The only diference is, even with the "error failed" message unlocking bootloader, now the device starts warning that the bootloader is unlocked.
But nothing that I try to downgrade works
Did you get any help?
thakkardeep18 said:
I was running 5.0.2 but the phone turned off automatically...Didn't find any firmware other than 4.4.4 online..
Click to expand...
Click to collapse
You can't downgrade. Best bet right now is flash TWRP and flash a custom ROM if you can't find stock 5.0.2
Tapped from My Moto X
neo.ank said:
You can't downgrade. Best bet right now is flash TWRP and flash a custom ROM if you can't find stock 5.0.2
Tapped from My Moto X
Click to expand...
Click to collapse
Can't.. The bootloader is locked and it gives me error while unlocking bootloader...
How am I supposed to flash TWRP before unlocking bootloader?
Hello my fastboot is useless for exemple
C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
so ... it's possible to fix that ?