Database Develop

XT1097 Marshmallow TWRP not loading

Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!

Jackson604 said:
Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!
Click to expand...
Click to collapse
You use Volume Up, not the power button to select Recovery. The mismatch is normal because you're flashing a non-stock recovery.

Wow I knew it was going to be something dead simple I was missing, thanks I'll give that a go when I get home!

Need a hand fixing my bootloop

Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.

try with C432B170 file... that may help

amageek said:
try with C432B170 file... that may help
Click to expand...
Click to collapse
Thank you for your suggestion. I grabbed the update.app file for HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU and extracted the BOOT.img, CUST.img, RECOVERY.img and SYSTEM.img with the HuaweiUpdateExtractor. After which I flashed my device again, console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.582s]
writing 'boot'...
OKAY [ 0.650s]
finished. total time: 1.234s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.196s]
writing 'cust'...
OKAY [ 3.977s]
finished. total time: 10.175s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.807s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.712s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.539s]
writing 'system'...
OKAY [ 7.464s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.425s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.435s]
writing 'system'...
OKAY [ 7.380s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.311s]
writing 'system'...
OKAY [ 7.180s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.624s]
writing 'system'...
OKAY [ 7.391s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.378s]
writing 'system'...
OKAY [ 0.809s]
finished. total time: 101.698s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
C:\adb>
However it did not end the boot loop sequence. I am presented with the logo then straight into a black screen. After 2 or 3 minutes the device reboots.
Did I do it incorrectly?

may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img

amageek said:
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.583s]
writing 'boot'...
OKAY [ 0.645s]
finished. total time: 1.231s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.805s]
writing 'recovery'...
OKAY [ 0.896s]
finished. total time: 1.704s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.192s]
writing 'cust'...
OKAY [ 3.968s]
finished. total time: 10.162s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.667s]
writing 'system'...
OKAY [ 7.465s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.933s]
writing 'system'...
OKAY [ 7.410s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.644s]
writing 'system'...
OKAY [ 7.389s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.462s]
writing 'system'...
OKAY [ 7.152s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.775s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.403s]
writing 'system'...
OKAY [ 0.805s]
finished. total time: 102.527s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
Still no luck through, however the reboot cycle is much faster if that means anything.
I transferred the dload folder onto a SD card in order to restore. Holding down the volume up and down buttons along with power for 12 seconds. While the device does vibrate as if command was accepted it never shows anything beyond the logo.
Do you have any further advice or an idea as to what is my device's problem?

can you go to recovery? if yes, then you can wipe everything again and see if that helps..

3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss

amageek said:
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
Click to expand...
Click to collapse
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
marcolomboss said:
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
Click to expand...
Click to collapse
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.

YetAnotherP8Owner said:
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
Click to expand...
Click to collapse
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss

YetAnotherP8Owner said:
Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
Click to expand...
Click to collapse
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)

marcolomboss said:
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
Click to expand...
Click to collapse
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
cristi.blidariu said:
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
Click to expand...
Click to collapse
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.

very interesting. You're in the wrong place, but where
Marcolomboss

YetAnotherP8Owner said:
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
Click to expand...
Click to collapse
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all

cristi.blidariu said:
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.

YetAnotherP8Owner said:
Flashed with the provided images; console results:
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
To enter the recovery mode you need to press and hold volume up and power buttons only

YetAnotherP8Owner said:
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all

cristi.blidariu said:
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?

YetAnotherP8Owner said:
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
Click to expand...
Click to collapse
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app

cristi.blidariu said:
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?

YetAnotherP8Owner said:
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
Click to expand...
Click to collapse
You can extract from any firmware stock recovery using huawei update extractor,what i gave you is a custom recovery,the command is fastboot flash recovery recovery.img
Sent from my ALE-L21 using XDA-Developers mobile app

Soft bricked OP3T

Hello my hope :3
actually i cannot access my recovery or the os, if i start the device, its just a bootloop.
Fastboot is possible, but bootloader is locked and im not able to tick something in the develeloper settings because there is no os anymore.
C:\adb>fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.529s
Click to expand...
Click to collapse
i tried the Snapdragon tool(MsmDownloadTool) also but only get this error: FirehoseWriteData Failed, do you have any suggestions? :c

how to unlock bootloader on bricked mobile?

Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head

iblda said:
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
Click to expand...
Click to collapse
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me

cxyqqz said:
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
Click to expand...
Click to collapse
I paid 15 € !!
I have this message on DC phoenix
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
and the mobile is on fastboot & rescue mode ..
if i try to pass the mobile with flight + & power, it shows me the same screen as the departure:
Error!
Func NO: 10 (boot image)
Error NO: 1 (security verify failed)

this morning another test with DC phoenix
error 10
error 1

iblda said:
this morning another test with DC phoenix
error 10
error 1
Click to expand...
Click to collapse
try : https://www.youtube.com/watch?v=8E43DkUQGMM

