Develop Bugs

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 Custom Recovery, Root, ...

Hello folks,
I need your help, I bought myself a OnePlus 9 Pro a few months ago and still use my OnePlus 6 because it still isn't configured finally. There are unfortunately too many open questions.
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
I nearly sure it's theoretical possible to find the solutions myself, so sorry for my maybe stupid questions.
Edit: after sending I see this guide.
What does AA, BA and DA mean?
Hope someone could help!
THX mcdoubleyou

mcdoubleyou said:
Hello folks,
I need you help, I bought myself a OnePlus 9 Pro a few months ago and still use my OnePlus 6 because it still isn't configured finally. There are unfortunately too many open questions.
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
I nearly sure it's theoretical possible to find the solutions myself, so sorry for my maybe stupid questions.
Edit: after sending I see this guide.
What does AA, BA and DA mean?
Hope someone could help!
THX mcdoubleyou
Click to expand...
Click to collapse
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
No. TWRP is ready for A12 ROMs as of now.
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
Yes, Magisk is the best solution...
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
Did not understand what you mean by 'stuck' If it is a brick, use MSM tool to flash back to stock.
What does AA, BA and DA mean?
These are just builds for specific regions.
AA - Global
BA - EU
DA - India

Sorry for my late reply vipinpvarghese and thank you very much.
As far as I know Magisk Hide isn't exist anymore so I have to use Zygisk - right?
Cheers mcdy

Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
No, OnePlus has not released A12 source code so this (as well as true A12 roms) cannot be built.
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
Magisk is still the preferred root method.
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
Make sure you've set the option in developer options but also run "fastboot oem unlock" in your fastboot, which WILL wipe your device.
What does AA, BA and DA mean?
AA = Global
BA = Europe
DA = India

Hey folks,
Don't know what I did wrong, but now I really stuck.
I downloaded Boot 12.C44_BA.zip linked in the other thread and installed it.
After that my phone reboots and I installed Magisk in Magisk and make a reboot.
Now I'm only able to boot into fastboot.
In a Thread I read that I could try to change my slot back, after that it start's normal.
So I decided to update Magisk in Magisk and then install Magisk again from inside Magisk, but it happens again.
What should I do to root my device not only temporary?
THX mcdy

mcdoubleyou said:
Hey folks,
Don't know what I did wrong, but now I really stuck.
I downloaded Boot 12.C44_BA.zip linked in the other thread and installed it.
After that my phone reboots and I installed Magisk in Magisk and make a reboot.
Now I'm only able to boot into fastboot.
In a Thread I read that I could try to change my slot back, after that it start's normal.
So I decided to update Magisk in Magisk and then install Magisk again from inside Magisk, but it happens again.
What should I do to root my device not only temporary?
THX mcdy
Click to expand...
Click to collapse
Which magisk build are you using? Afaik stable magisk still only supports OOS11. You need canary for OOS12.

terlynn4 said:
Which magisk build are you using? Afaik stable magisk still only supports OOS11. You need canary for OOS12.
Click to expand...
Click to collapse
Thanks, I tried it this way but with the same effect.
First I change the slot, then opened Magisk and change to Canary.
After that I do an update and installed to the inactive slot.
Any ideas?
THX mcdy

mcdoubleyou said:
Thanks, I tried it this way but with the same effect.
First I change the slot, then opened Magisk and change to Canary.
After that I do an update and installed to the inactive slot.
Any ideas?
THX mcdy
Click to expand...
Click to collapse
When you say you "change to Canary" did you actually install the latest Canary to your current slot and reboot, then make sure magisk is completely up to date? You need to actually be running the latest Canary prior to performing the update, as far as I know. At least that's how it worked a couple of versions ago with Alpha.

terlynn4 said:
When you say you "change to Canary" did you actually install the latest Canary to your current slot and reboot, then make sure magisk is completely up to date? You need to actually be running the latest Canary prior to performing the update, as far as I know. At least that's how it worked a couple of versions ago with Alpha.
Click to expand...
Click to collapse
Hey terlynn4,
it looks like it's jinxed.
After your info, I moved the phone back to the other slot, then let it boot.
Logged in and opened Magisk, checked that Canary is still there. Updated the app - seems there was one by now - and reinstalled Magisk to the current slot. Then installed Magisk on the other and rebooted.
But unfortunately it was then in fastboot again.
So I changed the slot again and was afraid that it would be useless because of the update, but fortunately it booted normally.
In short, on one slot the Magisk version seems to work, on the other not. Oo
Any ideas?
Thanks! mcdy

