Develop Bugs

Upcoming Update

If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.

Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.

You aren't going to need to do anything, other than NOT take the OTA. The only thing you will need to do is wait from 2-10 hours after the update is out in the wild for the devs to get their hands on it and give us a fully rooted build to flash. It does not take long around here. There is absolutely no need to unroot and take the OTA. Who knows, if you did that you may not even be able to root again. So basically all you're going to need to do for the update is wait for the devs, and then flash a rom as usual. Maybe some new radios or something too, who knows.
I'm more concerned about when they will push the damn update. *Supposedly* it's Q2, but I'd bet if that's true, it will be late Q2.

r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
Sure, lots of people say "wait for a rooted version of the update," but all I want to know is, is it POSSIBLE to safely upgrade even if you are rooted? Would flashing the stock update remove ClockWork recovery?

yes i was rooted before 2.2 and i was having a crazy day, long story short i accepted the OTA not paying attention and it got me a weird reboot then i was unrooted and on 2.2 i had to wait for a root method for it. but i heard of some people having their phone glitch in crazy ways, also that first OTA sprint rolled out had a bug that was bricking some phones

RileyGrant said:
If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Click to expand...
Click to collapse
Developers will simply make new roms, and then you can flash the "update" of that rom. it'd be the same way of flashing CM7 nightlies.

Or just make sure you are s-off, take the update, install it. Then install SU from recovery and you are good to go. Thats the whole point of s-off (other than flashing PRI, NV, and Radios of course)

rugedraw said:
If you rooted with Unrevoked and have Unrevoked Forever, then theoretically you should be able to flash the update and still be s-off to flash a rooted rom over the update. You'd have to push the custom recovery back onto the phone, though. However, I wouldn't be the guinea pig for the theory myself. I'd keep 2.2 until a rooted 2.3 rom is available and then flash that. No one knows what will happen if you flash the OTA update as no one has is or knows what's inside of it.
Once it starts being pushed out, it will just be a matter of time before some posts a thread either:
a) crying because the update broke their root.
b) gloating because the update did NOT break their root.
Basically, don't accept it. Play it safe and wait. We've been on 2.2 for well over half a year, so 1 more day isn't going to kill anyone.
Click to expand...
Click to collapse
To make it simple, the result of accepting the OTA would either:
A- luckily do nothing
B- "Break" your phone and not be able to re-root

r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct!

Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.

phsteve said:
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
Click to expand...
Click to collapse
The OTA update would include the new stock 2.3 rom in it. It would wipe whatever you have on your phone (regardless of whether it is Sense or not) and install the OEM Sprint 2.3-based rom that all will eventually be on all new Evos when HTC ships them out.

[Q] Remove carrier branding without rooting

Hi, new to this forum and relatively new to Android as well. I've searched and read through google and the forum, but not able to find an answer to my specific question.
I'm in the UK, and recently bought a HTC One M8 that was previously locked to O2 but now unlocked and using it on Three. The phone has carrier branding - O2 startup and shut down animations. The phone to my knowledge has never been rooted. I'm on 4.4.3 and software version 2.22.206.6.
I would like to remove the carrier branding and still remain unrooted/ untampered etc (due to work email integration restrictions in my company). I currently do get OTA updates but not sure if getting from HTC or O2. I would preferably like to get OTA from HTC direct in future and skip O2 as it's supposed to be quicker.
My questions:
Is software version same as firmware?
I assume that to remove the carrier branding, I'll have to flash the ROM. I've read that I don't need root to do this. But what exactly would I need to do? Appreciate if a guru could point me in the right direction.
I've read articles that mention stock recovery. Is my recovery "stock" if the phone has carrier branding? My assumption is stock refers to the vanilla version if buying from HTC directly. I don't know if O2 packages the phone with a custom recovery?
Thanks in advance.

No. You need root (aka... disabled write protection) to alter sysyem files, which the bootlogo is one of.

halfwaymark said:
I would like to remove the carrier branding and still remain unrooted/ untampered etc (due to work email integration restrictions in my company).
Click to expand...
Click to collapse
I don't have that problem... Can't keep my phone that I paid for the way I want i.e Tampered, unlocked, fun ...Then keep the e-mails, I got better things to do in my time at home. If you want me to get it away from my work place then don't give me crap like "integration policies", if that's an issue supply me with a company paid phone.
I assume that to remove the carrier branding, I'll have to flash the ROM. I've read that I don't need root to do this. But what exactly would I need to do? Appreciate if a guru could point me in the right direction.
Click to expand...
Click to collapse
You need to have your bootloader unlocked to flash ROMs. The moment you unlock it and flash a custom recovery is the moment your phone shows "Tampered", no more emails for you then
I've read articles that mention stock recovery. Is my recovery "stock" if the phone has carrier branding? My assumption is stock refers to the vanilla version if buying from HTC directly. I don't know if O2 packages the phone with a custom recovery?
Click to expand...
Click to collapse
Stock recovery refers to the recovery that comes with the phone when you bought it. Custom recoveries are like TWRP/Philz. If you haven't done any changes to the phone and you bought it new from the store then you still have stock recovery. Whether the carrier made changes to it(doubt it though) or not is irrelevant as it's stock to the device(as bought) and not custom build by 3rd parties so to speak.

