I did a factory reset and changed the Data partition to EXT4
still doesn't work
how do I fix it?
Edit: Fixed it using this https://forum.xda-developers.com/lenovo-p2/help/incredible-story-encrypt-phone-t3799057
Related
Hey guys
So i was trying to flash the new RR remix 7..
I formatted everything and now my TWRP shows 0 MB and i am unable to mount or flash ANYTHING except firmwares and recoveries.
I have NO clue what's going on
Any help will be greatly appreciated.
Thank you!
I was using 7.x the other day and tried to revert back to 6.x. Unfortunately, I couldn't because the data partition was set as f2fs. I tried changing it back to ext4 through twrp and it wouldn't work. It kept saying something about the data partition is busy or in use.
I fixed this by booting into fastboot and reformatting the data partition from there using the command: fastboot format:ext4 data (or maybe it was userdata?) I forgot lol.
Also, which partition did you reformat? I think it's only cache and data that is to be changed to f2fs for that ROM.
Hello.
I attempted to flash the Open Beta 7 (OTA_011) zip with TWRP to my OnePlus 3 and it broke everything.
The flash went normally, like with previous updates, but this time, I couldn't flash SuperSU over it. So I rebooted, hoping it worked.
I was presented by a "Decryption failed" screen, with the only option to factory reset.
The problem is, that I don't have any backups of my data, because FolderSyncLite aparently doesn't work at all.
When I got back into TWRP, my /data partition wasn't mounted, with the error
Code:
could not mount /data and unable to find crypto footer
TWRD shows the Data partition as 0MB. I know the data couldn't have just disappeared.
My best guess is that the userdata partition got corrupted somehow, and because it was encrypted, the entire partition is now useless.
TWRP's fsck.f2fs fails with error 255 (glitched error -1?), probably because it's encrypted.
Is there anything I can do to recover my data? Could I copy the raw partition to my computer and process it there?
Could I manually rebuild the broken header/footer? I still know the pattern/PIN and I don't think they're not salted.
I know there's some brilliant people on here. Please help.
Use the mega unbrick guide and everything will be fine
Edit: i didn't read that you're want to recover your data ... Hmm probably you can't recover your data anymore because your partition is currupted.
Look, change the data partition to ext4. It should work because sometimes the partition gets formatted to a corrupted form of f2fs. If it doesn't work, just wipe userdata and try again. It sure should work. Don't be shocked. Happens.
Thanks for the replies.
I tried a few more things, but the partition was beyond help. Full-disk encryption isn't very fault-tolerant.
I'll be using two sync programs from now on, just in case.
franga2000 said:
Thanks for the replies.
I tried a few more things, but the partition was beyond help. Full-disk encryption isn't very fault-tolerant.
I'll be using two sync programs from now on, just in case.
Click to expand...
Click to collapse
I have the same problem. The unbrick guide didn't help. Any ideas anyone?. Please help
Device storage corrupt
-The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
I tapped on reset but it just opened twrp and returned to this.
Story - I was trying to back up before a root. It said unable to mount /data so I watched a video that told me to change the file system. Now, this. I changed the system to vfat if it matters.
version - 7 model - SM-A504 build - can't access settings to check.
NVM I FIXED IT
HOW
Giphitt said:
Device storage corrupt
-The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
I tapped on reset but it just opened twrp and returned to this.
Story - I was trying to back up before a root. It said unable to mount /data so I watched a video that told me to change the file system. Now, this. I changed the system to vfat if it matters.
version - 7 model - SM-A504 build - can't access settings to check.
NVM I FIXED IT
Click to expand...
Click to collapse
How did you fix this issuse? My mother has just had the same problem with her phone, and I'm trying to look for a solution. thx in adv.
MorningGory said:
How did you fix this issuse? My mother has just had the same problem with her phone, and I'm trying to look for a solution. thx in adv.
Click to expand...
Click to collapse
You can fix it by changing the file format of the data partition to EXT2 and EXT4. This will mount the /data to twrp, and you will need to factory reset within twrp since if you reboot to the android, it will encrypt /data again.
what should be partitions format of data,system and cache?
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!
After installing the latest xiaomi.eu beta 20.12.9 (MIUI 12.3), OrangeFox no longer asks for decryption pattern. As a result, I cannot access my internal storage files. Before that I was on MIUI 11.0.12.0 and the recovery was prompting for decryption as usual. Has anyone encountered this issue? Is there any possible fix?
Format data partition
Already tried formatting data and re-installing to no avail but thank you for the suggestion. Everything gets encrypted again after first boot.