Develop Bugs

[Guide/Discussion] EMUI 9 China BETA versions

Hi guys
So recently there was some uploads to Firmware Finder of some BETA's of EMUI 9 of China models BUT please be sure to read this before you try anything with this beta sofware.
I recently, about a week ago when the BETA came out I was really excited like maybe you are but I did a mess noone on this Forum could fix literally.
DO NOT FOLLOW ANY PROCEDURE OF THIS!
Now what I did was:
1. I unlocked both FRP and bootloader of my device.
2. I flashed TWRP recovery
3. I backup my oem-info (ANE-LX1C432) and copied it to my sd card
4. I flashed the oem-info of the chinese model (ANE-AL00) which I copied to my sd card
5. I flashed the Hurupdater with all necessary files from the Firmware Finder.
6. Rebooted phone and it booted normally.
7. Setup screen did not appear and EMUI 9 took me directly to the home screen, I had no google play services of course since it's a chinese ROM, almost no system apps but gestures were present and quite smooth and fast actually. The ROM was fast.
8. Went to Settings-->System-->Developer options-->OEM unlocking was gray which I found pretty weird but then I searched Google and in China they do not have that option on Developer settings so maybe that's why it was gray.
Anyway since this option was gray I thought (stupidly) that maybe after a factory reset the option would become changeable again. It didn't. At that time the phone did a factory reset and afterwords by bootloader become "Relocked" and FRP was "locked. At that time system was unbootable no matter what you try.
Tried multiple commands via fastboot but since FRP is locked you can't do anything that change the system, even the FRP unlock code I got which I payed for (20€) did not work (Not sure why either but I think it's because since my oem-info changed the IMEI was changed randomly or something like it). I thought the command "fastboot boot twrp.img" would work right? but nope, nothing allowed.
Second thing I tried was the dload packages of course. I tried all kinds of packages. Tried the one I installed, the ANE-AL00C01 (9.0.1.100) one. Didn't work as it is the same version. Tried to downgrade for an older EMUI 9 beta package like ANE-AL00C01 (9.0.1.41) and did not work either.
Packages above ^ were from the Firmware so nothing is signed by Huawei.
Then I tried signed packages both from this ANE-AL00 model and my model ANE-LX1C432 but nothing seemed to work.
Only thing I thought of was to flash motherboard firmware which I looked deep into the FCC certification tests you can find this on Google:
https://fccid.io/QISANE-LX1/Test-Report/BLE-Test-report-3742444
Which tells us the motherboard base software version for my model is ANE-LX1 8.0.0.41(SP1C900).
But we don't have access to it of course since it's motherboard official software from Huawei, so maybe only some official Huawei Repair Center have the right tools for this.
BUT, on easy firmware you can get it for 15€. Easy firmware is trusted and they do have an unofficial tool that can flash official motherboard software.
Now before I tried it, I sent my phone to warranty. And I gotta say, I was not very confident about it. I sent it for repair on 6 of February and I said the phone couldn't boot and I installed a beta version via Hicare app (this is how I maybe thought they could believe me), by the way the eRecovery was in chinese so I said I installed a chinese official beta from Huawei from Hicare XDDDDDDDDD
Do you know what they did? It was not an official Huawei Repair Center, although I do have one in my country, it was just one authorized by Huawei, they said the phone didn't boot as well OK, but then they just replaced the whole motherboard due to a IMEI issue, flashed the base firmware from EMUI 8.
After that I payed nothing since it was on warranty, got "a new phone" pretty much, charging port is new but battery is the same I think, and learned something interesting, NEVER FLASH CHINESE OEM-INFO's !!!!!!!!
But seriously, I'm an IT Technician and I thought I had so much luck here because if they knew what I did I would have to pay for the repair and quite a lot (just the motherboard is 200€ btw) !
Altough I was quite pissed cause why the fk wouldn't they just flashed the board software again? YIKES
Anyways, I'm happy, while I had no phone I trusted my old moto g 2014 (titan) with sailfish OS 3 and I then realised how much I want a fkin Sony Xperia X or XA2 so I can have
that best OS of all time and still have those nasty android apps
And if you need a guide for the correct installation of EMUI 9 Chinese beta , please contact @qouet or check his thread here:
https://forum.xda-developers.com/huawei-p20-lite/development/port-nova3e-official-rom-to-ane-lx1-t3897076
I'm not sure how is it going but too have the gapps you gotta work a bit i guess,
People like me with a P20 Lite main phone, just wait for stable versions or flash european versions without changing oem-info's please Don't make the mistake I did and almost buy a new phone
Cheers to all!
AS