The only way I see, if you want to have an M8 without carrier branding to fit your companies security policies is to unlock bootloader and S-Off, change CID/MID, flash HTC stock ROM and firmware and then lock bootloader, remove tempered flag, and go S-On again.
It's some work to do in any case, but if your done your phone will be stock HTC WWE.
On the other hand I got a company paid phone as well, after I told them not to accept their company "security and integration policies" with respect to my private paid M8. I told them that if they wanted me to get my business mails on my private M8, they just had to accept the fact that with my property I'm gonna do what I like to do with it.

HTCNerdYoda said:
The only way I see, if you want to have an M8 without carrier branding to fit you companies security policies is to unlock bootloader and S-Off, change CID/MID, flash HTC stock ROM and firmware and then lock bootloader, remove tempered flag, and go S-On again.
It's some work to do in any case, but if your done your phone will be stock HTC WWE.
On the other hand I got a company paid phone as well, after I told them not to accept their company "security and integration policies" with respect to my private paid M8. I told them that if they wanted me to get my business mails on my private M8, they just had to accept the fact that with my property I'm gonna do what I like to do with it.
Click to expand...
Click to collapse
Exactly, if they paid and gave the phone, it's something entirely different. If you pay for it and they still want to enforce crap like that, it's almost the same as expecting you to buy a car(with your money) so that you can go on business trips for them. If you "pimp" out YOUR ride with a turbo and some amazing sound system, they refuse to have you do your job because your car is contrary to their "health and safety" policies. They can then take that job and shove it

There is a workaround for that problem when rooted exchange bypass security I think it's called you can you xposed or its built into some roms

HTCNerdYoda said:
change CID/MID
Click to expand...
Click to collapse
Thanks for your reply. As a noob, I understand most of your post other than this. What CID/MID should I change to?

the CID/MID has to be changed as they are checked by the OTA update server, thus you have to have one that fits the OS and firmware, for the update to be installed. So e.g. if you want to unbranded your One M8 you got to change CID to an original HTC-CID as well
After I gained S-Off, I changed to CID HTC__001 (HTC carrier ID - had a T-MOB CID before) as well as MID 0P6B10000. This is one of the WWE combinations. As soon I had done this I went on installing the WWE Backup 2.22.401.5 as well as the corresponding firmware. Thus I receive updates as soon as they get released by HTC, and haven't to wait for the carrier to approve it in the one hand, and don't have any T-Mobile bloatware or changes to the OS on the other hand. Just pure HTC Stock.
Sent from my HTC One_M8 using XDA Free mobile app

Hey guys, I've asked this question in several places so far with no luck, was wondering if you would be kind enough to help please?
I have an unlocked htc m8 cid 2___001 running 1.54.206.10, I have a constant nag of an ota update that I can't install (rooted) I want to ideally unroot and flash back to it's original state - can't find cid 2___001 nor 1.54.20.10 anywhere OR install a custom rom and firmware.
I've downloaded several firmwares including the popular 2.22.401.5 amongst others, but none take as I'm told they are the wrong version. I assume the cid is the issue? Any ideas how I can get around this please? I'm totally stuck now and getting any help is almost impossible, sadly.
Thank you in advance.

Do you think marshmallow update will make the phone unlockable again?

I'm a big fan of flashing roms onto phones, but i'm also a fan of stability and want to continue using official OTA for now. Once the OTAs stop coming, I will be willing to explore keeping my phone up to date via flashing ROMS.
Given the nature of the "fix" to unlock the bootloader (converting it to dev edition), it seems to me this is something that will always work, even in the future. Do you guys agree with that?
If it's not the case, I'd rather take necessary precautions now to get my phone converted over and possibly flash stock/de-bloated ROM going forward.
You guys think it's safe to just take OTAs for now?

I don't think the CID exploit used to unlock the bootloader will/can be patched out, but that exploit needs temp root to work. Who knows if/when temp root will be available for a stock Note 4 on MM?
I would do the dev conversion now. You can always flash a safe upgrade package once the stock MM update becomes available.

