I made a back up to flash to another rom... backed up only the three default options. When i try to restore it i get a boot loop... i am using Amon_Ra. My older back up works.. but i really need the new one... any suggestions? This is the second time this happened... making me thing about not using amon anymore.
Did you clear cache and dalvik before trying to restore?
i get that too from time to time recovery log says bad md5 O.0
WHich is why I backup everything except cache...
I didn't back up cache. I also tried clearing it before and after restoring.
I was trying to install JellyBlast, but when i choose wipe data this error appeared: "E:Can't mount/cache/recovery/last_log", same error goes on wipe cache. So i flashed the rom anyway and it got stuck in the boot animation. I'm pretty sure that its getting stuck because wipe data/cache did not work. Besides the error, it goes relly fast, less than a second, seems like it did nothing. What should i do?
Edit: NVM, the CWM was the problem, used another one and it worked.
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
mmbytes said:
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
Click to expand...
Click to collapse
You can't restore nandroid of CM10/9, i dont know why, but i also can't restore cyanogenmod nandroid backups, stock roms backups are restoring fine, but cm - still no luck. PS: your system is ext3, because we have locked boot. Data and other partitions restoring fine except cm backups.
mmbytes said:
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
Click to expand...
Click to collapse
That's the point formatting system & data to ext3, but make sure don't wip data & cache after rom installed without reboot , since you're still under CM10's bootmenu.
Hope this helps .
Sent from my GT-N7100 using xda app-developers app
donf6938 said:
That's the point formatting system & data to ext3, but make sure don't wip data & cache after rom installed without reboot , since you're still under CM10's bootmenu.
Hope this helps .
Click to expand...
Click to collapse
Sorry, no. I do not understand what you mean. Could you please describe the steps?
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?
i am having following error in twrp. due to this i cannot take backup. any way to fix this.
just now i wiped data completely, still it didn't fixed the error.
please help me to resolve this.
What version of TWRP are you using and exactly what were you trying to do before you got the error?
That looks like some encryption stuff to me.
This error displays as soon as I go to TWRP and i was unable to do nandroid back up.
I went to wipe advance wipe and selected data, instead of wipe, there was a button above the swipe option, i clicked that and repaired partition, and i think it fixed the issue.