cxyqqz said:
try : https://www.youtube.com/watch?v=8E43DkUQGMM
Click to expand...
Click to collapse
dc unlocker does not detect my mobile
only DC phoenix detects it
using the tab "update oeminfo" on DC Phoenix 0.0.0.63, I manage to put the mobile in "PHONE UNLOCKED"
from there I take the opportunity to try to flash BOOT, RECOVERY, SYSTEM with ADB commands.
everything goes smoothly and without error but by restarting the mobile always the same screen with the error in red.
message ADB:
Microsoft Windows [version 10.0.17134.407]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\Users\José>cd c:/adb
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
c:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY [ 0.539s]
writing 'boot'...
OKAY [ 0.683s]
finished. total time: 1.227s
c:\adb>astboot flash recovery recovery.img
'astboot' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:\adb> fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36166 KB)...
OKAY [ 0.894s]
writing 'recovery'...
OKAY [ 1.079s]
finished. total time: 1.981s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 18.360s]
writing 'system'...
OKAY [ 8.003s]
sending sparse 'system' (442517 KB)...
OKAY [ 20.055s]
writing 'system'...
OKAY [ 7.675s]
sending sparse 'system' (459746 KB)...
OKAY [ 17.637s]
writing 'system'...
OKAY [ 7.992s]
sending sparse 'system' (444901 KB)...
OKAY [ 18.492s]
writing 'system'...
OKAY [ 7.729s]
sending sparse 'system' (438286 KB)...
OKAY [ 17.082s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (150611 KB)...
OKAY [ 5.483s]
writing 'system'...
OKAY [ 2.622s]
finished. total time: 138.805s
c:\adb>

I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie

iblda said:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
Click to expand...
Click to collapse
Boot into eRecovery (Volume up whilw connected to PC, or when it shows "bootloader unlocked" warning, hold volume up.) Update to lates firmware
also if you get opportunity to update via HiSuite or from phone settings update it. Try as many times as you can to succed. It will aventually flash latest and greatest firmware.
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck

aciupapa said:
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
Click to expand...
Click to collapse
this method does not work
the mobile does not exceed 5% and then displays SOFTWARE INSTALL FAILED

Try using HurUpdater. Flash twrp, the download all these files.
1. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1727/g1647/v146015/f1/full/update.zip dont change name
2.For dualsim
http://update.hicloud.com:8180/TDS/...l/PRA-L31_hw_eu/update_full_PRA-L31_hw_eu.zip (change filename to update_all_hw.zip)
For single sim http://update.hicloud.com:8180/TDS/...l/PRA-L11_hw_eu/update_full_PRA-L11_hw_eu.zip (change filename to update_all_hw.zip)
3. http://update.hicloud.com:8180/TDS/...15/f1/full/public/update_data_full_public.zip (change filename to update_data_public.zip)
4. http://www.mediafire.com/file/ze5z78dq7zu3sxb/HuRUpdater_0.3.zip dont change filename
put all thesw files in one folder on an external sdcard
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd. Flash the HuRupdater_0.3.zip file and confirm flashing by pressing
volume down. After flashing is complete Reboot your phone. ic everything works, it works. If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)

aciupapa said:
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd.
Flash the HuRupdater_0.3.zip file and confirm flashing by pressing volume down.
After flashing is complete Reboot your phone. ic everything works, it works.
If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
Click to expand...
Click to collapse
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s

my big problem is the installation of a recovery custom.
I can not install it.
the mobile is good in fastboot with bootloader unlocked
but there is no way to flash the recovery:
c: \ adb> fastboot flash recovery twrp-2.8.7.1-p8.img
target reported download size of 471859200 bytes
sending 'recovery' (25880 KB) ...
OKAY [0.676s]
writing 'recovery' ...
FAILED (remote: image verification error)
finished. total time: 0.707s
this is the message I have for all recovery.
EDIT:
and now I have no access unlocking the bootloader with DC phoenix.
Looking for a device in fastboot mode
Device found: 9DCDU17124012020
05/12/2018 23:00:16 Starting to write device in FASTBOOT mode...
Device found: 9DCDU17124012020
IMEI: 862551034926948
Build number: RA-LX1C432B211
Product model: PRA-LX1
Batery state: 4279mv
Not enough credits
he was talking about 72 hours, the time is over.
it's really stealing this dunking thing. the mobile never finally landed, when it was back again it was blocked again.
really **** these huawei as soon as it's bricked.

RIP​
[emoji34][emoji35][emoji34][emoji35][emoji34][emoji35]
​
thanks anyway for your help, even if it did not work ..
Envoyé de mon MHA-L29 en utilisant Tapatalk

iblda said:
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
Click to expand...
Click to collapse
------------------------
In your command line you write: fastboot flash recovery TWRP-3.2.1-0.img
just write: fastboot boot TWRP-3.2.1.0.img.. Then TWRP will open.
Now in TWRP you can install TWRP recovery, after reboot you will be able yo use it.
I hope this help you.

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.