Develop Bugs

[Q] Galaxy Nexus Memory problem? can´t format

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?

Same problem
I have the same problem, cant erase, or flash data and cache. Can any help with this?

same boat here. except on a g3

Sounds like you need odin

Is your bootloader unlocked?
Have you flashed the latest bootloader, i.e., LC03, before trying to flash the system image?
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Is your bootloader unlocked?
Have you flashed the latest bootloader, i.e., LC03, before trying to flash the system image?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
good call!

This fix your problem? Unlock boot loader

I have a Verizon CDMA (toro) of this phone. I am Having the same exact problem. So far i've tried flashing stock from the toolkit, I've tried manually pushing all files through fastboot. and i've also tried recovering through odin, all with proper files for my device(toro files). None have worked so far.
None of the partitions will mount at all or do anything. The bootloader is unlocked. I've even tried relocking the bootlocker, so that i can try to bring it back to the Verizon store, but it will not stick, as soon as i reset the bootloader it shows as being unlocked again. When accessing the recover the phone also shows right away all the mounting errors pertaining to the cache
E:Can't mount /cache/recovery/command
E:Failed closing /dev/block/platform/omap/omap_h
smmc. 0/by-name/misc
(I/O error)
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_h
smmc. 0/by-name/misc
(I/O error)

I have something similar. Bootloader unlocked CWM flashed tried wiping in recovery, get "error mounting /data" and the rest of it. Get nowhere. Seems my sdcard is a bit screwed up. Tried Odin. Locks at userdata. Tried fastboot erase userdata. Have lastest bootloader LC03.
Could it be a hardware problem? or something else entirely?

extract userdata.img from stock rom, flash it over with fastboot.
sent from my i9250

bk201doesntexist said:
extract userdata.img from stock rom, flash it over with fastboot.
sent from my i9250
Click to expand...
Click to collapse
The same thing happened to me, but when I use the command "fastboot flash userdata userdata.img" the phone stucks on this moment: writing userdata.img and I can't solve my problem. Please help us.

whee1s said:
The same thing happened to me, but when I use the command "fastboot flash userdata userdata.img" the phone stucks on this moment: writing userdata.img and I can't solve my problem. Please help us.
Click to expand...
Click to collapse
This is exactly what happens to me too. Any solution would be greatly appriated.

Sounds like you all need to start studying up on Odin flashing.
DO NOT just jump in there and do it....read read read and read some more.
I'm certain that you can look up my old posts and find some specific directions and links to everything you'll need.
ODIN is the only thing that will recover your borked phones, every time.

Is ODIN equivalent to an sbf on Motorola?
Sent from my MB870 using xda app-developers app

ODIN would be comparable to RSD lite. It the Samsung software you run on the PC to flash.

Odin will run on a locked up phone.
Odin will restore all partitions and the file table.
It will also restore a borked boot image.
It will recover a bricked phone as long as there is no hardware problem causing the brick.
https://developers.google.com/android/nexus/images
You'll find every stock Gnex image there....all made to run on Odin.
http://forum.xda-developers.com/showthread.php?t=1671969
You can get a good idea of how it works here....be careful, some things are a bit different (as in we have no home key on a Gnex so ignore any calls to use it).
http://forum.xda-developers.com/showthread.php?t=1347899
You can get the mobile (on phone) version of Odin here (I do not know how this works as I have never used it myself).
http://www.google.com/url?sa=t&rct=...noHIBA&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw
That should be a direct D/L of Odin 3 1.85 which I use

n2ishun said:
[snip]
https://developers.google.com/android/nexus/images
You'll find every stock Gnex image there....all made to run on Odin.
Click to expand...
Click to collapse
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hehe, just to add, these are fastboot images.
Beamed from Maguro

efrant said:
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then I guess they didn't work when I used them either ???
If you KNOW how to use Odin you can use numerous different image types and some files need a .pit file and some do not.
There is a reason for everything.
Just because you cannot see the reason does not negate the fact that one exists.

n2ishun said:
Then I guess they didn't work when I used them either ???
If you KNOW how to use Odin you can use numerous different image types and some files need a .pit file and some do not.
There is a reason for everything.
Just because you cannot see the reason does not negate the fact that one exists.
Click to expand...
Click to collapse
Interesting. Please do share how you flashed those images from the link you posted in odin. I always re-packed them into an odin-flashable tar, but if you found a way to do it using the files in that link without repacking, I would really like to know.
Sent from my Galaxy Nexus using Tapatalk 2

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

[Q] Frozen at Google Screen

(Repost after posting this in the wrong section)
Hello there. A few days ago I was able to update (finally) my Nexus 7 2013 WiFi version to KitKat. However, during some weird screen freezing issues, the tablet refuses to go past the Google screen. I am able to get into fastboot and recovery, but when I try to wipe the device, I get a lot of "failed to mount cache" messages.
The root toolkit also fails because of this, and even sideloading won't work. When I try to unlock the device, I get the blue text screen, but then it freezes at "erasing cache" or something to that effect. Any ideas on how I can fix this? Thanks!

Maybe your cache partition got corrupted. Have you tried fastboot flash cache cache.img? How about just a normal full factory reset from recovery? It could also be a problem with recovery, in which case you would do the above fastboot but replace cache with recovery.

