Database Info

[Q] Boot loop after installing Gapps

Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.

stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?

malybru said:
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?
Click to expand...
Click to collapse
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps

stanix.de said:
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps
Click to expand...
Click to collapse
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.

malybru said:
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.
Click to expand...
Click to collapse
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)

stanix.de said:
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)
Click to expand...
Click to collapse
no it has not

Problem solved by flashing a new recovery image (CWM Touch 5.8.0.9)
Thanks!

FIX for bootloop after installing GApps
stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE

Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
I have done that, and it works, but I think the gapps install somehow corrupted my data, because after my phone didn't boot I backed up data just in case, and doing this it boots, but when I restore data it doesn't. do you have any ideas?

Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
Thank you so much, this worked for me. I was using CWM.

[Q] Install CM12S Update with TWRP recovery?

Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?

6andro said:
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
Click to expand...
Click to collapse
Just follow this...
STEPS:
1. Download http://builds.cyngn.com/cyanogen-os...263178b74/cm-12.0-YNG1TAS0YL-bacon-signed.zip
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot

Shankar9822 said:
Just follow this...
STEPS:
1. Download [lurl]
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Click to expand...
Click to collapse
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?

Update twrp first then flash. You will not loose personal data when doing the wipe.
Sent from my A0001 using XDA Free mobile app

6andro said:
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Click to expand...
Click to collapse
I think you are using the wrong version of TWRP.
http://dl.twrp.me/bacon/
Use the above link, download the latest version 2.8.6.0-bacon.img and flash it...

I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?

striker280 said:
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
Click to expand...
Click to collapse
It's normal for the stock recovery to be flashed during an OTA update. Yes you can flash it again. No it won't relock your bootloader.
Transmitted via Bacon

[GUIDE] The correct way to flash custom ROMs

Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices. For bypassing Decryption Issues, adb sideload the .zip files.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
[This is known as a dirty flash]
To update the custom ROM or fix a error (Bootloop after successful first boot, No Service, etc.)
I am assuming you used my guide to flash the custom ROM
These are basically the same steps but without wiping or formatting data
Turn off Lockscreen Security
Reboot to Recovery
Flash the ROM (has to be the same ROM, updated is recommended, older versions may cause issues) and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
LINKS:
Official GApps Website - GApps Github
Official TWRP Website - TWRP Github
Magisk Forum - Magisk Thread - Magisk Github
Official SuperSU Website - SuperSU Forum - SuperSU Thread - SuperSU Github
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy!

[Disabler-ONLY]
`This is basically the same guide just if you want to flash Zackptg5's "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers" or any other disabler which requires different steps.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Flash the Disabler, Magisk and then GApps
Reboot to System
Profit
Dirty Flash? You can't. Usually when using a Disabler you have to clean install your custom ROM.
To update use the method in the first post but for step number 5 Flash the Disabler, Magisk and then GApps

This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!

dpryor88 said:
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
Click to expand...
Click to collapse
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.

This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.

_Masked_ said:
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
Click to expand...
Click to collapse
Why are you angry? Haha.
And you linked this from the op6t forums so I'm commenting on that phone. And that's how it's done on that phone. And it does matter which twrp you use for THAT phone because one doesn't decrypt correctly.
Copy and paste? No... And nano is always best if you read xda basically anywhere. Not that I said you HAVE to use nano anyway.. it was just in my steps. And that works for me with any/every ROM. So don't be so opposed to other suggestions. Your method is really weird and involves way too much use of a computer/fastboot. Kind of defeats the purpose of using twrp, don't you think?

Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:

raiderep said:
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
Click to expand...
Click to collapse
Sorry for the late reply, but yes this is for bypassing TWRP Decryption issues.

_Masked_ said:
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data (Wipe)
Flash ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Go to Advanced, ADB Sideload then sideload GApps, the Recovery Installer and Magisk
Reboot to System
Profit
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy
Click to expand...
Click to collapse
this step means need do with pc not by twrp

ayed78 said:
this step means need do with pc not by twrp
Click to expand...
Click to collapse
This is to bypass Decryption issues.

Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
I mean I could make a tool for flashing a custom ROM but I'm sure that there's a tool for that already.

bump. (ignore)

_Masked_ said:
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
Click to expand...
Click to collapse
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?

Krullendhaar said:
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Click to expand...
Click to collapse
Just follow the steps, in order.

Hi.
What if I want to flash a custom kernel on a clean Rom flash? When should I do it? Together with Magisk and Gapps?

What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.

Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Click to expand...
Click to collapse
Same here, I do not understand why I should flash a recovery img when twrp does seem to stay installed after flashing everything. Maybe the custom rom I use does include twrp ?

Custom rom means bugs, possible privacy leak and overall less polished. Developer that are working on them are fantastic but they are most of the time nowhere near as what offer the stock one.
What you need is to check adb, doesn't need root but you can still remove apps (even system one) and do more tweaks.
If needed, check how to patch boot image with magisk, it works on all phone and get you root.
With that, you're free to debloat your device.

Hey just one little question: is it ok to dirty flash with encrypted data folder ?

Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Click to expand...
Click to collapse
Me neither, is it safe to assume that the step can be left out if TWRP is already there and I use it to flash the ROM?
Santi3598 said:
Thank you for this guide.
Click to expand...
Click to collapse
+1

[UMIDIGI F1] Project Treble?

EDIT: This is specifically for the Umidigi F1.
This is not my work, but I discovered this post in one of the hacking forums. I don't know how accurate it is yet (and given the publish date, I may be a fool), but I figured it was worth sharing.
https://forum.xda-developers.com/android/development/psa-project-treble-t3917284?nocache=1

LOL! Sorry man thats my thread I honestly didn't even realize yesterday was april fools! It's for real 100% legit .

That looks SO cool! Unfortunately I'm still struggling with TWRP as it simply cannot read anything (to be able to do step #9 on the OP). When I solve this, I'll post here as maybe it'll be good to update the steps

Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!

Leo_Freitas said:
Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!
Click to expand...
Click to collapse
Please tell me which ROMs did you try and what problems did you face ?

I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
That's a shame about the bootloop thank you for your post this helps me a lot.

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
Maybe a A/B partition problem? Could maybe flash rom on both partition slots.

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?

riceboyler said:
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?
Click to expand...
Click to collapse
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery​- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-

Shadow Of Leaf said:
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery​- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-
Click to expand...
Click to collapse
Boot and recovery only options i get in twrp

twrp bootloop

Hi,
after pitchblack test I have softbriqued my poco.
I used miflash pro for reinstall and everything was good.
but, after unlock again my phone, flash the recovery, (everything was good at this time) flash my rom, the rom doesn't want to boot.
I tried many rom , change the twrp, nothing.
If anaybody have a solution for this issue, you're welcome.
Thanks a lot.

may be flash again with MIFLASH(clean all ) and go to the end of the configuration and check if everything is good .
https://xiaomiflashtool.com/

have you done...
format data in TWRP after flash TWRP and before install ROM again?
best TWRP for me...
recovery-TWRP-3.4.2B-0623-REDMI_K30PRO-CN-wzsx150
start twrp, only via fastboot with my rom version xiaomi.eu_multi_HMK30Pro_20.10.16_v12-11

Thanks for your response.
I've got a first issue with miflash, but the second time was good.
I don't know why it was impossible to connect with fastboot! That's the game of flashing..

I forgot one thing during my flashing session.. : after unlock my bootloader, and reflash a new rom, I didn't set pattern password...... It was the issue!
edit: after miflash session I could repare my phone to stock global. But after this I want to change my rom, and the twrp bootloop became.really strange.
This morning I use miflashtools another time and I keep this version of miui.

I don't know why it impossible to reinstall another rom after complete miflafh process!
Always and always back in recovery, each time!

Lethalben said:
I don't know why it impossible to reinstall another rom after complete miflafh process!
Always and always back in recovery, each time!
Click to expand...
Click to collapse
Can you describe precisely how you proceed to install the rom and which twrp are you using?

NOSS8 said:
Can you describe precisely how you proceed to install the rom and which twrp are you using?
Click to expand...
Click to collapse
Twrp used: all! China twrp 0328, and maunofrio
Install rom: format data, always, reboot to recovery, always, flash, succeed, done.
Wipe cache dalvik.
Reboot, and it became to twrp.
With my Poco, I flashed maybe 30 or 40 times for test some roms.
But since I tested pitch-black twrp everything gone wrong!

Lethalben said:
Twrp used: all! China twrp 0328, and maunofrio
Install rom: format data, always, reboot to recovery, always, flash, succeed, done.
Wipe cache dalvik.
Reboot, and it became to twrp.
With my Poco, I flashed maybe 30 or 40 times for test some roms.
But since I tested pitch-black twrp everything gone wrong!
Click to expand...
Click to collapse
Which rom do you want to install?

NOSS8 said:
Which rom do you want to install?
Click to expand...
Click to collapse
Mmx 12.0.8.0.
I've not tried xiaomi.eu, maybe I could do it.

Lethalben said:
Mmx 12.0.8.0.
I've not tried xiaomi.eu, maybe I could do it.
Click to expand...
Click to collapse
So you must flash miui V12.0.3.0.QJKMIXM with miflash. (no need to configure it just restart in fasboot and install trwp chinesse)
format data(if red lignes reboot twrp format again)->reboot twrp flash MMX rom, format data->reboot system
(do not use WIPE).

NOSS8 said:
So you must flash miui V12.0.3.0.QJKMIXM with miflash. (no need to configure it just restart in fasboot and install trwp chinesse)
format data(if red lignes reboot twrp format again)->reboot twrp flash MMX rom, format data->reboot system
(do not use WIPE).
Click to expand...
Click to collapse
That's what I did!
I'm on stock 12.0.3.0 now, with maunofrio twrp. I tested with chinese to.
I can root the rom, use magisk as well.
I did may be, 3 or 4 miflash for flash stock rom.,and always the same issue.
When I flash I haven't any issues with redlines, everything gone fine.
With stock its OK, with custom not.

Lethalben said:
That's what I did!
.
Click to expand...
Click to collapse
No you forget to format after install mmx rom and you wipe Wipe cache dalvik.
Dont use magisk.

NOSS8 said:
No you forget to format after install mmx rom and you wipe Wipe cache dalvik.
Dont use magisk.
Click to expand...
Click to collapse
I didn't do that ever! I format before flash, never after! And it worked.

Lethalben said:
I didn't do that ever! I format before flash, never after! And it worked.
Click to expand...
Click to collapse
But now it's not working so format data before and after.

NOSS8 said:
But now it's not working so format data before and after.
Click to expand...
Click to collapse
Thanks for your help mate!
It's just incredible and I don't understand why I need to format data after install now!
One month ago, wipe cache dalvik was enough to launch boot!
Big up!

https://forum.xda-developers.com/poco-f2-pro/how-to/pitchblack-recovery-project-oneos-t4189133