Hey Guys,
I have a Android/WinCE Car Radio.
So I got Android on a SD Card and it booted well, but one day it stopped booting.
If I mount the SD from the internal Android on the device, there is a LOST.FOUND directory on the boot partition where boot.scr and so on is.
If I delete the directory and restart, the system boots from the SD again. But if I do a restart, the system won't boot again. I need to delete the LOST.FOUND directory every time...
I'll Attach the boot partition, maybe you can give me a solution to this.
Thanks
bump
If you run fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular, fsck might find data that looks like a complete file but doesn't have a name on the system — an inode with no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.
If you tell fsck to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. So fsck deposits the file in a specific directory, called lost+found (after lost and found property).
Files that appear in lost+found are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.
Files can also appear in lost+found because the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.
Click to expand...
Click to collapse
Make sure your boot files in the root of the partition are ok.
Make a backup of the files, copy the files in the lost.found directory over the existing files or use the original one (firmware download from device supplier?)
And make sure you unmount the SDcard safe.
Good luck..
THere are no files at the LOST.FOUND directory.
If I take a other SD and put the stock image on it, it's the same problem.
Related
Last week something burnt out in my Streak, it wouldn't turn on, so I needed to send it to get repaired/replaced, as a little data insurance I took a dump of the internal SD card (just using dd in Ubuntu).
Now O2 are replacing my Streak, so I'll have a new one with a different IMEI, etc, and I don't want to open this one (I only opened the other one as it was an emergency). So I'm looking for help on restoring the backup I've taken without opening the phone, and once done, leaving it in a warranty-friendly state.
Obviously the first step is going to be rooting it, but what then? Is it simply a matter of copying all the files? Just thinking that might cause conflicts due to the new IMEI.
so i've got a similar (but reciprocal) problem... i had a malformed update.zip that pooched my internal microsd's system partition and the streak won't boot at all... I have a nandroid backup and i've pulled the internal microsd to find an empty ext filesystem that mounts just fine when I plug it into a linux laptop, but there's not a clear mapping from the system.img that I have and the contents of the accidentally wiped system partition...
SO, two things would fix this....
1. someone could send me a link to their raw 'dd' image of the system partition (~200mb)
2. or, I can keep figuring out how to use 'dd' with the system.img that I have to get the same results as the 'flash_image' tool...
would someone be so kind as to speed me along on this by giving me their system partition dump (1) or quickening my learning curve on (2) so that I can restore with the flash_image formatted nandroid dump of a working system partition???
Please, please....
I wanted to enable full gpu rendering on my Samsung P6200... I am running 4.1.2, rooted. I downloaded the zip file, booted into recovery and installed the zip file, I rebooted, it shows the normal model number and that on the screen, and about the time when the boot animation starts it just goes blank, although it is still on, now, I rebooted back to recovery, I had made a backup moments before, I only had 770 MB of space left so it made a full backup except my /data partition, that failed, but I didn't want that backed up anyway. I thought well maybe I should restore, so I went to advanced restore and chose the boot partition to restore, restore was succesful, I restarted and did the same thing, now I try to restore the whole backup and it says md5 mismatch, I connect to adb and mount everything, and find my mnt folder is missing, now I don't know how to fix this, if I go to install zip from sdcard it shows all my files and folders there, but if I go to /sdcard/storage/sdcard0 in adb it only shows two folders, Download and Webzine. How to fix this, I don't want to restore my /data partition due to the fact that it only did like 5% of the backup of it and need a lot of that data, if I were to fix the md5 mismatch (don't know how) what partition would I restore to fix the boot error? And how do I fix the missing mnt folder issue?
Ok, sorry, found my files are stored in /sdcard/, although I could swear they were in sdcard0
Just recently I found my phone.
I resettled it after cwm went wrong
Then I repartioned external SD card. Through cwm. 6gb primary 1gb ext size and 196mb swap.
Then I downloaded zarchiver to move and delete stuff(internal SD card does not get wiped during factory reset.)I deleted the android folder and it failed I then went up a directory and back down. My SD card became read only. I can move and delete files with root browsers but the one cache file from the app tumble is not deleting. I tried through settings but to no avail. Then I read somewhere that someone had a similar problem. He tried RM and um but neither worked. So he rooted and tried again. He then used fsck_msdos to find the corrupt file and delete it and he rebooted and it worked. Now I have my fsck_msdos but not in its original filepath( I got rid of it because of media scanner problems).
Now a few things. Which partition is my swap size from my sdcard is (eg mmcblk"x"p"xx". "X" is a number)? Because I want to use swapper 2 .
Where is the fsck msdos file directory and also fstab.
And what command do I use with fsck or any other command to fix my problem. The guy I read about he did something like fsck /dev/vold/179:... I don't know and it fixed it for him.
Please help and thanks beforehand[emoji3] [emoji3] [emoji3]
[EDIT] I got my sdcard as read write. I turned my device on and off but the files still there. If I touch it it will make it read only again
Hi!
I wanted to reformat my internal sdcard to ext4 today to enable trimming (it should also help the /data partition, because it is on the same physical flash storage, right?).
To back up my data I thought about packing everything into a TAR archive to also save all permissions (for example of the ./Android/data/ folder). But now I have the following problem:
if I browse through /storage/sdcard0, I see all the permissions and the correct owners, but I dont have access to .android_secure. I am using a adb root shell, how can I not have access to this?!
if I browse through /mnt/media_rw/sdcard0, I have access to .android_secure, but all the file owners are set to "media_rw", which is not what I want to backup, I need the correct owner info to correctly restore the data later.
Could you please help me to answer these questions?:
As I understand, FAT doesnt support permissions, so how does android emulate the permissions in the ./Android/data folder?
How can I see the same folder (my internal sdcard) with different file owners? Is it mounted twice with special options?
How can I backup my whole sdcard (with owner/group info & permissions & file access dates) to restore everything 1:1 after reformating to ext4?
How do I reformat my sdcard to ext4? (which block device comes after "mkfs.ext4"?)
Thank you very much!!
GridLockFour said:
Hi!
I wanted to reformat my internal sdcard to ext4 today to enable trimming (it should also help the /data partition, because it is on the same physical flash storage, right?).
To back up my data I thought about packing everything into a TAR archive to also save all permissions (for example of the ./Android/data/ folder). But now I have the following problem:
if I browse through /storage/sdcard0, I see all the permissions and the correct owners, but I dont have access to .android_secure. I am using a adb root shell, how can I not have access to this?!
if I browse through /mnt/media_rw/sdcard0, I have access to .android_secure, but all the file owners are set to "media_rw", which is not what I want to backup, I need the correct owner info to correctly restore the data later.
Could you please help me to answer these questions?:
As I understand, FAT doesnt support permissions, so how does android emulate the permissions in the ./Android/data folder?
How can I see the same folder (my internal sdcard) with different file owners? Is it mounted twice with special options?
How can I backup my whole sdcard (with owner/group info & permissions & file access dates) to restore everything 1:1 after reformating to ext4?
How do I reformat my sdcard to ext4? (which block device comes after "mkfs.ext4"?)
Thank you very much!!
Click to expand...
Click to collapse
I'm not sure the answer to some of that, but you don't need ext4 for trimming(EDIT: although I don't know whether android enables trim on FAT) and /data is already ext4 by default. The /data partition is separate to /sdcard0
Most if not all gains from trimming would be made from trimming /system, /data, /cache, and /preload(if you use touchwiz based rom or stock)
Hi,
I was trying to restore backup via Titanium Backup but it was getting stuck at 0. While searching for solution I came across a solution that said to change the backup folder from storage/emulated/0/TitaniumBackup to storage/emulated/legacy/TitaniumBackup. When I did that, TiBu asked to copy the backup files and I gave permission. Now all the files that were there on my internal storage, which were visible on PC when connecting my phone via USB, have disappeared. I looked around in the root folder via MiXplorer and found that all the files have moved to legacy/TitaniumBackup which I cannot access via PC.
I thought I can just restore nandroid backup that I had taken but in TWRP the file does not show as the internal (emulated/0/) is empty. I can see the nandroid backup and all the other files in the legacy folder but cannot do anything about it since they are not showing in TWRP or PC.
Please help me in getting the old settings back.
/storage/emulated/0 and /storage/emulated/legacy are basically the same thing: simply 2 mount points pointing to the same storage device and partition. They do not take away more storage space, as it is only available once but shown twice, because they are sym links what redirect to original /data/media/0 folder.
If you create something in one folder, it will show up in the other. Same applies for deleting stuff.
jwoegerbauer said:
/storage/emulated/0 and /storage/emulated/legacy are basically the same thing: simply 2 mount points pointing to the same storage device and partition. They do not take away more storage space, as it is only available once but shown twice, because they are sym links what redirect to original /data/media/0 folder.
If you create something in one folder, it will show up in the other. Same applies for deleting stuff.
Click to expand...
Click to collapse
I moved all my files from storage/emulated/legacy/i to storage/emulated/0/i and all the files showed up on my PC as well as internal storage on MiXplorer. It was as simple as that. I thought I had botched up something in root partitions.