Database Develop

[Q] Question about using HoM and stock

I'm moving this from another forum, to post in the correct place.
From Me
Hello all, I really appreciate all the work that Samurai HL has put into HoB/HoM. I used it in the past, and still I'm very grateful.
I have installed SafeStrap 3.5 on my Bionic, and I've successfully installed CM10 on the Slot 1. However, what I seem to have done is also installed CM10 in the Factory slot. When I boot using that slot, it just sits there and does not do anything. I've tried several times to install the stock roms, but all I get are Error Flashing Zip messages.
My question is about whether HoM will solve my problem or not. Am I able to flash the stock slot with HoM or do I remove SS and try flashing the slot another way? I've searched and searched, but I haven't seen an issue quite like this.
Thanks for all your help.
From SamuriHL
Yes, you can use the House of Moto with the xt875 support file and the latest FXZ to restore stock. Use the KEEP DATA option. You will have to reinstall root and SS recovery once that's done. (No need to uninstall SS).
Click to expand...
Click to collapse
SamuriHL, I did exactly what you said, but now SS doesn't come up and the phone still sits after the M logo goes away.

Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.

SamuriHL said:
Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.
Click to expand...
Click to collapse
Is that the full option?

Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.

SamuriHL said:
Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.
Click to expand...
Click to collapse
I did both methods, and same issue. Do I need to try another FXZ version? I have all 4 from the sbf site.

Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.

