Develop Bugs

Can't pay with Android Pay on Lineage?

I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.

comady25 said:
I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.
Click to expand...
Click to collapse
The reason behind this is that lineageos is not a Google approved ROM. You can usually only use Android pay on stock factory ROMs, without root.

xBane_ said:
The reason behind this is that lineageos is not a Google approved ROM. You can usually only use Android pay on stock factory ROMs, without root.
Click to expand...
Click to collapse
This is false. You might be thinking of SafetyNet, which as I said, the phone passes. Otherwise, there is no reason why it shouldn't work, and indeed it has been confirmed that Pay works on Lineage. The app opens fine and I can add cards, it's just that paying doesn't happen.
My theory is that there's something wrong with the NFC drivers, as this is what happened with the OnePlus, but idk.

comady25 said:
This is false. You might be thinking of SafetyNet, which as I said, the phone passes. Otherwise, there is no reason why it shouldn't work, and indeed it has been confirmed that Pay works on Lineage. The app opens fine and I can add cards, it's just that paying doesn't happen.
My theory is that there's something wrong with the NFC drivers, as this is what happened with the OnePlus, but idk.
Click to expand...
Click to collapse
Excuse me then, on my Robin, and on my Nexus 4 (with custom ROM) it fails to work but I can still do NFC.

you need root and magisk to get android pay to work with lineage. No other way presently. Lineage worked with my Oneplus One with an unlocked bootloader but not with the Robin. I ended up restoring stock Nougat and it still wouldn't pass. Had to restore Marsh mellow, then lock the bootloader and do the ota update to Nougat. Android Pay now works. It's a shame because I'd rather have Lineage but Android pay is a deal breaker.
Hope this helps anyone in this situation.

comady25 said:
I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.
Click to expand...
Click to collapse
Since when are u able to have custom recovery and custom ROM and have a locked bootloader. I call false on that as well. Can't have a locked bootloader with at least custom recovery

the_rooter said:
Since when are u able to have custom recovery and custom ROM and have a locked bootloader. I call false on that as well. Can't have a locked bootloader with at least custom recovery
Click to expand...
Click to collapse
Code:
fastboot oem lock
Works now with the new LineageOS update anyway

​
comady25 said:
Code:
fastboot oem lock
Works now with the new LineageOS update anyway
Click to expand...
Click to collapse
The code will work but that is calling for a full brick of device. Can't have locked bootloader with custom recovery

the_rooter said:
​
The code will work but that is calling for a full brick of device. Can't have locked bootloader with custom recovery
Click to expand...
Click to collapse
Don't know what to tell you man but my phone is working fine. The bootloader only needs to be unlocked when you flash a new recovery.

If someone can get build.prop from latest stock ROM, I can make Android Pay working

hiimpig1 said:
If someone can get build.prop from latest stock ROM, I can make Android Pay working
Click to expand...
Click to collapse
No need to, Android Pay was fixed in the latest LineageOS build

[Qualcomm][MetroPCSXT1765]Do Not Take ANY Updates From March 2018 Onward

***Update August 31, 2018*** It has been reported from @Juanito216 that he's locked out of TWRP after taking an update, and this update is well past March when I first reported it. Be advised not to TAKE THE UPDATES OR YOU WILL LOSE ROOT/TWRP!
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid2 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.

You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Articul8Madness said:
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid02 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.
UPDATE 4/1/2018 - After finally being able to unlock the bootloader of the significant other and root it, I found something interesting. - if you take the pestering update that rolled out in March, you will be UNABLE to flash Magisk v14. You can flash No Verity and Superuser well, but you WILL NOT HAVE ROOT. The only alternative I have is to flash a custom rom and then flash Magisk.
Do Not Take the Update.
Click to expand...
Click to collapse
PimpMy5Ton said:
You seriously had to say that again?? Everyone I know uses custom roms anyway, just sayin'
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1766 using Tapatalk

PimpMy5Ton said:
You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Well, I said that because not everybody is going to read my guide. I've had such hell with this phone while others have sailed through it, I'm giving ALL the MetroPCS folks a head up. Most of the development is done on other variants of the phone as is, and a lot of info that is out there while Qualcomm does not really apply to us. Consider me like an ambassador for the Metro folks, lol.
If somebody said it, I haven't caught it in the threads. And honestly, hopefully this thread opens up a discussion on how we can flash back. I was completely unable to go back to the original stock on the significant other's phone AFTER that update too. Been tinkering with it since I posted that. Can't even flash some of the boot.img files successfully either that I explained in my post (in case of emergency section).
That update is something seriously nasty.
Update: Aaah...I see what I did there. Man, I'm doing too much in the middle of the night. Sorry bout that copy and paste thing. I was taking notes and writing and tinkering with the phone. Didn't want to forget the problem exactly.

Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.

Juanito216 said:
Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.
Click to expand...
Click to collapse
No, Juanito, no! That's why I said don't take the update. But now I'll correct it in my OP. Thanks for the info.
Can you follow my guide and see if you can get TWRP from ADB shell?

Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.

Juanito216 said:
Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.
Click to expand...
Click to collapse
I know you say you can't install TWRP. But can you load it through ADB Shell? If you can there's hope.
Did you start doing all this on Lineage or on Stock, or started back to stock and it crashed. You can always reunlock the bootloader through the Moto prompts on their website. It shouldn't be blacklisted.

Safe to flash trebel rooms?

Hey so I got the Nokia 6.1 unlocked from Best buy and noticed that it's a treble device and also has official twrp recovery. I noticed that we don't really have roms for this phone though and was wondering if I could just flash treble roms and if maybe that's the reason why? I really hope someone can help me out here lol.

There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.

runekock said:
There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.
Click to expand...
Click to collapse
The paid one is still working. I had to order last week, i had to downgrade from pie and unlock the bootloader, works fine. I can't recommend which one to order becuase of the rules of the forum, but at least one still works.

@SVcross
How did you downgrade?

runekock said:
@SVcross
How did you downgrade?
Click to expand...
Click to collapse
With the same service for unlocking the bootloader.

Well yes it's safe... currently i'm running havoc os 2.0....and it is working like charm...i haven't noticed any bugs yet...you can give it a try
But one thing to notice.... sometimes some magisk modules...like quickswitch for example....changes slot (from B to A in my case) when device is rebooted..and causes my device to stuck at bootloader aka download mode...idk why it happens...however it can be resolved by using fastboot....and typing fastboot --set-active=_b when device is in download mode....hope this helps...i encountered this a lot btw

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

Has anyone successfully rooted Moto G7 Play?

It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks

Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.

Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.

Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.

Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards

realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.

Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).

relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.

Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!

thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.

I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!

avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.

Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?

If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable

LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.

ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.

I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.

Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.

GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.

The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.