Develop Bugs

Cannot proceed with stable miui update

Hello everyone I did a clean flash of
Stable V10.2.1.0.OEIMIXM on my redmi note 5 ai
When I proceed with the setup,I get Google play services stop working and the setup would turn black and blank
I have unlocked bootloader, I flash the stable Rom via twrp

eddieleon7pc said:
Hello everyone I did a clean flash of
Stable V10.2.1.0.OEIMIXM on my redmi note 5 ai
When I proceed with the setup,I get Google play services stop working and the setup would turn black and blank
I have unlocked bootloader, I flash the stable Rom via twrp
Click to expand...
Click to collapse
The same thing happens to me

eddieleon7pc said:
Hello everyone I did a clean flash of
Stable V10.2.1.0.OEIMIXM on my redmi note 5 ai
When I proceed with the setup,I get Google play services stop working and the setup would turn black and blank
I have unlocked bootloader, I flash the stable Rom via twrp
Click to expand...
Click to collapse
Did you do clean flash or dirty flash. I wiped everything and then installed 10.2 miui it is working fine

divyangchauhan said:
Did you do clean flash or dirty flash. I wiped everything and then installed 10.2 miui it is working fine
Click to expand...
Click to collapse
I can confirm it's a clean flash
I use twrp and wipe every single partition

Do format Data (enter yes) then restart TWRP for remounting the partitions, copy the Rom and flash it

eddieleon7pc said:
I can confirm it's a clean flash
I use twrp and wipe every single partition
Click to expand...
Click to collapse
I can also confirm the clean installation. First I wipe all the partitions, then I do format data. then restart in twrp. Then I install the rom and then I start in Twrp and install Magisk or "disable encrip" with Magic included. After this, restart system. Everything seems to go correctly until the moment I log in to the Google account. Just before this the screen turns black and I can not continue the configuration.

Clean installation means Formatting not wiping the Data partition. The other point is to restart the TWRP after installing the Rom and then to install the magisk.
First try to format the Data will end with errors, so restart the TWRP and repeat format Data. After completion restart the TWRP again for remounting the partitions and copy the Rom

A note to everyone. Don't install magisk or remove encryption right after completion of the Rom installation. Reboot in TWRP again and then install magisk or remove encryption, otherwise you face black screen at the stage of Google data input

berda77 said:
A note to everyone. Don't install magisk or remove encryption right after completion of the Rom installation. Reboot in TWRP again and then install magisk or remove encryption, otherwise you face black screen at the stage of Google data input
Click to expand...
Click to collapse
Thank you very much for your answer. Tonight I will try to perform this method.

berda77 said:
A note to everyone. Don't install magisk or remove encryption right after completion of the Rom installation. Reboot in TWRP again and then install magisk or remove encryption, otherwise you face black screen at the stage of Google data input
Click to expand...
Click to collapse
I tried that method and it does not work for me.

eddieleon7pc said:
Hello everyone I did a clean flash of
Stable V10.2.1.0.OEIMIXM on my redmi note 5 ai
When I proceed with the setup,I get Google play services stop working and the setup would turn black and blank
I have unlocked bootloader, I flash the stable Rom via twrp
Click to expand...
Click to collapse
Exactly this is what happens. After that the screen turns black and you can not continue with the initial configuration. Any more ideas?

eddieleon7pc said:
Hello everyone I did a clean flash of
Stable V10.2.1.0.OEIMIXM on my redmi note 5 ai
When I proceed with the setup,I get Google play services stop working and the setup would turn black and blank
I have unlocked bootloader, I flash the stable Rom via twrp
Click to expand...
Click to collapse
tyr the fastboot rom and miflash.

raptorddd said:
tyr the fastboot rom and miflash.
Click to expand...
Click to collapse
I think the last time I try fastboot Rom and mi flash , it failed
Will try again

antonioantuan said:
Exactly this is what happens. After that the screen turns black and you can not continue with the initial configuration. Any more ideas?
Click to expand...
Click to collapse
use fastboot rom and miflash. i remeber having problems lke that and similar. flashing fastboot and clean all NOT relocking bootloader. with mi flash fix it.

Did you reboot the TWRP after the Rom installation?

I had this problem before, what i did is not directly install magisk after installing rom. Install the rom, let it boot for first time, than boot to twrp and install magisk.

Had the same issue, solved by flashing fastboot rom

I used official TWRP. I tried to install PitchBlack Recovery and the rom Miui Developer installed correctly.

[MOD][X01BD] Disable forced encryption of data partition [stock][pie]

Disable forced encryption of data partition​
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
To encrypt the rom again, flash encrypt(pie).zip and format /data

What is the meaning of forced encryption on data partition

#ArtFuL said:
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
Click to expand...
Click to collapse
In which recovery stock or on custom recovery?

Sdsahu101 said:
In which recovery stock or on custom recovery?
Click to expand...
Click to collapse
Custom recovery

Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.

nice_guy75 said:
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
Click to expand...
Click to collapse
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data

#ArtFuL said:
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
Click to expand...
Click to collapse
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....

