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 !

Gnex boot loop after battery dies before cache is wiped

So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!

cvrkickercomp said:
So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!
Click to expand...
Click to collapse
you have flashing stock with pit via odin as an option...

samersh72 said:
you have flashing stock with pit via odin as an option...
Click to expand...
Click to collapse
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler

cvrkickercomp said:
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler
Click to expand...
Click to collapse
Look in verizon forum, you should find odin package
sent from my Galaxy

samersh72 said:
Look in verizon forum, you should find odin package
sent from my Galaxy
Click to expand...
Click to collapse
So I've tried two different things, I've used galaxy nexus toolkit to try and return to stock that way, and i've also tried downloading the odin pda file and phone file and flashing through odin and neither has gotten rid of the boot loop.

What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.

beekay201 said:
What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.
Click to expand...
Click to collapse
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:

cvrkickercomp said:
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:
Click to expand...
Click to collapse
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.

beekay201 said:
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.
Click to expand...
Click to collapse
So i followed the tutorial you said to and i still have a bootloop... nothing failed to flash correctly... I'm so lost

I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...

cvrkickercomp said:
I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...
Click to expand...
Click to collapse
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes

beekay201 said:
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes
Click to expand...
Click to collapse
Will do after work :good: Thanks for the help/guidance

so i'm trying to format all my partitions before i flash anything this time and this is what happened
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot devices
0149CC3816013004 fastboot
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format system
erasing 'system'...
OKAY [ 0.016s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
sending 'system' (12488 KB)...
writing 'system'...
OKAY [ 3.062s]
finished. total time: 3.078s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>
Am i typing the right command to format the bootloader?

So I believe I have a problem with my internal memory. I just tried "fastboot oem lock" and it works, and the phone switches to "lock state - locked" but then when i select reboot bootloader, the phone says "lock state - unlocked" again. Is there any way to fix that?

Anyone? Please help!!

bump:good:

cvrkickercomp said:
bump:good:
Click to expand...
Click to collapse
There's no point locking your bootloader if it's all messed up. Leave it unlocked.
I don't think i can help you much but try this one
Make sure to follow this steps for a clean install. Hope it helps!
http://forum.xda-developers.com/showpost.php?p=44077732&postcount=5

E:failed to mount /data (Invalid argument)

Someone with the same error?
After unlocking the bootloader, I did a Wipe Data/Factory Reset and restart Mate stayed in the "Bootloop Android".
Try Flashing the ROM B923 from FastBoot, but I can not ...
Flashing boot.img
Flashing recovery.img
But system.img, I can not flash.
Then change the Recovery by TWRP (for FastBoot), try doing a Wipe Data/Factory Reset, but the same error appeared, then just turn off the Mate.
Any recommendations?
Thank You.

hasbrone said:
Someone with the same error?
After unlocking the bootloader, I did a Wipe Data/Factory Reset and restart Mate stayed in the "Bootloop Android".
Try Flashing the ROM B923 from FastBoot, but I can not ...
Flashing boot.img
Flashing recovery.img
But system.img, I can not flash.
Then change the Recovery by TWRP (for FastBoot), try doing a Wipe Data/Factory Reset, but the same error appeared, then just turn off the Mate.
Any recommendations?
Thank You.
Click to expand...
Click to collapse
try to make
unpack official firmware ( http://forum.xda-developers.com/showthread.php?t=2433454 ) SYSTEM.img DATA.img
connect phone via fastboot to pc
fastboot erase system
fastboot flash system SYSTEM.img
fastboot erase data
fastboot flash data DATA.img

acbka said:
try to make
unpack official firmware ( http://forum.xda-developers.com/showthread.php?t=2433454 ) SYSTEM.img DATA.img
connect phone via fastboot to pc
fastboot erase system
fastboot flash system SYSTEM.img
fastboot erase data
fastboot flash data DATA.img
Click to expand...
Click to collapse
Thanks.
But, for the HAM, doesn't exist DATA.img, only: CUST.img and USERDATA.img
Code:
C:\Huawei\ADB\ADB>fastboot erase data
erasing 'data'...
FAILED (remote: partition does not exist)
finished. total time 0.000s
C:\Huawei\ADB\ADB>

Solved...
Connect Mate as FastBoot
Install TWRP Recovery
Now we have to do a "Wipe Advenced"
Wipe> Wipe Advanced> System ('system' only)
After "Format Data"
Wipe> Format Data, confirm with "yes"
With this, we recover from these errors: "E: failed to mount / data (Invalid argument), E: failed to mount / system (Invalid argument), E: failed to mount / internal storage (Invalid argument)"

hasbrone said:
Connect Mate as FastBoot
Install TWRP Recovery
Now we have to do a "Wipe Advenced"
Wipe> Wipe Advanced> System ('system' only)
After "Format Data"
Wipe> Format Data, confirm with "yes"
With this, we recover from these errors: "E: failed to mount / data (Invalid argument), E: failed to mount / system (Invalid argument), E: failed to mount / internal storage (Invalid argument)"
Click to expand...
Click to collapse
hallo please help me. After "Format Data"
Wipe> Format Data, confirm with "yes" ---------------> type me FAILED in step format data... and not can flash update.app. typing: E: failed to mount / data or cashe or system...

This post:
sauat said:
Connect Mate as FastBoot as hasbrone said. Than install stock recovery - I took Huawei P6 recovery, works fine. Now you can use the dload method to install a stock rom.
Click to expand...
Click to collapse
Is the solution for your problem...
Thanks @sauat

I got same problem, but it is looking really bad as I'm unable to enter in fastboot mode!

i have same problem ...
i cant Wipe Data/Factory Reset (always fail)
and i tried to Flashing the fastboot.img or recovery.img or (recovery_TWRP_2810.img) by ADB but give me error and fail to write.
I hope someone have the answer.
HUAWEI ASCEND MATE MT1U06
thanks.

melad_thaeer said:
i have same problem ...
i cant Wipe Data/Factory Reset (always fail)
and i tried to Flashing the fastboot.img or recovery.img or (recovery_TWRP_2810.img) by ADB but give me error and fail to write.
I hope someone have the answer.
HUAWEI ASCEND MATE MT1U06
thanks.
Click to expand...
Click to collapse
Usualy flashing .img files is done through fastboot, not adb, so try that but make a wipe (with fastboot that is: fastboot erase system -w). After that make a data wipe.
Sent from my P6-U06

tileeq said:
Usualy flashing .img files is done through fastboot, not adb, so try that but make a wipe (with fastboot that is: fastboot erase system -w). After that make a data wipe.
Sent from my P6-U06
Click to expand...
Click to collapse
i get this error message
fastboot erase system -w
erasing 'system'...
FAILED (remote: Not allowed!
finished. total time: 0.001s

melad_thaeer said:
i get this error message
fastboot erase system -w
erasing 'system'...
FAILED (remote: Not allowed!
finished. total time: 0.001s
Click to expand...
Click to collapse
I am not sure what you are trying to accomplish but you can workaround that problem by unlocking the bootloader as following:
C:\bootCWM\android\huawei\sources>adb.exe reboot bootloader
C:\bootCWM\android\huawei\sources>fastboot.exe oem get-bootinfo
...
(bootloader) locked
OKAY [ 2.220s]
finished. total time: 2.220s
C:\bootCWM\android\huawei\sources>fastboot.exe erase system -w
erasing 'system'...
FAILED (remote: Not allowed!)
finished. total time: 0.000s
C:\bootCWM\android\huawei\sources>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\bootCWM\android\huawei\sources>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
C:\bootCWM\android\huawei\sources>fastboot.exe erase system -w
erasing 'system'...
OKAY [ 0.000s]
erasing 'userdata'...
OKAY [ 0.000s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 0.000s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 0.000s

same problem
Hello !
I guess i have the same problem with my MT1-U06, i can boot into revocery mode, but can't install anything.
Without recovery mode the phone shows the Huawei logo and stops booting with an white android logo.
In recovery mode Phone says:
E:failed to mount /data (Invalid arguments)
Installation aborted
E:failed to mount /cache (Invalid arguments)
E:failed to mount /data (Invalid arguments)
FAIL
E:failed to mount /cache (Invalid arguments)
ensure_path_mounted_failed
E:failed to mount /cache (Invalid arguments)
I can not connect my phone to pc, i am not sure if the drivers are missing.
I installed a few drivers, inkl. HISuite but nothing changed, but i am not sure if this were the right driver for the mate.
Does anybody have a download url for this ?
adb fastboot can not find the phone.
Actually i 've no idea what to do next.

fastboot says:
< waiting for any device >
Meanwhile drivers are installed, but phone isn't recognised :/
I try this on a Win10 machine, maybe thats the problem.

there must be a way to boot your device in bootloader mode (a key combination generally), find what it is, then you can
fastboot devices
your device will show up
and then carry on with whatever it is you want to do in fastboot mode

hasbrone said:
Connect Mate as FastBoot
Install TWRP Recovery
Now we have to do a "Wipe Advenced"
Wipe> Wipe Advanced> System ('system' only)
After "Format Data"
Wipe> Format Data, confirm with "yes"
With this, we recover from these errors: "E: failed to mount / data (Invalid argument), E: failed to mount / system (Invalid argument), E: failed to mount / internal storage (Invalid argument)"
Click to expand...
Click to collapse
thank you so much! it worked.

help me please!!!!
shashanksetty said:
thank you so much! it worked.
Click to expand...
Click to collapse
when i tried this the system wiped successfully and when i formatted the data the error came up and failed please help ALSO could you please help me as there is no OS installed please elp!!!!

shashanksetty said:
thank you so much! it worked.
Click to expand...
Click to collapse
+1 :good:
---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------
hasbrone said:
Connect Mate as FastBoot
Install TWRP Recovery
Now we have to do a "Wipe Advenced"
Wipe> Wipe Advanced> System ('system' only)
After "Format Data"
Wipe> Format Data, confirm with "yes"
With this, we recover from these errors: "E: failed to mount / data (Invalid argument), E: failed to mount / system (Invalid argument), E: failed to mount / internal storage (Invalid argument)"
Click to expand...
Click to collapse
+1 :good: Thank you

I have a very similar problem with an ASCEND P6-U06, the phone won't go into bootloader it just turn on and gets stuck on android logo and then it reboots itself and it keeps going until the battery is drained i guess, I used the 3 button method and it goes into "android recovery system" and all I get in there is:
E:failed to mount /cache (Invalid_argument)
E:failed to mount /cache (Invalid_argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid_argument)
I tried to wipe data/factory reset, wipe cache partition and apply update frome external storage and all that end up saying "FAIL"
I tried to flash trough ADB a TWRP Recovery but adb won't recognize the device, whatever i do in its stuck on "< waiting for any device >"
I dont know what to do next to get my P6 working again, any suggestion? I read up this post but like i said i can't get the device recognized in adb or anything that allow me to flash something.

You don't need to work with adb to get it done. What you need is to get to fastboot mode, then connect it to a computer and flash a custom recovery (twrp). With that you can wipe data partition and work your way from there. Once you have done all that, you can try installing stock recovery and rom.

Solamentezeus said:
I have a very similar problem with an ASCEND P6-U06, the phone won't go into bootloader it just turn on and gets stuck on android logo and then it reboots itself and it keeps going until the battery is drained i guess, I used the 3 button method and it goes into "android recovery system" and all I get in there is:
E:failed to mount /cache (Invalid_argument)
E:failed to mount /cache (Invalid_argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid_argument)
I tried to wipe data/factory reset, wipe cache partition and apply update frome external storage and all that end up saying "FAIL"
I tried to flash trough ADB a TWRP Recovery but adb won't recognize the device, whatever i do in its stuck on "< waiting for any device >"
I dont know what to do next to get my P6 working again, any suggestion? I read up this post but like i said i can't get the device recognized in adb or anything that allow me to flash something.
Click to expand...
Click to collapse
The fastboot and adb drivers are not correctly installed.
Windows has added some kinda security for third party drivers.. Somehow it sometimes detects adb but fastboot drivers are not installed correctly
So, disable the signature verification in windows(search on Google how to do that)
Then again reinstall the drivers then try command: fastboot devices
Then it will detect the devices...
If I was of any help to you please say thanks

Soft bricked and can't flash any ROM

So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )

What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.

redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S

tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.

Did you fastboot erase cache before installing TWRP, as I suggested?

Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.

It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.

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