[Q] Bricked phone?? - Huawei Ideos X5 U8800

Just flashed official b162 from aurora_ics. I had to wipe caches and data, so the installation process would start. After that phone boots, and goes to "android system recovery", where it says:
E: cant mount @ (or /dev/block/mmcblk0p6)
(invalid argument)
E:Cant mount cache:recovery/command
E:--->open cache partition failed
E:Cant mount @ (or /dev/block/mmcblk0p6)
(invalid argument)
E:Cant mount CACHE:recovery/log
E:cant open cache:recovery/log
E:Cant mount @(or /dev/block/mmcblk0p6)
(invalid argument)
So what could I do?

Wipe data in recovery and it will work.

thanks, it worked! Didn't think it would be that easy

Related

TWRP. E:failed to mount /sdcard (Invalid argument). How to fix that?

I'm trying to flash original amazon ROM with TWRP. But I'm getting:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
Any ideas how to fix this?
UPDATE:
"E:failed to mount /sdcard (Invalid argument)" basically means that your sdcard is not formatted correctly.
I finally found the way to fix this.

[Q] Nexus 7 (2012) Stuck in Startup Loop?

I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
So, update here: I tried to mess with it some more this morning and it seems that it got through the factory reset it was stuck on, but I'm still having issues with constant freezing.
I can get to the "Google" bootup screen and where the colored circles spin around before bringing me to the menus to set up my Wi-Fi and account and all that (like it did when it was first out of the box), but now it continues to freeze while trying to set up these settings.
I managed to input my Wi-Fi password and skip over the rest of the settings in hopes of getting into the system before another freeze and now it gets stuck on a black screen that only shows the "back" arrow at the bottom and the battery and internet indicators at the top right.
Any ideas, guys? I can effectively get into the bootloader now, but attempting to wipe through the recovery menu gives the same errors as before while clearing cache seems to work without issues.
I attempted to use a Nexus Root Toolkit to "Flash Stock + Unroot" with the "Soft-Bricked/Booloop" option selected and everything seemed to work until it got towards the end when the program stops responding.
Now I can't boot into the system at all and I only get a very primitive "bootloader" that says Google (instead of showing the Android) and that's it. I can use the volume keys to browse between "Start", "Restart bootloader", "Recovery mode", and "Power off". Both Start and Recovery mode bring me to the same exact screen while "Restart bootloader" seems to bring me to a complete bootloader, but choosing any of those options brings me right back to the screen without all the info.
I feel like I'm just messing this up more the more I mess with it and I'm not sure what else to try. This Nexus 7 is completely stock, by the way.
MrTripStack said:
I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
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/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
Click to expand...
Click to collapse
Hi, MrTripStack...
Unfortunately, this doesn't sound good at all, I'm afraid...
Your error outputs suggest some kind of partition corruption... and given that your device is running unrooted factory stock (ie, no modifications), I'm inclined to suspect hardware failure with the devices internal eMMC chip. The "failed to mount..." errors are suggestive of this.
The only thing I can suggest, is you attempt to fastboot flash back to factory stock (see download link in my sig. below for the factory image for your specific device).
Full instructions available here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
(But be aware of a known issue fastboot flashing the v4.23 bootloader that ships with some versions of factory stock; fastboot flashing it causes error messages. Pay particular attention to the comment in red, right at the top, in the very first post in the above link/thread.)
-----------------------------------------------------------------------
I'm not optimistic this will work though... if there is a problem with the eMMC chip, you will likely see a whole raft of similar error messages during the fastboot flash process.
For what it's worth... good luck.
Rgrds,
Ged.
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip).
GedBlake said:
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip) .
Click to expand...
Click to collapse
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
MrTripStack said:
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
Click to expand...
Click to collapse
I'm no hardware expert, but I really don't think it's possible to replace the eMMC chip. It's pretty much 'embedded' into the motherboard, and soldered into place by a computer controlled machine, with very fine and very precise spot soldering... way beyond the capability of any human equipped with a soldering iron to attempt.
You could though, consider replacing the motherboard itself, which has been attempted by another XDA member, and apparently, successfully...
http://forum.xda-developers.com/showpost.php?p=54798993&postcount=824
Rgrds,
Ged.