nice_guy75 said:
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
Click to expand...
Click to collapse
Then no need to format. You won't loose data

is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.

kayamokid said:
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
Click to expand...
Click to collapse
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.

legacy07 said:
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
it meams its just like the updated version of decrypt.zip? thanks sir.

Which one of these two files should be flashed

Karthik kollapureddy said:
Which one of these two files should be flashed
Click to expand...
Click to collapse
Choose according to whether you have to encrypt or decrypt

legacy07 said:
Choose according to whether you have to encrypt or decrypt
Click to expand...
Click to collapse
I'm a beginner so would you please tell me what's encypt and decrypt
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
Karthik kollapureddy said:
I'm a beginner so would you please tell me what's encypt and decrypt
Click to expand...
Click to collapse
I'm confused and the rooting step

Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.

sintoo said:
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
Click to expand...
Click to collapse
This mod works in X01BD and X00TD. Not sure if it work for Z01BD. You can flash this patch by following the steps in the thread but success isn't guaranteed. Take a system backup as if anything goes wrong. Also be ready to loose your data

legacy07 said:
... So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
I'm not sure about that... I am flashing this file (decrypt pie) for Oreo just. The phone does not boot in this case. I was forced to flashing old decrypt file for Oreo after and it all worked again.

It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?

anagramgenius said:
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
Click to expand...
Click to collapse
I think twrp official has decryption issues. Check with twrp 3.2.3

legacy07 said:
I think twrp official has decryption issues. Check with twrp 3.2.3
Click to expand...
Click to collapse
I checked with Rk585's TWRP 3.2.3 too. Same issue persists. It worked fine when I was in Oreo.
After flashing the zip, I booted back to recovery and copied the fstab.qcom to my PC to check if it has been replaced with the flashed zip. It did replace it. But when I boot to system, it starts encrypting my device and TWRP gets replaced by stock recovery. So I flashed the TWRP again and checked the fstab.qcom. Voila. It was unpatched. I don't know what is happening during the boot. The patched fstab is getting replaced by original fstab.
Edit: Seems there is a problem with the zip I guess. Or more files need to be patched to disable forced encryption in stock Pie rom. I tested in both PBRP and OFRP.
Case 1: I flashed stock rom in Official TWRP, then flashed PBRP zip and booted into PBRP. After booting into PBRP, it doesn't automatically disable forced encryption if no rom zip is flashed in it. So I flashed the decrypt zip provided in this OP. Then I booted to system, it started encrypting my device.
Case 2: I flashed stock rom in Official TWRP, then flashed OFRP zip and booted into OFRP. After booting into OFRP, it automatically disabled forced encryption even though no rom zip was flashed. Hence after booting into system, it didn't automatically encrypt my device as forced encryption was disabled automatically by OFRP.
So PBRP and OFRP do something else to disable forced encryption other than just patching fstab.qcom. Atleast in stock Pie rom. That's why I'm unable to disable forced encryption by flashing decrypt zip in any of the recoveries unless it is patched by recoveries themselves.

Root w/o custom recovery?

Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching

mmedei9 said:
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Click to expand...
Click to collapse
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.

polfrank said:
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery

mmedei9 said:
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
Click to expand...
Click to collapse
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?

polfrank said:
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
Click to expand...
Click to collapse
Of the handful of tutorials on the forums, which would you recommend for flashing TWRP and rooting the device?
Would it require me flashing the global rom in the place of my global (EEA) rom?

polfrank said:
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Attention because there will be no more updates for the redmi note 8 pro concerning the rom xiaomi.eu! (announcement on their site ...)

I flashed patched boot image without disabling avb and now I'm stuck in bootloop.
Is it necessary to disable avb before flashing patched image through fastboot?

Unable to encrypt after root

Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?

Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.

marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!

marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?

mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.

marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked

It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.

a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear

Stock ROM update to V12.0.2.0.RCOMIXM Android 11 - Magisk bootloop

My ginkgo had stock ROM V12.0.6.0.QCOMIXM (A10) and I updated to stock ROM V12.0.2.0.RCOMIXM using TWRP recovery (twrp_ginkgo-willow_3.4A9_23-12-2020_BL) However after flashing the rom zip, and after flashing magisk, my phone got into "MIUI" icon, then bootloops into recovery again with alphanumeric directory names.
I tried Disable Dm Verity Force Encrypt after flashing magisk.zip but same problem.
I have tried the following recoveries so far:
twrp_ginkgo-willow_3.4A9_23-12-2020_BL
twrp-3.5.2_10-2-ginkgo
orangefox R11.0_1 (with Disable DM-Verity, Disable Forced Encryption and Aggresive stock recovery deactivation all enabled).
But whenever I flash magisk, I still get the bootloop and alphanumeric directory names, and the only way to restore my phone without having to wipe data is to flash the recovery zip again (but without magisk).
Any suggestions on how to get around this?

bomberb17 said:
Any suggestions on how to get around this?
Click to expand...
Click to collapse
i already answered you here
use this DFE