Develop Bugs

Problem with flashing inc2

Hi, I have a Droid Incredible 2 that I rooted and installed a custom rom on, and everything went great for a about a week, then suddenly one day it just rebooted and would not go past the HTC screen. Now if I turn it on it just sits at the white HTC screen and does nothing. I can go in to recovery and it displays these errors:
E:Can't mount /cache/recovery/command
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
I first tried to do wipe data/factory reset and install a new rom, but every rom I try to install fails.
If I go to mounts and storage and try to format something I get an error, for example if I go to format /cache then I get:
Formatting /cache...
Error formatting /cache!
I get the same result not matter what I try to format from there. If I do wipe cache partition from the main menu it says it completed. If I do wipe Dalvik cache the screen scrolls and says nothing, does not say if it worked or didnt work. If I run Fix permissions is just says Done!
Lastly I tried to reflash recovery through ADB, it will do the first part (writing the file) and say OK! But when it gets to the second part it just sits there... and does nothing... I left it for over an hour and nothing. I have to pull the battery from the phone at this point.
So now I am at a loss of what to do since nothing wants to flash to it?
Revolutionary CWM v4.0.1.4 with S off

[Q] I think I bricked my KF

Ok people so I think I F***** up royaly. I had my KF for months now and swaps plenty of roms on i butthe other night I was flashing a rom and accidently erased everything off the KF. Now it won't boot flashed rom. It says installaton success but follows with e: cannot load or something in that effect. I finally got my computer to recognize KF and mount but it won't boot custom rom. it'll either stay stuck on the triangle screen, back to TWRP or boot but screen stays black. Idk what else to do . I tried dozens of things and I feel that my head is going to explode. Please someone help.
Btw when using KFU I get
ABD status offline
Boot Mode 0x5003

Anyone?

mr.f20b said:
Anyone?
Click to expand...
Click to collapse
Patience Grasshopper...
Did you remember to wipe system and factory reset before flashing the ROM?

yea I did. after it's done installing it says
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: cannot load volume /misc!
E: failed to mount /cache (invalid argument)
what am I doing wrong?

I finally got it to boot but now it's stuck on the boot animation..
Scratch that, I finally got it to work. Got it to normal boot. kept freezing on me but instead of holding the power button, i rebooted thru twrp. Did the latest update thru KFU , rebooted and did sustem wipe and factory reset, reinstalled and currently running Cyanogen Mod 9 Thanks for the help soupmagnet

In recovery, enter the following commands and post the results
Code:
adb shell
parted /dev/block/mmcblk0
print

Cache Errors in recovery

Hi Guys. I need some advice. I've been struggling with this issue for quite a while and no matter what I cannot solve my problem, many hours googling this issue has not been successful.
When I boot into TWRP, I get this error 90% of the time:
Code:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
This initial error doesn't prevent me from flashing the CM ROM but it does prevent me from flashing this kernel. If i wipe cache I can flash the kernel again, but later on, when I update my ROM and boot into recovery I get this problem again, so i have to wipe cache all the time. Though a small inconvinience, i wish i didnt have to do it, especially since it kinda interferes with my cyandelta update process of flashing the kernel right after the rom.
I've attached a log file produced by TWRP.
I get a similar error when using Clockwork Recovery.
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Fresh installs don't work either. I'm hoping this isn't a hardware issue... something about a fried emmc or something like that. Please say it isnt so.

Im having this issue on t999 s3, happened ever since i flashed new cm11 nightly. I cant even access recovert without it reinstalling the same cmupdate script.

Bricked? "E: Failed to mount"

So for some reason my tablet decided to reboot and it got stuck on the Google part of the restart animation.
I ended up going into recovery mode and now if I try to wipe the cache or do a factory reset, I am getting the error:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Can't open cache/recovery/log
Has my device been bricked? Any advice would be greatly appreciated.
Stock ROM, not rooted, 4.2.2

[email protected] said:
So for some reason my tablet decided to reboot and it got stuck on the Google part of the restart animation.
I ended up going into recovery mode and now if I try to wipe the cache or do a factory reset, I am getting the error:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Can't open cache/recovery/log
Has my device been bricked? Any advice would be greatly appreciated.
Stock ROM, not rooted, 4.2.2
Click to expand...
Click to collapse
See if anything in this thread helps you, in short, if the fastboot suggestion given by AndDiSa can't help you, then you may be looking at sending it to asus (or google if you got through them directly).

I had the similar problem with my tablet and I couldn't wipe any partition (but it was after flashing custom recovery or sth.). After reflashing stock ROM in fastboot mode this problem disappeared.

[Q] Stuck on CWM recovery, can't install zip or flash with ODIN

Long history: I was using Ivan_Meler CM 13.1 ROM for ~ 3 months, which was very stable. Last week I downgraded from build 10 to build 9 with only dirty flash and everything was working fine, just some occasionally FC. Then one night I left my phone ran on very low battery and when I woke up I found my GT-N7100 stuck on Samsung boot logo.
I'm still able to access ODIN download mode. When I get into recovery mode (CWM Philz Touch v6.26.6), I immediately get this messages:
E: could not mount /data to setup /data/media path!
E: Can't mount /cache/recovery/command
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: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install
What I've tried so far:
1. Restore Nandroid backup (KOT49H.N7100UBUFNK1) using CWM
->>>>> got E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p13
2. Flash, using both adb sideload and ODIN:
Stock ROM 4.3 (N7100UBUEMK4_N7100ZTOEMK3_ZTO) and 4.4 (N7100UBUFNK1_N7100ZTOFNK1_ZTO), downloaded from Sammobile
->>>> got "NAND write fail" on ODIN and
->>>> on adb sideload the file loads 100% but I got "error:closed" and after "failed to write data 'protocol fault (no status)' "
3. Flash only the hidden.img of the stock ROM's mentioned above, I got "PASS" on ODIN but after phone gets stuck on boot Samsung logo
Tried this guide, using stock 4.1.2 (N7100XXDLJ2_OXA_FACTORY) with and without re-partition
->>>> got "NAND write fail" as well.
So I have ran out of options can anybody please help :crying::crying::crying: I really like my Note 2 and I don't have money to buy a new phone right now.

SDS for 99%

Try flashing the latest stock rom using a different USB cables, different versions of Windows, and different USB ports. If none of these work, the memory chip may be damaged.