So i know there is alot of posts about this error but after reading many on different sites and trying just about everything im exhausted and really need some help.
A day after i had updated my streak to dj_steve's 1.9.0 everything was working fine, then after a sudden reset my phone would just loop on the dell logo. I went into clockwork mod's recovery and it had an error of:
E: Can't find MISC:
E:Can't mount /dev/block/innersd0p5
(file exists)
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
E:Can't mout /dev/block/innersd0p5
(file exists)
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
E:Can't mout /dev/block/innersd0p5
(file exists)
(excuse any errors i typed this in by hand)
After reading some posts people had said that it was an inner sd failure so i ran the fast boot test *#301# then option 10 to test inner sd.
Everything passed so that was not the issue
Afterward's i tried installing the 1.9.0 zip(dj_steve) through streak recovery thinking it was an issue with clockwork mod. Unfortunately this did not work either, but i can mount my sd card through the usb cable in streak recovery once again proving its not an sd issue.
After this i followed another thread on installing the stock recovery and rom image, this did not work either.
Next i used streak droid's QDL tool following all instructions and everything passed successfully, at this point things changed for once. I could use the streak stock recovery to apply an update.pkg (I used the stock offical dell rom) however afterwards the streak reboots and sits at the dell logo flashing purple with the 3 lower home led's flashing every 30 seconds or so (it previously was just showing the dell logo for a period of time then restarting). Unfortunately it just sits at this screen, forever...I even left it overnight unplugged and woke up to it drained and when i plugged it in it just did the same thing.
I have also tried a few other things but can't think of them off the top of my head, i've sunk in about 24 hours of non stop reading and flashing to fix this and still turn up with nothing.
Any help would be GREATLY appreciated
I'll even give you some paypal money to buy redbull and stay up to help me fix this. SO MUCH REDBULL
Related
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849
Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.
having the same problem.. so should i try to wipe the cache and see what happens?
I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.
I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?
What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?
@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?
As I cannot post in the thread most probably relevant to this: http://forum.xda-developers.com/showthread.php?t=1590523, I will post here. After running this cleaner, I now receive the following error in CWM:
E:Can't mount /cache/recovery/command
E:Cant 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 had not had this issue before. I am still able to operate CWM with no issues, besides these messages spamming my screen. If anyone can be of assistance?
I am running ICS AOKP 31, with Harsh 1104 kernel. I have flashed 3 different recoveries, 5.0.2.0, 5.0.2.8, and 5.8.1.3. On the 5.8.1.3, because I cannot post in that thread either, I must say it works very well, no issues to report, besides the error above.
Jakkumn
I got the this error too since just getting a new phone cause my previous phone I got off craigslist had a small crack in the corner of the screen so I nullified the phone then flashed the stock recovery back on the phone and told them my phone wasn't starting and ever since I got my new phone I get this message and never got it with my old phone.
So far... the only progress I've managed to make, and it seems to be temporary, is just formatting the /cache partition in CWM. It fixed it for a while, and by a while I mean like 5 minutes. It then returned. So far I haven't run into it again. I'll keep you posted on any progress I make.
Hey guys,
I flashed the leaked firmware when it was released and since then, my DS was a bit slow and had an unbearable battery drain (200 mAh). No battery stats app helped figure out where was the drain from so I thought about changing the firmware again. I flashed the "20.28b.30.0805U_38.03.02.11" one but after flashing, my DS kept displaying the CM9 boot animation for 35 min. I tried the Vol Down + Up + Power combination but it didn't work. I left it another 10 min but it was still stuck. I then removed the battery for a min then inserted it again. Same thing for about 30 min. I removed the battery, inserted it and booted into the bootloader but it detected the radio file and I couldn't access the recovery. Any suggestions how to solve this problem. Could it be an eMMC fried?? Please help
Nothing to do with eMMC.
You're most likely doing 1 or 2 of the following bad things, not to be done:
1) You're installing a ROM without wiping.
2) You unlocked using HTCDev and you're not flashing the kernel through fastboot.
Remove your SD card from the phone, take a card reader, plug it into PC, remove the PG88IMG.ZIP from it, return it to the phone.
or:
Check if your phone is visible to ADB while it's stuck in boot animation, and execute the following command:
adb reboot recovery
I've done nothing from both. I've unlocked via AlphaRevX from exactly a year and the last time I flashed a different ROM from CM9 was 3 weeks ago. I don't have a SD card reader so I'll try ADB. Thanks for the quick reply
Ok, I solved the problem with another way. ADB didn't work and since I don't have a SD card reader, I thought about removing the SD card. It worked and I was able to access the recovery but upon accessing I found the horrible message waiting for me
"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 know that this means that the eMMC chip was fried. I thought about flashing the cache even though I know it wouldn't work but unbelievably, it WORKED!!! I can't understand how it worked but at least my phone is up and working again . One question though, the battery drain still exists but it's a bit smaller. Leaving the mobile it keeps getting between 10 and 20 mA and using it instantly jumps to 80-150 mA. Any suggestion how could I know what's draining the battery??
Idle current of 10-20mA is fine, jumps to 80-150mA aren't. Something is waking up your phone, either one of the apps that doesn't play well with ICS (did you restore apps from backup or reinstall?), or one of the system services has some trouble. You could try looking at logcat output when the phone is in sleep mode to see what's waking up the phone.
Good work wiping /cache. Not all /cache mounting errors are fried eMMC, sometimes the partition just gets corrupted.
That does not always mean fried emmc chip. It happened to me once changin to a 3.0 sense rom to a 3.5 sense one and the only thing I did was format /cache with 4ext recovery. If not you can try this http://forum.xda-developers.com/showthread.php?t=1146601 Look where it says Fried emmc chip?
Karimmunir said:
Ok, I solved the problem with another way. ADB didn't work and since I don't have a SD card reader, I thought about removing the SD card. It worked and I was able to access the recovery but upon accessing I found the horrible message waiting for me
"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 know that this means that the eMMC chip was fried. I thought about flashing the cache even though I know it wouldn't work but unbelievably, it WORKED!!! I can't understand how it worked but at least my phone is up and working again . One question though, the battery drain still exists but it's a bit smaller. Leaving the mobile it keeps getting between 10 and 20 mA and using it instantly jumps to 80-150 mA. Any suggestion how could I know what's draining the battery??
Click to expand...
Click to collapse
this exact same thing happend to me about 9 month ago, except i took the sd card out and formatted it in a pc, wiped the phone in recovery and all was well, seemed like sd card coruption to me not eMMC
Hi.
First post in the forum.
Just bought myself a brand new Lenovo A830, seems pretty new as there are very few custom roms out there.
It also doesn't help that this is a Chinese model and I can't seem to find support for it anywhere.
I got it delivered from etotalk.com with etotalk's own rom installed, and immediately started searching for custom roms.
Reason for this was faulty English, force close etotalk tools and Chinese info/submenues.
After trying out a few different roms, I've somehow gotten to a point where the internal memory is unavailable.
I think that one of the roms I installed switched the internal and the external memories, because I noticed a bunch of system
folders on the external sd. After that I wiped and formatted everything I could find from CWM 6.0.3.0, and after this, I'm unable
to install or mount anything. I hope this is possible to resolve without involving the external sd into the puzzle, because really, it seems to me
that I've managed to screw up the internal partitions.
Now, when I startup CWM, I instantly get the following messages:
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
Click to expand...
Click to collapse
I tried to recreate the partition table, using this tutorial:
http://forum.xda-developers.com/showthread.php?t=1158377
I was able to complete the tutorial, but it was not successful. Meaning I was able to create all of the partitions, but still have issues.
I've tried installing these roms:
http://www.needrom.com/mobile/lenovo-a830-5/
(worked installing before, got it up and running, then started messing around again)
and this
http://www.needrom.com/mobile/lenovo-a820-12/
(was also able to install, but showed some nasty "washout" stripes on the screen, which Is why I started messing around again)
and this
http://www.needrom.com/mobile/lenovo-a830/
(was not able to install this one, didn't try it before the mounting issues started.
When I try to mount /sdcard storage now, I get "Error mounting /sdcard!"
Same for /sd-ext.
Also, the internal sd card shows up with "no media" now when mounting usb to PC.
So, the only thing I'm able to do on this phone now is to enter CWMR.
I've searched for days now on several forums, I'm desperate. Please help me!!
Hey guys, got my 2 year Samsung Galaxy S3 GT-i9300 that suddenly turned off and won´t start. It gets stuck on the page that says in white letters GALAXY SIII...etc before the logo with the samsung blue thing circling appears.
So, tried to go into safe mode. No luck.
Recovery mode:
green android dead on it´s side, red sign and...
e: failed to mount /efs (no such file or directory)
e: failed to mount / system (nsfod)
#Manual Mode#
Applying Multi-CSC
same failed to mount but with system, then cache and then cache/recovery
Did a wipe cache partition and this appears:
e:/format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Cache wipe complete.
e: failed to mount /cache (block device required)
e: can´t mount /cache/recovery/log
e: can´t open /cache/recovery/log
and lots of similar lines.
Now...I´m not an expert, don´t have my phone rooted. After reading hundreds of threads last night, I opted to try the ERASE DATA / FACTORY RESET, and nothing happened.
Downloaded KIES, it will stay in the page saying ¨Connecting¨ so it doesn´t recognize the phone, but I still went into the 2nd option of tools to reload a firmware. It asks for Model and S/N, goes into download...take 5/10 minutes to download it....but then stays in 0% when installing it. It stays like this for hours.
Tried unplugging, and changing USB slots...but still doesn´t go past 0%.
My phone has been having trouble lately with the power button...sometimes when I take the battery out and put it back in it starts on it´s own.
I really don´t mind loosing my data...but if I could retrieve it somehow before deleting everything it would be the topping on the cake!
Thanks for anyone who can assist me on this.
Nico
(Oh...errors that happened 5 minutes before it went dead: something like Messenger stopped working, 3 times....I was doing something else so I decided to uninstall FB Messenger. A couple minutes later the phone died and I couldn´t get past the splash screen (heard you call it like that to the first screen that appears in white letters?).