Question wanting to update to most current OOS11 unsure where to start

i just ran the MSM to get back to factory OOS11 so i can flash a custom rom, i am wanting to update to most current OOS11 but unsure how to do it, if i run the OTA update offered on my phone will that update me to OOS12 or the latest version of OOS11? the update i see it offering is 11.C.48 makes me believe its OOS11 but just wanted to verify
right now im on 11.2.2.2, just tried to boot the latest OOS11 through fastboot but it kept me on the same version for some reason

Veid71 said:
i just ran the MSM to get back to factory OOS11 so i can flash a custom rom, i am wanting to update to most current OOS11 but unsure how to do it, if i run the OTA update offered on my phone will that update me to OOS12 or the latest version of OOS11? the update i see it offering is 11.C.48 makes me believe its OOS11 but just wanted to verify
right now im on 11.2.2.2, just tried to boot the latest OOS11 through fastboot but it kept me on the same version for some reason
Click to expand...
Click to collapse
You should check the file size, usually a 4GB update indicates it's OOS12, if it's less than 1GB it's likely OOS11.

razercortex said:
You should check the file size, usually a 4GB update indicates it's OOS12, if it's less than 1GB it's likely OOS11.
Click to expand...
Click to collapse
awesome thanks, looks like its 522MB oddly enough though when i check the list of OS's C48 ( which is the one asking me to update to) is OOS 12 so i wonder if im already on oos12 and need to downgrade

Veid71 said:
awesome thanks, looks like its 522MB oddly enough though when i check the list of OS's C48 ( which is the one asking me to update to) is OOS 12 so i wonder if im already on oos12 and need to downgrade
Click to expand...
Click to collapse
It may also depend on which country's version you are looking at. I am from India and running the Indian version OOS 11.2.10.10LE15DA. Later versions have C in the middle and as far as I know, what I have is the last version of A11 on OOS. Anything with a C whether 46, 47 or 48 is A12. This is my understanding but I may be wrong.
As I don't want the issues associated with A12 OOS, I continue to stay on A11. If you don't have issues, remain on the current version whether 11 or 12.

TNSMANI said:
It may also depend on which country's version you are looking at. I am from India and running the Indian version OOS 11.2.10.10LE15DA. Later versions have C in the middle and as far as I know, what I have is the last version of A11 on OOS. Anything with a C whether 46, 47 or 48 is A12. This is my understanding but I may be wrong.
As I don't want the issues associated with A12 OOS, I continue to stay on A11. If you don't have issues, remain on the current version whether 11 or 12.
Click to expand...
Click to collapse
im trying to flash the CRdroid rom and am having a few issues
#1 i have no cell service for some reason, also
#2 theres no hardly any apps at all to include a playstore lol (i suspect this is the case because i didnt install Gapps)
#3 when i do sideload Gapps i get an issue CRdroid home constantly forceclosing itself so i cant use anything on the screen and it just flashes but i can still pull down the notification bar and access the settings and everything but when i try to fix this by just wiping and re flashing it i get an error that the device is locked (which it shouldnt be but theres also no developer settings for me to check nor OEM when i try to search the settings with the search bar) so i have to run the MSM and restart the process
so maybe im doing something wrong let me list my steps and make sure i got everything correct
#1 i flash the MSM it puts me on 11.2.2.2
#2 i sign in, enable OEM and adb
#3 i reboot to fastboot and flash twrp
#4 once in twrp i install the 11.2.10.10 zip via this file to both slots (i manually just swap within twrp) https://android.googleapis.com/packages/ota-api/package/a074a7205a681509f1b84d6a2e0f75ddc2c6ab9b.zip but i get a lot of errors about not being able to save to system ext and others but it says successful not sure if it makes a difference
#5 reboot into the system and verify it updated to 10.10
#6 boot into fastboot and fastboot flash the CRdoid recovery image to both A and B slots that i got from here https://sourceforge.net/projects/crdroid/files/lemonadep/8.x/recovery/boot-23.06.2022.img/download
#7 once thats complete i boot into recovery mode (the crdroid one that was just flashed) and i factory reset and then go to apply an update and i sideload the CRdroid zip that i got from here(https://sourceforge.net/projects/cr...oid-12.1-20220623-lemonadep-v8.6.zip/download)
#8 reboot into recovery again once its complete and sideload the Gapps from the first post
and i havent done this yet but then i would flash the magisk boot img that i got from here https://sourceforge.net/projects/cr.../recovery/magisk-boot-23.06.2022.img/download

