I seem to have a damaged data partition on my Nook HD. All attempts to wipe, restore or write to the partition are unsuccessful using multiple TWRP versions and CWM. Attempts to flash ROMs, including all stock ROMs are unsuccessful. Once in a while I see a warning: "This /data backup was made with ext4 file system! The backup may not boot unless you change back to ext4." (Yes, that's ext4 x 2, but restoring usually just exits on an error).
Does anyone know a way to reformat or otherwise repair my /data partition?
Thank you.
Related
I found my data and cache partition corrupted, and i dont know why.
I don't know anyway to fix it but do SBF flash (so far I am doing the THIRD SBF flash today, really frustrating)
[edit] why i think data and cache partition corrupted:
1. I couldn't mount data and cache and psd partition in recovery, but i can mount sdcard (and can't unmount system partition, is it supposed that system can't be unmounted?)
2. when i booted up the system(Kayant's AOKP), the size of internal memory is 0.0B, as shown in the settings->storage
[/edit]
Is there any to fix without doing SBF flash?
another question:
How to prevent it/any precaution so that the partition wont mess up? (I probably did some wrong thats why the partition was messed up, but I have no idea what I had done wrong)
here is what i did:
I had had this problem before so I do a SBF flash and the problem is gone.(I installed Kayant's AOKP rom -4.1jb)
Yesterday I decided to flash another rom (that was Quarx's cm10.1 rom) i did a nandroid backup first, then installed the rom and installed some apps, after that I installed Kayant's Slim rom(from the new aokp paradise), i found some bug and at last decide to return to Kayant's AOKP rom. I installed the 2nd Init boot menu(coz i did the nandroid backup with CWMrecovery, not TWRP), and problems came while restoring it. It failed to restore /data partition, I tried more times but couldn't fix this. So at last I turned to SBF flashing.
I flashed and rooted it with SuperOneClick and installed 2nd Init boot menu then install the AOKP rom(didn't restore the nandroid this time) then factory reset-ed it with stock recovery, and I found the /data and /cache partition messed up again(obviously the partition isn't messed up right after SBF flashing because i can install the 2nd Init app).
Now I am doing the third SBF flash.
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
hotdog125 said:
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
Click to expand...
Click to collapse
should I use aroma wiper and do a ext4 wipe if i am going to flash jb roms (like cm10/android 4.1 or higher), to prevent messing it up?
is it necessary to do wipe before or after install a new rom?
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
dicksonlok said:
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
Click to expand...
Click to collapse
Yes, format to ext4 for JB ROMs. Full wipe not necessary but recommended.
Start afresh, install the ROM and restore data.
Plus, you shouldn't have installed 2ndinit again. You should have installed dual recovery and tried.
Got same problem, data and cache partition corrupted.
Fortunately I have TWRP installed so I went to File System utility and format data and cache (I choose ext3).
Then restored previous backup and everything worked like before!
I've had a few problems installing ROMs recently; boot loops, errors etc. And then when I try to restore my back-up, having wiped everything - /system, /data, /cache, /(int)sd_card, it reports a failure to restore the /data. But when I restart my phone, it's still how I left it: apps, phonebook, messages are still there and still work. I can read and write to the /data partition with ES or Xplore.
It first occurred using CWM but it did the same thing with TWRP, as well. TWRP reports 'failed to mount data', CWM, in Mounts & Storage, says "unmount /data" but nothing happens when I click on it. It just flashes and stays on 'unmount' option.
Backup data from both recoveries is fine. It's the right size and if I copy it to my PC and unpack it, everything is there so recovery has no problem reading the /data partition. Just writing to it. Or formatting it.
Any clues as to what's causing this would be greatly appreciated.
I'm running V20E Android 4.1.2 by szymel.
Hi.
I Have a problem on my SM-G900M (Klte)
After Interrupt(I pull off battery of a freeze while wiping System Partition) a Wipe in System Partition,
I Tried to flash Stock Firmware, Not Starting up, Not Booting
I Try to install a Custom ROM, Wiping not Working (TWRP 3.0.2-2): Could not mound /Data and unable to find crypto Footer.
"Failed to mount "/Cache /System /Data"
"Failed to Wipe Dalvik, System/Data, Cache, Internal"
How i Solve this problem?
Thank you.
EDIT:
I FOUND SOLUTION
I go to Wipe Section in TWRP, Repair or Change partition
System and Data, Changed Ext4 to EXTFAT
And changed back to Ext4
Partition Working normal.
killerBRs said:
Hi.
EDIT:
I FOUND SOLUTION
I go to Wipe Section in TWRP, Repair or Change partition
System and Data, Changed Ext4 to EXTFAT
And changed back to Ext4
Partition Working normal.
Click to expand...
Click to collapse
Nice to notice you find a solution to your pb.
And nice to see you explaining how you fixed it.
Best regards
Franck
Thanks helped solve a flashing problem
This was just what i needed as i had forgotten my partitions had been encrypted.
Great clear explanation worked great for me :good::laugh:
killerBRs said:
EDIT:
I FOUND SOLUTION
I go to Wipe Section in TWRP, Repair or Change partition
System and Data, Changed Ext4 to EXTFAT
And changed back to Ext4
Partition Working normal.
Click to expand...
Click to collapse
I love you
[HOWTO] [GUIDE] Repairing corrupted /data partition
[HOWTO] [GUIDE] Repairing corrupted /data partition
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited...
forum.xda-developers.com
So I finally unbricked and booted the stock rom. Now im trying to reroot the thing.
When I go to format/unencrypt in TWRP I get ERROR 255 -t 0 /dev/block/mmcblk0p54
Is my data partition permanently corrupted? I know that partition exists inside /data.
I've already tried to manually format /data, repairing it, changing it from f2fs to ext4 and back. All failed.
I'm have a similar problem. I cannot mount anything thru twrp. System, data, cache, can't do a wipe all fail. I've tried changing file system the back but it fails. I was able to mount my sdcard and start the recovery but.... its. Been "working" for and hour with no process increase. I'm wondering if I can force a fix partition thru adb sideload. Or... how can I decrypt it. Also the internal storage registers as 0 out of 0, same as /data
Sent from my SM-G930T1 using Tapatalk
Hello guys,
I had Lineage OS installed on my Galaxy S10+ and it got into boot loop after my phone lost power a few times because of low battery. The system halts at the Lineage Logo animating forever.
The problem is I canont access encrypted files on /data partition as it seems default Samsung encryption is used (and I have not disabled encryption when I was installing Linaage - I know - my mistake...) What I'm thinking to do is to do a dirty flash of the same system or an upgrade.
But before I will do it, I would like to do full backup of /data partition - sector by sector, so if my dirty flash won't work I can restore /data partition again and try to fix it again without loosing my data.
So my question is: How can I backup whole /data partition as an image? And how can I restore it?
My system is going into boot-loop, but I can get into recovery.
Thank you very much!!!
Encryption keys not withstanding it's the user partition that's likely been corrupted. You see where I'm going with this?
You try safe mode?