Phone bricked itself E:failed to mount /cache (invalid argument) - ZenFone 2 Q&A, Help & Troubleshooting

Hey guys!
I hope I can get some help here. Got a ZE551ML Zenfone, it died on me yesterday. It ran out of battery and turned off, then when I recharged it and tried turning it on, it wouldn't boot up. It gets to the Asus logo and the turning circle and just sits there forever. I tried restarting many times, but the result is the same.
I tried going into recovery and wiping cache, but any action in recovery just gives the error:
E:failed to mount /cache (invalid argument)
Just booting into recovery gives that error, mounting /system, adb sideload, factory reset.
I tried doing things in fastboot, but get a similar error on everything:
Code:
Erasing 'cache' FAILED (remote: 'Can not mount the necessary partition')
fastboot: error: Command failed
And same if I try to format or flash anything. Tried to get TWRP, but can't flash it, same error.
I read a lot of threads about debricking, but they're all focused on getting fastboot or recovery up and then just flashing something. My recovery and fastboot work, but I can't flash anything. Is there anything else I can do to debrick it? I'm not an expert so I'm not sure if any of the other tools would be useful, like AFT or xfstk. Is there anything I can flash with them that would restore the partitions or something?
And if it's really a hardware failure, is there any way to get the data off it at least?
Any help would be much appreciated!

It is an eMMC failure. The exact same thing happened with mine and a friend's ZenFone 2 (both 4 GB RAM, 16 GB ROM and 1.8 GHz CPU). eMMC is the internal storage of the phone and to my experience the 16 GB chip was from SK hynix in both the units (H26M52103FMR). The chip does not have high endurance and wears out over time. We got both our motherboards replaced. AliExpress sells motherboards cheap for ZenFone 2.

Yes looks like you're right. The motherboards are close in price to a second hand working Zenfone 2 haha. Looks like it's the end for it.

Related

[Q] How bricked is this Nexus 7? Advice appreciated

A friend asked me to help unbricking his Nexus 7 (Wi-Fi, 2013 version) ("flo") (it's stuck on Google white logo screen that shows after boot-up), as I am the only person he knows who have some custom ROM installing/etc. experience, but I am hardly an expert. I tried my best, but after few hours I am stumped.
I found the guides at XDA and elsewhere, and they all suggest I need to start by unlocking his bootloader. I tried two (similar at core) methods: first, using the command prompt fastboot.exe from the ADK, and second, using the Nexus Rooting Toolkit. The device is detected through fastboot devices command, but after running fastboot oem unlock, fastboot terminal is stuck at (bootloader) erasing userdata... for many minutes (whereas the action should take no more than few seconds). NRT is also stuck; while the device is frozen on the confirmation of unlocking screen. I read somewhere that some USB ports are problematic (3.0?), so whereas I am not sure how to check (in Win 7) which USB ports I have, I tried 5-6 on 2 computers (laptops) I have at home; both provide exactly the same result. I may try a 3rd (work) computer tomorrow, but I wonder if the device is beyond help?
Now, I was able to enter the Stock Recovery mode, too, and it starts with several errors (yellow script at the bottom). I wonder if it means that the internal SD card is gone, or such?
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
same fir last_log and last_install
E:failed closing /dev/block... (I/O error)
Factory reset from stock recovery gives
-- Wiping data...
Formatting /data...
E:failed to mount /cache... and a bunch of can't mount/open followed by
Data wipe complete.
Then more failures to mount/open ending with the I/O error and a final failed to mount /cache (Invalid argument).
Any suggestions what can be tried, if anything, would be appreciated. Just please, if someone links me to a guide to unbricking that starts with "your device has to be unlocked", for pity's sake, remember I cannot unlock this damn contraption, so I need either a solution that bypasses unlocking, or suggestions on how to unlock this given my failure to do so on two computers.

[Q] Bricked Nexus

Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
EDIT: Fixed, formatted data as ext2, ran e2fsck, then formatted as ext4 again, then flashed userdata.img, system.img, and boot.img in fastboot.
CraftedAndroid said:
Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
Click to expand...
Click to collapse
Try using the Nexus Root Toolkit by Wugfresh to unbrick.
It will automatically install the latest stock firmware, making your device as good as new.
Just boot into bootloader mode, plug the device into a computer, open up the program, click "flash Stock", and watch as the magic happens.
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
alexfone said:
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
Click to expand...
Click to collapse
I'm looking much better than you. I only cannot mount /data and anything under it, like /data/media. Yours looks a bit irreversible if I've ever seen irreversible.
Fixed, updating OP
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 09e4b977
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7448 KB)...
Click to expand...
Click to collapse
some attempts from fastboot flash also ends up with failure
any ideas?
fr3ker said:
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
some attempts from fastboot flash also ends up with failure
any ideas?
Click to expand...
Click to collapse
Try doing fastboot flash userdata userdata.img, fastboot flash system system.img, and fastboot flash boot boot.img in that order.
i did that too, I tried flashing tru a lot of method ... it just wont boot at all
does it have anything to do with the partitions? i cant find how to repair a partition for Nexus devices ...
^ So what's it say when you flash each .img individually? You get the "OKAY"?
You say some end in failure which ones? Throw in a fastboot format cache for the hell of it. Your bootloader and baseband are correct?
If you're getting the okay on all images and wiped everything in stock recovery.. I don't know man I might be stuck.
If you figure it out let us know. We can erase and format the partitions, usually you don't even need to use those. Hmm.. I clean flashed flo with just boot system and userdata (bootloader stayed the same as 5.1.1). Worked perfect.
Seems that we're stuck ... I've flashed a custom ROM and works perfect but when I flash any stock firmware it'll stuck at the bootani ... Flashing process were cleared until end ... I get everything as expected. I did everything founded on google and it's still fcuked up ..
Sent from my Z1 using Tapatalk