Nexus 7 2012 Unbricked Fastboot Not Working

Hello to all
I Have A Problem .
My Nexus 7 2012 Device Can Not Start , Automatic Going To Recovery Mod And Get This Error On Display :
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
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 to mount /cache (Invalid argument)​
Fastboot Not Working !
Please View Attachment Image .
Please Help Me , Thanks
Up !
safinoor said:
Hello to all
I Have A Problem .
My Nexus 7 2012 Device Can Not Start , Automatic Going To Recovery Mod And Get This Error On Display :
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
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 to mount /cache (Invalid argument)​
Fastboot Not Working !
Please View Attachment Image .
Please Help Me , Thanks
Click to expand...
Click to collapse
Hi, safinoor...
It looks as though you might have some kind of partition corruption... If this is the case, then it's beyond my technical abilities to help you.
However, you mention that you can't access fastboot...
So what happens when you... Long Press VOL DOWN + HOLD.... whilst holding, Long Press POWER BUTTON.
Hold both buttons for a good 30 seconds, and this should 'break' you out of whatever state your Nexus 7 is currently in (and from your screenshot, it looks like the stock recovery from the last version of KitKat 4.4.4 - KTU84P), and boot you into the bootloader, and hopefully from there, you **should**, hopefully, be able to fastboot flash a factory stock image.
Hope this helps..
Rgrds,
Ged.

Zte s6 plus unbrick

Hello i buy zte s6 plus on auction portal.... phone boot only to recovery and stay in.. wipe not helping.... previous owner fash this phone firmware eu version and phone is asian version
The error will somehow as pasted below when You boot into recovery:
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
adb sideload recovery.zip
E:failed to mount /cache
E: failed to set up xpected mounts for install: aborting
installation aborted
E: can't mount /cache/recovery/log
etc etc
Please help me

Error flashing stock ROM Samsung S7 Edge SM-G935FD, FRP lock on, not rooted

Tried wiping cache partition, wiping data/factory reset before flashing stock ROM.
Error flashing stock ROM, used G935FXXS2ERH6_G935FOLB2ERGE from sammobile.
Error after flash stock ROM:
#fail to openrecovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed..
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
Also tried flashing with TWRP via ODIN but failed due to FRP lock.
Can anyone help or have experienced the same issue?
Did you try to FORMAT data (not wipe)?
123keelos said:
Did you try to FORMAT data (not wipe)?
Click to expand...
Click to collapse
Yup, I also did that too.
- Are you flashing the ROM via TWRP?
- Wipe DATA, then FORMAT data
- Head into DOWNLOAD mode and flash the stock ROM via ODIN (make sure there is a file that matches CSC, BL, AP, etc)
123keelos said:
- Are you flashing the ROM via TWRP?
- Wipe DATA, then FORMAT data
- Head into DOWNLOAD mode and flash the stock ROM via ODIN (make sure there is a file that matches CSC, BL, AP, etc)
Click to expand...
Click to collapse
Don't have TWRP because it was blocked by FRP when I flashed ROM with TWRP via ODIN.
6r3k0z said:
Don't have TWRP because it was blocked by FRP when I flashed ROM with TWRP via ODIN.
Click to expand...
Click to collapse
What carrier is your device running from? Some carriers prevent any sort of modifications on their phones (like at&t)
Take a look at this: https://forum.xda-developers.com/s7-edge/help/to-bypass-frp-lock-s7-edge-sm-g935f-fd-t3816607
6r3k0z said:
Tried wiping cache partition, wiping data/factory reset before flashing stock ROM.
Error flashing stock ROM, used G935FXXS2ERH6_G935FOLB2ERGE from sammobile.
Error after flash stock ROM:
#fail to openrecovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed..
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
Also tried flashing with TWRP via ODIN but failed due to FRP lock.
Can anyone help or have experienced the same issue?
Click to expand...
Click to collapse
Can you please clarify which rom,CSC,PDA you had before this failed flashing?
Take care, if you changed the room ,then you try to flash the same room ,always put the 4 .tar ap,bl,cp,csc.
Sent from my Galaxy S7 Edge using XDA Labs

Categories

Resources