Database Info

How To Install Pixel Experience ROM on Poco F1 with automated batch file

This thread is old. And I don't think I'll have time to update it so... rip. XD
Hello!
I am new in the xda developer community and wish to help others!
So I made a program (batch file) to do most of the commands in adb and fastboot to install TWRP and Pixel Experience on Poco F1.
It's really easy. Unfortunately the program only works on windows. I will also post a youtube video soon to show how to use it.
Disclaimer: I am not responsible to any harm done to your device (software and/or hardware). Please use the program with care.
This tool is made to help people who doesn't understand commands to flash Pixel Experience on their Pocophone F1.
Poco F1 Tool (Might not be up to date) : drive.google.com/open?id=1eMW--ryJc_rAnzsZjBPUkL0jsQOe1Ykt
YouTube video how to install: youtu.be/besm07mYCeI
Step by step guide:
Before everything, make sure that you have usb debugging enabled as well as OEM unlocking on the pocohpone f1 --> youtube.com/watch?v=VTQYl_d-FGg
after that make sure that you have ADB Drivers installed on your computer. (it comes with the file Install PE on Poco F1.7z)
1. Unlock bootloader with Mi Flash unlock.
to unlock the bootloader you need to create a Mi account. --> account.xiaomi.com/pass/register?&_locale=en
Unlocking the bootloader will erase all data on the phone
The 1st command in the POCO F1 Tool helps you unlock the bootloader.
To help the process go smoothly remove PIN/Password/Pattern and fingerprints.
The only thing you need to do is to connect your mi account on your phone and have a sim card in it.
You do not need to download anything else as they are already included with this tool.
After you connected your mi account on your phone, you can now proceed by opening the tool and pressing the key 1 to open the miflash unlock program.
If needed press allow on your Pocophone f1
Your phone should be in fastboot mode.
The miflash unlock program will open and simply connect your mi account on it.
Then press on unlock bootloader (in the program).
The first time will not work and a wait time of 72 hours (or less) is needed.
Come back when the time is done!
Use option 4 to reboot your phone to the system.
2. Install TWRP Recovery on POCO F1.
This option will install TWRP Recovery on POCO F1 and make you able to install Pixel Experience ROM.
Make sure that you do not have a PIN/Password/Pattern and also make sure that you have usb debugging enabled as well as OEM unlocking.
This option will send a file to use in TWRP (disableforceencryption_treble.zip) and TWRP Recovery (recovery.img).
You will see TWRP logo (teamwin). When you see the logo watch this video: youtu.be/nWV9YCg67fo?t=148
Allow modification.
Wipe --> format data.
home.
Reboot --> Recovery.
IGNORE THE PART WHERE HE SENDS FILE TO PHONE IT IS ALREADY DONE.
Make sure all partitions are enabled.
back.
Install --> DisableForceEncryption.zip.
Swipe to confirm flash.
home.
Reboot --> Recovery.
Reboot --> System.
Reconfigure device and make sure that you have usb debugging and oem unlocking enabled.
3. Install PixelExperience on POCO F1.
This option sends the file to flash Pixel Experience in TWRP recovery.
This will only send the file to flash.
You need to flash Pixel Experience in TWRP.
Watch this video: youtu.be/HCfjha3hqhA?t=268
Wipe --> Advanced Wipe.
select Dalvik/ART Cache, Cache, System and Data
Swipe to Wipe.
home.
Install --> vendor-firmware.zip
Swipe to confirm flash.
home.
Install --> PixelExperience_beryllium-9.0-OFFICIAL.zip
Swipe to confirm flash.
Reboot system.
Done! You have succesfully installed Pixel Experience on POCO F1!
If you have any questions feel free to ask me!
TheSb Tech.

Step by step guide
Before you work on the video, kindly share a step by step guide on how this works and everything...

aydensaruni said:
Before you work on the video, kindly share a step by step guide on how this works and everything...
Click to expand...
Click to collapse
I have updated the thread. There is a vague step-by-step guide on how to install it. The video is also there to help.

Hello, thank you very much for your tool. I am going to try it since me Poco arrived today. I would like to ask - will this guide install the CAF version? Since it is better than AOSP as I have heard. Thanks.

CatBug said:
Hello, thank you very much for your tool. I am going to try it since me Poco arrived today. I would like to ask - will this guide install the CAF version? Since it is better than AOSP as I have heard. Thanks.
Click to expand...
Click to collapse
Sadly, no. But you can change it by downloading PixelExperience CAF and renaming it --> PixelExperience_beryllium-9.0-OFFICIAL.zip and put it in the folder platform-tools (replace the existing PixelExperience_beryllium-9.0-OFFICIAL.zip by the CAF edition and rename it the same) . It should do the work.

