Database Info

this issue after update to MM version H900

After updating to MM When I try to configure the screen lock I get this error, and does not recognize my sim card
Does anyone know how I can repair this?
{
"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"
}

Have you tried factory reset? Also dial *#06# and check whether the IMEI is displayed correctly or as 0/null.

Affangta said:
Have you tried factory reset? Also dial *#06# and check whether the IMEI is displayed correctly or as 0/null.
Click to expand...
Click to collapse
i already did factory reset, and the EMI it's incorrect, exist someway to fix it?

yulianov25 said:
After updating to MM When I try to configure the screen lock I get this error, and does not recognize my sim card
Does anyone know how I can repair this?
View attachment 4102748
View attachment 4102750
View attachment 4102772
Click to expand...
Click to collapse
I have exactly the same problem
It seems that one of the users (another threath LG H900 5.1 > 6.0 problem) is right and I upload software h900 6.0 via KDZ via TOT even via octopus and nothing, even the same error is possible that the main card is not h900 but another variant?, He says he solved the problem by loading vs900 software because the main card was not h900 but refurbished vs900.
I opened the phone and I was right, now i am going to load the correct software and tell you.

I am facing same problem
I don't know what i can do i brought from in dubizzle for second hand...att h900 and for me mobile hostpot not working...

Everyone getting same problem who update has phone by LGUP. Who update from FOTA like who living in US so they don't have any problem.
I brick my phone in reupdating my mobile in LGUP then I install again lollipop root version .
I face error many times but I try again and again and now I downgrade finely.
Anti roll is 2.0 that's why u can't go back to lollipop from marshmallow. But there is a way
Everything is possible if u use ur mind because it's made by human not God.

khalilrehman17 said:
Everyone getting same problem who update has phone by LGUP. Who update from FOTA like who living in US so they don't have any problem.
I brick my phone in reupdating my mobile in LGUP then I install again lollipop root version .
I face error many times but I try again and again and now I downgrade finely.
Anti roll is 2.0 that's why u can't go back to lollipop from marshmallow. But there is a way
Everything is possible if u use ur mind because it's made by human not God.
Click to expand...
Click to collapse
Please make a more detailed description, I have managed to skip antirollback protection with octopus but I leave the dead phone completely brick, another way is to force the rom but also end up killing the phone, phone no logo no load, no update mode or anything if Have you been able to bypass the protection without killing your LG could you share your method?

Any suggestion how to repair that type of problem, or how to go back to 5.1.1
thanks

I TRIED
jesemazari said:
i have exactly the same problem
it seems that one of the users (another threath lg h900 5.1 > 6.0 problem) is right and i upload software h900 6.0 via kdz via tot even via octopus and nothing, even the same error is possible that the main card is not h900 but another variant?, he says he solved the problem by loading vs900 software because the main card was not h900 but refurbished vs900.
I opened the phone and i was right, now i am going to load the correct software and tell you.
Click to expand...
Click to collapse
i tried but i can not install error coming..
If you have solution let me know...

tmdmoosa said:
i tried but i can not install error coming..
If you have solution let me know...
Click to expand...
Click to collapse
same probleme... And there no updates anymore for this lg v10 h900 at&t ???

Hellow Guys
I have a Problem With My LG V10 H900 At&t Android 5.1.1 . I cant Repair My IMEI Number ..Can some one guide me.
[email protected]

General [Download] P11(TB-J606) Android 11 Global ROM

Android 11 Global ROM
WIFI:
https://rsdsecure-cloud.motorola.com/download/TB-J606F_S320029_210923_ROW.zip
LTE:
https://rsdsecure-cloud.motorola.com/download/TB-J606L_S320030_210923_ROW.zip
{
"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"
}

@qwer1335 I've changed the prefix of your thread from "Development" to "General" as the thread didn't qualify for the first one. Please review the sticked guidances of the responsible moderators' team prior to your next posting and do not change the prefix back! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.

Hallux_ said:
Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.
Click to expand...
Click to collapse
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.

i tried but the link doesn't work
EDIT: i tried from rescue and smartaassistant, and i found the update

asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
I have the global version.

Hallux_ said:
I have the global version.
Click to expand...
Click to collapse
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.

asukav said:
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.
Click to expand...
Click to collapse
Sorry, I am not sure if it is what you are looking for, but I downloaded the new ROM with LMSA and I do have all the IMG files in the download directory. I do not know if you can do the same not having the exact same tablet model.

asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?

famicom9x said:
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?
Click to expand...
Click to collapse
Still a "NO". It's the same: "system and hardware not compatible".
So I flash back to 0520.
I do hope I could spare some time to unpack those imgs to have a check on some specific files next week.
Just be busy all the time with my work...
Engineers from Lenovo China give me no useful answers. I think I can only count on myself.

I tried update to 210923 via LMSA, but not boot.
Then I tried again with qpst 2.7.496, it boot up and get a minor update to 0925.
Still lost serial number.

Que??

Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.

tnt1212 said:
Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.
Click to expand...
Click to collapse
It's because your device is Region locked. Within this XDA there is a forum on how to region unlock ur device. You have to use QCN file to change it.
Mine won't update because of region lock and now it's working perfectly

Hey guys, do you know if we still have widevine L1 after updating this ROM with locked bootloader?

Development ONE PLUS 9 EU MSM TOOL TESTED

This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
https://www.mediafire.com/file/gyv5gza7t4ibn7j/OnePlus_9_EU_lemonade_22_E.10_210609.zip/file
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!

wow this is nice. can someone test it?

dear @allenjthomsen a
Found that MD5 checksum failed
{
"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"
}

ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone

lockmunk said:
dear @allenjthomsen a
Found that MD5 checksum failed
View attachment 5479725
Click to expand...
Click to collapse
It will fail md5 verification because msm tools in this file were originally global i just swapped the ops file.
lockmunk said:
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
Click to expand...
Click to collapse
this is good im glad it was able to restore your phone to EU

My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?

azizolmez said:
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
Click to expand...
Click to collapse
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.

allenjthomsen said:
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
Click to expand...
Click to collapse
Converted oos11 then flashed havoc. Now I want to go back to stock.

Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD

azizolmez said:
Converted oos11 then flashed havoc. Now I want to go back to stock.
Click to expand...
Click to collapse
you can use it with no problem, i have LE2110 too, but i live in Europe. Until now i was using GLOBAL MSM to get OOS and flashing Europe by local update.

Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
I'm not sure thats possible unless the msm files could be found like the ones provided in the thread that i linked, best i can say for now is just use the provided msm i made and update via settings to latest firmware.

Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
When I try this files, I also on this version. Should be no problem. Then now I updated to 11.2.10.10 without any problem.

allenjthomsen said:
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
OnePlus_9_EU_lemonade_22_E.10_210609.zip
drive.google.com
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
Click to expand...
Click to collapse
Work fine on my OnePlus 9, thank you for saving my phone

I flashed with MSM Tool to my LE2110 but Model Number doesn't change

isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
based on my experience with OP devices the model number will not change on your device even if you flash a different msm.

isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
The model number wont change by flashing a diferent region rom. Only if you flash the weirdo OOS12 update you will see LE2115 xDD

I flashed with MSM Tool to my LE2110 works very well , but im unchecked all
the model name remain the same too, but no problem finally we have a tool to re-alive our op9
thanks boss

Would this work with the T-Mobile op9? I went that whole India 9pro direction and now my phone can't use the fingerprint sensor or proximity sensor. Any feedback would be great thanks.

I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?

akboy7015 said:
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
Click to expand...
Click to collapse
no changement, no change name model remain all perfect as a new model

moto g pure fastboot magisk_patched image error

i have a moto g pure from xfinity mobile i found a stock zip file using the lenovo rsa i then copied the boot image then ran it through the magisk app i then fast boot it and this is the error i get i did oem unlock in settings and also fastboot oem unlock it sends to phone then starts to write and this is the error can someone smarter please help
{
"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"
}

moderater sorry im new please foward to appropiate forum thank you

My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com

jwoegerbauer said:
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
Click to expand...
Click to collapse
not a driver problem its a failed verification on the stock patched.img through magisk diferent verifiction key for the two images

OK

So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....

Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
No I never did how did you get your bootloader unlocked?

Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
Newportswag74 said:
No I never did how did you get your bootloader unlocked?
Click to expand...
Click to collapse
There is your boot img

Newportswag74 said:
There is your boot img
Click to expand...
Click to collapse
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes

Agent_Orange1488 said:
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Click to expand...
Click to collapse
Really when I tried that at the Lenovo website it said my pure wasn't eligible

did patching that boot work?

i managed to patch the latest firmware with march security update, and root the stock rom, now i need to mess with gsis

Question how to downgrade sm-a12/5u from sw_rev3 to sw_rev1

i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded

wouldnt there be a way through twrp or brom mode?

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
Nope you can try brom mode but i dont trust if works
If you buy a samsung device depending of the device (like this A12 and the MTK imei bug) is not a good idea to upgrade

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help

I tryed to downgrade via TWRP flashing baseband and BL
Now my A12 is DEAD and i dont had a box to repair it (after flash i see the security error screen and flashed again the Binary 3 BL once odin tell me passed the phone doesn't booted again)
I just wanted to get the imei working because the firmware on the binary 3 (11 and 12) android system uses all my ram memory trying to get the signal working
F*** *** Samsung and mediatek next time i bought an exynos or qualcomm variant

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
The last rom that i used on my A12 was pixel experience and worked perfectly on binary 3 android 11 based firmare (A125MUBUS3BVF1) just installed TWRP with nulled vbmeta flashed the image as system (not as super) and wiped the data (not advanced wipe) rebooted and the gsi was booted (only bugs mentionated on the thread and the touch bug)

Allehandro said:
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
Click to expand...
Click to collapse
i can access brom mode if that helps

tekkitheidiot said:
i can access brom mode if that helps
Click to expand...
Click to collapse
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.

Allehandro said:
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Click to expand...
Click to collapse
i downgraded to the earliest binary 3, then used test points. worked perfectly

tekkitheidiot said:
i downgraded to the earliest binary 3, then used test points. worked perfectly
Click to expand...
Click to collapse
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
its relatively easy tbh. just be careful around the volume buttons, but everything else is okay. there arent too many cables to rip

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
Its easy to open but be careful with the power/fingerprint sensor flex i think the testpoint is near of the charger flex in the mainboard (i see youtube tutorials to access to Brom mode and preloader)
{
"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"
}

Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.

LAST_krypton said:
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
Click to expand...
Click to collapse
where would i find this scattar firmware?

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
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%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working

MauriJ2001 said:
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%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
Click to expand...
Click to collapse
ill look through it. thanks

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
You generate it your self

To unlock bootloader on these the easiest way is to convert it to an a125w xac by flashing the a125w bl files. Unlock bootloader with seccfg. Then flash ap, cp, and csc from a125w with odin and when it boots up it should show as a125w. Also in download mode it shows the same. My imei says unknown but i believe thats caused by unlocking bootloader so if you relock it after converting it should go back to normal. Playing with mtk modem tool to rewrite imei. Tried using xposed imei changer but didnt seem effective.