I agree. Just wait for a stock "safe" upgrade package to be released. I would at least postpone immediate install of the released official UG to see what it does to the phone.
For me, I have finally got control back on my phone. I went from the note 2 to note 4. I'd still be on the 2 if it hadn't got run over by a car, But the 4 is a good hardware upgrade but I felt it was an overall downgrade with the locked boot loader. Now that I have it, I would stay on 5.1.1 forever if it meant keeping the boot loader unlocked.

Has anyone even heard any info about an update?? I figured it would be outside the window for them to consider it.

rpn377 said:
I'm a big fan of flashing roms onto phones, but i'm also a fan of stability and want to continue using official OTA for now. Once the OTAs stop coming, I will be willing to explore keeping my phone up to date via flashing ROMS.
Given the nature of the "fix" to unlock the bootloader (converting it to dev edition), it seems to me this is something that will always work, even in the future. Do you guys agree with that?
If it's not the case, I'd rather take necessary precautions now to get my phone converted over and possibly flash stock/de-bloated ROM going forward.
You guys think it's safe to just take OTAs for now?
Click to expand...
Click to collapse
Don't touch any OTA or boot.img until I look at it and make a post in my OP.

What are my options on a 2PS6400 with Android versions Rooting and S-OFF

I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?

boot into download mode. If it was a true brand new sprint phone that was unlocked it would still have sprint apps. People on ebay are either buying new phones and flashing new roms themselves or buying new phones thatve been flashed by some other company.
Hold vol down and power button until the htc logo lights up and it should boot into download mode. Take note of the red colored data up top and write down the radio and os. Also do a imei and serial number check. If its anything other than an htc 10 send it back

mswlogo said:
I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?
Click to expand...
Click to collapse
The last update for the Sprint HTC 10 was for 2.51.651.31
You can download the RUU.exe directly from HTC for it, or you could check for updates in settings > about for the OTA
Here's a link for the RUU.exe Scroll down to the "Manual System Update Instructions" and read them. The download is at the end of the instructions.
If you would prefer to flash the RUU via your SD card, or you don't have a Windows computer (you need one for the .exe), let me know and I'll extract the ROM.zip (RUU.zip) for you so you can flash it that way. You could also probably just find the .zip with a Google search.
EDIT: Apparently Sprint has released Oreo via OTA, but there isn't an RUU for it yet

Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg

mswlogo said:
Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg
Click to expand...
Click to collapse
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU

xunholyx said:
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU
Click to expand...
Click to collapse
Nobody did anything to it. He sold 60 of them and it was clearly factory sealed. I see it mentioned a lot when googling around with other people just as puzzled exactly what it is. It's some sort of developer phone.
Someone had a 2PS500 as well that sounded identical. It had S-Off and same bare bones Sprint firmware version.
Ting says it will activate. But it says no on other carriers. I don't care though, but if I ever sold it, it looks like Ting (at least) would work.
It would not let the Unlocked ( *.617.*) RUU Run firmware flash.
The current firmware it had is 2.42.651.66 which is a Sprint Variant.
The CID is set to 1111111
So I tried the Sprint 2.51.651.31 RUU update and it flashed fine. And now has all the Sprint Garbage on it. I don't care. I now know what I can flash to it or not.
It still shows S-Off and Unlocked and Official after Sprint RUU.
It would be nice to know if I could safely flash the Oreo Sprint RUU (which I highly suspect will also flash fine once released) and then go BACK to the Nougat Sprint one as needed back and forth.
Since it's S-Off etc. It would be handy to be to test Android 7 and 8 with one phone.
If I bricked it, I can return for 30 days. So I rather brick it now than later

I took a shot at updating to Android 8 OTA and it worked fine. Will test if I can flash back to Android 7 with the same RUU I used above.
I can't get a very good GPS lock on this thing. Every other deactivated phone I have can get a good lock.

sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore

I can still get a gps lock just not a great one and sluggish to get a lock.

Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.

kimba99 said:
sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore
Click to expand...
Click to collapse
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)

JohnSoong said:
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)
Click to expand...
Click to collapse
unfortunately no... still trying to hunt for a solution. so yours was a 2PS6400 before... sprint? mine was a 2PS6500 though, as written on its backside (XC edition with 64GB internal btw)

mswlogo said:
Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.
Click to expand...
Click to collapse
Just a follow up. I sent mine back. Got a new real Verizon one for $200.00 on eBay (had no box but it looks new with fairly recent build date too). Works perfect, including GPS without being activated.
I had to manually flash it to the last Android 7 update via adb/fastboot couldn't do it OTA (WIFI) which I thought was a little odd.

Question Custom OTA sideload with November radio?

My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?

The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/

Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?

If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.

I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)

Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.

TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.

chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​

roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.

I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.

NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.

chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!