Question T-Mobile (LE2127) where are firmware stock for the updates?

Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?

cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
To get OTA updates, you need to uninstall magisk and restore the stock image in the Magisk app. Been there and done that. However, I would suggest staying with Android 11 and not update to A12. A12 is the pits...besides that with A12 you can have custom bootanimation and a custom systemwide font... Just like me. I have the LE2127 OnePlus 9 Pro 5G as well!

cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
Plus T-Mobile doesn't like their builds out there in the wild. You can use msm read back to get images also.

Yeah, I guess you're right. Mine is LE2127_11_C.17, and it is Android 12... I don't see any problem or bug coming to me, but we noticed two problems: an annoying update from itself (need to install C.19) and recovery firmware. Unfortunately, I have no idea how to install custom recovery firmware; maybe you have any idea for me?

Oh! I almost forgot to ask you, WHERE is ROM, image, that already downloaded the file (update)? Path in Root Explorer or something? That might help us find a way to do the stupidest manual update.

The slightest question is, is it in the path at system/cache that update file already downloaded or somewhere?

If you can manage to convert it to 2125 I would highly recommend doing so.. I have the 2127 and converted to 2125 it's so much smoother and no issues on A12 running version C.62

Is 2125 causing any issue after you flashed real 2127?

cat139lyleb said:
Is 2125 causing any issue after you flashed real 2127?
Click to expand...
Click to collapse
I mean, deepest issue?

luckylui said:
If you can manage to convert it to 2125 I would highly recommend doing so.. I have the 2127 and converted to 2125 it's so much smoother and no issues on A12 running version C.62
Click to expand...
Click to collapse
Can you have a custom systemwide font and custom bootanimation? Will Fontfix app change your font?

TheGhost1951 said:
Can you have a custom systemwide font and custom bootanimation? Will Fontfix app change your font?
Click to expand...
Click to collapse
That I am not sure... Don't use any of that. But, if you do want that, I'd recommend going to 2123 which is EU or 2125 which is NA/Global depending on your region and installing a custom ROM after the conversion.

cat139lyleb said:
I mean, deepest issue?
Click to expand...
Click to collapse
So far the conversion from 2127 to 2125 has been going great! I'd highly recommend reading the instructions on how to do the conversion before jumping in blind. Took me a bit to convert because I skipped a step or two, but finally managed to get it done. Plus, you won't have all that T-Mobile bloatware running.

I'm still on LE2127, albeit on stock 11.2.9.9 firmware, fully rooted with R/W mounted partitions, no bloatware, custom bootanimation and custom systemwide font....smooth as silk. Tried A12 and didn't like it at all. Went back to A11....

TheGhost1951 said:
I'm still on LE2127, albeit on stock 11.2.9.9 firmware, fully rooted with R/W mounted partitions, no bloatware, custom bootanimation and custom systemwide font....smooth as silk. Tried A12 and didn't like it at all. Went back to A11....
Click to expand...
Click to collapse
2127 converted to 2125, A12 over here. So much smoother!

luckylui said:
2127 converted to 2125, A12 over here. So much smoother!
Click to expand...
Click to collapse
Maybe so, but you don't have full root privileges. Try installing FontFix app from the play store and see if you can change your font....

cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
Use the system update for Android 12 apk but uninstall the system update app after you install the update but before you reboot or it won't let you use it again. After you uninstall the system update app. Then manually restart with the power button.
LE2127_11.C.19_0190_202208020022 incremental
https://android.googleapis.com/packages/ota-api/package/d2eb4ccd7fefc991d3bae6a2d7b914521ecd8ecb.zip

How did you find this link? And how am I uninstalling that update from the system app since I got an error that uninstalls failed? So please help and teach us way easier to do step by step for whom having problems with this issue.
Plus, I noticed that I felt like I failed to understand because I have no idea which kind of update software must be removed from the system first before we can go ahead and install a local update; that's why I'd ask you, please help anyone who is in the boat as I have an issue with following the steps are because some of you didn't explain clearly and how to do right step by step.

Question Cannot update to C.47

Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.

Which phone version do you have?

luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120

skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.

luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?

Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.

luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.

skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/

luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.

skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.

luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing

I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....

If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.

luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....

TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.

luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!

To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!

TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!

luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,

I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.