Develop Bugs

[Q] Writing 'system' FAILED, any ideas?

This is my third Nexus to play with and this is the first time I encountered this problem on flashing.
Using fastboot commands seems to flash the other imgs, but specifically on the system.img and radio.img it says
writing 'system.img' . . . FAILED (remote: Write Fail)
I tried searching on different forums even Nexus One's and Nexus S', but still to no avail.
Any ideas? It will be greatly appreciated!
Mico

Corrupt system partitions? Bad cable? These are some possibilities does this process work on other Nexus's ?
Sent from my Galaxy Nexus using xda premium

I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?

Mickosis said:
I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?
Click to expand...
Click to collapse
You don't. And I could never trust Samsung stock cables... very thin and long. That's a lot of room for error. I'm just spitting out possibilities. In hope to narrow itndown
Sent from my Galaxy Nexus using xda premium

So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Update : I tried adb-ing in CWM a nandroid and restore, it didn't spit out an error, but it seems it goes on a boot loop when I boot it up.

Mickosis said:
So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Click to expand...
Click to collapse
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?

anton2009 said:
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?
Click to expand...
Click to collapse
Yes, I tried yakju and takju. The system.img always give that error. Everything else can be pushed and written.

Try 'fastboot erase system', then flash system.
Trying this on windows or Linux?
Which adb version are you using?
Sent from my i9250

I got it fixed, weird, I tried fastboot flashing on a different PC and it worked.
Thanks to all who replied, you may close this now