Did you try to change oeminfo using HwOTA?

Zerogoki_00 said:
Did you try to change oeminfo using HwOTA?
Click to expand...
Click to collapse
I woulded have tried but since I can't flash or boot a twrp image you can't do much on those cases HwOTA relies on a TWRP recovery.
Thanks!
AS

Is there already Dark Theme on EMUI 9? Thanks.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app

gelo01 said:
Is there already Dark Theme on EMUI 9? Thanks.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey
For now I only know that the feature is only present on Huawei Mate 20RS, Mate 20X and Mate 20 Pro due to higher capacity batteries, here's the official info:
https://consumer.huawei.com/uk/support/faq/have-you-tried-the-new-dark-interface-from-emui-9/
But maybe it will come eventually in the future for all Huawei phones with EMUI 9 as a standard feature but for now nope...
Cheers,
AS

Question related to "After updating, you will not be able to downgrade..." message

Question related to "After updating, you will not be able to downgrade..." message
Hope you guys are safe and well.
Currently my A50 on August update. I have no problems with this update but I like to update to Android 10 for additional features. I'm reluctant to update because of this message. I'm afraid that if I had problems or something wrong with the new update, I won't be able to go downgrade to August update.
So, Is it really impossible to downgrade using Odin with an official firmware?
I'm coming from iOS and hence the fear of updating. As you may know, iOS downgrade is impossible when Apple sign-out the old software.
Thanks in advance.

Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.

pripyaat said:
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
Click to expand...
Click to collapse
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.

Screen not responding after update
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!

sheidyly said:
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
Click to expand...
Click to collapse
Try to flash the ROM manually using ODIN

redymedan said:
Try to flash the ROM manually using ODIN
Click to expand...
Click to collapse
I'm sorry but I'm new to all of this and I seem to read some comments saying the phone was bricked after flashing.
And if I will try flashing, do I use the old firmware or the new one?
Thank you so much!

mistpsn said:
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Click to expand...
Click to collapse
I think... and I could be completely wrong, but it keeps track of the highest version of bootloader you installed. So it will not allow you to boot if you flash the older one. However, I am not sure how it behaves if the bootloader is unlocked.

If anyone have the same concerns I had. I found out that only security updates seems to have this message and risk bricking your phone in case you downgrade to lower version. Some people confirms that they were able to downgrade without any problems from android 10 to android 9 on their A50.
It also made sense that there are no problems since the warning message only included with security updates. The android 10 Update change list have no warnings related to downgrading to older versions.
March security update had the warning message. And I had to do the security upgrade before the android 10 update was available OTA.

shall i update firmwares?

Hi guys, I just bought a brand new note 10+ N975W (canada version). I'm on stock firmware. It keep asking me to update. Shall I update? which version is best to keep the battery last as long as possible?
Also, can i downgrade to previous versions or stock if i dont like the upgraded firmware?

Yes update. It's probably just security updates at this point, so there would be no reason to go back. The Note 10 firmware is fairly mature by now.

chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.

Belimawr said:
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Click to expand...
Click to collapse
my phone is still running on android 9.0.

aznboix said:
my phone is still running on android 9.0.
Click to expand...
Click to collapse
Since the phone is new. Before getting to far into configuration, run the update, then do a factory reset. It'll do a fresh install of Android 10 and any security updates.
That will give you a nice clean install you can then setup.
Sent from my SM-N976V using Tapatalk

You should always update. They are mostly Security Updates, these are for security reasons (Hence the name ). Yeah there are some system modifications and enhancements too but the main reason is to ensure the device is as secure as possible

Is there a custom firmware that works perfectly?
can i root my device?
can i flash to another firmware? Asia firmware for exemple
what are the apps that i can't miss on note 10+?
which firmware that has vietnamese language?
thanks

Question Unable to update after rooting phone

Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!

Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.

vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.

Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.

Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.

I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.

On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.

I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).

bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.

So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)

drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!

drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.

bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?

I really want that update as I'm reading it made the battery much better. What to do!

I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.

TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?

vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.

Question LE2127 + Microsoft Intune problems

Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.

razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?

SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.

If I have no sims detected am I able to flash something to regain sim detection and data?