pixel experience not booting
please tell me how did it take to boot? for the first time....i flashed the latest pixel exp today with latest beta vendor...it booted 3 times after first boot...is it normal?....its been almost 12 mins
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
Swarup Paul said:
please tell me how did it take to boot? for the first time....i flashed the latest pixel exp today with latest beta vendor...it booted 3 times after first boot...is it normal?....its been almost 12 mins
Click to expand...
Click to collapse
please help me

Swarup Paul said:
please tell me how did it take to boot? for the first time....i flashed the latest pixel exp today with latest beta vendor...it booted 3 times after first boot...is it normal?....its been almost 12 mins
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
please help me
Click to expand...
Click to collapse
Normally, I wouldn't answer this since you've a follow-up without waiting 24 hrs but you can't expect help when we don't know what you did. Details are important. What order did you flash and specifically, what did you flash. Version numbers are important. Saying the latest does not cut it.

Ok...it worked out...I figured out...the problem was with my dfe( without magisk)...I got it from the telegram grp......I formatted my data...and flashed w/o dfe...it booted in no time...but still thanks for the help...

Sorry...
Swarup Paul said:
Ok...it worked out...I figured out...the problem was with my dfe( without magisk)...I got it from the telegram grp......I formatted my data...and flashed w/o dfe...it booted in no time...but still thanks for the help...
Click to expand...
Click to collapse
I'm sorry I couldn't help. Glad you managed to solve the problem. Could you give me more information about what went wrong? Did you follow the instructions in the video?

PE Android 10 not Booting UP
I flashed FirmwareVendor 10.3.8 + PE Android 10 + Nomagisk DFE. but i waited more than 20minutes to boot it up into system but it showing G icon only.

tanmaysrkr said:
I flashed FirmwareVendor 10.3.8 + PE Android 10 + Nomagisk DFE. but i waited more than 20minutes to boot it up into system but it showing G icon only.
Click to expand...
Click to collapse
Sorry I don't think I can help you beacuse this thread is for flashing android 9. I suggest you go back to stock firmware and try ro re-flash without any custom kernel or stuff like that. I don't think this thread will help you. Again Sorry

Infinix smart 5 x657

Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks

I
Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
I have been searching for it's twrp but have not been able to get it so incase you do inform me please

Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.

actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).

Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
Where you able to root the phone in the first place? If you were, you shouldn't have so much need for TWRP. You should be able to flash GSIs from fastboot itself.
Traditional-Wind said:
actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).
Click to expand...
Click to collapse
Trying to flash what image: the stock image of or custom one?

Traditional-Wind said:
Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.
Click to expand...
Click to collapse
is x657 the same as x657C? if not, whats the difference

VicKrypt said:
Trying to flash what image: the stock image of or custom one?
Click to expand...
Click to collapse
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.

MrKonic said:
is x657 the same as x657C? if not, whats the difference
Click to expand...
Click to collapse
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).

Something to note. The phone asked me to send a bug report twice. And gave me the share dialogue (meaning that I can send it to whomever I choose). I sent them to myself using whatsapp. And now, I'm saving a copy of 2 bug report that I assume they should be sent to the company (seems like the bug report was produced by the system). AFAIK it's useless, but just in case. Here's the output of `tree` on linux. If someone thinks there's something useful there. I'll share it.

bt
Traditional-Wind said:
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).
Click to expand...
Click to collapse
btw, have you rooted yours?

There certainly are not any custom ROMs f
Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!

VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
please elaborate this simply for the newbies present. including mineself

VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).

MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).

Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
I've seen the firmware on a couple of sites bro

MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
Talking about root, with the correct firmware (and techniques) there shouldn't be any reason why the phone would be non-root-able. There's no official TWRP for the device and I haven't seen anyone port one for it, so going the TWRP way would most likely cause a brick. But after patching the boot.img from the correct firmware and disabling AVB by flashing the VBMeta (which most people ignore), patched_boot should be flashable in fastbootd if not in fastboot.
Talking about custom ROMs, there are no custom ROMs for the device (just like there aren't for the Infinix Hot 8, Smart 3 Plus, Hot 10 Play, e.t.c), but a lot of people have successfully flashed GSIs. Generic System Images are pure AOSP code that run on Trebllized devices. You can do more research on GSIs yourself.

Traditional-Wind said:
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).
Click to expand...
Click to collapse
I did not suggest you do exactly what was done in that video. The method may vary slightly for MTK devices. It'd be more similar to this (for rooting)
https://www.google.com/url?sa=t&sou...o7QBegQIBRAB&usg=AOvVaw1dN51TuGa6a9LA07Nota-q
For flashing GSIs it'd be similar to this
How to install GSIs on dynamic partition devices

