hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
n0te8user said:
hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
Click to expand...
Click to collapse
If you are using twrp from this thread, it's mentioned on the 3rd post
corsicanu said:
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Click to expand...
Click to collapse
or maybe try to disable data encryption which is mentioned on the 1st post
corsicanu said:
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Click to expand...
Click to collapse
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
ace2nutzer said:
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
Click to expand...
Click to collapse
i know i tried this but mine stock rom installed after flashing with odin (turkey) and after apply twrp format data stock rom are very different. the second i said seems like global rom. it contains weird settings and apps I will do what you say and take a screenshot,1 2 hours later you will understand me better.
Related
Hey guys,
My work switched to Google Apps for their email so i wanted to test it out on my phone. Doing so required them to encrypt my phone. What this appears to have done is encrypt the data partition. So now when i go into (TWRP) recovery and try to do a backup / wipe / or anything else, it says it is "Unable to mount /sdcard" I'm unable to do a factory reset of any kind so i'm essentially stuck on this rom (ARHD) until i can figure out how to wipe data and get the /sdcard to be not encrypted. Does anyone have any ideas? I'm imagining that with the modified recovery not being able to access the data partition that i'm going to have to do some adb type stuff?
Please help! I want to keep flashing new roms!
Anyone??
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Guich said:
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Click to expand...
Click to collapse
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
jrun said:
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
Click to expand...
Click to collapse
Hi! Only TWRP recovery can solve your issue just do this...
Boot to TWRP recovery->Wipe
From there there are 2 options the left is the advance wipe and on the right is Format Data
Just select the format data button and it should reformat the whole data partition.
1st one would prompt so many errors and reformat then reformat it again 1 time and it should fully reformat your phone.
In theory it should reformat data partition even when encrypted but just in case it fails and I won't be able to go back to this thread just boot in bootloader and type
"fastboot erase userdata"
Well none of that works. TWRP doesn't support decryption yet for this device.
sevenalive said:
Well none of that works. TWRP doesn't support decryption yet for this device.
Click to expand...
Click to collapse
What I instructed basically doesn't decrypt the partition. It reformats it.
Riyal said:
What I instructed basically doesn't decrypt the partition. It reformats it.
Click to expand...
Click to collapse
I know what you instructed, it doesn't work. Only way I got it to work. Flash the stock recovery. Boot into system. Take off the encryption, phone reboots and removes the encryption, data is formatted. Then flash TWRP again.
I basically ran into this exact problem. I was hoping that I'd still be able to back up the encrypted device, but forget about it. What a pain in the ass.
Someone should make add something to the guides about how encrypting your device makes nandroid backups impossible.
So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?
Same problem...
Format data in twrp to fix encryption error
CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?
marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.
Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data
CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage
CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.
edit: wrong thread
Hi,
I made this guideline for those who want to convert filesystem from EXT3 / EXT4 to F2FS on lavendar, for amazing speed & performance.
I already had MIUI EU beta working on my phone.
Note: Internal data storage will be wiped. Make sure to have a backup.
Steps:
1. Install Orange Fox Recovery (latest one)
2. Reboot to recovery
3. Go to Manage Partition
4. Select "Cache" and click orange tick button, then choose F2FS as the file
system and proceed.
5. Again, select "Data" and click orange tick button, then choose F2FS as the file
system and proceed.
6. Reboot to Recovery again.
7. Install a custom kernel which support F2FS (i.e Evira)
8. Install Universal F2FS support patch file. (otherwise causing boot loop)
9. Reboot
Enjoy the speed.>>>>>>>>>>>
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Click to expand...
Click to collapse
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
jalzate94 said:
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
Click to expand...
Click to collapse
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Plast0000 said:
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Click to expand...
Click to collapse
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Plast0000 said:
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Click to expand...
Click to collapse
... Well, my info is wrong then... In this case it would be useful
Sent from my Note 5 / 5 Plus using XDA Labs
White_Lion said:
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Click to expand...
Click to collapse
No, the data partition will be converted back to ext4 everytime you do "format data".
Not formatting your data could keep the f2fs status, but it's risky to not formatting data when changing ROM in lavender due to it's strict encryption issue.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
Click to expand...
Click to collapse
Miui.eu ROMs doesn't fully support F2FS. The rom does, but the kernel doesn't.
You need to make sure both the ROM and kernel has F2FS support.
if one of them don't, you'll get bootloop.
Plast0000 said:
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Click to expand...
Click to collapse
I've been on F2FS since.. April I think, and I've installed and tried so many roms without any problem.
here's what I normally do and it works all the time:
- Make sure data & cache are ext4
- format data
- reboot recovery,
- wipe cache, dalvik, system, data, internal,
- flash firmware
- flash ROM
- flash gapps (optional)
- flash magisk
- flash kernel that has f2fs support (optional, if the rom's kernel doesn't support F2FS)
- reboot system
————————————————————————
it's necessary to install the rom in EXT4 because automatic encryption doesn't work in f2fs partition (I think... based on my experience). granted, you can do the encryption manually from settings, but it's require to have 80%++ battery and the more stuff you have in your internal, the longer it'd take to manually encrypt the device. automatic encryption is just easier to do. You can leave your internal decrypted as well, but you won't be able to use your fingerprint or any screen lock methods. That's just how redmi 7 family works.
————————————————————————
- once you get into system, reboot to recovery once again
- convert cache & data to f2fs
- flash magisk
- flash universal f2fs patch
- reboot
now your /data and /cache are in f2fs.
If you're already on a rom and kernel that support f2fs, you can just do the later half of this tutorial without the need to reinstall rom and everything, but you'd lose all your data. good luck!
What's the benefit of changing cache into F2FS?
begging
Seeking flash tutorial videos
Thanks
thx for guide.
Which custom rom that support f2fs?
Hy i have problem my phone after half an hour after of fresh instal (factory reset) change file system from ext4 to emmc,
when i wipe It than I can acces in storage, but for now is 0mb avilable, i tried to flash dm verity but my phone on first start up
tell some problems and need again factory reset.
I have installed magisk and elementalx kernel
When I get in twrp it ask for password
Could I make a back up, and than change file system to ext4 and restore files?
sory for bad english
I solved the problem, if you lose your memory and ask password when you turn on twrp, just type yoar pasword to
unlock yoar phone or "default_password"
Andrea Buti said:
Hy i have problem my phone after half an hour after of fresh instal (factory reset) change file system from ext4 to emmc,
Click to expand...
Click to collapse
I am not sure what you mean here. ext4 is a file system. but emmc is a date storage device , on which you can create partitions which then you can format with a file system of your choosing such as ext4 or ext3. Can you describe what you actually did?
When i get in recovery, twrp ask me password if you not put password you can't install anithing you can yust wipe.
You need to put password when you get in and than is ext4
I just did a full flash and erase with sweet_global_images_V13.0.12.0.SKFMIXM_20220801.0000.00_12.0_global ROM.
after a quick rom setup with no sim and no wifi, I went back to TWRP and the data partition can't be mounted.
I tried then the usual advanced wipe, setting the partition to ext2 then to ext4 and the rom does not boot and goes back to recovery.
If from recovery I do a wipe, then the rom starts, but after setup, going back to TWRP gives agaion the same problem and the data partition can't be mounted.
Any Idea?
which TWRP version you use?
Zibri said:
....Any Idea?
Click to expand...
Click to collapse
Have you format data partition before starting the new rom?
Format is neccesary to remove the encryption of the formal rom.
Wipe data isn't enough for that.
yes I did... but I think MIUI reformats it.
which twrp are you using?
Maybe the twrp you're using doesn't support encryption yet
it worked with MIUI 12.5.9.. but MIUI 13.0.12 reformats the userdata partition if it is formatted with twrp.
maybe because of dm-verity but I am not sure.
I just did this:
FULL FLASH from EDL or FASTBOOT without relock and including userdata.
Then fastboot boot twrp-3.6.2_11-0-sweet.img
Form TWRP I reformatted userdata as EXT4.
Then booted the system... after booting for the first time the system, userdasta is again encrypted.
Yes, seems u are using twrp which not support decryption yet, change ur twrp/ofox then (there is 1 that already support android 13)