[SOLVED] Nexus 5X Not Booting after Flashing Pixel Mod2 (/vendor & /system)

Help! I flashed the Android Oreo Pixel 2 Mod over Android Oreo 8.1.0 with my apps and data on it, and then the phone wouldn’t boot. So I went back into the recovery (TWRP 3.2) and tried to wipe the phone. TWRP wiped everything except for /vendor, returning the error “Failed to mount /vendor (invalid argument),” and "Failed to mount /system (invalid argument)". In TWRP I also tried mounting /system and /vendor, but it wouldn't let me check the box. So tried installing the stock android from the google page, and while sending sparse file ‘system’, It says FAILED (data transfer failure(Unknown Error)). Please Help, I’m a pretty much a noob at this kind of stuff.
EDIT: SOLVED
After browsing online, I wiped the phone one more time, re-flashed TWRP, tried a few commands, I tried repairing the file system of /system, re-installed the vendor.img(probably this), then It worked!
I'm just thankful it works now.

Installed .img in the wrong partition from TWRP

So as I just said, by mistake, I installed an image to the firmware partition and suddenly I couldn't install roms anymore, have tried factory resetting, deleting data, some commands that never worked for my device, its shows me the following message: Failed to mount /firmware (invalid argument), what I am thinking to do is flashing the device again starting from zero but how do I do it from the TWRP? Is it really needed or can I do something else to fix my problem?
which partition did you flash? QPST to stock and unlock bootloader

A520F Can get into only recovery and download mode, stuck on samsung logo. ESF empty

Hello guys,
Long story short. Two days ago I tried to install lineageOS, managed to do it = no sim card error. Tried installing 15.1 same, did some wiping, erasing without knowledge or backups. Now installed latest [BALTIC] rom from sammobile, stuck on samsung logo during boot, in recovery mode it says some errors:
No support single-sku
E:Failed to mount /efs (Invalid argument) like 4x times
dm-verity verification failed...
E: Failed to clear BCB message: Failed to find /misc partition
I have no backups. Is it still possible to fix this phone? Or I screwed it up totally?
Thank you
Respectfully,
Tomas

Categories

Resources