Back in the day I had my phone encrypted with data as a ext4 partition, I switched to using f2fs for a long time.
Now that I've tried to go back to using data as a ext4 partition while booting android asks for a invalid decryption password
using a really old pin number (I've had it encrypted several times since then using f2fs with different pin numbers) from the first
time I encrypted my partition while it was ext4.
Now when ever I wipe my data partition and try and use it as ext4 while booting android asks for a decryption pin which I can enter
but then complains that the filesystem it is trying to decrypt is corrupt.
I've tried doing a data format in twrp but it automatically formats it f2fs which doesn't solve the problem since
the problem only shows up while data is formated ext4.
I've tried every piece of wisdom I can find on the internet.
factory reset,
formatting all partitions,
dd front and back of userdata and then make_ext4 on userdata,
twrp format data,
recovery --wipe_data --set_encrypted_filesystem=off (from within twrp with the partition formated ext4),
format f2fs then boot up and reset and format ext4,
etc.
How do I give data the ultimate clean slate for being formatted ext4?
Or where is the remnant of the old encryption info stored from the first time I encrypted my phone?
I can format my data partition f2fs but frankly I was a little stunned when I saw the kind of overhead that filesystem has,
its space using overhead is way more then I want to have in a filesystem, or any filesystem I've ever seen.
Also is the problem not what I think it is?
Faced the same behaviour on my xt1524. Would be interesting to know if there is a solution for this
Is there a way to generate a new encryption from within the recovery?
Since it won't boot with data formatted as ext4.
Formatting it ext4 and then putting a new valid encryption on it?
From what I've found it, if the UI to unlock the partition on boot had a cancel button the system would boot as normal.
Unfortunately there is no cancel button on the unlock encrypted partition screen on our device. =/
Tried flashing a different recovery and using it wiping tools on data.
official twrp-3.0.2-0-surnia.img.
mkfs-f2fs -t 0 /dev/block/mmcblk0p44
process ended with ERROR:255
Unable to wipe Data.
Unable to format to remove encryption.
Also data wiping on TWRP is defaulting to trying to format data as F2FS which isn't even the default,
and while the partition has been switched to ext4.
I'd like to fastboot erase userdata and then fastboot format userdata.
But its giving me this error message.
fastboot format userdata
(bootloader) has-slot:userdata: not found
Formatting is not supported for file system with type 'raw'.
I've already done a lot of looking around on this issue, I'm normally not worried about this but
formatting internal system partitions that I don't understand how its different from a standard
desktop computers layout does worry me.
Should I be doing a full wipe and format everything to stock and then back to a custom rom?
God I wish this was a desktop computer right now, wipe the hard drive and reinstall the operating system,
there is something to be said for being simple and straight forward.
WTB cellular modem support in standard operating systems, and handheld devices that
can run standard operating systems.
I'd ditch this overcomplicated vendor locked sht so fast and never look back.
Following this guide to setup a new system encryption with rom in one go from the start with data as ext4 to see if I can bypass it this way.
But I'm getting a cannot find libraries error running cryptfs format command from adb shell or twrp terminal. b(>.<)d
http://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting
All this because someone thought it would be a great idea to take off the cancel button on data decryption
during boot.
This is why god invented beer and soaking you're brain in alcohol.
Damn been at this thing all day and still no luck.
Can I smoke the whole userdata partition with DD without bricking the phone?
In fact what can I effectively zero on a android phone without bricking it?
Am I miss reading this problem? Is the new inbuilt ext4 encryption (ext4 filesystem now has built in encryption support on newer kernels) support assumed to be on?
Never mind not as solved as I thought, But I just found another way to have my partition set to F2FS with letting me know. (^.^)
God this illustrates why formatting utilities that take shortcuts and 'ghetto erase' stuff are bad.
*Edited*
Default filesystem from the factory was F2FS (I have a bad memory : ) looks like it doesn't support putting data on Ext4.
Editing this post because I did a lot of post updates on what I was trouble shooting, but that might have
pissed people off because it does 'bump' the thread.
Sigh I'm throwing in the towel and formatting F2FS and moving on, F2FS is a one way door one which you never get back to ext4 from. > : (
Or ext4 formatting utilities suck balls and don't do their jobs.
Format all partitions to f2fs reboot to recovery again and format system and cache to ext4 now make a factory reset and reboot.
Was the original filesystem Ext4 or F2FS on the Moto E's Data partition?
Also does it support any other filesystems?
Its been too long I don't remember.
dreyeth said:
Was the original filesystem Ext4 or F2FS on the Moto E's Data partition?
Also does it support any other filesystems?
Its been too long I don't remember.
Click to expand...
Click to collapse
F2FS is the original file system of data partition. System and cache partition filesystem is Ext4.
Badrikesh said:
F2FS is the original file system of data partition. System and cache partition filesystem is Ext4.
Click to expand...
Click to collapse
I have a really bad memory, I was doing a ton of trouble shooting to figure out why I couldn't switch it back to Ext4.
Almost bricked the thing doing a bunch of tests, though I learned alot about the recovery process. >_>
All because I couldn't remember the original filesystem was F2FS on data.
Thank you. xD
If I remember, is ext4.
Welcome!
Why not able to format system partition to f2fs? Data and cache worked well but if i.try to format sytem to f2fs it is still ext4. G925F latest twrp.
Hey,
basically the title. I have rooted my Redmi Note 10 as i am doing some analysis using autopsy. Surprisingly, i was unable to analyse the userdata partition as autopsy does not support f2fs. I was not expecting a f2fs data partition as the system partition is also formatted as ext4. Without switching to a custom ROM, is it possible to force MIUI 12.5.5 to use ext4 by re-formatting and re-flashing the device?
in my humble opinion you shouldn't mess with partitions
Well, that does not solve my problem^^ I tried to change the partition using TWRP. However, whenever i flash the MIUI ROM, the process formats the userdata partition back to f2fs. Even TWRP will reformat the userdata partition to f2fs when i format the data. Where is defined to which format TWRP formats the partitions? Has anyone an idea on how to solve this issue?
After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Edit: New thread here. <<<
Try format . Wipe dalvik cache / cache / data
resty1 said:
After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Click to expand...
Click to collapse
What method do you use for flashing twrp recovery?
Not all devices use ext4. Are you sure this one does?