SamuriHL said:
Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.
Click to expand...
Click to collapse
Fastboot, and here's the log.
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt875.bat
rebooting into bootloader... OKAY [ 0.006s]
sending 'mbm' (256 KB)... OKAY [ 0.029s]
writing 'mbm'... OKAY [ 0.480s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'mbmloader' (41 KB)... OKAY [ 0.011s]
writing 'mbmloader'... OKAY [ 0.288s]
sending 'mbm' (256 KB)... OKAY [ 0.314s]
writing 'mbm'... OKAY [ 0.477s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
rebooting into bootloader... OKAY [ 0.293s]
erasing 'cache'... OKAY [ 0.012s]
erasing 'userdata'... OKAY [ 0.012s]
error: cannot load 'lbl'
sending 'logo.bin' (854 KB)... OKAY [ 0.065s]
writing 'logo.bin'... OKAY [ 0.281s]
sending 'ebr' (16 KB)... OKAY [ 0.294s]
writing 'ebr'... OKAY [ 0.444s]
sending 'mbr' (16 KB)... OKAY [ 0.294s]
writing 'mbr'... OKAY [ 0.401s]
sending 'devtree' (512 KB)... OKAY [ 0.336s]
writing 'devtree'... OKAY [ 0.447s]
sending 'system' (262144 KB)... OKAY [ 18.319s]
writing 'system'... OKAY [ 21.761s]
sending 'system' (229120 KB)... OKAY [ 16.152s]
writing 'system'... OKAY [ 19.797s]
sending 'boot' (8192 KB)... OKAY [ 0.625s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'recovery' (9216 KB)... OKAY [ 0.949s]
writing 'recovery'... OKAY [ 1.524s]
sending 'cdrom' (12032 KB)... OKAY [ 1.167s]
writing 'cdrom'... OKAY [ 2.052s]
sending 'preinstall' (262144 KB)... OKAY [ 18.260s]
writing 'preinstall'... OKAY [ 22.709s]
sending 'preinstall' (49152 KB)... OKAY [ 3.410s]
writing 'preinstall'... OKAY [ 4.335s]
sending 'webtop' (262144 KB)... OKAY [ 18.449s]
writing 'webtop'... OKAY [ 22.590s]
sending 'webtop' (262144 KB)... OKAY [ 18.218s]
writing 'webtop'... OKAY [ 22.377s]
sending 'webtop' (262144 KB)... OKAY [ 18.481s]
writing 'webtop'... OKAY [ 21.559s]
sending 'webtop' (262144 KB)... OKAY [ 18.192s]
writing 'webtop'... OKAY [ 22.479s]
sending 'webtop' (262144 KB)... OKAY [ 18.124s]
writing 'webtop'... OKAY [ 21.669s]
sending 'webtop' (54016 KB)... OKAY [ 3.768s]
writing 'webtop'... OKAY [ 4.137s]
sending 'radio' (21896 KB)... OKAY [ 1.445s]
writing 'radio'... OKAY [ 2.697s]
rebooting...
Press any key to continue . . .

UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.

SamuriHL said:
UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.
Click to expand...
Click to collapse
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.

Akivaran said:
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.
Click to expand...
Click to collapse
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.

SamuriHL said:
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.
Click to expand...
Click to collapse
Will do.

OMG IT BOOTED. I about lost my crap when I heard the noise. Thank you so much for being patient with me.
What I don't understand is why I was pointed to the other files. What are those for?

They're old versions which can't be used anymore. Delete the old FXZ's so you don't run into this problem again. The sucky part is that it bricked because of the wrong FXZ so had you used the proper one in the beginning, you wouldn't have lost the data partition. Ah well.

Stock ROM slot wiped

As the title says the stock slot was wiped on this Bionic. I have tried using BionicRestorer to fxz to 5.5.893 and 5.9.901 and it encountered a couple of errors. I'm not sure exactly what the mean though. The phone boots to the Moto logo, then the screen goes blank and the soft keys stay lit. Nothing else happens and I have to pull the battery. I tried booting into recovery mode but after selecting recovery I get the android laying on his back with a triangle/exclamation point above him.
I'm not sure what else I can do with this and would greatly appreciate some help. I do have a charger so I'm not worried about the battery getting low. I'm using Linux but do have access to Windows as well.
Here is the command line output from the BionicRestorer script:
Code:
Here we go, I don't stop on errors, once it starts there is no stopping
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.453s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbmloader mbmloader.bin
sending 'mbmloader' (40 KB)... OKAY [ 0.009s]
writing 'mbmloader'... OKAY [ 0.289s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.451s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.007s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase cache
erasing 'cache'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase userdata
erasing 'userdata'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.061s]
writing 'logo.bin'... OKAY [ 0.267s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbr mbr
sending 'mbr' (16 KB)... OKAY [ 0.007s]
writing 'mbr'... OKAY [ 0.397s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.041s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.514s]
writing 'system'... OKAY [ 21.258s]
sending 'system' (229120 KB)... OKAY [ 14.442s]
writing 'system'... OKAY [ 18.771s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.533s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.600s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 0.771s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.499s]
writing 'preinstall'... OKAY [ 22.208s]
sending 'preinstall' (49152 KB)... OKAY [ 3.106s]
writing 'preinstall'... OKAY [ 3.931s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash webtop grfs.img
sending 'webtop' (262144 KB)... OKAY [ 16.516s]
writing 'webtop'... OKAY [ 23.794s]
sending 'webtop' (262144 KB)... OKAY [ 16.515s]
writing 'webtop'... OKAY [ 23.305s]
sending 'webtop' (262144 KB)... OKAY [ 16.507s]
writing 'webtop'... OKAY [ 21.253s]
sending 'webtop' (262144 KB)... OKAY [ 16.521s]
writing 'webtop'... OKAY [ 22.130s]
sending 'webtop' (262144 KB)... OKAY [ 16.514s]
writing 'webtop'... OKAY [ 22.110s]
sending 'webtop' (54016 KB)... OKAY [ 3.408s]
writing 'webtop'... OKAY [ 5.240s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash radio radio.img
sending 'radio' (21768 KB)... OKAY [ 1.377s]
writing 'radio'... OKAY [ 3.805s]
I think I've tried flashing the wrong file in a mad case of Idon'tknowwhati'mdoingsoIshouldhaveleftittheheckalone. So I'm going to try flashing http://sbf.droid-developers.org/download.php?device=12&file=162 with RSD Lite as suggested in some other posts I've read today.

Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd

Ryan11271 said:
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Click to expand...
Click to collapse
That's what I plan on doing. I can still get to recovery and ap fastboot mode. I'm going to d/l rsd now.

The biggest thing is that you cannot flash back to an earlier version than what had been installed. You can only flash the same version or newer.

How about this, I ordered a droid bionic, I'll root and put on safestrap, Once I do all that good stuff I'll make you a stock rom backup and send you the zip. I'll pm you when I get it

Probably doesn't have safestrap installed anymore, so a backup from safestrap wouldn't help.

Ohhh, I didn't think of that XD

Yeah I borked safestrap too but thanks for the offer though. I'm about to reboot into windows and try to rsd what I believe to be the correct version.

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

Need to go back to n6f26u to fix speakerphone.

Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.

bwquestion said:
Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.
Click to expand...
Click to collapse
Did you unlock the bootloader?

sd_shadow said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
I ran the command
fastboot flashing unlock
The result showed OK [0.000s]
The phone screen shows
Device is UNLOCKED. Status Code: 3

I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...

bwquestion said:
I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...
Click to expand...
Click to collapse
Did it boot up?
Sent from my PH-1 using Tapatalk

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone was still showing the same screen. I did not want to mess anything up. When I read your reply I pressed the button on the right to "START".
The circle patterns are doing someting now. I will let you know when it is complete.

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone did boot. The set up ran and the settings show March 5 2017.
Thanks for you time.

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.

bwquestion said:
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.
Click to expand...
Click to collapse
try a factory reset in recovery

As a general cautionary statement, when on a newer release and trying to go to an older release, don't use the flashall method. Fastboot flash system, boot and data separately. You don't want to run a chance that the bootloader downgrades. That might be one of the few ways to brick an N6.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

sd_shadow said:
try a factory reset in recovery
Click to expand...
Click to collapse
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.

bwquestion said:
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.
Click to expand...
Click to collapse
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches
Click to expand...
Click to collapse
N6F26U is showing to be that release. I have loaded the factory image for March 2017, and also the factory image from February 2017 then side loaded the OTA for March 2017. Users still tell me there is an echo on the speakerphone when they talk to me. I can't figure out if I am doing something wrong or if it is just not working.

android 12 fastboot FAILED (remote: Partition system not found)

I get my pixel 4 xl oem unlocked(auto reset after the unlock) and try to flash Android 12 beta image of below link
https://dl.google.com/developers/android/sc/images/factory/coral-spp1.210122.022-factory-0b84a8a1.zip
but durning run flash-all.sh, it failed in writing system, any idea how to deal with this?
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.070s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot_b' (65536 KB)...
OKAY [ 2.810s]
writing 'boot_b'...
OKAY [ 0.221s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.459s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending sparse 'system' 1/4 (262140 KB)...
OKAY [ 10.958s]
writing 'system' 1/4...
FAILED (remote: Partition system not found)
finished. total time: 15.109s

finnally I find the issue:
the fastboot on my test machine(ubuntu20.04) need sudo fastboot to run ,and with sudo , it uses the android studio old fastboot bin. after force replace the fastboot bin to newest , the flash is good
but any idea the fastboot flash need a sudo?