I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
bigmikey307 said:
I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
Click to expand...
Click to collapse
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Yes, I was running the international software and had this same issue. Flashed back to stock T-Mobile software due to horror stories of the update to Android 10 bricking converted devices. Tried to turn these on again, and same story... Stock messaging app worked, Google's didn't.
I have converted to International and upgraded to 10.0 using Oxygen Updater then downloaded Google Messenger app and it works great. I do have a unlocked bootloader however.
qbanlinxx said:
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Click to expand...
Click to collapse
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
pyrorob said:
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
Click to expand...
Click to collapse
RCS on the stock TMobile firmware isn't the issue. Latest beta message installed, carrier services updated, still no RCS on my device.
Related
Is G930AUCS4BQE1 (May 24/25 2017) the latest SMG930A firmware?
I'm on a factory-provisioned SMG930V (Verizon) and and looking for the latest U(nlocked) and A(T&T) firmware, to try them each out and see how they play.
Also related, as I understand it, the 5th letter from the right ("4" in the above example) indicates the bootloader version, which cannot be downgraded. Is that correct? i.e. I couldn't go to G930AUCS2APH1, which has v2 of the bootloader?
Thanks.
You are correct about the bootloaders, and the most recent OTA for ATT is QH1 from August. But we should be seeing Sept leak soon, and hopefully beta 7.1 as the Note8 is suposidly shipping with 7.1
As far as the U firmware goes, I personally dont keep up with that as I didnt want to give up videocalling/volte and cannot do without wificalling.
twizt3d said:
You are correct about the bootloaders, and the most recent OTA for ATT is QH1 from August. But we should be seeing Sept leak soon, and hopefully beta 7.1 as the Note8 is suposidly shipping with 7.1
As far as the U firmware goes, I personally dont keep up with that as I didnt want to give up videocalling/volte and cannot do without wificalling.
Click to expand...
Click to collapse
Thank you very much.. I need to do some more research on U vs. A firmware, it seems. one of my big pet peeves is the carrier bloat. Has your AT&T phone got much bloat?
Also, regarding wificalling, am I correct to presume that it's integrated with the phone itself, and not just another form of something like the Google Hangouts Dialer?
My phone has all the bloat froze or disabled, so its managable. You can search on here for a debloating app or script.
as for wifi calling, its cooked into the rom, but no one has been successful in getting it to actually function on ATT.
twizt3d said:
My phone has all the bloat froze or disabled, so its managable. You can search on here for a debloating app or script.
as for wifi calling, its cooked into the rom, but no one has been successful in getting it to actually function on ATT.
Click to expand...
Click to collapse
Thanks.
I came across this, which suggests there are fixes/patches that can be used (and one person insinuating they've done so) to get wifi calling operable on the U firmware:
https://forum.xda-developers.com/showpost.php?p=68011352&postcount=36
I've got a couple of debloat scripts in my S7 folder; just prepping the final path of whether I to A or U firmware... I've heard that the U firmware should be (carrier) bloat-free, but no wifi; I'm using a V model on AT&T so the AT&T would be useful, but I"d need to deal with carrier bloat.
Have you found that OTAs still work properly, after freezing or disabling bloatware, or have you had any adverse impacts to functionality?
mine works fine no issues. And that thread is for verizon's wifi calling which is different from ATT. It would also require root.
twizt3d said:
mine works fine no issues. And that thread is for verizon's wifi calling which is different from ATT. It would also require root.
Click to expand...
Click to collapse
Actually, it's in the Verizon section, but it's about taking a Verizon model to Unlocked firmware.
If you are on the U firmware, flash S7_or_S7Edge_Fixes_Debloater_V15.zip then Verizon_VVM_Volte_Wifi_Calling_G935U_Fix.zip
Note: I realize it says G935U, but it works on the G930U firmware as well.
Click to expand...
Click to collapse
Didn't catch the reference to root, I'll continue to dig.
Cheers.
I just received my Oreo update for my Unlocked S8+. Has anyone else received it yet? I'm thinking since we have Safestrap and now custom rom support that I'll cancel the update and wait for an AOSP rom.
ajsmsg78 said:
I just received my Oreo update for my Unlocked S8+. Has anyone else received it yet? I'm thinking since we have Safestrap and now custom rom support that I'll cancel the update and wait for an AOSP rom.
Click to expand...
Click to collapse
What carrier are you with? Did you have beta?
I just got it also. I'm on cricket
xmckinzie said:
What carrier are you with? Did you have beta?
Click to expand...
Click to collapse
I was on T-Mobile but switched to MetroPCS two days ago. (Same network)
It's true... I am on Sprint with G995U1 and I am currently downloading a 1354.14MB update.
I had to check for it, but it found it and downloaded it. My phone is unlocked. Update applied without issues.
Loving finally having the auto fill API.
Just checked my software updates for the first time in weeks and there it was! Unfortunately they're working on our electrical system, so I won't be able to download it until WiFi is back up, but it'll give me time to back things up.
Factory unlocked running on T-Mobile
Can anyone confirm if Hotspot remains functional after the update without carrier involvement.
Thanks
Aridon said:
Can anyone confirm if Hotspot remains functional after the update without carrier involvement.
Thanks
Click to expand...
Click to collapse
I used the hotspot yesterday at a clients and I also just switched carriers a few days ago and the hotspot worked fine. I did end up taking the OTA to Oreo.
I live in albania and no update, I have the unlocked firmware running in vodafone network. Currently im on BRB1? Any ideas why I dont have an update yet? Thanks
Can someone please confirm which bootloader is bundled with this update?
hazard666 said:
Can someone please confirm which bootloader is bundled with this update?
Click to expand...
Click to collapse
Bootloader 2
clownin72 said:
Bootloader 2
Click to expand...
Click to collapse
Awesome. Thanks!
There is an app in Google play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
My question is if I can use this software to update my op6t to beta or if I'll need to use a modified msmtool?
Been a while since I've been on here to read up on what's going on here at xda. Thank you in advance
If your phone is currently TMobile branded, use the msm tool.
Once you've converted, just use the local update feature within the ROM to update. You can go to beta that way, and update the betas.
This app isn't really needed and won't do anything that the local update feature in the ROM won't do.
hartleyshc said:
If your phone is currently TMobile branded, use the msm tool.
Once you've converted, just use the local update feature within the ROM to update. You can go to beta that way, and update the betas.
This app isn't really needed and won't do anything that the local update feature in the ROM won't do.
Click to expand...
Click to collapse
Yeah I converted it several months ago from Tmo to op stock. Just wasn't sure if it would cause an issue with my OP6T going this route. Thank you for the info, I appreciate it
I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.
bigmikey307 said:
I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.
Click to expand...
Click to collapse
Yes, T-Mobile is excluded from this beta until now. We found a way to flash the ROM but it has some issues that need to be fixed.
bigmikey307 said:
I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.
Click to expand...
Click to collapse
For what it's worth, Android 10 Beta showed up via OTA on my TMobile 6T running international ROM. Was excited and installed it...same result as for you...won't boot and shows the same message.
OTA's have never worked, just fyi.
Dark Nightmare said:
OTA's have never worked, just fyi.
Click to expand...
Click to collapse
I have had no problem with OTA's on my tmobile 6t running the international beta. I have taken 6-8 of them with no issues.
I've gone from each beta to 17 since i switched to international with no issues. Android 10 does partitions different amongst other things and that's why it doesn't work via OTA.
Scott said:
Yes, T-Mobile is excluded from this beta until now. We found a way to flash the ROM but it has some issues that need to be fixed.
Click to expand...
Click to collapse
Could you post a link to how we can flash the ROM?
Dark Nightmare said:
OTA's have never worked, just fyi.
Click to expand...
Click to collapse
They've always worked for me, you must've not read the original post. And I just received the Android 10 OTA but I'm not gonna install it bc apparently it'll still brick the phone.
bigmikey307 said:
They've always worked for me, you must've not read the original post. And I just received the Android 10 OTA but I'm not gonna install it bc apparently it'll still brick the phone.
Click to expand...
Click to collapse
Same here. All Android 9 OTA updates worked fine for me. That's why I didn't really think twice to hit INSTALL when the Android 10 OTA showed up. I was on the BETA channel, btw, which I am sure you are too.
The notification is driving me crazy.
You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.
GeorgeSRL said:
You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.
Click to expand...
Click to collapse
You can by using the fastboot OB1 mentioned here in these forums, but it's still far from stable. Best to wait for the stable Android 10 from OnePlus. It may be another month though before we see it.
Sent from my ONEPLUS A6013 using Tapatalk
GeorgeSRL said:
You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.
Click to expand...
Click to collapse
No OTA? Oh ok..
Don't install the OTA of you're TMobile, as everyone has said, it will soft brick your device
Fortunately I have the Oneplus 6T International Purple variant. I wanted to be able to use 2 SIMS just in case I need a phone for work I'll just install a second SIM.
So, I have a T-Mobile branded 6t. I was running Havoc OS 2.9 Pie. My device is full unlocked(bootloader AND sim). I decided I wanted to wipe everything and msm back to stock then go to OOS and then back to Havoc 2.9 Pie. I've done this so many times its easy lol. But the weird this is, I had something unexpected happen. After I msm to OOS, I did a local update as usual to the last version of Pie. After everything was successful, before I flashed twrp, I got a notification that OOS 10 was ready to install. Not a scam/virus/malware. My question is this, what would have happened if I upgraded to Over the air update instead of local? Remember, I have a T-Mobile branded 6t
jamescable said:
So, I have a T-Mobile branded 6t. I was running Havoc OS 2.9 Pie. My device is full unlocked(bootloader AND sim). I decided I wanted to wipe everything and msm back to stock then go to OOS and then back to Havoc 2.9 Pie. I've done this so many times its easy lol. But the weird this is, I had something unexpected happen. After I msm to OOS, I did a local update as usual to the last version of Pie. After everything was successful, before I flashed twrp, I got a notification that OOS 10 was ready to install. Not a scam/virus/malware. My question is this, what would have happened if I upgraded to Over the air update instead of local? Remember, I have a T-Mobile branded 6t
Click to expand...
Click to collapse
So are you unlocked or locked? Are you on 9.0.15?
I'm on 9.0.17 and got the update
gs2jb4.1.1 said:
I'm on 9.0.17 and got the update
Click to expand...
Click to collapse
So you are on International
PapaMag said:
So you are on International
Click to expand...
Click to collapse
yeah I'm on the international rom, but debating if I should update cause the play store not being certified.
gs2jb4.1.1 said:
yeah I'm on the international rom, but debating if I should update cause the play store not being certified.
Click to expand...
Click to collapse
Yeah I have been back and forth because of this issue but really like the dark theme option Android 10 has. Wish T-Mobile would hurry up I would just go stock.
PapaMag said:
Yeah I have been back and forth because of this issue but really like the dark theme option Android 10 has. Wish T-Mobile would hurry up I would just go stock.
Click to expand...
Click to collapse
Nobody is answering my question lol. My phone is T-Mobile branded, so will the OOS 10 update work? Normally we can't get an update notification because its branded and not from Oneplus, so how was I able to get this notification?
I read earlier this month that someone had tried to ota the way you're asking about and it didn't work. From what I remember they had to msm back.
I've been on 9.0.17 with 0 issues and got the update notice yesterday. I DLed the full update available here and did the local upgrade following the instructions in the ultimate guide. It went ok. My only issues are ctsProfile false and the Play store not certified. I would have rather stayed on 9.0.17. I'm not sure what those issues would mean for you going to Havoc.
jamescable said:
Nobody is answering my question lol. My phone is T-Mobile branded, so will the OOS 10 update work? Normally we can't get an update notification because its branded and not from Oneplus, so how was I able to get this notification?
Click to expand...
Click to collapse
The only time I have received a update notification after converting is through Oxygen Updater