same problem! can´t format nor flash system.img
I have a stock firmware GSM version 4.04, and suddenly from one day to the other it doesn't boot anymore and I'm stuck in Goggle logo.
Trying to do a factory reset (from recovery) it gives:
--Wiping data...
Formatting /data...
Error mounting/data!
Skipping format.....
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
formatting /sd-ext...
formatting /sdcard/.android_secure...
Error mounting mounting /sdcard/.android_secure!
skipping format...
Data wipe complete...
E:Can't mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed closing /dev/block/platform/omap/omap_hsmmc.0/by-names/misc
(I/O error)
Also trying to mount /system ->
Error mounting /system!
from fastboot if I try to reflash System and userdata ->
C:\galaxy>fastboot flash system system.img
sending 'system' (321251 KB)...
OKAY [ 29.667s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 47.294s
C:\galaxy>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)...
OKAY [ 12.642s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 20.180s
Is it a hardware problem?

Like the post above yours, have you tried another PC?
Sent from my i9250

bk201doesntexist said:
Like the post above yours, have you tried another PC?
Sent from my i9250
Click to expand...
Click to collapse
+1. This.
It is probably a driver or cable issue.

Writing 'system failed'
efrant said:
+1. This.
It is probably a driver or cable issue.
Click to expand...
Click to collapse
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?

nictew said:
Is it a hardware problem?
Click to expand...
Click to collapse
Per the I/O error, I would say yes, there's a hardware problem.

nictew said:
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?
Click to expand...
Click to collapse
have you tried erasing first, then flash? in fastboot?

Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
so, hardware issue ? anything i can try to fix it (soft/hard)? replacing the motherboard would work ?
thanks in advance !

julienvt said:
Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
I am having the same issue
Click to expand...
Click to collapse

Hi,
you can see the full discussion about my issue here:
http://forum.xda-developers.com/showthread.php?t=2309568
the phone's been sold for pieces...
let me know if you managed to solve this !

Possible to Recover Data with Fastboot Only?

Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?

Phylum said:
Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?
Click to expand...
Click to collapse
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.

Petrovski80 said:
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.
Click to expand...
Click to collapse
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only

qtwrk said:
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only
Click to expand...
Click to collapse
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM

kyokeun1234 said:
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM
Click to expand...
Click to collapse
so , we can use ADB commands in Recovery just as the same way we do in Android ???

qtwrk said:
so , we can use ADB commands in Recovery just as the same way we do in Android ???
Click to expand...
Click to collapse
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?

on$ said:
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?
Click to expand...
Click to collapse
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app

Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
mrgnex said:
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??

on$ said:
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??
Click to expand...
Click to collapse
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Click to expand...
Click to collapse
OK- so here's what I get
>fastboot boot recovery.img recovery
cannot boot a boot.img *and* ramdisk​
however if I use the OTHER command
>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7890 KB)...
OKAY [ 0.613s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.760s​
on my phone the initial fastboot display reads as follows:
AP Fastboot Flash Mode (S)
10.9B(*) (SHA-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 32GB
Device is LOCKED. Status Code: 0
Battery: OK
Transfer Mode:
USB Connected
Invalid image size for partition recovery​
it gave me the same response for both the Clockwork Recovery and the clockwork Touch Recovery which I copied into the directory and renamed "recovery.img" in both cases... going to try the TWRP and oudhs next..but I'm wondering if I might actually have a variation of the xt926 and not know it?? (it is a droid razr maxx HD)... any other suggestions??

Your device is locked. But when you unlock it you'll lose all your data..
Sent from my Galaxy Nexus using xda app-developers app

Similar issue
mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s

xtravaluemeal said:
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s
Click to expand...
Click to collapse
Can you still boot into the OS?
If you can remove an app and see what happens, if moments later or after reboot the app is there again your EMMC might be fried.
To check that lock the bootloader. If that is locked upon reboot you're fine, if not the EMMC is fried. If this succeeds though your data is lost.
If all this does not apply to you, then it is probably a driver culprit.

Remove encryption fastboot

I have am unlocked bootloader with TWRP recovery.
My company forces encryption and I accidentally encrypted my Verizon HTC One. I used it for a while and I wanted to update the ROM. I did a hard reset from TWRP but that did not remove the encryption. I did the advanced wipe and chose every option on the list. Now the phone wont boot up. I can still get into recovery but I can't do anything from recovery. None of the partitions can be mounted so the wipes do not work.
my questions:
Is there a way to remove the encryption from TWRP?
If not, is there a way to remove encryption from fastboot?
I ran these and both failed:
fastboot.exe -w
erasing 'userdata'...
FAILED (remote: not allowed)
fastboot.exe flash zip update.zip
sending 'zip' (1086411 KB)...
OKAY [ 39.503s]
writing 'zip'...
FAILED (remote: not allowed)
What options do I have at this point to restore the phone?
Thanks,

Resolved
To give more information on this, the option "Format Data" under "Wipe" in TWRP would not remove the encryption. It kept giving an error that it could not access /data.
Through fastboot I saw that I could only access and flash /system and /boot. I could do anything with /data and /cache.
I am not certain if this was a TWRP issue or not but for those interested I fixed this by flashing clockwork recovery through fastboot. From clockwork I was able to flash wipe /data and /cache and that took the encryption off. I then flashed the ROM using adb sideloade feature in recovery.
killershot20 said:
I have am unlocked bootloader with TWRP recovery.
My company forces encryption and I accidentally encrypted my Verizon HTC One. I used it for a while and I wanted to update the ROM. I did a hard reset from TWRP but that did not remove the encryption. I did the advanced wipe and chose every option on the list. Now the phone wont boot up. I can still get into recovery but I can't do anything from recovery. None of the partitions can be mounted so the wipes do not work.
my questions:
Is there a way to remove the encryption from TWRP?
If not, is there a way to remove encryption from fastboot?
I ran these and both failed:
fastboot.exe -w
erasing 'userdata'...
FAILED (remote: not allowed)
fastboot.exe flash zip update.zip
sending 'zip' (1086411 KB)...
OKAY [ 39.503s]
writing 'zip'...
FAILED (remote: not allowed)
What options do I have at this point to restore the phone?
Thanks,
Click to expand...
Click to collapse

Fastboot failing

Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.

Terrarist said:
Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.
Click to expand...
Click to collapse
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery

Thant said:
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery
Click to expand...
Click to collapse
This is a big problem. I've got the burnt out IC that blacks out the screen so unless I connect to a monitor I can't see anything. And I have a working MHL cable but it doesn't work in recovery or bootloader mode. Sweating profusely now

Ascend P6-U06 stuck on boot loop suddenly

Hi, XDA community.
I got this phone today and user reported that suddenly is boot looping until battery dies.
When trying to wipe, stock recovery prompted:
Code:
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
I tried the following so far:
============================================================================
(#1)
If I wipe data or cache I get a big FAIL message and then
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
cust copying files...
copy cust files system error!ret = -1
I have no info if it's running JB or KK, nor B116 or whatever (I assumed it might be running JB).
============================================================================
(#2)
I can ADB and FASTBOOT to it, but device cannot be recognized properly.
Code:
C:\huawei>adb.exe devices
List of devices attached
? recovery
C:\huawei>adb.exe reboot bootloader
C:\huawei>fastboot.exe devices
????????(?(???O?(???????(?(? fastboot
I think that the bootloader is locked.
Code:
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) locked
OKAY [ 2.201s]
finished. total time: 2.201s
I tried to unlock it with something I found somewhere and apparently it worked:
Code:
C:\huawei>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
I tried to delete the stock recovery and install TWRP, some other Open Recovery, and it prompted OKAY.
However after rebooting to recovery, is gone, I faced the exact same stock recovery with the same E:failed to mount /cache (Invalid argument) and the big FAIL when trying to wipe.
When going back to ADB and FASTBOOT, the bootloader is back to locked status. I can unlocked again (somehow) with the UUUUUUU thing but I'm not sure if this is actually flashing something.
============================================================================
(#3)
I tried to download Ascend P6 Software (P6-U06,Android 4.4.2,Emotion UI 2.3,V100R001C00B520,Latin_North_America-Channel,05011SYH).zip from the main portal (I am located in LATAM).
http://consumer.huawei.com/ve/support/products/manuals/ascend-p6-ve.htm
I got a UPDATE.APP file of 1.61GB. I copied the file on a 4GB microSD leaving it on the root under dload folder, inserted on the phone and rebooted using VOL+ VOL- combination, not plugged on the USB.
It didn't work. I ended in the same stock recovery with the E:failed to mount /cache (Invalid argument) error and the big FAIL again if tried to wipe.
I am running out of ideas. I will try to get in touch with Huawei later to see if I can get a bootloader unlock code for this phone since I cannot get the Product ID with the *#*#whatever, of course because is bricked.
Does anyone have anything that I might be missing here?
Should I tried with a 4.2.2 stock update.app instead of this 4.4.2?
Thank you so much for your time.
Hope to hear back from anybody.
UPDATE:
============================================================================
(#4)
I tried to extract and flash the boot, recovery, efi, system, cust, userdata, cache images from the 4.4.2 UPDATE.APP with the latest HuaweiUpdateExtractor_0.9.9.3 I found here. I used the fastboot flash for that (I had to unlock the bootloader again with the UUUUUUU command).
It took all of them with OKAY messages, excepted for the system one which prompted.
Code:
target reported max download size of 838860800 bytes
Invalid sparse file format at header magi
And when rebooting, it came back to the boot loop in the ASCEND logo, and when VOL+ VOL- same thing, back to stock recovery with mount /cache error and the BIG FAIL message when trying to wipe.
I am not sure if the thing that I keep getting the bootloader back to locked status everytime and reboot the phone is a bad sign.
Still no progress... will continue tomorrow.

Try wiping all infastboot and then reflashing clean. Files to make the prio list are boot.img recovery.img and cust.img Dont reboot untill you reflashed the files or you will get to a hard brick. So make a wipe and right after that flash. No reboots inbetween.
Sent from my SM-G850F