I have an S3 (i9300), and in recovery (TWRP 2.8.6.1) It will give me errors that it can't open folders in the data partition, so Aroma installer roms cannot format data, and I get a long error every time i data reset.
Data/misc/audit is unopenable (can't see it in file explorer in system, but i can see the folder in recovery)
Data/data/com.samsung.dcm - a folder in there is unopenable, is named as a tilted square with a "?"in ES.
Ashab7013 said:
I have an S3 (i9300), and in recovery (TWRP 2.8.6.1) It will give me errors that it can't open folders in the data partition, so Aroma installer roms cannot format data, and I get a long error every time i data reset.
Data/misc/audit is unopenable (can't see it in file explorer in system, but i can see the folder in recovery)
Data/data/com.samsung.dcm - a folder in there is unopenable, is named as a tilted square with a "?"in ES.
Click to expand...
Click to collapse
For anyone still with this problem, the solution is to reformat and repair any faulty partitions in the advanced wipe menu in TWRP.
I am having this problem with an S3 that I'm trying to restore to stock. I can get TWRP on the phone but no image will install nor saved backups will restore. The reason is the data partition is corrupt. When I try using the Advanced Wipe option to repair the partition it reports:
/sbin/e2fsck -fp /dev/block/mmcblk0p15 process ended with ERROR: 4
Unable to repair Data.
Click to expand...
Click to collapse
Any other thoughts on how to repair the data partition? It was just working before trying to restore to stock, so I doubt it is a hardware problem.
For those facing the same problem. I did fix this but I can't tell you exactly what did it. I used the Terminal in TWRP to repair the partition manually. I think I used "e2fsck -cvf /dev/block/mmcblk0p15" and accepted all repairs. Be sure to say "no" to the first question that recommends you to stop. Then I used TWRP to format the partition and then it mounted just fine. I did many repairs on the partition using e2fsck and not all of them worked so I'm not 100% positive I know which options did it. I think it was "-cvf" but maybe "-B" also played a role. Either way, you gotta get that partition repaired before it will format and then mount.
Maybe flashing a stock ROM, with or without a pit file, would also work?
audit13 said:
Maybe flashing a stock ROM, with or without a pit file, would also work?
Click to expand...
Click to collapse
I tried that. That's what led to my /data partition being corrupted. I tried Kies 2.0 and stock ROMs with Odin. I couldn't get beyond the corrupt file system. I even got to the point where download mode was complaining to me about things being jacked. I thought I bricked the thing for a while.
Did you try flashing a stock ROM with Odin? Kies can't be used to flash a stock ROM unless you use the emergency recovery option.
scottlindner said:
For those facing the same problem. I did fix this but I can't tell you exactly what did it. I used the Terminal in TWRP to repair the partition manually. I think I used "e2fsck -cvf /dev/block/mmcblk0p15" and accepted all repairs. Be sure to say "no" to the first question that recommends you to stop. Then I used TWRP to format the partition and then it mounted just fine. I did many repairs on the partition using e2fsck and not all of them worked so I'm not 100% positive I know which options did it. I think it was "-cvf" but maybe "-B" also played a role. Either way, you gotta get that partition repaired before it will format and then mount.
Click to expand...
Click to collapse
thanx scottlindner actually "-cvf" is work.
thank you allot:good:
Related
I bought my mother an Archos 101 internet tablet (Gen8) for Christmas. I got the product used. She has been using it ever since with no problems. When I went to visit her today she stated that it hasn't been working for a month and just boots over and over.
My thought was to enter recovery, reinstall the firmware and be on my merry way so that she could go back to browsing the web and reading books.
And that's where the problems start (like the boot loop wasn't a big enough problem). Every time enter the recovery > Update Firmware > and copy the .aos file to the drive, when I press power to update it says "Update Failed (1)". I have tried both the normal firmware and the SDE firmware. Both give the same error.
The only post I could find out of a google search the resembled the same problem I am having was that someone posted and said that they had a issue with the internal member and had to send the tablet back to Archos for replacement.
Unfortunately, since I bought the product used, I do not have that option.
Has anyone else had this problem before and able to fix it?
I would also like to mention that I have also reformatted the device (through recovery) and tried to repair. All give the same results. One thing that I did notice is that when I transfer the "firmware_archos_android_gen8.aos" file to the drive, whenever I remount the system, it is no longer there and I have to copy it from the PC to the internal memory every time.
Why dont you just try to reset android from the recovery? You can also format the device and apply the firmware but make sure you paste it with it's proper name without (1) at the end. It can be caused by corrupted download or different name instead the name it has to be else it wont work.
Also, make sure you haven't downloaded the FW file for the A70b by mistake...
I once did that mistake while recovering mine from a bad flash.
Also, before reflashing, I would do a full format from the recovery menu. That will wipe all data from it before reflashing the firmware.
Mavasilisk said:
Why dont you just try to reset android from the recovery? You can also format the device and apply the firmware but make sure you paste it with it's proper name without (1) at the end. It can be caused by corrupted download or different name instead the name it has to be else it wont work.
Click to expand...
Click to collapse
This was actually the first thing I tried to do, I guess I didn't mention that in the OP. The flashing the FW was going to be a last resort type thing.
drf666 said:
Also, make sure you haven't downloaded the FW file for the A70b by mistake...
I once did that mistake while recovering mine from a bad flash.
Also, before reflashing, I would do a full format from the recovery menu. That will wipe all data from it before reflashing the firmware.
Click to expand...
Click to collapse
I'm pretty sure I downloaded the correct FW. It was the one labeled on the Archos website as "Download Archos 28/32/35/43/70/101 internet tablet - Archos 35 home connect/smart home phone OS v 2.4.83 (91861Kb)"
I did do the full format from the recovery menu before flashing. As I boot into recovery I went to Format System > Reformat Device... > I understand. I assume this is what you are talking about.
P.S. I appreciate the feedback and help. All other thoughts and suggestions are appreciated.
sryan1983 said:
I'm pretty sure I downloaded the correct FW. It was the one labeled on the Archos website as "Download Archos 28/32/35/43/70/101 internet tablet - Archos 35 home connect/smart home phone OS v 2.4.83 (91861Kb)"
I did do the full format from the recovery menu before flashing. As I boot into recovery I went to Format System > Reformat Device... > I understand. I assume this is what you are talking about.
Click to expand...
Click to collapse
That's the right FW, and you used the good format option in recovery. I guess you also tried redownloading the file again, just in case the copy you had was somehow corrupted?
Outside of that, I could only think of a bad flash memory block on the device... I hope it's not your case.
drf666 said:
That's the right FW, and you used the good format option in recovery. I guess you also tried redownloading the file again, just in case the copy you had was somehow corrupted?
Outside of that, I could only think of a bad flash memory block on the device... I hope it's not your case.
Click to expand...
Click to collapse
I have a funny feeling that it is going to be the memory block. Gives me a good excuse to open up the device to tinker with it I .
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
The eMMC of my Galaxy Nexus is broken. It can't be written to anymore, so it continuously bootloops.
I can still get app data from the phone in recovery mode, but this is a plain copy of the /data partition and not a backup file.
I tried copying the /data/data/com.app.xyz directory (for app xyz), but after that the app usually crashes on startup.
Which files do I need to restore on my new phone to get an app working with the old data?
Condor70 said:
The eMMC of my Galaxy Nexus is broken. It can't be written to anymore, so it continuously bootloops.
I can still get app data from the phone in recovery mode, but this is a plain copy of the /data partition and not a backup file.
I tried copying the /data/data/com.app.xyz directory (for app xyz), but after that the app usually crashes on startup.
Which files do I need to restore on my new phone to get an app working with the old data?
Click to expand...
Click to collapse
If the eMMC of the Nexus is dead, then how would you be able to recover data from it, even while in recovery? Or do you mean there is a corrupted partition?
es0tericcha0s said:
If the eMMC of the Nexus is dead, then how would you be able to recover data from it, even while in recovery? Or do you mean there is a corrupted partition?
Click to expand...
Click to collapse
All partitions are read-only. The last thing i tried was flashing the Google stock ROM. This took a very long time and gave no errors, but in the end no data was changed.
I found several forum members with the same problem and nobody was able to repair this.
Since all data is read only i can only boot from a temporary recovery and copy the data off.
I have rooted my phone and sim unlocked it. Then i wanted to install custom rom, downloaded files:
1. cm-12.1-20150430-UNOFFICIAL-i9100
2.CM-12-Kernel+Recovery-I9100
3.gapps-5.1.x-20150404-minimal-edition-signed
4.Odin 307
5.ROOT-UPDATE-SuperSU-v2.46
6.TriangleAway-v3.26
I have transfered files to phone and shut down the phone, then installed "CM-12-Kernel+Recovery-I9100" via Odin.
I wiped/factory reseted phone, wiped cache, dalvin...
After i went into Recovery mode (Home button+Volume UP+Power button) and chose install zip.
I chose from sd card and chose cm-12.1-20150430-UNOFFICIAL-i9100.
The process started and then error turned:
"detected filesystem ext4 for /dev/block/mmcblk0p9".
That held for more than 15 mins and i took battery out and phone wont turn on.
What should i do?
gamemaster123 said:
The process started and then error turned:
"detected filesystem ext4 for /dev/block/mmcblk0p9".
What should i do?
Click to expand...
Click to collapse
Sounds like CM or install routine does not like the filesystem.
Maybe destroyed or wrong filesystem.
Try to "format sdcard" (only internal one) with recovery and use another filesystem.
Look into the thread of your ROM which one ist preferred.
Okay, there ist no failure message, so maybe no error but the install file stucks.
Try to download the whole file again and copie it to external sdcard again.
If fails, try adb push command in recovery, after mounting an formatting internal sdcard, and push the file into internal sd.
Try to install from there.
gamemaster123 said:
I have rooted my phone and sim unlocked it. Then i wanted to install custom rom, downloaded files:
1. cm-12.1-20150430-UNOFFICIAL-i9100
2.CM-12-Kernel+Recovery-I9100
3.gapps-5.1.x-20150404-minimal-edition-signed
4.Odin 307
5.ROOT-UPDATE-SuperSU-v2.46
6.TriangleAway-v3.26
I have transfered files to phone and shut down the phone, then installed "CM-12-Kernel+Recovery-I9100" via Odin.
I wiped/factory reseted phone, wiped cache, dalvin...
After i went into Recovery mode (Home button+Volume UP+Power button) and chose install zip.
I chose from sd card and chose cm-12.1-20150430-UNOFFICIAL-i9100.
The process started and then error turned:
"detected filesystem ext4 for /dev/block/mmcblk0p9".
That held for more than 15 mins and i took battery out and phone wont turn on.
What should i do?
Click to expand...
Click to collapse
There is no problem with that message appearing, happens with every LP rom. However, 15minutes is too excessive for installation. It seems that your phone froze, which could be due to corrupted partitions or wrong recovery. Have you tried using a USB jig to see if your phone is completely dead or not? Is there battery left on your phone?
---------- Post added at 09:11 PM ---------- Previous post was at 09:03 PM ----------
RtGh43 said:
Sounds like CM or install routine does not like the filesystem.
Maybe destroyed or wrong filesystem.
Try to "format sdcard" (only internal one) with recovery and use another filesystem.
Click to expand...
Click to collapse
I agree and also disagree with what you've said. I agree that it could be due to corruption, but it has nothing to do with the internal storage itself, but more accurately the system, data partitions on our phone, which can't have its filesystem changed. Ext4 is the only file system that is used for these inbuilt partitions, and so changing the file system of the SD card will give no benefit.
gsstudios said:
There is no problem with that message appearing, happens with every LP rom.
Click to expand...
Click to collapse
Not on Beanstalk 5.0, my last installation f.e.
Happend with RR with old CMW-Version last time.
Have you tried using a USB jig to see if your phone is completely dead or not? Is there battery left on your phone?
Click to expand...
Click to collapse
Yes he should try to achieve download mode, perhaps flash stock ROM and try to flash all again - in the end maybe.
I agree and also disagree with what you've said. I agree that it could be due to corruption, but it has nothing to do with the internal storage itself, but more accurately the system, data partitions on our phone, which can't have its filesystem changed. Ext4 is the only file system that is used for these inbuilt partitions, and so changing the file system of the SD card will give no benefit.
Click to expand...
Click to collapse
Yes.
But if I understand flashing, odin and CMW, correctly, both take the partition file in tar or zip and replace it in the device.
So could be a NAND write error?
Not long ago, I remember right now, I were confronted with a similar problem: CMW gave such an error, did not write correctly and closed the thread.
I flashed a new CMW recovery, or twrp maybe (came with another ROM or so).
In corresponding thread was suggested to format:
http://forum.xda-developers.com/showpost.php?p=60483702&postcount=5491
RtGh43 said:
Not on Beanstalk 5.0, my last installation f.e.
Happend with RR with old CMW-Version last time.
In corresponding thread was suggested to format:
http://forum.xda-developers.com/showpost.php?p=60483702&postcount=5491
Click to expand...
Click to collapse
Thanks for the link. However, this would be irrelevant if you can flash all other KK, JB roms or flashing anything in general. I guess it wouldn't hurt to try. From what I've flashed, the message occurs when flashing: CM12.1, SlimLP and similar roms. So in the OP's case, that message means nothing and should just be ignored. It's just the freezing that we should be worried about. I guess we just need to wait until the OP responds.
Fixed
After hours of search i found that the phone was soft-bricked.
I installed stock rom (because phone was without any software, just with recovery).
Then i found solution on youtube.
The same "error" appears.
Same way i left phone for some time (little longer for my phone) and it installed without any issues.
I got my F1 this morning and followed everything in the pixel edition guide. After first booting my phone I saw that I lost access to my PC connection (thought the drivers went bad but that wasn't the case) and my storge seem to be completely inacccessable from TWRP (but SD card was recognized). On the device itself I can't access the zip files that I had on preboot or anything the camera shoots. I did flash the Disable forced encryption and the Magisk Zips so I'm not sure why my device got encrypted anyway!
Where do I go from here to get back my file access and (presumably) dycript the device? My theory is that I should place all the files I need to do a clean install on the SD and wipe everything. But I'm not sure if that'll prevent encryption because it didn't the first time. Also, I'd be thankful if you pointed me to which zip files combination is the most functional since there's just so many different versions of everything!
Try format data then mount your local storage from twrp (you should see your storage pop on Windows) put your rom inside and flash it again
Format data not in advance wipe and then flash dfe.
SamyakJ said:
Format data not in advance wipe and then flash dfe.
Click to expand...
Click to collapse
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check
Abd121 said:
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check
Click to expand...
Click to collapse
In twrp you can't see anything except zip files but I think can see in file manager of twrp(haven't tested this)