It first started when I flashed an ICS rom. Thereafter I have been unable to get working any other roms. I read somewhere that I need to format /system /boot /cache /data partitions. /boot makes sense because any other rom that I flash hangs on the HTC splash screen. But here is my problem, I cannot find an option in TWRP 2.0 for formatting /boot. I have flashed CWM 4.0.1.4 and same thing, no option for format /boot. How can I format /boot?
the superwipe ZIPs that are floating around the forum should be able to do it, alternatively, I think it can also be done from fastboot, somebody who knows more than me should be able to confirm it.
The fastboot command to erase boot is:
Code:
fastboot erase boot
But i dont know why you should have to do all that. Should be sufficient to clear data and flash a new rom, they all include boot.img files.
Eighteen90 said:
It first started when I flashed an ICS rom. Thereafter I have been unable to get working any other roms. I read somewhere that I need to format /system /boot /cache /data partitions. /boot makes sense because any other rom that I flash hangs on the HTC splash screen. But here is my problem, I cannot find an option in TWRP 2.0 for formatting /boot. I have flashed CWM 4.0.1.4 and same thing, no option for format /boot. How can I format /boot?
Click to expand...
Click to collapse
Flash CWM 5.0.2.0 via ROM Manager and you can wipe your boot partition from there. Just please do be careful, formatting boot is NEVER usually a good idea unless the partition has become corrupt. Have you tried wiping dalvik cache along with system, data, cache, and battery stats? I'd give that a try beforehand. Good luck, mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
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.
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
aleksandar9999a said:
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
Click to expand...
Click to collapse
I didn't just suggest to format anything...
The important thing is to reflash twrp via fastboot.
The point is that after doing this you might even be able at all again to format data...
If you follow the further steps I think you're good to go and don't need to change any file system.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
Thats because maybe on a backup you select another storage that nota the internal storage....maybe you select otg storage ir something....put the selection on Internal storage....and it resolves
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Stonner_99 said:
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Click to expand...
Click to collapse
me either, my problem. RRD. pls anyhelp?
Hutabarat said:
me either, my problem. RRD. pls anyhelp?
Click to expand...
Click to collapse
Hi, I had the same problem. (Redmi Note 4, Mido)
But after installing RedWolf (Build 27)
with adb/fastboot and everything works fine - without formating everything.
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
solution about unable to mount data on s7 edge
Hi,
Make sure to do a backup of your data, all data will be erased
after many attempts to find the solution
i tried to go to recovery latest twrp:
go to wipe
select data
for me i choosed ext3 and make repair
than i select Fat and again ext3
you can choose another file system
Thank you
Thanks this worked for me
This is the best answer to solve the problem:
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Thanks to you I was able to recover my wife's Redmi 5. Cheers :good:
could not mount data and unable to find crypto error
Good morning guys im using Xiaomi Redmi note 4x(mido) i installed LineageOS 15.1 then the gapps, but the google photos and other google apps keep crashing and recommended me to uninstall and install again. so i wen to twrp and installed the gapps again, then it keeps crashing again. so what i did is to wipe in twrp then installed linneage and the gapps but when rebooting it asked my password then after than i can't no longer boot it keep sayingf could not mount/data and unable to find crypto. i tried all the steps and fix i found here and in other sites but it does not work when i try changing it to other file system it says mke2fs -t ext3 -b 4096 /dev/block/mmcblk0p49, and error 64. Please help thank you
Still not able to mount storage.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
I tried everything that is:
-changing file system also gives "unable to mount storage " in every format like fat, ext2, ext3, ext4.
-factory reset also gives same error "unable to mount storage"
-I also tried different recovery.
Please someone help me!!!
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Format data solved everything. But before format data, you better backup all your files. Because all of it will be erased like new.
Thank you.
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
I LOVE YOU!!! U saved me when nothing worked. Ty so much !!
Hey King,
I do not use a Redmi Note 8, yet I had the same problem with my Moto G5 Plus.
Until I read your post and now my phone works.
Thank you!
Hi, i have TWRP 3.6.0 installed on my mi 11 lite (courbet), and then it shows "unable to mount /data". I know, formatting helps, but what to do if i don't want to format it, only i want to update the rom?
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?