Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE
Can you make written tutorial?
Thanks for your efforts!
Never heard of this being an issue on Moto's... if we have a problem it is usually booting into the bootloader constantly, and the fix for that has nothing to do with TWRP...
fastboot oem fb_mode_clear
Otherwise this problem is a new one to me.
Here a more complete guide.
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Great news!
thanks for the guide buddy.
Please explain by video?
Stock camera workink? Or need flash mi a1 cam module?
blue4 said:
Stock camera workink? Or need flash mi a1 cam module?
Click to expand...
Click to collapse
everything is working
you just can't set password for hotspot
if you are using your phone as a hotspot. it will be open
Gapps?
ouroboros12 said:
Gapps?
Click to expand...
Click to collapse
Since this guide's first step is to install TWRP, use TWRP to flash the latest Gapps.
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
rosiepie said:
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
Click to expand...
Click to collapse
It's the same because now encryption is disabled(formatting data in the classic way with encryption enabled cause a bootloop, this is why i suggest to use userdata from stock).
I will update mainpost.
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Txatxiquesi said:
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Click to expand...
Click to collapse
Because the one from your actual rom is encrypted and can't be read by other roms(if not you can skip this step, but i assume not).
I don't know why formatting with twrp cause a bootloop if device is encrypted, the only way i've found to clean data without issue is flashing userdata from stock... if anyone find another please tell me .
Thx for guide. Working.
blue4 said:
Thx for guide. Working.
Click to expand...
Click to collapse
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Thank you for this guide! Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data. "Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs. Best results - no bugs @All I got with the combination of @yshalsager´s twrp (18.08.) as kernel combined with stock 9.6.4.0 (july sec patch). You can patch the old twrp with the official afterwards.
Twrp inofficial yshalsager: - mtp not working, vendor not able to being backuped vs official twrp: sdcard not working... And no twrp that can work with pie encryption... Hopefully some dev will find a solution!
Voodoojonny said:
Thank you for this guide!
Click to expand...
Click to collapse
Welcome!
Voodoojonny said:
Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data.
Click to expand...
Click to collapse
I've seen that re-installing twrp fixes, could you try?
Voodoojonny said:
"Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
Click to expand...
Click to collapse
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Voodoojonny said:
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs.
Click to expand...
Click to collapse
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
mac12m99 said:
Welcome!
I've seen that re-installing twrp fixes, could you try?
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
Click to expand...
Click to collapse
I tried to reinstall twrp with
a) patched stock 9.6.4.0 with and without dm-verity
b) patched stock 9.6.9.0 same as above
Both leads to bootloop flashing userdata.bin doesn't fix
c) a and b with magisk and permissiver - > bootloop
Only Yshalsager's twrp as boot with 9.6.4.0 vendor works... All other vendors: broken wifi; all other kernels: bootloop (no dm verity, permissiver, root - nothing helps)
And if you flash userdata.bin you can read data with twrp, but booting havoc will change data, sothat twrp can't read it anymore. Flashing official twrp installer doesn't change anything...
It'slike a circle... Simply: stock twrp is only compatible with encryption of stock userdata... Only solution: decrypt...
I will send you logs tomorrow! Thank you!
mac12m99 said:
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Click to expand...
Click to collapse
Yes and no. I flashed directly patched_boot.img for magisk and only booted twrp with fastboot for flashing Gapps and format data. But this procedure is good. The rom is very fast but sometimes micro-lagging more than stock.
Offline charging not work. (Rooted boot.img issue)
---------- Post added at 09:53 PM ---------- Previous post was at 09:07 PM ----------
Pixel Experience working too and smoother than Havoc for me. (Cam)
Apparently, since the last build of Havoc, is not necesary changing selinux, no bootloop on enforcing.
mac12m99 said:
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Click to expand...
Click to collapse
Installed aex, the camera does not work. Havoc does not work either.But there is a good news. I made a backup in twrp and then restored it. Restoration of backups works fine.
Then I tried to flash the gsi project treble. In twrp, I did wipe data, system, dalvick and internal storage. then it rebooted into twrp.connected to the computer and downloaded gsi havoc.a, then clicked the installation setting img. and chose the system image. after installation, I rebooted the phone in twrp, and then booted into the system. and the system worked well. the camera and hotspot did not work.
I think many problems people are having here are due to the fact the tutorial, while useful, is incomplete. I had to stuggle a bit but I got everything working as it should (well, besides SELinux Enforcing). I can make a clear English-language thorough tutorial if anyone wants. I don't want to steal anyone's thunder.
Enjoying some Havoc Pie myself atm
I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu
Hi, I've OrangeFox Recovery, I've flashed Disable DM Verity Force Encrypt. When I flash a Custom ROM, it is flashed successfully but when I click Reboot System, it automatically reboots into recovery again.
I've tried the Reboot to System option from Recovery but it didn't work, also tried many different ROMs but always get into recovery automatically after flashing ROM.
I also tried to flash Stock MIUI ROM via Mi Flash Tool But it gives the error and the phone boot into bootloader. Please help me fix this problem
on encrypted device you have to format data (yes) after you flash the custom ROM
I have realme c12 ui1 or v1 as what they call it.
Have tried flashing:
PixelPlusUI_3.7_RMX2185-11.0-20210711-1108-OFFICIAL
PixelExperience RMX2185-11.0-20210227-1533-BETA-UNOFFICIAL
lineage-18.1-20210421-UNOFFICIAL-RMX2185
CipherOS-1.5-CRYPTO-20210318-0847-RMX2185-OFFICIAL-STABLE
But I am having issue with wifi with this, It says that wifi mac address and bluetooth address is unavailable, how to fix this?
Please, my phone is not usable now, I dont know what to do, I did every steps as they told me.
Unlock bootloader
Install twrp ( temporary )
Pull boot.img ( stock rom )
Patch with magisk > Install magisk
Boot to recovery > WIPE > Advance Wipe
>Dalvik / ART Cache
>Data
>Cache
>Internal
Install Custom ROM
Format Data
Successfully boot to Custom ROM, but wifi and bluetooth not working.
What did I do wrong guys?
Thanks for the reply.
any solution bro?
There's now an Android 12 build of CipherOS which installs over RUI2.0 version C.05 which has Bluetooth A2DP working. Only other major problem at the time of writing this is that MTP is broken. So no USB. https://sourceforge.net/projects/cipheros/files/KNIGHT/