Stuck in TWRP after OTA update - Redmi Note 8 Questions & Answers

Hi,
I was following this guide to finally update my redmi note 8 to MIUI global 11.0.12.00 (I don't remeber which version exactly I had before). I flashed the zip with TWRP and everything went fine, but I cannot boot now, I always go into TWRP when rebooting.
What could be causing this? I was rooted before, through magisk, and I did not reflash it. Would that help?
Any help appreciated
Edit: I installed magisk through TWRP, which was successful but I still wasn't able to boot. I then reflashed the OTA update and immediately installed magisk, which also did not work.
I read that flashing the stock recovery might help, but I don't know what to try next
Edit: I extracted boot.img from the OTA zip and ran fastboot boot boot.img, still got sent to TWRP
Edit: I flashed the stock recovery, now instead of booting into TWRP I boot into the MIUI recovery, which I suppose makes sense. I really wish there's something I can do without wiping my data.
I've reflashed twrp for now, and I'm gonna sleep for today. Hopefully I have some replies by the morning. Next I'm planning to flash the latest rom directly from en.miui.com (11.0.11.0)
Thanks

Also, in case I have to do a factory reset, which partitions can I then restore with TWRP (If I back them up now)? Most of all I really want to keep my app data. Am I forgetting anything else that's important?

try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works

oindividuo said:
Hi
Click to expand...
Click to collapse
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work

Baim alif said:
try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works
Click to expand...
Click to collapse
Just to clarify, dtbo.img is the one inside the OTA zip and dm-verity can be the Disable_Dm-Verity-09.02.2018.zip file found here? https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/

loopypalm said:
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work
Click to expand...
Click to collapse
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way

Baim alif said:
[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
Click to expand...
Click to collapse
use this bro

oindividuo said:
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way
Click to expand...
Click to collapse
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed

Baim alif said:
use this bro
Click to expand...
Click to collapse
So first I flash dtbo with fastboot (fastboot flash dtbo dtbo.img?), then boot into twrp, then flash dm-verity?
Thank you

good luck bro

Baim alif said:
good luck bro
Click to expand...
Click to collapse
Now I'm not being redirected to TWRP, but I'm in a bootloop :/

loopypalm said:
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed
Click to expand...
Click to collapse
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance

oindividuo said:
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance
Click to expand...
Click to collapse
you can't browse data folder without root
you can do it with the recovery file manager but it will take too much time
orangefox file manager is better if you don't want root ...

Related

TWRP backup - Can I restore some app data without restoring the whole image?

So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Titanium Backup can do that.
danvee said:
Titanium Backup can do that.
Click to expand...
Click to collapse
Ok, can it read the data in the TWRP folder? I have used TB a lot in the past but didn't think it might be able to use the TWRP data.
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
Ah, need the pro version. Hmm, thanks. I'll check it out.
Coronado is dead said:
Ah, need the pro version. Hmm, thanks. I'll check it out.
Click to expand...
Click to collapse
Use Nandroid Backup Manager. It's free.
It can restore apps and/or data, SMS messages, Call logs and more from your nandroid backup. It can also decompress the backup if it's compressed.
Advance Restore and just click restore data only on twrp
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
thank you man thank you. i just had this http://forum.xda-developers.com/showpost.php?p=49548141&postcount=136 problem and your post is gonna help me i hope thanks. btw im on 4ext recovery
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
Good day: Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Or, did you mean that Nandroid Manager has an advanced menu?
Regards
galearned said:
Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Click to expand...
Click to collapse
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
tetakpatak said:
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Pfeffernuss said:
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Click to expand...
Click to collapse
Of course. TWRP has no advanced backup&restore features because it doesn't need them: you will be prompted before each backup&restore action about the partitions.
For data of just single apps use better Titanium Backup. It can extract them from your nandroid backups
tetakpatalked from N7100
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
does it restore gapps too?
javigbox said:
does it restore gapps too?
Click to expand...
Click to collapse
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
jassalmithu said:
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
Click to expand...
Click to collapse
Exactly what I do.
marsmallow 6 will update apps + data from your google account. Not sure it's fully implemented yet but it's supposed to work. I've tried it yesterday with a Mm6.0.1 on nexus 7 2013 and many apps were already configured. Not all of them. Going from MM6 to MM6.0.1 might complicate it so maybe it's better to restore with google and do a little work by yourself, to make sure. I gave up on those restore apps. It also give you the opportunity to do a clean up
Coronado is dead said:
So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Click to expand...
Click to collapse
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
---------- Post added at 08:57 AM ---------- Previous post was at 08:24 AM ----------
DIGVIJAY24 said:
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
And believe me, I could repack the data into my new ROM just like that!
Not sure if this messes up with your system but I'm going great so far.
So you Upgraded to a higher OS and find some of your apps to be crashing on your new ROM & have a nandroid of your stock:
You are going to switch data files between stock & custom ROM!
1.Flash the Stock ROM & copy app data from the system files to readable memory, as mentioned above, just add a letter & Rename the copy(which again you can do with TWRP!) so that TWRP may not confuse with the new folder
2.Flash the new ROM, uninstall the app that crashes & install the compatible version from the store
3.Allow storage permission from settings; open the app & perform some action so that a storage directory is created,if not already, in the system storage
4.Boot to TWRP recovery in the new ROM , so now you have the data/data folder of the new app you just installed(which is empty) as well as the data/data folder from your stock ROM on your SD/Ext.SD
5. You know were this is going[emoji16] Delete the data/data folder on your running ROM & MOVE(again with TWRP only!) the one from SD ,after restoring its original name, to the data folder from were you just deleted the other.
6.Wipe Dalvik/caches & reboot
7. Other than receiving a pop up that there may be some trouble with your android system, on startup, everything works just fine for me & the App is fully restored!![emoji7]
Didn't even use a PC!!
Such a tool TWRP is[emoji7][emoji120][emoji120][emoji120]
Forgive me, but try this at your own risk, coz as a newbie Im completely unaware of the consequences
Hope this helps somebody[emoji4]
Sent from my GT-N5110 using Tapatalk
DIGVIJAY24 said:
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
Click to expand...
Click to collapse
I don't understand this step. I go to file manager, then navigate to /external_sd/TWRP/BACKUPS/... and there are files like data.f2fs.win009. Now what?

[FLASHABLE_SCRIPT][UPDATED_ERRORS FIXED] Increase system space to 1.2/2GB [15/7/2017]

-By following this you can can increase /system space from default 800MB to 1.2GB/2GB
-You can flash gapps on CM ROMs without insufficient space issue.
-You can flash regular MIUI ROMs too,without any issue.
Statutory warning
*Repartition can kill your phone forever if anything goes wrong,so proceed with caution (and make sure you have at least 30% battery)
*This process would format your internal sdcard,backup its contents
*I'm not responsible If your phone dies during this procedure under any circumstances beyond control
Prerequisites:
1)Redmi 1s partition script_system space 1.2GB.zip/2GB.zip
2)Parted
3)Twrp v3.0.2-1.zip
4)Download and copy all these files to external sdcard
Procedure:
1)Flash Twrp recovery(incase if aren't already using it).
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manager for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Redmi 1s partition script_system space 1.2GB.zip/2GB.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)Install your ROM(don't flash gapps now).
9)Back again to Twrp start screen select "Wipe"-->Advanced wipe-->select/mark "System"-->press "Repair or change file system(notice that size hasn't increased to 1.2GB/2GB)-->Resize file system.
10)Back(though size of partition appears unchanged, its actually increased to 1.2GB)-->Back>select/mark"System"-->Repair or change file system-->Notice size of partition increased.
10)Back to Twrp start screen and flash gapps,that's it.
Reset to default partition:
1)I am also giving link for flashabe script file "Reset to default partition.zip" for restoring default partition sizes.
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manage for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Reset to default partition.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)that's it you are back to default partition.
PS:
1.Need for "Resizing System partition"(step 9) comes only with CM14.1(haven't tried other CM versions or other custom roms) no need to do that if you are flasing MIUI ROMs(i,e you can skip step 9 if you are flashing MIUI ROMs)
2.If you still need more System space or want to further modify partition table(only if you know what you are doing),you can edit "update-binary" file inside the zip as per your needs.
Credits:
1)forumber2_ Samsung Galaxy S III.
2)slst_for his valuable input.
3)owaisnaim & fefifofum Twrp for redmi 1s.
Downloads:
1)parted:https://drive.google.com/folderview?id=0B6_hhjS3nx4IU05yLVc2Mk9uOEk
2)Repartition script Redmi 1s_1.2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRkJFZzAtMjZEa2s
3)Repartition script Redmi 1s_2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRXlDZUU1cEJ3Smc
4)Reset to default partition:https://drive.google.com/folderview?id=0B6_hhjS3nx4IeGtXb0liazdLWVk
5)TWRP 3.0.2-1.zip:https://drive.google.com/folderview?id=0B6_hhjS3nx4IdzFHXzdfNXVCYm8
good work mate
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
no you just have to go to
wipe >mark on system>click repartition
go back you can see system size 1.2gb
after doing this can i flash latest twrp ?
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
vinayak.ghimire said:
after doing this can i flash latest twrp ?
Click to expand...
Click to collapse
Ya you can.
and whats the size of userdata and cache partition ?
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Based upon the scenario, the only concern is the system partition coz newer or update partition is too large. Cache partition is ok because it only use as a temp file partition. The userdata partition is large as internal storage because it shared as the same partition. That is the good thing at xiaomi phones, data partition is large as long as you have space in internal storage.
Sent from my HM 1SW using Tapatalk
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Install diskinfo app and check
Thanks for the script. It will help us a lot in now and in future also.
I know, i am asking too much. I bet we all are from developers but I will be very glad if you can provide me link of flashable file of TWRP and philz recovery 6.55.
Thanks Loads.
Anyone have checked this tutorial working ??
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Here is screenshot
apoorvpandey41 said:
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Click to expand...
Click to collapse
Thanks mate appreciated.
Thanks man works perfectly fine. Awesome tutorial.
Guys please help me:
Today morning I reparationed my Redmi 1s as the Op said. it went successful. after using for 5hours I've found an update from CM. So I updated using CM UPDATER APP. after reboot I've lost my Google play store and Google app (after updating to todays CM update using CM UPDATER APP). When I went to see the system partition size, it's size went back to the default 782mb (around 782mb, I don't remember exact size).
I checked whether it is disabled or what in apps. But I can't find there also. I tried Show system apps and reset app preferences, but nothing showed them.
I tried to get them back (play store and Google app) by resizing the partition to 1.2 gb (wipe>advanced wipe> Mark system>change or resize partition>back> checked system partition size whether 1.2gb or not>wipe cache and dalvik cache> reboot to system). But nothing worked.
So please help me in getting them back. Please exclude solution such as factory reset or flash gaggs again.
Is anybody else also facing the same issue or it's just me?:crying::crying::crying:
freeshared said:
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
Click to expand...
Click to collapse
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
sharathe100111 said:
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
Click to expand...
Click to collapse
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
freeshared said:
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
Click to expand...
Click to collapse
Thank you brother for your reply. Now i am on miui as i am not being able to go to CM14 anymore. But i can flash CM11. (it seems i can use only kitkat).
Here are the screenshots: for MOUNT, ADVANCED WIPE, CACHE, SYSTEM, DATA. And problem struck on patching system image unconditionally

