Develop Bugs

Can't get past hands free activation on any rom

Decided to go back to my S-oFF Sprint htc one m8 from over a year ago.
First thing I did was update my firmware only, no recovery no boot, firmware only. I upgraded firmware to 6.20.651.3 using this link: http://forum.xda-developers.com/showthread.php?t=2729173
I then updated my twrp from 2.8.50 to 3.0.2-0.
after I try any rom, even sprint roms, I can't get passed the hands free activation and prl update screen. It will reboot before the phone boots up. I have tried a few gpe roms and it wont get past the boot screen.
I tried loading up a nandroid i made over a year ago and its a lollipop rom that works, but still wants to go through handsfree activation. I am able to turn it off there, but want to get back to marshmallow and newer roms. I called sprint support and they said it shows as fully activated on their end.
What else should I try? Should i upgrade firmware, recovery and boot?

I hate bumping, but im out of options here. Any advice?

memekmek said:
I hate bumping, but im out of options here. Any advice?
Click to expand...
Click to collapse
I've gone through countless threads like these: http://forum.xda-developers.com/showthread.php?t=2716834
my situation seams to be unique, where my phone will actually reboot right after hands free activation, thus rendering it useless. I've been able to mount the system in twrp and delete the htc service apk, but on the marshmallow roms, i can't get LTE to work.
Im stumped. :crying:

So I've managed to read through threads and turn off hands free activation by:
1. Using wifi at initial setup (this helps get passed the initial hands free activation)
2. Mounting system in twrp, then deleting htcservice apk in twrp (this helps getting past the initial setup if its a problem)
3. freezing vdm client in titanium backup to avoid having the hands free activation keep popping up.
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Any help on the LTE and firmware issues would be very much appreciated!

memekmek said:
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Click to expand...
Click to collapse
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).

redpoint73 said:
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
Click to expand...
Click to collapse
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.

memekmek said:
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
Click to expand...
Click to collapse
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.

redpoint73 said:
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
Click to expand...
Click to collapse
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?

memekmek said:
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
Click to expand...
Click to collapse
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).

redpoint73 said:
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
Click to expand...
Click to collapse
Welp, did the RUU last night. It changed nothing, and did nothing for me other than making it a pain to reinstall twrp and get my nandroid back up. booo
lte and data is still spotty on 6.0 roms. The only other possible reason i think this could be happening is because i tried to carrier unlock this phone a few months ago, but i downloaded sim card info app, and it all appears to be ok.

Root new Android 7 stock ROM

Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!

Njoatun said:
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Click to expand...
Click to collapse
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system

Mat08.cc said:
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Click to expand...
Click to collapse
Do we need to modify system in twrp? before installing this?

shaygia said:
Do we need to modify system in twrp? before installing this?
Click to expand...
Click to collapse
No there's no need, at least I didn't change anything and it worked well

I just wanted to add this as a note as I did not see anyone else having these issues in nougat (7.0). Do not install SuperSU 2.78-201609011115. If you do your mobile data option in the notification bar will be grayed out. Your cell signal will have a slash through it and cell signal will no longer work. I do not know if other versions of SuperSU will also cause this symptom.
If this happens to you restore from a backup in recovery or if need be run the RUU again.
Mat08.cc's linked version of SuperSU does work!!!! Thanks!

My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.

dohcvtec said:
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
Click to expand...
Click to collapse
Excuse me, I did not understand.. The phone has received the upgrade but can not install it?

Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!

dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Have you installed this one << https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip >> ? (2.78-SR5)

dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698

Okay. Will try and get back to you. Thanks
P. S. Am I the only ine who is experiencing Messages failing and sending reports to HTC? Ever since I switched to Nougat, every time when I receive/send a text the app fails and when I try to access notifications it fails automatically as well. Ideas? Thank you

idontkn1 said:
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Click to expand...
Click to collapse
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards

dohcvtec said:
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
Click to expand...
Click to collapse
You might want to read the latest posts in the TWRP thread. The important part starts here.

Flippy498 said:
You might want to read the latest posts in the TWRP thread. The important part starts here.
Click to expand...
Click to collapse
I just read the threads you gave me. I understood the process. I will search for the zip file cause this seems to stop me right now. Everything else makes sense from top to bottom. Thank you very much once again.

Converted dev phone, reception with 4.14.617.6 but not after OTA to 4.19.617.1

