Hi,
I have rooted my device(Micromax A106 unite 2) long back and now When I flashed MIUI ROM in the device, I lost imei number. Today I accidentally formatted the device with the help of sp flash tool. Now my device is not even starting and the recovery also showing:
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/Last_log
I have tried so many recoveries to work out, but all useless.
And the most important thing is, I am not able to restore the backed up data. I have
.userReturn
kr-stock-conf
userdata_20150130_230923.backup
files which I backed up.
Please help me out How to restore the backup or any other solution to get rid out of this.
Thanks
Sideload MIUI (or any ROM) to the device using ADB on your PC & see if it helps
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?
Hi all,
I have recently flashed RevolutionROM with Galaxian kernel onto my SGS I9000.
I then flashed Darky's ROM 10.2.2 to my wife's phone (same model) and love it so want to flash it to mine too. So I need to flash Darky's Resurrection 10.2 first but can't get any PC (I've tried 3 of them - 2 with Ubuntu Linux and 1 with Windows 7) to recognise the phone over USB.
I plug in the USB and it vibrates and charges, but I get nothing on the phone display (i.e. USB mass storage screen) and the PC doesn't detect it at all.
I also tried it in Download mode but it was again not detected by the PC (Heimdall).
I'm figuring there is something wrong with the physical USB connection in the phone, as the same cable and PC worked on my wife's phone just yesterday.
So, a couple of questions:
1. Any suggestion for how to fix the USB issue?
2. Assuming I can't figure out the USB issue, is there any way to flash a ROM without USB connectivity?
thanks
Aaron
Anyone? Thanks
Sent from my GT-I9000 using XDA App
Have you tried reinstalling the drivers on your pc?
Hi,
Thanks, I appreciate your response but ask that you read my original post again - as i stated I tried it on 3 different PCs and that my wife's phone is detected fine.
It seems to be moot now unfortunately as I think I may have bricked my phone last night. I tried restoring a previous nandroid backup via CWM recovery and ended up in a boot loop. I was able to get back to recovery but now when I try to do anything I just get a heap of error messages saying it's unable to mount/find various filesystem locations.
I can get into download mode but without access by USB it is no help to me.
cheers
Aaron
Your device is not bricked. As long as you can get into recovery mode, you are fine. Have you tried using a new SD card, placing a rom on it then flashing it via CWM Recovery?
Theonew said:
Your device is not bricked. As long as you can get into recovery mode, you are fine. Have you tried using a new SD card, placing a rim on it then flashing it via CWM Recovery?
Click to expand...
Click to collapse
Thanks Theonew. Can you help me with how to go about that?
When I go into CWM recovery and try to restore a backup it simply shows several messages on the screen basically saying it can't mount or find any of the locations it's looking for (sorry I'm at work and don't have it with me to get the exact error messages) then returns to the recovery menu.
With that, I made the (possibly incorrect) assumption that the recovery is not going to be able to access any ROM that I might be able to put on the external SD card (and certainly not on the internal SD card).
If there's a way to do it though, I'm keen to give it a try. I have a 2GB external card that I can place a ROM on, but how would I get CWM recovery to flash it from there?
thanks
Aaron
Now that I'm back from work, here's the error messages I am consistently getting in CWM recovery.
Pretty much anything I try to do results in a variation of these errors appearing:
This one was after trying to apply update.zip from sd card.
Code:
E:unknown volume for path [/sdcard/update.zip]
E:Can't mount /sdcard/update.zip
Installation aborted.
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Try looking for the zip of the rom instead of the update.zip (install zip from SDcard -> Choose zip from SDcard)
Best bet is just put a new ROM in the root (i.e not in any folder) and look for it and flash make sure to clear out all the old stuff.
Hi, thanks again for the response. There are no actions I can take in CWM that don't result in the errors and failure (except reboot and test keys!)
I can't access anything that is stored as it's not mounting any partitions.
I can't add anything to the root because my USB isn't working.
thanks
Aaron
aaronlp said:
Hi, thanks again for the response. There are no actions I can take in CWM that don't result in the errors and failure (except reboot and test keys!)
I can't access anything that is stored as it's not mounting any partitions.
I can't add anything to the root because my USB isn't working.
thanks
Aaron
Click to expand...
Click to collapse
Try flashing a new version of ClockworkMod Recovery.
Theonew said:
Try flashing a new version of ClockworkMod Recovery.
Click to expand...
Click to collapse
Thanks again. How? I can't find any solutions that don't require USB.
Cheers
Aaron
aaronlp said:
Thanks again. How? I can't find any solutions that don't require USB.
Cheers
Aaron
Click to expand...
Click to collapse
Use rom manager. Just hope that you don't get the error during flashing.
Theonew said:
Use rom manager. Just hope that you don't get the error during flashing.
Click to expand...
Click to collapse
Thanks but I can't get into the OS at all, it's boot looping unless I get into download or recovery.
i flashed my micromax a60 with adt, using rom jetmod2.2.. now i am facing several problems such as wifi not working,cant able to connect usb, sd card is not showing, and main thing i cant see any changes in my about phone its still in android 2.1 version.. now i tried to do backup and also to install some other rom but i cant..
i got errors such as
E:can't mount/cache
E:can't mount/cache/recovery/log
and some other errors and also i tried to flash it using adt but its not working saying no device found.. but my mobile is connected to the system. pls help me to recover my phone..
Hello Developers
Yesterday, i tried to do a CWM back up of my ROM and it stopped in the middle with below errors
E:Can't open/cache/recovery/log
E:Can't open /cache/recovery/log
[Read Only File System
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I Know there are many threads with this question, however mine is litte different; How?
1. I am able to mount my SD CARDs to PC
2. ADB works fine
3. Format Cache - Works fine
4. Wipe / Factory Data Reset - Works fine
5. Format System Works Fine
6. Wipe Dalvik Cache - Exits without any error
When the system reboots, I get a message "ENCRYPTION UNSUCCESSFUL" Reset phone, when clicked on Reset, phone reboots into Recovery.
ADB works fine, but i am not able to use Flash_image - Error Message file not found [it was placed in root of the memory card]
Tried to flash recovery through SP flash tools, i get an error Message - SDA SDMMC write failed
MTK Root tool does not recognize phone.
Please let me know if this is a permanent brick or is there any work around to resolve this.
My phone is only 6 months old, but cannot claim warranty because of CWM and Boot logo changed
Hi there...
sorry i'm completely a noob in this aspect as this is my first time having an android device..
my android device has MT6589 Android version 4.4.2 by default and 3.4.5 kernel version... my stock ROM, well, i don't know but it's customized by one of the university in my country, my recovery is CWM v5.5.0.4
so i searched any guides that might work and then bump into a guide in http://forum.xda-developers.com/showthread.php?t=2707438
custom ROM which i tried to port is from
http://www.mediatekguides.com/2015/12/mt6589-miui-v7-rom-multilanguage-edition-port.html
it was said that it is for all MT6589 devices even though it's basen on Kitkat 4.4.4 and accidentally my dad have a hh that installed MIUI v7 with 3.4.5 kernel version(or so i remember), so i thought it will work cause its still within Kitkat
cause it's my first time.. by some chance i made a mistake in first attempt to port.. that is copied all text from recovery.fstab to A11Q file (From registering device to kitchen) and doing all the steps... and of course it didn't succeed but it became bootloop...
seeing that.. i tried using SP Flashtool to restore my stock ROM but it was the same.. stuck in the logo(bootloop)..
and then i tried opening CWM Recovery and it shows
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
and then.. i tried to seach for solution, it said to format /cache.. but when doing that, it shows:
E:format_volume:make_extf4fs failed on /dev/block/mmcblk0p6
Error formatting /cache
when trying others formatting, it was the same, just differ in mmcblk0p_
i still didn't try porting with SP Flash Tool as i was trying to restore my Stock ROM with it and still failed..
Anybody can Help me please?
OP reposted in the correct section:
http://forum.xda-developers.com/and...ft-bricked-t3417460/post67725136#post67725136
Thread closed.