Related
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
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 !
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.
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
A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
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
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!