Related
Hi,
yesterday i went through the process of flashing custom rom and i just want to share my experience.
My daily driver was the latest MIUI7 because it was very stable and battery life was good (stock global stable, locked bootloader). But i decided to try custom rom mainly because i had strange performance issues every now and then.
1. Applied for official unlock - Unlock Page
2. I read many posts and i tought it might be best to upgrade to MIUI8 first. I updated with the official updater app.
3. Unlocking didnt work because you need a Developer Rom of MIUI installed to link the device to you Mi account and successfully unlock. I downloaded latest global dev rom and flashed with official updater app.
4. Unlocked successful with official Mi Unlock Tool.
5. Installing TWRP ZCX - worked and was easy
6. Backup System, Data, Firmware, Modem with TWRP (didnt need it so far)
7. Flash Nitrogen OS
8. Reboot to system - "to start android enter password" - surprised and shocked so i googled and found a hint to "format data" because storage might be encrypted.
9. In TWRP - Wipe i "formated data" so all files were deleted! be sure to backup everything!
10. Nitrogen OS booted (no need for Gapps - everything is built in)
11. Flash fingerprint fix - apparently i have the Goodix and need this fix for fingerprint to work
12. I was confused because there was no caller app (call worked but no UI) so i flashed new and again and tried Psy Firmware but i just had to set the caller app in settings.
13. All is working good so far :fingers-crossed:
Thanks for all the work done by this community. I greatly appreciate all the cool stuff! :highfive:
EDIT: I have FPC sensor not Goodix. The fix is for FPC! Thanks to @Denis:) for pointing that out.
You are wrong on some points ;p
Its so easy to flash roms on all snapdragon devices
Theres a need for gapps, it doesnt come preinstalled on roms, which is a good thing.
If you flashed fpc fix and it works now, it means you have FPC sensor, not goodix (which is good -like me), dev of NOS will make fpc default from now on.
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Denis:) said:
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Click to expand...
Click to collapse
I have installed LineageOS several times over MIUI but I didn't need to format data. Why does this happen in nitrogen os, any idea?
Denis:) said:
...
Click to expand...
Click to collapse
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
If you didnt wipe system aswell, gapps and ROM persisted.-dirty flash (update ROM)
If you want to update ROM + gapps, you must wipe System aswell with dalvik/art, cache
Then flash ROM+gapps , wipe cache and reboot
F2FS is done in twrp but you must have f2fs compatible twrp - I successfuly use rc1 latest by TheStrix, obviously if you choose to format data, cache you will lose data and you will have to clean flash ROM.
P.s By the way, when was your device made? Im just curious
funkymaster said:
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
Click to expand...
Click to collapse
If you want to experiment please try to format the partitions using f2fs and tell us your results.
I tried it but was unsuccessful since when I tried it there was no recovery that could support f2fs. Remember only dadii's TWRP works still I recommend you confirm it again.
Im using this one by thestrix and it works perfect;
https://www.androidfilehost.com/?fid=529152257862707658
currently i don't feel like tinkering with my phone any more. So i keep the F2FS in mind for some time in the future
Hm i don't know where to find the build date of my phone i bought it April 2016
currently on the latest LOS 16 with latest vendor firmware. but, just wondering, if i were to flash newer firmware over my existing, would i lose all data etc and need to flash ROM / Gapps etc etc?
or should i just backup data/storage/boot, flash latest firmware then restore backup - would that work, or is it not advised?
sorry if that's a complete noob question!!
reg66 said:
currently on the latest LOS 16 with latest vendor firmware. but, just wondering, if i were to flash newer firmware over my existing, would i lose all data etc and need to flash ROM / Gapps etc etc?
or should i just backup data/storage/boot, flash latest firmware then restore backup - would that work, or is it not advised?
sorry if that's a complete noob question!!
Click to expand...
Click to collapse
I can tell you for certain that flashing of firmware/modem on OP3 does not affect the ROM, Gapps, Magisk or data. I am sure it will be the same on the F1 also.
However, it is possible that your device gets encrypted during first reboot after flashing firmware update. In this case you would have to format data to get rid of encryption, which means loss of your data. To avoid this, simply flash disable force encryption zip prior to first reboot.
mideg said:
However, it is possible that your device gets encrypted during first reboot after flashing firmware update. In this case you would have to format data to get rid of encryption, which means loss of your data. To avoid this, simply flash disable force encryption zip prior to first reboot.
Click to expand...
Click to collapse
Ah yes I forgot about encryption, it did say on first boot of Los that it was encrypting. Are you saying that I can flash decryption zip now and everything will be decrypted? Or do you mean everything is lost and I should only flash decryption before first boot of newly flashed rom?
Just reboot to twrp and see if you can read your files in clear text. If not, then your device got encrypted and you will have to format data.
To my understanding, you will get encrypted every time you chance from miui to aosp, or aosp to miui, or you flash a new vendor firmware zip, on reboot system this is. In these cases you should flash dfe zip prior to reboot system. You probably won't get encrypted changing between aosp roms. Though it won't hurt flashing dfe zip in this case either, just to be sure.
So i installed Pixel E as said in the forum post and videos and it was working fine, TWRP was fine and installed with no problems, then i went back to MIUI for the L1 certificate update and decided that i wanna try oxygen OS
i install TWRP like i did the first time but this time i didnt get the menu that says swipe to allow modifications, after that i went and mounted vendor and system like i did the first time, and i went to wipe the data i didnt find the vendor option there, it was weird and i thought there`s something wrong with the phone
i go back to the install, i install the disable force encyption file and try to install the rom, i get the success thingy
i restart and it says encrypting your phone and i boots back to recovery
can anyone help with that please? i tried 4 different roms all are the same
and how can i show the vendor option again?
OxygenOS Comes With A Modified Vendor So When You Flashing OOS You Need To Flash DFE Due To Encryption Problem.
Decrypt Your Data By Formatting internal Storage.
Go To Wipe format Data Type Yes Reboot to system.
Just Allow that modification when you decrypt your phone and flashing a Rom that TWRP modification sign comes.
When you wipe data system , Vendor Partition will be Automatically Wiped.
Flash Orange Fox Recovery You Will Also Get that Vendor Partition.
iHookar said:
So i installed Pixel E as said in the forum post and videos and it was working fine, TWRP was fine and installed with no problems, then i went back to MIUI for the L1 certificate update and decided that i wanna try oxygen OS
i install TWRP like i did the first time but this time i didnt get the menu that says swipe to allow modifications, after that i went and mounted vendor and system like i did the first time, and i went to wipe the data i didnt find the vendor option there, it was weird and i thought there`s something wrong with the phone
i go back to the install, i install the disable force encyption file and try to install the rom, i get the success thingy
i restart and it says encrypting your phone and i boots back to recovery
can anyone help with that please? i tried 4 different roms all are the same
and how can i show the vendor option again?
Click to expand...
Click to collapse
just download
https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.4.8-9.0-vendor-firmware.zip
and flash it via twrp! and reboot
Olystem said:
OxygenOS Comes With A Modified Vendor So When You Flashing OOS You Need To Flash DFE Due To Encryption Problem.
Decrypt Your Data By Formatting internal Storage.
Go To Wipe format Data Type Yes Reboot to system.
Just Allow that modification when you decrypt your phone and flashing a Rom that TWRP modification sign comes.
When you wipe data system , Vendor Partition will be Automatically Wiped.
Flash Orange Fox Recovery You Will Also Get that Vendor Partition.
Click to expand...
Click to collapse
I did that and it worked, thanks but the swipe to allow modifications page still didn't appear, it booted right to main page of TWRP
YasuHamed said:
just download
https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.4.8-9.0-vendor-firmware.zip
and flash it via twrp! and reboot
Click to expand...
Click to collapse
I downloaded Vendor firmware but it still gave me the same problem, what fixed it is installing DFE after the rom not before, thanks a lot appreciate you helping
iHookar said:
I did that and it worked, thanks but the swipe to allow modifications page still didn't appear, it booted right to main page of TWRP
Click to expand...
Click to collapse
That Sign Comes Only One Time.
Swipe To Allow Modification Means You will not getting any error while Flashing.
Check in Mount Partition System Keep Read Only If It's Enabled Simply Remove that Mark or Tick Reboot To System.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs. Orange Fox, along with other TWRP derivatives, allow complete access to virtually all of the phone, so it is very easy to accidentally hard brick the phone if you don't fully understand what your doing.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
It is recommended to have encryption removed when flashing, but this is easily done by temporarily removing lock screen security before flashing and adding it back after.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
Do I need to update my vendor and firmware when flashing a new ROM
-----------------------------------------------------------------------------------------------
Probably not.
If you currently have MIUI installed and it's up to date, then you will have the latest firmware and vendor and won't need to flash them.
If you're moving from one custom ROM to another, then it depends on how up to date your current ROM is. If the vendor and firmware requirements of the new ROM match the requirements of your current ROM, then will have the current vendor and firmware already installed and so do not need to flash them again.
Only when the new ROM needs a later version of vendor and firmware than you have currently installed will you need to flash them. This isn't such a common occurrence, so you'll not need to flash vendor and firmware often.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Thank you
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
AkashNP said:
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
Click to expand...
Click to collapse
Since, I think, Android Marshmallow, Google have added forced encryption. Before this you had the security menu option to encrypt your phone storage, which required a separate password to be entered on every reboot. Now encryption is done as standard and uses your lockscreen security PIN/password as the key.
Initially your phone will be unencrypted, but as soon as you first set-up lockscreen security the phone will be automatically encrypted.
Many people see this as a good thing. Should you lose the phone, you data is secure and cannot be accessed without the lockscreen PIN/password. Other people don't care about this and so prefer to disable encryption, as it makes life a little easier when flashing custom ROMs.
Some people, incorrectly, believe that disabling encryption is necessary when flashing custom ROMs, or that disabling encryption is the only solution to problems seen when flashing. This is not true and disabling encryption should only be about a users personal choice to be unencrypted.
Think of vendor and firmware as the equivalent to device drivers for PC components. They are a collection of compiled code files, provided by component manufacturers and the phone manufacturer, to allow Android to communicate with the hardware components in a standard way. Occasionally these files might get updated, as part of a MIUI update, to fix a bug or to add extra functionality. When these files are updated, custom ROM devs will include them so that they get the bug fixes or extra functionality. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
AkashNP said:
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
Click to expand...
Click to collapse
Follow this guide, assuming you've downloaded the recovery ROM.
https://c.mi.com/oc/miuidownload/detail?guide=1
If you view this on a mobile, it might be a blank page. In this case, you need to change the mobile browser to desktop mode when viewing this page.
The most simplest and right guide on the xda forum, well done! Thank You
Noob here
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
jaydeep0712 said:
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
Click to expand...
Click to collapse
As far as I'm aware, there shouldn't be any noticeable difference in speed. The whole data partition is encrypted as a block, so, in use, accessing files is done on an already unencrypted partition. The individual files are not encrypted/decrypted on demand on an individual basis.
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
I've never gone for the screen refresh rate mods, so can't comment on them.
Thanks for replying.
Robbo.5000 said:
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
Click to expand...
Click to collapse
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
jaydeep0712 said:
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
Click to expand...
Click to collapse
I'm currently using LOS. It's mostly bug free. There seems to be a current issue with wired headphones - on calls it is using the phone mic instead of the headphone mic. For my use, I don't see any other issues, but there could be other things around functionality I don't use.
Fingerprint recognition is about as good as it gets on custom ROMs. Not quite as good as MIUI, but good enough.
Thank you so much for busting so many myths, I was dying for someone to speak up but couldn't muster the courage myself. Hats off, and I support everything you said 100%.
Robbo.5000 said:
With the latest Flipkart sale, there have been a number of new owners asking a lot of old questions.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Click to expand...
Click to collapse
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
XXXLR8 said:
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
Click to expand...
Click to collapse
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Robbo.5000 said:
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Click to expand...
Click to collapse
I did the TWRP format (which prompted me to type yes to continue) and wipe data partition,but didnt wipe the partition itself, rebooted, installed pixel experience, and still same, i even got into a boot loop, which i got out to, by forcing my way out by fastboot, and reinstalled MIUI,
Im currently at MIUI, currently stable.
So Im going to try again some other time about this, when i have another available device to use while i reinstall pixel experience in Mi9T Pro
But, your guide is helpful, it failed on me probably because of a mistake I made.
Thanks anyways!
Best Regards.
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
FuriousFrodo said:
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
Click to expand...
Click to collapse
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Robbo.5000 said:
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Click to expand...
Click to collapse
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
FuriousFrodo said:
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
Click to expand...
Click to collapse
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Robbo.5000 said:
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Click to expand...
Click to collapse
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Sent from my [device_name] using XDA-Developers Legacy app
FuriousFrodo said:
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Click to expand...
Click to collapse
Yes, both things are normal. You should be good to go with your new ROM. No need to reinstall it.
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.