Upgrading from 3.2.8 to 4.0.1 while keeping data, root and encryption.

Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Vitriol_Drinker said:
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Click to expand...
Click to collapse
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
let92 said:
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
Click to expand...
Click to collapse
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
All right, I'll try this weekend and will post here the result
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery and update through the official OTA Then flash the recovery and root again :good:
Click to expand...
Click to collapse
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
hiredantispammer said:
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
Click to expand...
Click to collapse
It seems more simple the @Viper The Ripper's method: in that way I only need to flash the stock recovery, boot the phone (I think the phone will boot on OOS 3.2.7, my actual version), then download OTA (using a VPN to Germany because the update hasn't begun in Italy ), factory reset (will the phone keep Nougat or come back to manufacturer Marshmallow version?), flash recovery by @eng.stk and root phone.
Correct?
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
Click to expand...
Click to collapse
Will this work for me ? Applying the OTA won't relock bootloader will it ?
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
sahed01 said:
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
Click to expand...
Click to collapse
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
let92 said:
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
Click to expand...
Click to collapse
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Only suggestion that i will give is what worked for me. So here is what i did and successfully upgraded from 3.2.8 to 4.0.1 OOS without losing data and keeping encryption on ext4 /data.
1. Keep full OTA zip, and SuperSU latest in the folder or Stable, whatever you want, and the latest recovery by eng.stk v11.
2. Remove security from your phone (pin/password/fingerprint), and Go to recovery flash v11 recovery by eng and reboot to recovery.
3. Wipe system, cache, and dalvik.
4. Flash full OTA, flash TWRP recovery img again. If on rebooting, you find stock recovery, just flash v11 from fastboot again.
5. Don't reboot into system, reboot into recovery again, flash SuperSU zip and make sure SuperSU flashes properly. You need to read the installation process and determine that it flashed properly.
6. Reboot to system, you will have all of your data safe and the way it was in MM.
7. Be careful, the moment you assign pin/pattern/fingerprint security to your device, TWRP would ask for a pattern in recovery and it won't decrypt your data. (Works fine if you are on f2fs). If you are like me and don't flash zips that oftenly, it's good to go.
I hope this method helps. Be sure to remove security from phone before flashing and rebooting as recovery won't work if you have security applied. It's a cheap workaround but it works nevertheless.
sahed01 said:
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Click to expand...
Click to collapse
Maybe Titanium wants the storage permission even if it doesn't ask for it
Try to give it, delete app cache and restart the phone.
Then try to restore one app.
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Go to Supersu apk and choose the option in settings to unroot completly your phone
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Will this work for me ? Applying the OTA won't relock bootloader will it ?
Click to expand...
Click to collapse
If you apply the official OTA you won't lose nothig from your current rom
Yes it'll work and nope, applying the OTA won't relock your bootloader :good:
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Click to expand...
Click to collapse
People that want F2FS will lose their data converting their filesystems unless they back it up; no method listed in this thread gets around this. All the options listed keeps the users on ext4 because the official OTA does not convert your /data partition to F2FS as shown in the updater script code below from official 4.0.1 full firmware and update file.
Code:
getprop("ro.display.series") == "OnePlus 3" || abort("E3004: This package is for \"OnePlus 3\" devices; this is a \"" + getprop("ro.display.series") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
You can see that all it does it overwrite the system partition with the new changes, writes the radio file, and flashes the extra firmware to bring you up to speed with nougat. If you want to do this right and be on F2FS you have to do it manually.
Viper The Ripper said:
Go to Supersu apk and choose the option in settings to unroot completly your phone
Click to expand...
Click to collapse
Thank you! I'll try your method so!
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
I've managed to do all this and end up wit 4.0.1 with F2FS and no encryption. If I encrypt the phone, it changes the format of the data partition and TWRP won't decrypt it. If I understand this thread, this is to be expected. There is no way to end up with encrypted F2FS that TWRP can decrypt?
Revolised123 said:
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
Click to expand...
Click to collapse
I didn't. Just boot back to recovery after flashing everything. With this TWRP data can be decrypted.

Installed the Begonia Recovery Project and all files in my main storage have random letters

I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Sqorpz said:
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Click to expand...
Click to collapse
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
If your device boots back to TWRP, it might be triggering Rescue Party. (click the 3rd button on the bottom of the screen to view the logs)
Fytdyh said:
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
Click to expand...
Click to collapse
I had installed twrp like this before and never had this type of error. But yes, the smart thing would definately be to always have backups. Lesson learned for next time!
Canny1913 said:
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
Click to expand...
Click to collapse
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Sqorpz said:
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Click to expand...
Click to collapse
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Canny1913 said:
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Click to expand...
Click to collapse
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Sqorpz said:
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Click to expand...
Click to collapse
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
T
Canny1913 said:
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
Click to expand...
Click to collapse
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Sqorpz said:
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Click to expand...
Click to collapse
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Canny1913 said:
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Click to expand...
Click to collapse
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Sqorpz said:
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Click to expand...
Click to collapse
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Canny1913 said:
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Click to expand...
Click to collapse
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Sqorpz said:
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Click to expand...
Click to collapse
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Canny1913 said:
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Click to expand...
Click to collapse
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Sqorpz said:
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Click to expand...
Click to collapse
Google One app can backup photos,SMS, phone call history and redownloads all of the apps (except apps that were installed from an apk file)
Pixel Experience actually bypasses the Google Photos storage limit so you can backup your entire gallery without problems.
For notes just use Google Keep, it syncs the notes to your Google account.
App data can be backed up by Titanium Backup or Migrate. (i suggest you test them before backing up your entire app data as suggested by Migrate developer)
I don't exactly recommend backing up Data as a whole since your only option is TWRP and TWRP loves to complain when it comes to backing up and restoring.
Thanks for the best wishes and i wish you all the best too. Have a good one.

Is my encrypted data lost forever after the Android update?

Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes

Categories

Resources