Hello,
After some troubles I've converted my S-OFF x.xx.410.xx phone to a dev edition 2 weeks ago by reading a lot on this forum. I believe I did the following:
- flash 0PJAIMG nougat.zip from bootloader mode / SD
- run 4.14.617.6 RUU after flash
This worked for perfectly for a time.
On 1-1-2017 I got the 4.19.617.1 OTA notification which I accepted as I did not modify the system in any way. OTA completed succesfully however after OTA the phone lost mobile reception. In Android IMEI was not visible. In fastboot I saw IMEI with "fastboot getvar all".
Re-flashing RUU 4.14.617.6 worked to regain mobile reception however OTA nofication would of course still appear. Today I retried but with the same results -- no mobile reception after OTA.
To confirm with the new RUU available I ran the 4.19.617.1 RUU to re-flash phone and indeed no signal at all.
Then I ran the 4.14.617.6 RUU and signal again.
I read this in the FAQ:
"Q1: Everytime I flash a custom rom I lose my IMEI, my mobile reception and my phone stops recognizing my sim card. What's the reason for this?
A: You probably flashed a custom rom that is based on firmware 3.35.x although the firmware of your phone is 3.y (with y being any other number than 35). The boot image of 3.35.x based roms is not compatible with your firmware version. The solution of the problem depends on the question whether you are trying to install a Sense-based rom (like ICE or ViperOneM9) or a non-Sense-based rom (like CM): For Sense-based roms you just need to re-flash the stock boot image of your current firmware version."
This seems like my problem except I run RUU directly from HTC. Any idea on what I can do to accept OTA / reflash phone with 4.19.617.1 RUU ?
Thank you!

Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.

@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You've used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching. Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
shivadow said:
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
Click to expand...
Click to collapse
If the phone was rooted the OTA wouldn't have been installable.
And please stop posting things that aren't true. The dev firmware is not a beta version. It's the US equivalent of the European 401 firmware or the Asian 708, 709 or 710 firmware. Beta firmwares look like this one: 2.10.401.180. They have three numbers behind the last dot. If you compare the 3.x firmware of SKU 401 and 617 you'll notice that 3.35.401.12 and 3.35.617.12 are almost exactly the same except for some contintent-specific tweaks.
It is true that the dev edition is not necessarily better than the 401 one. However, it's up to every single user to choose whether he or she wants to wait until the latest update gets released for his/her SKU or whether they want to convert to the dev edition which receives all updates first (in case of the M9).

Flippy498 said:
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You're used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching.
Click to expand...
Click to collapse
Yes, that's what I thought.
Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
Click to expand...
Click to collapse
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
If the phone was rooted the OTA wouldn't have been installable.
Click to expand...
Click to collapse
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.

Fritti said:
Yes, that's what I thought.
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Click to expand...
Click to collapse
You could use the decryption tool that is linked in the readme thread for extracting the system image and the firmware files.

Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.

Gawain1986 said:
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Click to expand...
Click to collapse
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.

Fritti said:
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Click to expand...
Click to collapse
I have some news. I took the 4.19 No-Wipe firmware and flashed it by putting it on my SD card as 0PJAIMG.zip. It flashed and now I'm working on the 4.14 ROM with 4.19 firmware. All is working wel, most notibly making calls and using data.
This leads me to believe there is something in the Kernel/ROM of 4.19 that breaks our calling and data.
Does anybody have any other ideas to make 4.19 work?

The plot thickens .
I installed ICE ROM 4.19 after flashing firmware 4.19 and I had the same problem back, out of service area.
So I started comparing the build.prop files in the 4.14 ROM from HTC and the 4.19 ICE ROM. Then I changes a few lines to these values and I was able to call:
ro.ril.hsxpa=4
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=6
ro.aa.rid=115
To get data (and be able to log in to a google account) I did another thing. I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!

Gawain1986 said:
The plot thickens .
I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Click to expand...
Click to collapse
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again

bonesy said:
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
Click to expand...
Click to collapse
No such luck for me... As soon as my phone sees LTE, the phone force closes and aftter I have no Data and I'm out of service area again.

So I know this is nearly a necro but I wanted to give an update that I cannot try this anymore -- shortly after the failures started my phone got stuck in a bootloop. This had to be hardware error as it simply started one morning while I did not change anything. The Vodafone shop I brought it to agreed and send my unit in for (warranty!) repairs. I've since got it back with Android 7.0 on version 4.28.401.3, so there is no need for me to switch to dev edition now. I cannot say whether the signal issues were a symptom or a cause for my unit to fail.
Hoping that Gawain1986 has fixed his issues as well!

What is the best rom to update to?

HI, Im just wondering what the best rom to update to is for my HTC 10.
Im currently on UK EE network.
I have unlocked the bootloader (via HTCdev), I have S-off (via sunshine) and i am still running stock recovery and official rom on android 6.0.1.
I am hoping to update to nougat.
My plan is to hopefully lock the bootloader again after once i have updated so i can use Android pay again. Their damn safetynet app stops me from running it having an unlocked bootloader.
Answering my own question though, would android pay still work with a custom rom? or can I use an official Nougat rom then lock the bootloader to fool it?

with magisk and phh su safety net currently also passes on rooted custom roms.

j to the 4n said:
with magisk and phh su safety net currently also passes on rooted custom roms.
Click to expand...
Click to collapse
I never used Android pay before my HTC10. the last phone I rooted was an old Galaxy S4, I had installed TWRP, SU, and used resurrection remix for it. it seemed to work perfectly fine. until I loaned it to someone an now its dead, (suspect water damage).
I'm currently at the stage of whether to install TWRP & SU to root it then go on to install a custom ROM, or leave as is.
I was tempted to go S-off,/Locked to allow it to work via sunshine but I would need to reset to S-on first.
Not entirtely sure of which route to take at the mo

