Hello,
I have unlocked my boot loader to install a custom rom. Everything is working fine and the rom is working. The problem is, I have to encrypt my phone for using my companies google account. When I try to encrypt the phone is only booting and is not going to the encryption routine...
Phone: XT1068
CWM: TWRP and Philz, same result
System: [ROM][5.0.2][titan][CM 12/Android 5.0.2]CM Prime ROM[JAN 24](v1.0.5 BETA) other Lollipop Systems - same result
Any Idea? Thank you for helping.
Stefan
You have to flash stock recovery to have working the encryption.
Related
Hello all,
I have recently been asked to use email on my work phone (instead of my preferred web-app option). My device (S4 i9505 running a Cyanogenmod 12.1 nightly) was/is rooted but after the (standard) encryption process the phone was stuck on a black screen/bootloop/problem.
This was resolved by re-flashing the CM 12.1 rom using TWRP which booted and the device was encrypted with my work email on the phone. SuperSU is installed but the binary needs to be updated and the phone is saying it's not rooted when checking the root using Root Checker.
I want to reinstall/reinstate SuperSU, but I am wondering if this will freeze the phone again, as it is encrypted. What are the known problems with rooted phones/SuperSU and encryption?
Cheers
Solved
Hi all,
Solved it by simply flashing the latest SuperSU zip via TWRP in recovery. It seems that you can use a rooted phone with encryption enabled. However, when I encrypted it (via the standard way) it was stuck in some kind of bootloop problem where the screen was black but the phone was on. To solve this, I presume the problem was with SuperSU. I would first make a backup of your ROM before encrypting then I would temporarily disable SuperSU, or uninstall it, then encrypt the device. Afterwards re-enable or re-flash SuperSU from recovery. If you do get a boot problem, you can flash a ROM or recover your old one and start again.
My steps were: encrytp, then got the boot problem so I flashed a new CM 12.1 nightly. Afterwhich the phone booted normally and the phone was encrypted, but "not" rooted. I then downloaded the latest SuperSU zip and flashed it from the recovery leaving me with an encrypted, rooted phone.
By the way, encryption is annoying as you must enter a pin everytime you use the phone, after it is locked. My S4 only lets you use a pin, no pattern allowed. However, it is preferred by employers/IT.
I was finally able to get past the issue with the password encryption whenever booting into twrp by mr.raines. All I had to do was downgrade to MIUI 8, and then reinstall everything. I am trying to flash roms now using twrp by mr.raines but, it keeps failing to install the rom. Is this still the best verison of TWRP to use?
Hello
Yesterday I unlock the bootloader to flash Xiaomi.eu Rom on a Chinese MI8 and I noticed that is not encrypted.
When I try to encrypt it, I get a brick. Seems that twrp-3.2.3.0.-dipper not support encryption partitions and I not able to see the sdcard partition and I had to flash in fastboot to revive the phone.
The second test was flashing the official chinese ROM since it’s encrypted from beginning with twrp-3.2.3.0 and recovery-TWRP-3.2.2-0711-XIAOMI8-CN-wzsx150. With the last, the phone hangs on boot, and with twrp-3.2.3.0 boots but the filesystem seems encrypted from TWRP.
I come from MI5s Plus and it ask me the encrypted password when it try to mount the filesystem.
anyone succeed the encryption?
Seaching for a solution as well. I had similar experience like you with global beta and global stable, bl unlocked, twrp.
I need magisk as well, so only solution for now is to run unencrypted, if I activate encryption I cannot boot anymore.
@grootooter , I can confirm you that the recovery TWRP 3.2.3-0918-XIAOMI8-CN can read the encrypted filesystem in the chinese rom.
It not boot only with "fastboot boot recovery.img", you need flashing it.
I don't know if you can use magisk with encryption because dm-verity.
That's the reason because I stay in the chinese ROM, that has native root.
Someone would have to try this TWRP with Xiaomi.EU, then encrypt the filesystem and post the results.
I was running a custom ROM (Skydragon) earlier. I simply booted into TWRP, did the basic wipe then flashed the official zip file. Then after booting, its stuck on the boot animation for more than 20 minutes now. Any ideas how to resolve this?
I too faced the same issue. formating the data partition and flashing community beta build booted successfully for me. before you do this, completely back your phone contents to pc
You must flash with TWRP 3.2.3.0 or older!
i had the same issue. formated data had 3.3.0 twrp but still bootloop so i used unbrick tool to put my phone back to stock and then updated to last build though stock recovery and then unlocked bootloader, installed twrp, magisk and done.
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out
Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?
I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again
If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.
For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.