Traditional-Wind said:
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).
Click to expand...
Click to collapse
'Bricked beyond repair'? A phone is hard-bricked only if it doesn't turn on at all when plugged in, and doesn't show up on the PC or show any sign of life. Else, you'd still be able to recover it.

Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)

VicKrypt said:
Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
View attachment 5642989 57c View attachment 5642991 View attachment 5642999 View attachment 5643001 View attachment 5643003 View attachment 5643005
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)
Click to expand...
Click to collapse
what's the process please
can you write down the steps
but mine isn't X657c

Help - Device after Flash Rom not able reboot

Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you

ak9999 said:
Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you
Click to expand...
Click to collapse
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.

SubwayChamp said:
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.
Click to expand...
Click to collapse
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you

ak9999 said:
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you
Click to expand...
Click to collapse
To know which direction to take, first we have to know how exactly you flashed the ROM you mentioned, which ROM was and through which tool.

Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you

ak9999 said:
Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you
Click to expand...
Click to collapse
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And also in case you used fastboot to flash your device, I recommend you try through EDL mode

SubwayChamp said:
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
View attachment 5482635
And also in case you used fastboot to flash your device, I recommend you try through EDL mode
Click to expand...
Click to collapse
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.

ak9999 said:
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
Click to expand...
Click to collapse
Not the option Clean all & Lock because this will lead your hopes even far distant, a locked device with Qualcomm only can be flashed through EDL mode, fastboot mode will be impossible if you relock bootloader. I suggested using the option Format data because WHEN the flashing is successful one of the things that avoid the device to boot normally is the old data that it is still there. Anyway, this won't make difference while you don't get the tool to flash properly.
ak9999 said:
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Click to expand...
Click to collapse
Some Xiaomi devices, while bootloader is unlocked can be sent to EDL mode using hardware buttons, with device off pressing the both volume buttons at exactly the same time you connect your device to PC, in case this method doesn't work you should need to use "the test point method" is a way slightly difficult to get it but... to flash through EDL mode you need to install the Qualcomm 9008 USB drivers https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
And if you want to keep trying in fastboot mode, you could switch to other Mi Flash tool versions if it makes difference. Always is better to move all your firmware to the same directory where Mi Flash tool is, also avoid all the spaces in the path/name.
ak9999 said:
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.
Click to expand...
Click to collapse

{Mod edit: Quoted post has been deleted - Oswald Boelcke}
What does this mean? You only quoted my post.

{Mod edit: Quoted post has been deleted - Oswald Boelcke}
Actually i din't not flash any file at first, it stuck at MI Logo due to some auto upgrade , i not sure it's MIUI Upgrade or Android Upgrade but i saw the word Android ......too bad half way due to my batery issue.......when i reopen MI Logo keep appear so i wish reflash the ROM able to help but it seem.....not really....

How To Guide Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)

It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.
First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821
If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.
Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.
Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.
Download it and unzip it somewhere.
Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Fire up command prompt in the folder you have your platform tools and run:
adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)
This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.
It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.
Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.

Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
Click to expand...
Click to collapse
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy

THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.

applyscience said:
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
Click to expand...
Click to collapse
Did you use the copy partitions zip? You will brick if you don't do that after a MSM.
Process is:
MSM
Upgrade to C.48
Extract boot, dtbo, and vendor_boot from ROM
Fastboot flash dtbo, vendor_boot, and boot in that order
Reboot to recovery
Factory reset
Run copy partitions script
Reboot recovery
Flash ROM
Reboot
It shouldn't brick if you follow that process exactly.
zacattackkc said:
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
Click to expand...
Click to collapse
Awesome, glad that it worked for you! There were two other testers before you as well as myself that have confirmed this method works, I guess I should have put that in the post. Thanks for being a guinea pig

question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?

zacattackkc said:
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
Click to expand...
Click to collapse
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.

EtherealRemnant said:
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
Click to expand...
Click to collapse
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of

zacattackkc said:
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
Click to expand...
Click to collapse
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.

EtherealRemnant said:
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
Click to expand...
Click to collapse
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.

YourLocalDund33 said:
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
Click to expand...
Click to collapse
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?

EtherealRemnant said:
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
Click to expand...
Click to collapse
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.

YourLocalDund33 said:
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
Click to expand...
Click to collapse
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.

