Develop Bugs

Android Q Beta on the Pixel 3a XL

Anyone been able to successfully receive an OTA to the beta yet? Enrolled my device last night the moment I got it home and nothing so far.
Disclaimer: I'm using a carrier and bootloader locked T-Mobile version; still hoping I can eventually get TForce to carrier unlock this for me sooner rather than later otherwise i'll just return it and get one direct from good old El Goog.

Did they get magisk for the 3XL yet; last I read over there they didn't have it for Q on the XL.

This true. I spent a couple hours on this last night and it does not work. I went back to pie.

I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.

P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
That's pretty much what I figured, but wasn't certain. Good to have some feedback from others; sounds like we can pretty much confirm that it isn't being pushed to the 3a devices yet.

I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?

DanRyb said:
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
Click to expand...
Click to collapse
Yep. It's possible they are withholding the OTA from carrier devices...

P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.

alphahere said:
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
Click to expand...
Click to collapse
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.

P$udo said:
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
Click to expand...
Click to collapse
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html

Looks like Pixel 3a and 3a XL were removed from eligible devices on the beta sign up page.
I wonder what's up?

if anyone is looking for the download you can find it here

alphahere said:
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Wow. Thanks for that. I thought fastbootd was a mistype when they were compiling. I didn't know that it was a whole other thing. Seems to be more akin to what recovery previously was on some older devices.

I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.

elpindian said:
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
Click to expand...
Click to collapse
I did not get the OTA. I downloaded the firmware image and flashed it.

Android q beta isn't ready for the pixel 3a/3a xl until June

An FYI... I just wandered over to Papajohnwu's Twitter and he is saying he'll be ready for Q.That's some good news, hate to be stuck on Pie forever.

If you have a 3a (xl) from a carrier like T-Mobile where to boot loader is locked, if you're able to use adb/fastboot to flash beta 3, you very well may not be able to revert the phone to Pie. I'm stuck as I got mine on the day TMO put them on sale, then opted in to the beta expecting to be able to opt out, well considering they removed that option, I'm now stuck on Q..

Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.

I'm curious how you got it unlocked from T-Mobile. I picked mine up on release day and when I got around to checking, OEM Unlocking was greyed out. Did you do this before installing a SIM?
Thanks!
PhoenixPath said:
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
Click to expand...
Click to collapse

Can't get firmware updates [SOLVED]

Some time ago I loaded a firmware onto my VZW S8+ (G955U) which I thought was a legitimate firmware. However, I've never been able to update the phone since. The firmware that I loaded was CRE1 and since loading that, no OTA updates have occurred and even trying to use the VZW update tool, I get an error saying no update for that firmware or something to that effect.
I assume that I would need to flash back to a base version 8 firmware and then see how things go from there but I haven't been able to locate a base v8 firmware - assuming that is the direction I need to go.
Can anyone advise? The phone is not rooted. I did see one other similar thread with CRE1 firmware from 2018 - I can try downloading the closest firmware to CRE9 that I can find, which is CRK9, and see if I can get it to load.
Other suggestions/ideas are welcome!
[UPDATE]
So I essentially followed another post here and using Odin 3.13.1 I loaded CRK1, the oldest I could find that was near CRE1, and the phone came back up and pretty much immediately notified of an OTA update. About 12 or so OTA updates later and I'm at the current OTA release.

I'm having the same issue. I bought a VZW S8+ (G955U) from eBay Seller mistyelectronics that was supposed to be new in box. It has never updated since I received it almost a year ago. It stuck on Software Version G955USQS5DSE5. Any insight or advice to go the same route? I used Odin years ago. Where would I look for the files to load to the phone?
I appreciate any help you can give.

Cannot update past 10.0.3.HD63CB

Hello, I have a T-Mobile HD1907. I unlocked the bootloader and used the pixel experience ROM. I had issues with the microphone not working over calls so I used MSM tool to put it back to its original locked state. It worked well and the phone is back to stock. Unfortunately the phone will not OTA update to android 11. Specifically the update 11.0.1.5.HD63CB. The update will start downloading for about 1 sec and then instantly pause. am having the same issue as described here https://forums.oneplus.com/threads/oneplus-7t-fails-on-system-update.1162696/ however I am not eligible for a phone replacement.
If anyone can help me manually update the phone (perhaps using fastbootd to manually flash it?) it'd be greatly appreciated.
EDIT: have also used oxygen updater app, it doesn't work as I have the t-mobile variant
EDIT2: also when I use the newer MSM tool (for android 11 tmobile) I get "param preload" and "No valid trg ID"

