Hi together,
i have an problem with the tablet encryption.
i wanna swap from xiaomi.eu to another more actual custom rom..
i tried PixelExperience , Havoc-OS, dotOS, ArrowOs .. and everytime i activate the encryption it's end in an bootloop regardless of pin,password,pattern ..
I'm using the latest TWRP Version
- Wipe Dalvik/ART Cache, Cache, System, Vendor, Data
- Flash from zip
- start os and enable encryption
-> bootloop
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
aes32 said:
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
Click to expand...
Click to collapse
Hi,
thanks for your answer. As i wrote i delete nearly everything
The OS booted, but at the point where i want to enable encryption most roms get stuck in a bootloop.
After endless roms i found carbonrom which works.. Additionally i found an post from TWRP about encryption.. i don't know if it's connected, but i guess it's an similar problem cause AOSP..
Why doesn't TWRP support encryption on my device?
Why doesn't TWRP support encryption on my device?TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, wh...
twrp.me
So i found a working rom, but not the solution or true cause of the bootloop problem
Ok, I understand.
I guess I don't know the encryption feature well enough to help.
Found some interesting stuff to read about it, not sure if it applies to the Mi Pad 4 and its custom ROMs, though:
Any way to encrypt /data/data and /sdcard on Xiaomi EU ROM?
Hello, Xiaomi EU ROM is running decrypted, that's a security breach... Is there a way to use Xiaomi EU ROM, based on Miui 10, in a encrypted phone? Thanks
forum.xda-developers.com
So the bootloop seems to be expected and if I got it right then the fstab.qcom needs an edit at least.
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
xXZaretXx said:
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
Click to expand...
Click to collapse
Yes, sorry, I fully understand your point of view.
It is confusing me as well.
I'm currently experimenting with some ROM's, so yesterday I gave encryption on Havoc-OS a try - even by starting with encrypted stock rom, flashing Havoc-OS and modifying fstab.qcom - but without success. It rebooted immediately and then seemed to be hanging idle during boot for a long time.
I was not interested in encryption so far, but of course it would be great if it worked. And I should be interested for the sake of privacy.
Thanks for reporting that it works with the carbon ROM.
Edit: In Lineage OS it will probably work too, based on the description of the ROM.
I will probably try that one next, because it is also supposed to have the "split screen" feature which I am looking for.
Encryption in Lineage OS seems to work fine, as expected.
I tried to analyze Havoc OS encryption once more: It seems not to be supported at all.
It does "something" trying to encrypt... because TWRP asked for a password the next time I rebooted to recovery. Problem is, decryption in TWRP did not work with the previously given password and the data partition seemed to be messed up (file system type was "emmc", and the data partition was not responding to any of tune2fs, e2fsck or alike).
I looked at the dmesg log, it seems during the boot attempt, the system just cannot work with data any more (hence the idle hang, I assume).
There are many many log lines, showing attempts to work with data and that the system actually expects an ext4 file system for "userdata" (=mmcblk0p64):
Code:
[ 2.990548] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.990698] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996651] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996795] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
Related
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.
When I try to format my Data partition to F2FS it shows:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda9 process ended with ERROR: 1
Unable to wipe Data.
Error changing file system.
And also when I format System to F2FS it succeeds but when I install a ROM (AOSiP) it won't install unless I reformat it back to ext4.
Hope anyone can help..
Thank you!
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Jabbzz said:
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
Click to expand...
Click to collapse
Heyyo, hmm if that is the case I think AOSPExtended doesn't support quota for storage.. the only way to resolve this is to backup your data, copy it to USB OTG or to a PC and then going to wipe > format data > yes. After that you can copy back your data and restore the data backup.
drml said:
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Click to expand...
Click to collapse
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
ThE_MarD said:
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
Click to expand...
Click to collapse
f2fs ist superior to ext4 especially in write operations. That's way if you use f2fs you don't be affected to the slowness who comes with the time with the ext4. Otherwise ext4 exist longer and is more, lot of people assume this, stable. I use f2fs long enough to say that my last freezes with the f2fs filesystem are way back to 2014. Even then I would say that the troubles come with the custom roms than with the f2fs.
I use in my x2 the Lineage unofficial with f2fs without a single performance degradation and before that used Infrag nougat aicp with f2fs. F2fs is better but lot of people have trouble or they don't know how to convert the /data partition and before that that they must Backup the /internal Sdcard as the convert process wipe the whole /data + /internalsd
Here more Infos why f2fs is the better filesystem
https://www.google.com.cy/amp/s/www...ms-matter-interview-stan-dmitriev-tuxera/amp/
https://www.linux.org/threads/flash-friendly-file-system-f2fs.8931/
I try official releases of lineage 15.1, Omnirom and when I run encryption from option (with password), android reboot without encryption of /data partition.
I have seen that unoffical release of lineage 16, Aosp 9 has issues in hardware encryption. No problem with official MIUI Rom also.
Are there any custom rom for mido that allow encryption ?
(My configuration, special MIDO TWRP treble support)
Thanks for your experience return.
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
i am using lineage os 15.1 with encryption.
I didnt manually encrypted my phone but it got encrypted during installation of los 15.1
BK said:
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
Click to expand...
Click to collapse
I use ext4 on another encryptedr mido with miui official.
Rohit338 said:
i am using lineage os 15.1 with encryption.
I didnt manually encrypted my phone but it got encrypted during installation of los 15.1
Click to expand...
Click to collapse
Are you sure ? because the assistant does not prompt for encryption but only for lock password.
I have tryed to reset with flashboot flash_all.sh but no difference after Los 15.1 install
What recovery do you use ? TWRP or REDWOLF ?
BK said:
I think it depend of the data partition if its F2FS or EXT4 , but i dont encrypt anymore , the one who would crack my phone would be left with unsatisfaction, at the end it would just prove that humans are never satisfied.
Click to expand...
Click to collapse
I can now answer, F2FS make no difference, same problem no encryption with custum rom
neo_mat said:
Are you sure ? because the assistant does not prompt for encryption but only for lock password.
I have tryed to reset with flashboot flash_all.sh but no difference after Los 15.1 install
What recovery do you use ? TWRP or REDWOLF ?
Click to expand...
Click to collapse
For installation i used twrp posted on 1st page.
but now i am using red wolf recovery.
yes it doesn't prompt for encryption but i think setting the lock pattern encrypted the phone as i have to draw the same pattern to access internal storage using red wolf and during booting.
Rohit338 said:
For installation i used twrp posted on 1st page.
but now i am using red wolf recovery.
yes it doesn't prompt for encryption but i think setting the lock pattern encrypted the phone as i have to draw the same pattern to access internal storage using red wolf and during booting.
Click to expand...
Click to collapse
Curious because, android need the password in order to decrypt…
Did your recovery prompt for password ? (recovery is OS independant) if not, your device is not encrypted.
neo_mat said:
Curious because, android need the password in order to decrypt…
Did your recovery prompt for password ? (recovery is OS independant) if not, your device is not encrypted.
Click to expand...
Click to collapse
yes recovery asks for password to decrypt internal storage by the way have you checked the screenshot i have attached.
thanks, yes i have seen sreenshot.
I really don't understand because it s do basic.
I use the same twrp,
I wipe all partitions
after that, the redmi note 4 is empty (no system, no data...)
I install los 15.1
run encryption with assistant
the redmi immediatly reboot without pass throught mi boot logo screen
and no encryption
I can loop that everytimes.
It's curious because the redmi immediatly reboot like a bad reboot. (like an error)
I don"t know if there is any log of that
steps that i followed
flashed twrp
wipe all
advance data format (entered YES to format)
and finally flashed los.
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
neo_mat said:
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
Click to expand...
Click to collapse
Great news! Does it mean you could encrypt your device on a Pie ROM?
Of course !
I can now encrypt my device.
neo_mat said:
Of course !
I can now encrypt my device.
Click to expand...
Click to collapse
That's great news. I am pretty used to flashing my beloved mido but I never used the tool you mentioned (resize2fs). Would be great if you could provide some kind of documentation how to do this?
neo_mat said:
I found it !!!
This can save people.
I have to leave 4K block into userdata partition.
In fact, fastboot, and TWRP can break filesystem and resize filesystem to all partition size.
Encryption need 4K block in order to write encryption data about userdata patition.
I have resized my ext4 filesystem with resize2fs.
Now all is OK !!!!
After that, I also format from ext4 to f2fs.
Thanks
Click to expand...
Click to collapse
how to do it, can you explain it please?
I'm trying to disable encryption because with pretty much every ROM I tried the phone ends up encrypted. Which is very annoying as it prevents dirty flashes (+ updates) and flashing things like Magisk after first boot
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
tzagaritos said:
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
Click to expand...
Click to collapse
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
SubwayChamp said:
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
Click to expand...
Click to collapse
thanks a lot , i did not know that i could flash zip files in that way, you saved me thanks again
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
borg4571 said:
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
Click to expand...
Click to collapse
Is possible to send me the img file through Google drive or anything familiar;its a mess trying yo download from the Chinese site
I have Android pie
I´ve tried to find any specific info on the subject for this phone but found none.
Maybe someone can help.
All was good on my phone when using Havoc custom rom. Yesterday I tested an android 11 custom rom on the device but decided to go back to 10. Orange Fox recovery restore gets stuck in the boot process. When using TWRP it can´t acess Data partition, so I´m unable to make any backups of data partition with it.
I´ve tried two diferent versions of either, and on TWRP after formating data the partition is once again acessible, but as soon as I flash a custom rom (tried two diferent one´s), boot to it and then reboot to recovery the Data partition is once again unacessible (encrypted) showing "0 MB".
Orange Fox recovery allows to access the data partition and so allows for backups to be created, but the restore process always ends up suck at boot (odly enough when enabling MTP on Orange Fox and connecting the phone to my Windows 10 machine two internal storage partitions appear in Explorer along side the SDCard one - all with the same content exactly). Something weird is going on here.
I´ve tried the steps on this post regarding DM verify (I do not know if it has got something to do with it) but it did not work (the fstab file already shows decryption on its entries):
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Has anyone had similar problems or knows what might be going on on my device?
Is the internal flash memory going bad maybe? I´m at a dead end here.
Apreciate any idea.
Thank you.