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?
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Phone is working, I suppose doing his job in the process. The problem is that I am waiting already 20 minutes. I am afraid of getting CPU burnt (it is at 51 grades of Celsius).
I have read about the issue and about also the solution [enabling rm -rf in the twrp settings]... But now I am in the process, so not sure if I should shut the phone down or not..
Did you do a factory reset or advanced wipe?
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
binuralka said:
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
Click to expand...
Click to collapse
No. Your bootloader is already unlocked, otherwise it wouldn't have let you flash TWRP.
Have you tried factory reset? Or mounting system manually?
You can also try to mount system by using TWRP's built-in terminal emulator.
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
binuralka said:
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
Click to expand...
Click to collapse
Error 7 means the ROM is not compatible with your model.
Have you tried different version of twrp?
That was a really terrible testing day... I tried every twrp till version 2.8.6 that worked after odin flashing. I managed to mount system and do all wipes. I flashed ROM and gapps, everything went smoothly... But the thing was that the phone started to shut down by itself. Without a message, simply black screen and restart and bootloop after samsung logo. I decided to load 4.4.2 stock with repartitioning (pit file)... 10 hours ok and then again shutting down by itself.
Have you experienced this kind of behaviour?
Hi,
I have LineageOS 14.1 installed on my Moto G4 Plus. All of a sudden it rebooted and was stuck on the booting screen. I can get to TWRP. Things I tried that didn't help
wait 30 minutes
plug in phone to charger
clear cache
fully power off then on
If it comes down to it, I could flash a new ROM, but would like to save/backup the text messages/whatsapp messages.
@lightningglasses
Anything you installed/flashed before rebooting ?
try to dirty flash ROM and check if it boots or not.
____Mdd said:
@lightningglasses
Anything you installed/flashed before rebooting ?
Click to expand...
Click to collapse
nothing.an mp3 player app
try to dirty flash ROM and check if it boots or not.
Click to expand...
Click to collapse
will that loose the text messages etc?
lightningglasses said:
will that loose the text messages etc?
Click to expand...
Click to collapse
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..
____Mdd said:
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..
Click to expand...
Click to collapse
hmm didn't work, any other ideas?
lightningglasses said:
hmm didn't work, any other ideas?
Click to expand...
Click to collapse
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)
____Mdd said:
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)
Click to expand...
Click to collapse
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?
lightningglasses said:
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?
Click to expand...
Click to collapse
There is no other way to get your device back without losing data.
I have never used Titanium backup app but i know there is feature to restore data from TWRP backup, you can take backup of /data and restore backup of whatsapp.
I am still not sure about that feature, if you have time then i can test that feature, otherwise there is no way to keep data.
Edit: whatsapp makes chat backup every night at 2AM, if you haven't had any important chats after that, you can go for wipe.
If you can pay for titanium backup there might just be a way. I am not 100% sure but take a backup of the "data" partition(you can backup everything but data is most important) in twrp in internal storage only. Then clean flash everything. Then install titanium backup and buy the pro key. Then restore from twrp. If you find an option to restore only data then that's a better option. Downloading the app and restoring the data is better than restoring app and data. I'm not sure if it will work. But if nothing is working and your data is 100% vital you may wanna try this.
Another tip, don't restore blindly everything cuz bootloop may occur again