I recovered my bricked LE2110 from Oneplus 9 pro Indian msm tools and I wish to restore it to Oneplus 9 global rom. I try to use the "Fastboot enhance (version 1.3)" to flash the payload.bin into my LE2110, but I cannot find any "lfash" button ! The only button I can see is "Extract Image", am I missing something ? I try local upgrade but it cannot find the firmware file ! Please help !

EtherealRemnant said:
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
Click to expand...
Click to collapse
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.

YourLocalDund33 said:
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
Click to expand...
Click to collapse
Which mod are you using? There have been a bunch posted in this forum.

EtherealRemnant said:
Which mod are you using? There have been a bunch posted in this forum.
Click to expand...
Click to collapse
the one from the op. its the one thats said its multi support for indian and global

YourLocalDund33 said:
the one from the op. its the one thats said its multi support for indian and global
Click to expand...
Click to collapse
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.

EtherealRemnant said:
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Click to expand...
Click to collapse
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?

YourLocalDund33 said:
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
Click to expand...
Click to collapse
It's not the MSM Tool that's borked, it's the ROM itself.

Looking for a stock c61 LE2115 Global boot.img (oneplus 9)
I overwrote mine trying to root and now I can't get the phone to boot back into c61. I have access to fastboot though

General SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)

Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99% sure the methods will work for any mediatek version of this phone just make sure to use your correct firmware
the tools included will allow you to :
Enable OEM Unlock +Unlock the Bootloader
Create Scatter Firmware
Unbrick your device if stuck in Brom/Da mode
Root Your Device / Install TWRP
Enter Brom Mode
and more
All instructions are included inside the main folder of tools, seriously... and i mean seriously...please read the 3 or 4 different guides/methods to see which ones you actually need to do. Some are not needed depending on your end goal. I spent a month making every error possible and testing things so you dont have to so save yourself the trouble and read through
Ill do my best to answer any questions or issues you might have but please...please use your eyeballs and google.. i really dont want to have to answer questions like "how flash magisk" etc. Google is there.. it is your friend , use it. XD
A12 Toolkit.zip | by Privyetcyka for Galaxy A12 Nacho
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com

Thank you, I hope I can figure it out with the translator, I went to try ..

fackstrot said:
Thank you, I hope I can figure it out with the translator, I went to try ..
Click to expand...
Click to collapse
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you

PrivyetCyka said:
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
Click to expand...
Click to collapse
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware

fackstrot said:
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
Click to expand...
Click to collapse
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included

PrivyetCyka said:
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
Click to expand...
Click to collapse
I followed the steps, I was inattentive myself) but still ran into a problem

when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error

well, if I put it from SM-A125W, then the rollback error

Will that work for the Samsung Galaxy A13

Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.

Ansemseekerofdarkness said:
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Click to expand...
Click to collapse
I have no idea which directions your directions your talking about the only ones I wrote are the ones in the main folder , probably with a bunch of exclamations. I can't remember and don't have the file with me right now but as far as unlocking the bootloader you just need to get the phone to accept different firmware. Try flashing Sm-a125w Canadian version XAS

fackstrot said:
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
Click to expand...
Click to collapse
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included

PrivyetCyka said:
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
Click to expand...
Click to collapse
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center

fackstrot said:
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
Click to expand...
Click to collapse
Nothing is supposed to happen if nothing happens that is good . Just leave the phone connected how it is and use a mediatek unlocking tool

When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!

ronnieshane1 said:
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
Click to expand...
Click to collapse
Change date to 25 may 2022 to get working

Ok... im trying to repair mi phone and failed i follow exactly as i seen in the readme instructions on the unbrick folder and nothing... i got 2 errors in relation of super.img (im trying to flash the last android 11 firmware on the phone A125MUBS3BVF1) if i uncheck the super the phone flash correctly but doesn't boot so what next...?

fackstrot said:
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error View attachment 5664401
Click to expand...
Click to collapse
And now i had this error i think using the format all + download relocks the bootloader sp flash tool is asking me to download signed images i can't exit from that so i give up and buy another mainboard

My last reply...
I uploaded some images to get BROM working on A125M this zip includes
Preloader and PGPT files from 4 firmwares
Android 10 Binary 1 (AUC1)
Android 11 Binary 1 (BUF9)
Android 11 Binary 3 (BVF1)
Android 12 Binary 3 (CVH3)
Plus i will modify this post because im uploading CVH3 firmware for SP Flash tool flash (Includes the scatter) pls disable the auth using mtkmeta or the python coded program (used 3.7.9 and worked using the shell)
PGPT and Preloader images