Fixed this by flashing
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/OnePlus_7T_T-Mobile_OxygenOS_10.0.3.zip
then
https://onepluscommunityserver.com/...CB/Q/OnePlus_7T_T-Mobile_OxygenOS_10.0.13.zip
and then finally
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/R/OnePlus_7T_T-Mobile_OxygenOS_11.0.1.5.zip
I guess u cant skip versions. sorry for making a thread. hopefully this helps someone else

Question LE2127 + Microsoft Intune problems

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

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

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

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

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

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

Question T-Mobile device converted to Indian, can't take full updates

Hi all,
I have an issue with my device and ended up using SMT Download with a modified MSM I made to restore T-Mobile firmware back. I did lose my Widevine and data but was quickly able to fix it by flashing back param and modemst1/2 and relocking my bootloader.
I'm currently having an issue where I can't take full updates, i.e. from Android 11 to Android 12, but I can take minor ones, i.e. 11.2.4.4 to 11.2.10.10. Does anyone with a bricked T-Mobile OnePlus 9 Pro have a similar issue? Also, if anyone knows how to convert the Indian target back to T-Mobile, please share! I know it's been posted somewhere that it's impossible, but if the Indian MSM can write to the target in the first place, there definitely is a way.
To my fellow T-Mobile OnePlus 9 Pro users who ended up having to use the Indian MSM to unbrick and the rest of XDA, I would appreciate your thoughts on this.
Thank you

razercortex said:
Hi all,
I have an issue with my device and ended up using SMT Download with a modified MSM I made to restore T-Mobile firmware back. I did lose my Widevine and data but was quickly able to fix it by flashing back param and modemst1/2 and relocking my bootloader.
I'm currently having an issue where I can't take full updates, i.e. from Android 11 to Android 12, but I can take minor ones, i.e. 11.2.4.4 to 11.2.10.10. Does anyone with a bricked T-Mobile OnePlus 9 Pro have a similar issue? Also, if anyone knows how to convert the Indian target back to T-Mobile, please share! I know it's been posted somewhere that it's impossible, but if the Indian MSM can write to the target in the first place, there definitely is a way.
To my fellow T-Mobile OnePlus 9 Pro users who ended up having to use the Indian MSM to unbrick and the rest of XDA, I would appreciate your thoughts on this.
Thank you
Click to expand...
Click to collapse
I believe you have to have 11.2.10.10 to update to a12

gillim74 said:
I believe you have to have 11.2.10.10 to update to a12
Click to expand...
Click to collapse
I do have 11.2.9.9 which is basically the T-Mobile version of that update, but there's something still preventing me from going to A12.

razercortex said:
I do have 11.2.9.9 which is basically the T-Mobile version of that update, but there's something still preventing me from going to A12.
Click to expand...
Click to collapse
Not too familiar with tmobile but do they offer a way to do a local upgrade?

I made this guide the 9 but it's the same idea with the 9 Pro. Since you're already on OOS11, skip the part about the MSM and just download the global 9 Pro OOS11 downgrade package and follow the instructions for flashing with Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com

Awesome!
One more thing, I tried to restore my persist.img from my backup, but I can't enroll my fingerprints anymore, it shows a fingerprint calibration error, any ideas on how to fix?

gillim74 said:
Not too familiar with tmobile but do they offer a way to do a local upgrade?
Click to expand...
Click to collapse
They do not unfortunately. The only way to upgrade is directly from the server.

razercortex said:
Awesome!
One more thing, I tried to restore my persist.img from my backup, but I can't enroll my fingerprints anymore, it shows a fingerprint calibration error, any ideas on how to fix?
Click to expand...
Click to collapse
That's not something that I have ever had to deal with, hopefully someone will come along who knows.

razercortex said:
They do not unfortunately. The only way to upgrade is directly from the server.
Click to expand...
Click to collapse
I would try to msm again then boot to system then msm one more time.it fixed a issue i was having with my phone when i did it that way.it cant hurt to try

I forgot to share that this problem only occurs with locked bootloader, unlocked bootloader is fine.