What did you end up doing here, I'm on EE 1.95.91 and want to get onto N and a custom ROM - any suggestions?

SailorJerry01 said:
What did you end up doing here, I'm on EE 1.95.91 and want to get onto N and a custom ROM - any suggestions?
Click to expand...
Click to collapse
Ive ended up using Leedroid. But I have lost the WiFi calling option. Im presuming that this is because of My HTC10 being locked to EE and having the EE branded firmware on. Lee an me have been trying to figure this out as I seem to be the only one
The latest Leedroid can be found on his website.

aceniz said:
Ive ended up using Leedroid. But I have lost the WiFi calling option. Im presuming that this is because of My HTC10 being locked to EE and having the EE branded firmware on. Lee an me have been trying to figure this out as I seem to be the only one
The latest Leedroid can be found on his website.
Click to expand...
Click to collapse
Youre s-off so update the firmware and install either viper or leedroid.. Both work fine. I'm in ee too although I don't care about wifi calling and android pay.. Magisk may allow them to work.

dladz said:
Youre s-off so update the firmware and install either viper or leedroid.. Both work fine. I'm in ee too although I don't care about wifi calling and android pay.. Magisk may allow them to work.
Click to expand...
Click to collapse
Yeh Im S-off but I cant seem to update the Firmware for some reason. Or I havent been trying the right ones. I tried an update from HTCdev to update me to 2.41 but it failed.

aceniz said:
Yeh Im S-off but I cant seem to update the Firmware for some reason. Or I havent been trying the right ones. I tried an update from HTCdev to update me to 2.41 but it failed.
Click to expand...
Click to collapse
ensure you supercid, then flash the WWE (401) firmware from the thread of @Sneakyghost

j to the 4n said:
ensure you supercid, then flash the WWE (401) firmware from the thread of @Sneakyghost
Click to expand...
Click to collapse
Thanks, SuperCID done, had to mess about a little as bloody Powershell has took over cmd despite disabling it.
The latest fw on htc for unlocked/developer HTC10 is 2.41.617.3, I presume this would be the same thing done via RUU and Sneakyghost's has no particular changes to it?

aceniz said:
Thanks, SuperCID done, had to mess about a little as bloody Powershell has took over cmd despite disabling it.
The latest fw on htc for unlocked/developer HTC10 is 2.41.617.3, I presume this would be the same thing done via RUU and Sneakyghost's has no particular changes to it?
Click to expand...
Click to collapse
correct, just that it won't wipe your data..
You have a Dev Edition device? If not, you would need the 2.41.401.3 firmware.

j to the 4n said:
correct, just that it won't wipe your data..
You have a Dev Edition device? If not, you would need the 2.41.401.3 firmware.
Click to expand...
Click to collapse
Right Ill use Sneaky's version then.
My HTC is direct from EE, but now as I've rooted it etc it says its a dev for the obvious security check.
My problem has always been as it had original EE based firmware on it. a little googling shows a lot of network features dont work unless you use it. I know currently my VoLTE doesnt work as it drops to 3G when i make a call.

Question My phone(CPH2451) can not Update

Hello everyone.
It's my Oneplus11(CPH2451/Chinese version Global Rom), I can't update from CPH2451_11_A.06 to CPH2451_11_A.07.
Running the update from the settings fails, and using [OPLocalUpdate.apk] also fails.
Even if you do it right after factory reset, it will fail.
The files used are as follows.
・FW Official : https://android.googleapis.com/packages/ota-api/package/11ca82d836bbd2530659d57bca236d2da0caf5dd.zip
・APK : https://www.androidfilehost.com/?fid=15664248565197176984
Please help me.

Same here man. im using chinese op11 flashed to indian 2447A.06 and i cant update it to A.07 either. I did multiple factory resets and still cant

Same here. Really hoping someone can help with this.

Can't be done. Should convert to EU which gives full release every time

MrSteelX said:
Can't be done. Should convert to EU which gives full release every time
Click to expand...
Click to collapse
Thanks your information.
First, convert to the EU version.
There are several threads about conversion, but which one should I refer to?

Apito said:
Hello everyone.
It's my Oneplus11(CPH2451/Chinese version Global Rom), I can't update from CPH2451_11_A.06 to CPH2451_11_A.07.
Running the update from the settings fails, and using [OPLocalUpdate.apk] also fails.
Even if you do it right after factory reset, it will fail.
The files used are as follows.
・FW Official : https://android.googleapis.com/packages/ota-api/package/11ca82d836bbd2530659d57bca236d2da0caf5dd.zip
・APK : https://www.androidfilehost.com/?fid=15664248565197176984
Please help me.
Click to expand...
Click to collapse
Same here, I am facing exactly the same issue as you. Though I have searched around, I still can't find the solution.

China op11 convertet to oos can not make a ota uodate
After ota (full pack ) the phone have a bootloop and you have (only with unlocked bl) to flash a image from coloros back to the phone without this inage bootloop
Simple
With unlocked bl flash the full rom over fastbootd and flash the one coloros image back qnd reboot (delete when you have the cow partition and than reboot )