prsterero said:
Maybe your cache partition got corrupted. Have you tried fastboot flash cache cache.img? How about just a normal full factory reset from recovery? It could also be a problem with recovery, in which case you would do the above fastboot but replace cache with recovery.
Click to expand...
Click to collapse
Thanks a lot for the reply!
I tried the cache.img, and it still said "erasing cache..." for 10 minutes without any sign of advancing. I tried the recovery.img, and it said this:
fastboot flash cache recovery.img
sending 'cache' (7424 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
Which I don't understand since it is hooked up and appears under "fastboot devices"
Thanks again for the assistance!

ZReese23 said:
Thanks a lot for the reply!
I tried the cache.img, and it still said "erasing cache..." for 10 minutes without any sign of advancing. I tried the recovery.img, and it said this:
fastboot flash cache recovery.img
sending 'cache' (7424 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
Which I don't understand since it is hooked up and appears under "fastboot devices"
Thanks again for the assistance!
Click to expand...
Click to collapse
That's because you made a typo. It's fastboot flash recovery recovery.img

prsterero said:
That's because you made a typo. It's fastboot flash recovery recovery.img
Click to expand...
Click to collapse
D'oh, how dumb of me. So I went to try that out, and it stopped me because it says the device was locked, and due to the aforementioned freezing at erasing userdata, I can't get further.
fastboot flash recovery recovery.img
sending 'recovery' (7424 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s

ZReese23 said:
D'oh, how dumb of me. So I went to try that out, and it stopped me because it says the device was locked, and due to the aforementioned freezing at erasing userdata, I can't get further.
fastboot flash recovery recovery.img
sending 'recovery' (7424 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
Click to expand...
Click to collapse
What about "fastboot format cache"

prsterero said:
What about "fastboot format cache"
Click to expand...
Click to collapse
Just tried that for about 20 minutes. It's stuck on " erasing 'cache' ".
Thanks again for the help.

Have you tried re-entering bootloader? I think sometimes if you try doing everything in one session it can get stuck. Do fastboot reboot bootloader. Then try formatting cache again.
prshosting.org

prsterero said:
Have you tried re-entering bootloader? I think sometimes if you try doing everything in one session it can get stuck. Do fastboot reboot bootloader. Then try formatting cache again.
prshosting.org
Click to expand...
Click to collapse
Did the reboot and tried again. Waited about 20 minutes, and still stuck at "erasing 'cache ". I assume it doesn't take anywhere near this long. T_T

ZReese23 said:
Did the reboot and tried again. Waited about 20 minutes, and still stuck at "erasing 'cache ". I assume it doesn't take anywhere near this long. T_T
Click to expand...
Click to collapse
I think it should only be a few minutes or so. Are you using the factory cable and have you tried different USB ports? Maybe we can use team viewer and I can take a look if you have some time to kill lol
prshosting.org

prsterero said:
I think it should only be a few minutes or so. Are you using the factory cable and have you tried different USB ports? Maybe we can use team viewer and I can take a look if you have some time to kill lol
prshosting.org
Click to expand...
Click to collapse
I have tried two different cables and moved it around to different USB ports per past suggestions. It just seems to stop when I go to format the cache like it won't mount. Maybe the memory became corrupt.
And sorry, I'd prefer not to do the team viewer, but I am following your directions accordingly!

ZReese23 said:
I have tried two different cables and moved it around to different USB ports per past suggestions. It just seems to stop when I go to format the cache like it won't mount. Maybe the memory became corrupt.
And sorry, I'd prefer not to do the team viewer, but I am following your directions accordingly!
Click to expand...
Click to collapse
Is it just cache it can't format? Is it able to do anything else like data?

prsterero said:
Is it just cache it can't format? Is it able to do anything else like data?
Click to expand...
Click to collapse
I tried to format userdata and cache, and both hang at "erasing" without any indication of moving further.

ZReese23 said:
I tried to format userdata and cache, and both hang at "erasing" without any indication of moving further.
Click to expand...
Click to collapse
Maybe the computer is low on resources and can't complete the operation. Have you tried rebooting?
prshosting.org

lol, I don't think it's that. I have tried it out of a cold reboot do to messing around with the different tools that are available, and each time I tried it things hung there. =[

If everything else fails and you already wiped your data off it, you can try flashing the stock image from Google and use it as a fresh starting point.

Yeah, that's just the thing. There's no way for me to flash it, it seems. I can't unlock the bootloader, and when I go to flash it using Recovery, it just tells me it can't mount the cache. E: so on and so forth.

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

after encryption rom flashing soft brick help

condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains

try to use EMMA with UB to restore your phone.
VooDoo.maGiK said:
condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains
Click to expand...
Click to collapse

will do, i think i may have had given emma a shot at saving my little z1c but will double check to be sure, what is UB? cant seem to find anything related to that acronym
cheers for the tip

Unlocked bootloader
Wysłane z mojego D5503 przy użyciu Tapatalka

cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee

VooDoo.maGiK said:
cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee
Click to expand...
Click to collapse
if flashtool fails and you have luckily a unlocked bootloader and fastboot works you can allways restore your phone with EMMA.
unfortunately EMMA works only with unlocked bootloader.
thanks for the offer. but to me it is enough that the phone working again :good: