Develop Bugs

Problems with Safety Net

After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,

Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone

TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991

hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse

You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.

p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!

hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader

So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?

hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot

TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.

jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version

TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.

Mediatek MT6737M S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOU ND

I have a BLU Grande X LTE running a Mediatek MT6737M board. I'd like to flash TWRP on it. I have SP Flash Tool with an scatter file from the OEM recovery files. I replace the recovery image with a TWRP image, select the download agent from the BLU recovery files, select "Download only," but then I get this error:
DA Connected
executing DADownloadAll...
Download failed.
Disconnect!
BROM Exception! ( ERROR : S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND (6045) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
Does that mean I need the auth file to get past Mediatek lock-down on custom flashes? If so, any tips where to find it?
Thanks!

theexternvoid said:
I have a BLU Grande X LTE running a Mediatek MT6737M board. I'd like to flash TWRP on it. I have SP Flash Tool with an scatter file from the OEM recovery files. I replace the recovery image with a TWRP image, select the download agent from the BLU recovery files, select "Download only," but then I get this error:
Does that mean I need the auth file to get past Mediatek lock-down on custom flashes? If so, any tips where to find it?
Thanks!
Click to expand...
Click to collapse
Just want to check the obvious... is your bootloader unlocked? Is the TWRP version specifically for your device?
Are your firmware images signed? If so, you may need to un-sign them...

neil_swann80 said:
Just want to check the obvious... is your bootloader unlocked? Is the TWRP version specifically for your device?
Are your firmware images signed? If so, you may need to un-sign them...
Click to expand...
Click to collapse
Sorry for the very late response. I missed the notice for this post.
Yes, the firmware is unlocked. The TWRP version is not for my device, but I hope to find one that works or make one. But can't test it unless I can flash it. My original firmware images are signed and I can flash the factory OEM image. Problem is if I unsign them I don't think it will accept them since it requires signed files. So I guess the question now is, how does one find the key to sign a custom recovery?

theexternvoid said:
Sorry for the very late response. I missed the notice for this post.
Yes, the firmware is unlocked. The TWRP version is not for my device, but I hope to find one that works or make one. But can't test it unless I can flash it. My original firmware images are signed and I can flash the factory OEM image. Problem is if I unsign them I don't think it will accept them since it requires signed files. So I guess the question now is, how does one find the key to sign a custom recovery?
Click to expand...
Click to collapse
If your bootloader in unlocked, you should be able to flash unsigned images. Are you using SP FlashTool?

How to downgrade Realme X to Android 9/ Color OS 6 from Android 10 /Realme UI?

Hello devs,
I upgraded my Realme X to android 10 using OTA.
Although there are no serious bugs, the UI has minor glitches now and then. But the camera has lost its quality significantly. It is taking comparatively bad photos now when compared to Android 9.
Can You kindly write a guide on how to downgrade to Android 9? It will be really appreciated.
Thank You in advance.
@SagarMakhar @gritik95 @indroider

Download Stock rom released on 19th Feb and flash it manually if your bootloader is unlocked or if you have custom recovery

rupeshmaurya35 said:
Download Stock rom released on 19th Feb and flash it manually if your bootloader is unlocked or if you have custom recovery
Click to expand...
Click to collapse
Bootloader is locked. Can't I flash older versions?

I have the same query. Any help would be highly appreciated.
Bootloader is locked. I just purchased the phone and upgraded to Realme UI. Now I want to downgrade to colorOS so I can either use it or flash the phone to other ROM(s) which is completely impossible as of now in Realme UI.

U can unlock bootloader using In depth test app and adb but u can't use TWRP because TWRP is not supported in android 10.

What about fastboot? Can we flash Android 9 using fastboot? Have you successfully downgraded?

ShattrdChain said:
Hello devs,
I upgraded my Realme X to android 10 using OTA.
Although there are no serious bugs, the UI has minor glitches now and then. But the camera has lost its quality significantly. It is taking comparatively bad photos now when compared to Android 9.
Can You kindly write a guide on how to downgrade to Android 9? It will be really appreciated.
Thank You in advance.
@SagarMakhar @gritik95 @indroider
Click to expand...
Click to collapse
Hi
I've bricked my realme x and that lead me to start searching ow to unbrick it, and with that i can tell you there's a way to make a downgrade of the android version.
The first thing you need to have is the .ofp file of the software version you want (if you have the india/global version you will not have any problem finding it, but if you have the chinese version you probably could not find it *i've been searching a lot for this file, if you find it, please let me know*)
once you have the ofp file you need the flashing tool of oppo, known as msmdownload tool, the issue with this is the tool will ask you for username and password, because its for oppo workers, and a lot of patched versions don't reconize the file.
If you made this far its pretty simple, select the ofp file, connect the device pressing volumen + and volumen -, and push in the icon of flash.
you can do it in another way, unlocking the bootloader (theres a tutorial in this forum), and then flashing a recovery (you migth flash a custom rom first via adb/fastboot) a zip file with the twrp, and then using the flashable zip of color OS
I hope this help you, but if you're not very mastered in this i reccomend u let realme work of improving the rom or using a gcam

Irvinukis said:
Hi
I've bricked my realme x and that lead me to start searching ow to unbrick it, and with that i can tell you there's a way to make a downgrade of the android version.
The first thing you need to have is the .ofp file of the software version you want (if you have the india/global version you will not have any problem finding it, but if you have the chinese version you probably could not find it *i've been searching a lot for this file, if you find it, please let me know*)
once you have the ofp file you need the flashing tool of oppo, known as msmdownload tool, the issue with this is the tool will ask you for username and password, because its for oppo workers, and a lot of patched versions don't reconize the file.
If you made this far its pretty simple, select the ofp file, connect the device pressing volumen + and volumen -, and push in the icon of flash.
you can do it in another way, unlocking the bootloader (theres a tutorial in this forum), and then flashing a recovery (you migth flash a custom rom first via adb/fastboot) a zip file with the twrp, and then using the flashable zip of color OS
I hope this help you, but if you're not very mastered in this i reccomend u let realme work of improving the rom or using a gcam
Click to expand...
Click to collapse
But how can u flash custom recovery in android 10. As i know TWRP or any other custom recovery are not fully developed for android 10 .

rupeshmaurya35 said:
But how can u flash custom recovery in android 10. As i know TWRP or any other custom recovery are not fully developed for android 10 .
Click to expand...
Click to collapse
you have to flash the recovery after flashing another rom
thats why i suggest you flashing a custom rom via ADB and then flashing the color os rom

Irvinukis said:
you have to flash the recovery after flashing another rom
thats why i suggest you flashing a custom rom via ADB and then flashing the color os rom
Click to expand...
Click to collapse
It is very simple if you say "I DON'T KNOW"

[UPDATED] Unlock bootloader of Meizu M5c and install TWRP

I am not responsible for any brick.
I tested this guide myself and decided to share it.
Make a backup before this guide because you will lose your data!
The unlock method has been updated and now you can unlock the bootloader more easily without the risk of bricking after an OTA and without changing the bootloader.
Now you can safely unlock the bootloader using mtkclient.
Link: https://github.com/bkerler/mtkclient
TWRP can be installed via mtkclient or manually from rooted Android.
TWRP Download link: https://github.com/XRedCubeX/twrp_meizu_m5c/releases
IF you unlocked the bootloader with the old method you can follow these steps:
1) Download the attached package.
2) Download OTA zip from flyme, link: http://www.flymeos.com/firmwarelist?modelId=70&type=1
3) Download the latest version of SP Flash Tool.
4) Download MTKClient and follow the instructions to install it.
5) Power off the phone and keep unplugged it from PC.
6) Open SP Flash Tool, select the downloaded package and select all partitions, then press the download button, don't plug phone for now.
7) Boot to recovery with vol +, plug the phone on PC, depending on recovery, TWRP or stock, use adb sideload or put update.zip in internal memory and install the zip.
8) Let the phone reboot or reboot it manually.
9) Now start the flash from SP Flash tool automatically, let it finish.
10) After the flash, unplug the phone and reboot into recovery.
11) Paste the update.zip in the phone and flash it.
12) After reboot, let your phone reboot into android and power off.
13) You can follow the guide to unlock bootloader with mtkclient.
FAQ:
A) But will I lose the data with this guide?
Yes.
Make sure to back up your data in any case!
B) But this guide is a bit different than usual, where is "fastboot oem unlock"? Or "fastboot flashing unlock"?
Meizu has not implemented an unlock command and in this case to unlock the bootloader we have to use a tool that makes us change the unlock status.
C) Are there Custom ROMs?
There is only one custom ROM for this device, the Lineage OS 14 but I advise against using it because it has a bit of a bug but I haven't had more time to work on it yet.
D) But wasn't the guide different?
It has been updated with a better method with more advantages.
E) My device is in Hard Brick! How can I solve?
There are various types of Hard Brick and it depends from situation to situation.
F) I have installed Lineage OS 14 but I am not satisfied, I want to go back to Flyme!
Flash update.zip from official website.
G) Can I relock the bootloader?
From MTKClient readme:
for relocking use:
python mtk da seccfg lock
Click to expand...
Click to collapse
H) TWRP? I am interested in Device Tree, where is the link?
Here: https://github.com/XRedCubeX/twrp_meizu_m5c
I) I have a Meizu A5 (Chinese M5c) will it work on it?
I can't assure you anything but it could work, the only way to be sure is to test on a Meizu A5.
J) Can I flash twrp from fastboot?
Fastboot refuses to flash partitions, strangely, I don't know if downgrade or anything changes the situation but for now I was able to flash it with mtkclient.

I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?

Mortaux said:
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Click to expand...
Click to collapse
Im working on a Lineage OS 14 for this device.

I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?

thiagosousa777 said:
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
Click to expand...
Click to collapse
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these

XRed_CubeX said:
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
Click to expand...
Click to collapse
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.

You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works

Mortaux said:
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Click to expand...
Click to collapse
For now I can't make the video because I can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly

thiagosousa777 said:
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
Click to expand...
Click to collapse
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would

XRed_CubeX said:
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
Click to expand...
Click to collapse
I'll try that, thanks a lot!

thiagosousa777 said:
I'll try that, thanks a lot!
Click to expand...
Click to collapse
Did you finally manage to fix the device?
Were you able to get on with the guide?

XRed_CubeX said:
Did you finally manage to fix the device?
Were you able to get on with the guide?
Click to expand...
Click to collapse
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.

thiagosousa777 said:
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
Click to expand...
Click to collapse
Ok good luck

XRed_CubeX said:
Ok good luck
Click to expand...
Click to collapse
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.

thiagosousa777 said:
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
Click to expand...
Click to collapse
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom

XRed_CubeX said:
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
Click to expand...
Click to collapse
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again

thiagosousa777 said:
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
Click to expand...
Click to collapse
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering

XRed_CubeX said:
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
Actually, the ROM I installed with SP Flash Tools was not the update.zip from the official Flyme OS website. I downloaded the stock rom from needrom.
I have done this several times before.
But now, strangely I can no longer update to the latest version. The version I'm running is Flyme 6.0.2.0G. I tried to download the update.zip file and install it manually by clicking on it, and it appeared "corrupted file". I also tried to use the Update application and "network error" appeared. But everything else is working perfectly.

XRed_CubeX said:
if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
XRed_CubeX said:
can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
Click to expand...
Click to collapse
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?

thiagosousa777 said:
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
Click to expand...
Click to collapse
Ok, I'll explain in detail how it works: In the guide you will have read that you cannot return to the flyme using the stock rom or an unmodified OTA. This is a tip because once you flash the Engineering ROM, the engineering bootloader (which is essential for unlocking) will also be flashed, but the problem is that if you flash the stock bootloader (the flyme one, the one you surely have when you get the phone), the device for a reason unknown to me, probably the Engineering ROM modifies something in the device (?) and then goes into brick if you try to return to the flyme bootloader. To flash an OTA flyme on TWRP, you must first have some precautions: you must take the OTA on your computer (or a file explorer capable of editing zip files) and remove the following files: lk.bin preloader.bin (it will have a name longer but you still have to remove that) and tz.bin / trustzone.bin. Done like this, now the OTA becomes safe to install, you install it from TWRP, at the end of the flash it will give you an error but it is because it does not find the files we have removed but we can safely ignore it because it will have successfully installed the flyme on the device.
Regarding lineage: I'm still working on it a bit and gradually I'm discovering bugs. I already warn you that the camera will not work in the Lineage, I have tried in every way to try to make it work but it does not want to go, I have asked for help everywhere but no one has been able to answer so I do not know what to do, for the rest I want to keep a little longer the ROM under test to fix the remaining bugs

Question Can anybody extract its rom images for me?

Recently I broke my smartphone and now it is in a bootloop and I can't install the official rom to it. Ofp file is a piece of **** because nothing can flash it even Realme flash tool says central directory not found. I am lost. If anybody can give me it's rom extracted from it's phone i will thank you.

Have you tried using SP flash tool ?, what region is your phone ?

Yes I am trying but you know thanks to the mtk secure stuff it is almost impossible to get the phone in brom mode.

Use mtk client to temporarily bypass security and flash using sp flash tool, when using sp flash tool always use DOWNLOAD ONLY otherwise your phone will stop booting