Related
I've done a bit of searching for my answer, however, am not able to find the answer.
I am having a problem running a restore in AD Recovery in the Magldr (v1.13).
Let me explain the situation:
I wasn't able to get App2SDPro to carry over apps to my SD card. I was informed it was because it was that I did not have an EXT2 or EXT3 partition on my SD.
I did that and then my SD was erased, but luckily I make regular backups of my SD card.
So I put all the information back on my SD card. I then realized that my ROM was erased as well.
So I tried running the backup I made from the recovery and got the error mentioned in the title.
I then tried to reload a ROM that I have on my SD at all times and then tried to do an advanced restore of the data and system and cache while leaving the boot but nothing works..
Am I destined to start from scratch, lol? (I had 140 apps installed)(and I'll be using a different form of backup next time, lol)
i have the same problem . while i was recovering from nand backup i have this notification 'Nand Kernel Open Failed'
Just flash again the kernel of your rom or the rom without wipe
you have to flash your rom om the kernel again and hopefully the problem will be solved
CLIO94 sorry i just see your reply
So just wanted to share this in the event anyone else runs into the problem. I was running CWM 2.5 and CM7 RC2 just fine for a while now and I decided to clean my SD card yesterday since I have tons of empty folders from prior app/rom installs. After deleting some folders, my SD card would not be read by the phone. I rebooted and it sent it into a bootloop. Tried to format SD card in recovery and the settings menu, no avail. Tried to partition in adb to correct the issue and /DATA would not mount for the life of me. I could get it to mount via adb, but not in recovery. Any time I tried to factory reset or format DATA, it would say it cant mount the partition.
Anyway, I tried the latest version of CWM (3.8) and it managed to format each partition without any issues. I could then install CM7 without any issues and it booted right up.
So if anyone is experiencing SD card issues when altering the filesystem in any way, try upgrading the recovery image. It would have saved me a good number of hours troubleshooting, but hey at least I learned adb better lol
I am having the same exact problem, bootloop with no way to access card. How did you get CWM updated?
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?
[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.
Anyone have any idea?
Thanks
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?
You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes
I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.
you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)
Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.
Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.
I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?
Hi guys, i'm stuck in Rock and a hard place here and couldn't figure this one out. I've installed CyanogenMOD previously but that was a while ago and different process. What happened is I installed LineageOS 2 days ago and everything worked fine except No Sim Card is detected so I can't make phone calls and log into my Google account to sync.
Hence to resolve the Sim Card issue, what i did is to attempt to flash Bootloader, System , Radio images but it didn't work when i try to flash and also install LineageOS zip file. And in order to try resolving Mount issue, I proceed to Advanced Wipe -> checked System, Data, Cache -> Repair and Change File System -> changing ext4 to ext 2 . This formated all my User data which includes the ROM zip file i needed to install and load. I tried using Nexus Root Toolkit to restore into stock but it says no Fastboot/ ADB detected. And my computer couldn't detect my Nexus 6p.
Please provide solutions. Desperate here.
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Exodusche said:
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Click to expand...
Click to collapse
Thank you for replying Exodusche. But i have switched back to EXT 4 and finds the system formatted and user data deleted! Plus my computer is unable to recognize my phone while i'm stuck at Bootloop =( Talk about difficult situations. So i'm unable to test your no sim solution at this point. Need to retrieve deleted files or at least push files from Desktop to Phone.
Any ideas?