Error mounting cache HELP - Micromax Canvas A1

So i installed cm13 and cwm recovery some weeks ago and it was running fine until yesterday it decided to stop working and gave me random app crashes
so i decided to reboot it, which got it into a bootloop, so I wiped the cache and dalvik/art cache, but i get an error whatever i click in the cwm interface
" E: can't open /cache/recovery/last_log
E: can't open /cache/recovery/last_install"
etc.
and on top of all that, I managed to screw it up even more by clicking clean to install new rom, which probably removed the old rom ( im not a techie )
please help
now it's stuck on micromax logo, i can access recovery but i get around 5-6 error messages whenever i click anything, like the ones i mentioned above
nothing works
this phone is a disappointment, i'm planning to get the new OP 3T but i cannot buy it anytime before summer '17. so im kinda stuck with this broken phone
help please i have very important files in it

Related

[Q] HELP!!!!!! NEED A PROFESSIONAL!! error wiping data/formatting data in stock ics

BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
WangLung said:
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
Click to expand...
Click to collapse
yeah thats what it looks like. I guess my only question now would be is there any way to salvage the media thats on my internal sd? photos/music stuff like that?
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
It's not bricked just reflash using odin or cwm back to stock
Sent from my SGH-T989 using Tapatalk

Recovery gone wild.

hey,
the past, well, almost half a year i was happy with my slim rom, but yesterday i thought, lets try something new.
a mistake obviously. i tried fresh flushing enother rom, but for some reason twrp recovery hes failed to install. then i flushed my old rom and everything was back to normal.
i googled the problem, and came to the conclusion the my version of twrp is old. the installed newer version, the 2.7, and tried flushing again.
here is the part the gone weird. the 2.7 failed to flush my rom, the i rebooted my device, and it got stuck. so i tried going back to the recovery. and from out of nowhere comes cwm. i remember installing it like a year ago. but i didnt see it since then.
ok so after this long ass story, now im stuck without rom, with cwm, witch i sort of hate, and to top it off, he cant boot ****. everything i try ends with an error. "e:can't mount /sdcard"
or
"e: cant open /cache/recovery/[email protected]
i tried like 4-5 different roms, nothing. it just says that installation is aborted.
i might add that i use adb to push files into the sd card, because the computer doesnt recognize my phone.
i really need help. :cyclops:
thanks in advance.
never mind. managed to solve this weird pickle....
thanks for listening to my heartbreaking story

[Q] Boot Issue

Well somewhat long story to this. I purchased the Desire 816 (A5_CHL) through VM, received my phone, activated it, and immediately started modding it. I installed ClockworkMod and CM, everything went fairly smoothly minus some minor bugs in CM. I was starting to get frequent Google app crashes for some unknown reason, (seemed to get progressively worse). Notably I did install Xposed which I thought might be causing Kernel crashes and etc.
I went to go start fresh again however with a clean install of the latest CM and etc. however I was receiving errors within Clockwork that weren't there before:
Code:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log...
I attempted to restore from a clean backup of CM, now the phone is stuck at the HTC boot screen. At this point, I'm able to access the boot menu as well as the recovery module still. So I thought maybe re-installing the recovery would help, so I did so using Fastboot. Now when I select recovery from the boot menu, it just vibrates and returns to the main menu. Still confused, I reset once and nothing, screen is black. I assumed it was bricked so I RMA'ed for a new one.
Two days later, started the whole process over again with my new phone, this time I made thorough backups of the stock ROM as well as other settings. I unlocked the bootloader, and installed the same exact things. Now I'm receiving the same recovery errors, I was able to boot into the OS however it seemed to have lost it's service settings. I rebooted once more and restored from a clean backup, now it doesn't boot into the OS. (Backups are verified working prior to incident).
So at this point I'm unsure if I should flash another recovery, then try restoring from backups or how I should go about this. I'd rather not re-brick my phone again so I'm just seeking some guidance on this. Thanks in advanced for any help!
Edit: I recall the recovery issue occurring directly after wiping the cache, not sure if it's even related.
account2442 said:
Well somewhat long story to this. I purchased the Desire 816 (A5_CHL) through VM, received my phone, activated it, and immediately started modding it. I installed ClockworkMod and CM, everything went fairly smoothly minus some minor bugs in CM. I was starting to get frequent Google app crashes for some unknown reason, (seemed to get progressively worse). Notably I did install Xposed which I thought might be causing Kernel crashes and etc.
I went to go start fresh again however with a clean install of the latest CM and etc. however I was receiving errors within Clockwork that weren't there before:
Code:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log...
I attempted to restore from a clean backup of CM, now the phone is stuck at the HTC boot screen. At this point, I'm able to access the boot menu as well as the recovery module still. So I thought maybe re-installing the recovery would help, so I did so using Fastboot. Now when I select recovery from the boot menu, it just vibrates and returns to the main menu. Still confused, I reset once and nothing, screen is black. I assumed it was bricked so I RMA'ed for a new one.
Two days later, started the whole process over again with my new phone, this time I made thorough backups of the stock ROM as well as other settings. I unlocked the bootloader, and installed the same exact things. Now I'm receiving the same recovery errors, I was able to boot into the OS however it seemed to have lost it's service settings. I rebooted once more and restored from a clean backup, now it doesn't boot into the OS. (Backups are verified working prior to incident).
So at this point I'm unsure if I should flash another recovery, then try restoring from backups or how I should go about this. I'd rather not re-brick my phone again so I'm just seeking some guidance on this. Thanks in advanced for any help!
Edit: I recall the recovery issue occurring directly after wiping the cache, not sure if it's even related.
Click to expand...
Click to collapse
I went ahead and RMA'ed the phone, you can go ahead and close this thread.

