Related
I am on miui 8.1.4.0 rooted rn3p. So my question is can i use dual boot patcher and dual boot lineage os 14.1
Anyone ??
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots, go back into TWRP and check your log again.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Thanks buddy trying it now
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Androbots said:
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Click to expand...
Click to collapse
Umm... not sure what you're talking about. Maybe DT2W? I tried out Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Filip013 said:
Umm... not sure what you're talking about. Maybe DT2W? I tried our Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Click to expand...
Click to collapse
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Androbots said:
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Click to expand...
Click to collapse
OK. Let me know if you manage to get DBP to work.
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Androbots said:
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Click to expand...
Click to collapse
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
---------- Post added at 04:08 PM ---------- Previous post was at 04:03 PM ----------
Androbots said:
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Click to expand...
Click to collapse
I didn't see this post until now. Well, of course you can't use DBP when you're encrypted. If you want to try DPB, you have to format data.
Filip013 said:
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
Click to expand...
Click to collapse
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Androbots said:
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Click to expand...
Click to collapse
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Filip013 said:
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Click to expand...
Click to collapse
Anyways I will be resting my device next month maybe and then I can try and let u know
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Androbots said:
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Click to expand...
Click to collapse
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Filip013 said:
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Click to expand...
Click to collapse
Gotcha that means in wipe section i have to go to format data right??
Androbots said:
Gotcha that means in wipe section i have to go to format data right??
Click to expand...
Click to collapse
Yes. Good luck.
Filip013 said:
Yes. Good luck.
Click to expand...
Click to collapse
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Androbots said:
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Click to expand...
Click to collapse
LOL. Fine. Next month then.
Hi all. I have tried out both AOSP and NOS Oreo, but am unable to set password or pattern or pin - trying to do so force closes the settings app.
Here's what I've tried:
- Wiping data, cache, system, internal, dalvik and then flashing the rom
- Using the Format Data option and then flashing the rom
- Flashing miui 7.7.2 firmware and then flashing the rom
- Flashing the rom with and without the gapps
- Flashing the rom and Agni 10.5 kernel for NOS Oreo
None of the permutations seem to be working. I'm using TWRP 3.0.0-0 (update: tried using latest version of redwolf twrp too) and my bootloader is unofficially unlocked., if that is somehow related to what's going on here. I found one or two person facing this problem in the rom threads, and posted this myself in that thread, but the only suggestions received were to clean flash the rom.
Would really appreciate a helping hand here.
Here is the logcat recorded while reproducing the issue - Though I started the logcat at just the right moment, the log became rather large very quick
post logcat, it would help the developers to debug
Have you tried to use Red Wolf Recovery instead?
Yes, tried using redwolf about an hour back.
Yes sir, tried using latest redwolf too. (The first answer I try to comment on doesnt display the add comment textbox. Weird.)
flash the latest firmware that included aboot (bootloader file)
Hey. Thanks for the suggestion. I'm out of the loop of the current development though, can you please provide me the link to the firmware you are talking about? I tried googling with "aboot bootloader redmi note 3" but couldn't find much. Thanks a lot already.
IT WORKED! Led me to a miui forums thread, where a user had posted this " i reccomended to using zcx twrp for unofficial bootloader.first u need to download about_mod.zip, i dont have the link so u can search in google. Flash like usual the rom what u want via twrp than flash about_mod.zip before u rebooting the phone. im using unofficial ubl too and im using that way to change the rom or upgrade my rom ps. always to backup before u try. always wipe dalvic, cache, data, system if u change ur rom."
Voila, problem was solved. Thanks a ton, friend, I have been stuck at it for like 10+ hours now.
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
So i am now on pixel experience Rom. and in the future i would like to try other roms what to do and how to install them using TWRP ?
like should i wipe data like when i installed my first rom only ? or data and system ?
and should i install vendor ROM and Disaple force encryption again after i wipe ?
or just delete data and install the new rom ?
i will really appreciate the help !
Thanks in advance !
TheVow said:
So i am now on pixel experience Rom. and in the future i would like to try other roms what to do and how to install them using TWRP ?
like should i wipe data like when i installed my first rom only ? or data and system ?
and should i install vendor ROM and Disaple force encryption again after i wipe ?
or just delete data and install the new rom ?
i will really appreciate the help !
Thanks in advance !
Click to expand...
Click to collapse
Remove your password pin pattern then wipe data system cache if you don't clean flash then you will get alot of force crashes. You can dirty flash on top of the same rom though if it's just a incremental update.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI.
2. Wipe all except internal storage and external storage.
3. Flash vendor and rom.
4. Flash disableforceencryption with magisk 18.0.
5. Flash your twrp again so it isn't replaced by stock.
pingufanpoy said:
Remove your password pin pattern then wipe data system cache if you don't clean flash then you will get alot of force crashes. You can dirty flash on top of the same rom though if it's just a incremental update.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI.
2. Wipe all except internal storage and external storage.
3. Flash vendor and rom.
4. Flash disableforceencryption with magisk 18.0.
5. Flash your twrp again so it isn't replaced by stock.
Click to expand...
Click to collapse
Thank you! I understood every step except for 5.
I am installing roms using twrp how is it gonna be replaced?
I thought replacing happens when i install miui.
Am i missing something?
TheVow said:
Thank you! I understood every step except for 5.
I am installing roms using twrp how is it gonna be replaced?
I thought replacing happens when i install miui.
Am i missing something?
Click to expand...
Click to collapse
hey bro
search for MULTIROM thread
you can flash multiple roms and your primary one won't be touched or affected as long as you follow the instructions.
for me ,i always use one of miui roms as a primary ( some bugs occur if miui used as secondary )
& AOSip/ pixel experience/ ..... as secondary roms.. add as much as you want.
learn the procedure carefully then you are ready to go.
ahmd gom3aa said:
hey bro
search for MULTIROM thread
you can flash multiple roms and your primary one won't be touched or affected as long as you follow the instructions.
for me ,i always use one of miui roms as a primary ( some bugs occur if miui used as secondary )
& AOSip/ pixel experience/ ..... as secondary roms.. add as much as you want.
learn the procedure carefully then you are ready to go.
Click to expand...
Click to collapse
Mbrt74 l 7war el multi roms dh :"D
TheVow said:
Mbrt74 l 7war el multi roms dh :"D
Click to expand...
Click to collapse
???? welcome ya kbeer
elfekra en 3ndk primary untouched in case u dont like 2ry.
Yes, Multirom is the way to go
https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
TheVow said:
Thank you! I understood every step except for 5.
I am installing roms using twrp how is it gonna be replaced?
I thought replacing happens when i install miui.
Am i missing something?
Click to expand...
Click to collapse
No, you are right. Only OEM ROMs which have recovery built in will replace TWRP. None of the custom ROMs to my knowledge have recovery built in. So no need to flash TWRP again unless you are flashing OEM ROMs.
Even when flashing OEM ROMs, if you flash Magisk immediately after the ROM before booting, TWRP will remain.
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.