I'm using a Asus Zenfone 5 LTE T00P (A500KL) that has been upgraded to the latest official 5.0 ROM for a few months. Phone has not been rooted & is completely stock.
Suddenly out of the blue today, a series of forced stop error messages started appearing and I was unable to cancel all of them without rebooting the phone.
I decided to reboot into the recovery mode and that's when I saw a string of error messages that the cache partition cannot be mounted.
I have not seen this before previously.
Even when I tried to clear the cache partition, the same error message appears.
Is there a way to recover from this error without factory resetting the whole device?
I have not backed up all the data since upgrading so I'm somewhat hesitant to proceed with the FR.
I have been able to run a ADB Backup but I'm not sure if the backup.ab would be useful after the FR.
Any advise from anyone familiar with this situation?
Try to flash the actual ROM again, it shouldn't erase anything but it could help.
have you fixed this issue?
I can not flash anything in my phone anymore
Related
Hi, today i wanted to do a factory reset and clean install my phone
im using TWRP 2.3.3.3
after factory reset in the wipe menu, at the end i see a line E:/error opening '/data/lost+found'
basically i know what does lost+found folder does in linux, but i forgot whether i have seen such error line before when i do factory resets.
in the file manager of TWRP i then see /media and /lost+found in the /data partition. when pressing into /lost+found, TWRP cannot open it
after this, wiping /system will also give me the same message at the end even it is "Done", as well as cache and dalvik, etc
then i go on flash rom, gapps, kernel, after 1 or 2 boots i go back to recovery and wipe cache, there are no such line anymore
however there is now TWO /lost+found folder in my /data partition
is this a normal behaviour? i didnt pay attention but are there 2 lost+found folders in /data partition for everyone else too?
i have backed up my sdcard and is ready for a /data wipe, any advice is appreciated. thanks in advance!
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Miasmic said:
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Click to expand...
Click to collapse
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
just had this issue and was solved by dropping back to twrp 2.4.x.x and doing data format.
misspost
mitchallica said:
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
Click to expand...
Click to collapse
No his error and mine are different. We have two lost+found dir and no file. If i delete them and make new lost+found folder. It automatically makes 2.
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Full Format data worked for me
NVijapura said:
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Click to expand...
Click to collapse
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
szurheal said:
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
Click to expand...
Click to collapse
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
That worked perfectly. Thanks!!!
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
leijonasisu said:
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
Click to expand...
Click to collapse
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Hi all,
I tried to update the custom ROM on my A200, but in the process, the data wipe failed.
What I did exactly, is use ROM Manager to load the latest JellyBean CM ROM for A200, selecting the option to wipe the data partition (do a factory reset). My device rebooted, and it started trying to wipe the /data partition, but it just stopped right there. No error or anything, the system just hung there for 2 hours before I turned it off. As I feared, the system was rendered unbootable.
However, CWN Recovery *is* still available, which I guess is a good thing. So, I can boot in recovery, but I can't really get it to function. I tried formatting the data partition again - system hangs. I tried installing the image from sd card - system hangs.
Does anybody know how I can recover from this? It seems to me that there's nothing *really* broken, just that my data partition is corrupt somehow -- and I suppose there has to be a way to recreate these partitions.
Thanks!
I've had CWN Recovery run for 24 hours now, and still nothing. It fails to format the data partition.
Anyone knows how to tackle this problem?
my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
m7mdrda said:
my problem is that suddenly my TPT hangs and keep rebooting, it starts the system normally then it hangs for 3 sec then reboots and so on
-from CWM i did wipe data factory reset and wipe cache partition, but the problem still occurs
-i tried to restore a backup and i get this message "error while restoring /system"
-i tried to make advanced restore, all options can be restored normally except for restore system i get the above message
-the new now the tab is not rebooting and stuck at the lenovo screen
-now i tried to install CM10 ROM from my internal memory and it installs normally
-when cyanogenmod screen loading then it freezes for 3 sec and reboots again and again
any advice and suggestions will be greatly appreciated
Click to expand...
Click to collapse
I'm in the same boat. Boot loop, can get into CWM recovery, but can't do anything to get it functional; factory reset, wiping cache, reflashing koshu's 0.91 build, none of these work. Only other suggestion I've seen is getting an ADB shell while in CWM and checking the partitions are not corrupt. As per this post:
http://forum.xda-developers.com/showpost.php?p=39917591&postcount=7
At the bottom of that thread there's reference to a possibly related Lenovo thread of people suffering similar problems, which was closed in Feb with a message about an extended repair program, valid until August.
It'd be a shame if it's a hardware issue, that we can't claim on because we're running custom software... you have to accept that risk when you decide to flash a custom ROM, but I don't think I'll be buying Lenovo again; mine's been repaired once already, and now this.
So apologies is this is done to death, but I've screwed something up.
My phone is rooted/unlocked and I had twrp installed.
I tried to install a lineageos rom but it didnt work, and it would get stuck booting.
I can still get into fastboot and twrp, but I don't know what to do from there. I have tried install the stock recovery and then installing the stock emui rom but it doesn't seem to be working, and I can't seem to find a thorough walkthrough of what I need to do.
I have the Japanese version of the phone (WAS-LX2J) if that helps.
So I can force into TWRP using adb reboot recovery
When I get into TWRP the UI is all red - it used to be blue? I might have just installed a different version but seems strange to have gone red now.
Whenever I try to wipe data, or format data, I get a bunch of errors:
unable to recreate /data/media folder
unable to mount storage
unable to mount /data/media/twrp/.twrps
unable to open '/dev/block/dm-0' to wipe crypto key
etc
I am also unable to repair, resize or change the file system apparently.
Okay I reinstalled twrp (from here) and that problem seems to be solved. (in red)
I would basically just like to restore my phone to factory but I don't know how, any help would be hugely appreciated.
I can provide any more info if required, I just dont have a way to screenshot my phone atm
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.