tab s 8.4 t700 brick help

Ok, long story short, i tried to flash a rom that needed a newer version of twrp, i thought i was up to date, turns out i wasnt, it didnt work so i did a recovery, updated twrp of the build i though i needed, reflashed, still didnt work, tried to reflash the recovery but did not work, stuck on boot, tried it a couple more time and no luck, gave me "error 255" or something, saw error "data can not be mounted" same with cache, so i youtubed how to fix, they said go to wipe, advance wipe, select partition, selected cache, system data and i think internal, did a change file system to which the video described, they said it did not matter which system, dont know what i chose first, tried to restore again, no luck saw system not compatible with restore, so made sure i changed file system to EXT4 which i thought it was.
so couple of questions
1. what is the default system for t700
2. can i fix this by fixing change system
3. if not how can i?
4. can i just flash a stock rom to fix this?
the only reason i was trying to flash a new rom, was because i get about 2hrs max of battery lige, even with a new battery, and i heard it my be system OS problems and twrp/cwm can fix this.
please help i really need this tablet and cannot afford a new one
Seeing as you've gone all out and just wiped everything you may as well just flash the stock firmware.
This will fix everything.

Failed to clear BCB message - A520F

Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Hir0xM said:
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Click to expand...
Click to collapse
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
SnowFuhrer said:
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
Click to expand...
Click to collapse
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Hir0xM said:
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Click to expand...
Click to collapse
No problem. Report if it doesn't work.
SnowFuhrer said:
No problem. Report if it doesn't work.
Click to expand...
Click to collapse
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
UmangA said:
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
Click to expand...
Click to collapse
When you get into work phones, things get really ugly. Can you wipe data by flashing just csc in Odin?
Similar problem with S7, it just keeps rebooting
I have an S7, I have the same problem, the phone started freezing and rebooting every minute. So decided to Wipe out the cache and do factory reset, saw this message "E:Failed to clear BCB message:failed to find /misc partition"
The phone never goes past the Galaxy S7 Android logo screen most of the time, if it did manage to go pass, it freezes after 2 to 3 mins and reboots.
So I tried and successfully rooted, installed TWRP, took a backup and tried to wipe cache, it failed.
formatted the and tried to restore from backup and it failed, as it never went pass the S7 logo screen.
so I tried Lineage OS 17 and it worked like a charm
then tried back to Android 9 ROM from Samsung, it too started to hang and freeze - If it was an Hardware issue, I would expect Lineage OS to freeze too.
I think and it looks like Samsung is forcing its customers to buy new phones .....
Please help
thanks
Z
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call aler
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call alerts?
My phone is Samsung galaxy j7 prime
when I factory reset it show me this error E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory
Galaxy tab A 8
Even without appearing to have any hardware problems, my galaxy tab shows exactly the same messages described above and the same situations. I suspect it is even programmed obsolescence. Would anyone have any reliable tutorial on how to reset it completely and install a rom that was stable and compatible? Thank you :fingers-crossed::fingers-crossed:
Exactly the same problem
Hi guys,
I exactly do have the same problem. I upgraded from LineageOS 16 (which was working smooth.y ) to LineageOS 17.1 and faces a problem wit IMEI, So I tried to revert back to Stock ROM, flashed via ODIN latest version.
I could flash the stock ROM (doing NAND Eras and Re-Partition due to Vendor partition). But after reboot, the ROM won't boot and stuck with SAMSUNG screen blinking.. I managed to access the Stock Bootloader and could do a full factory reset, but I still get the error message like above.
If anyone has an idea how to solve...
My sister had many randomly chrashing apps and ask me how to fix it.
In recovery the same message was printed. BCB and /misc ...
Well I tried to clean install stock rom (A5 2017) with odin, but the user data was never deleted ... Don't know how to use odin ...
I have then flashed lineageos and now there are random reboots and apps are only crashing sometimes once opened.
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Anyone knows what causing these? And if they are still related to BCB and/or /misc?
houston_ said:
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Click to expand...
Click to collapse
Somehow tha attachment was delincined.
Log_2020-12-01_21-40-15.txt
drive.google.com

Categories

Resources