Develop Bugs

Any Updates on Unlock for 4.4.2

Are there any updates on an unlock method for 3.11.605.1? I'm having a pretty serious problem with streaming Internet Radio apps cutting out with the screen off after about 5 minutes. The app Data Connection Fix has helped out a lot, but I wanted to try out other ROMs to see if I can find 1 without this issue. It's such a shame that I'm having this issue because the HTC One seems like such a great phone. Unfortunately, streaming Internet Radio at work is the main thing that I use my phone for and my older Droid X2 on 3g outperforms this phone in that aspect. It's so sad a newer 4g device has this issue and makes me wonder if I should ever mess with another HTC device or Android device period. I wanted to get away from iOS, but I'm finding that almost every Android device I've been using needs to be unlocked/rooted to fix really simple features that should work right out of the box and with every update. The Bluetooth A2DP quality problem with most JellyBean devices has been a nightmare. That's what made me ditch my LG G2. I tried just about every custom ROM and music through bluetooth was horrible no matter what I tried, even on the newer KitKat ROMs.

pda48428 said:
Are there any updates on an unlock method for 3.11.605.1? I'm having a pretty serious problem with streaming Internet Radio apps cutting out with the screen off after about 5 minutes. The app Data Connection Fix has helped out a lot, but I wanted to try out other ROMs to see if I can find 1 without this issue. It's such a shame that I'm having this issue because the HTC One seems like such a great phone. Unfortunately, streaming Internet Radio at work is the main thing that I use my phone for and my older Droid X2 on 3g outperforms this phone in that aspect. It's so sad a newer 4g device has this issue and makes me wonder if I should ever mess with another HTC device or Android device period. I wanted to get away from iOS, but I'm finding that almost every Android device I've been using needs to be unlocked/rooted to fix really simple features that should work right out of the box and with every update. The Bluetooth A2DP quality problem with most JellyBean devices has been a nightmare. That's what made me ditch my LG G2. I tried just about every custom ROM and music through bluetooth was horrible no matter what I tried, even on the newer KitKat ROMs.
Click to expand...
Click to collapse
I'm pretty sure there's just a setting you're missing that keeps the radio from cutting out. I used to stream Sirius XM and had the problem but I remember getting it fixed somehow. If I think of it I'll let you know. And no, you can't gain s-off on 4.4.2. If you read at all on here, you'll know when you can.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
I'm pretty sure there's just a setting you're missing that keeps the radio from cutting out. I used to stream Sirius XM and had the problem but I remember getting it fixed somehow. If I think of it I'll let you know. And no, you can't gain s-off on 4.4.2. If you read at all on here, you'll know when you can.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Could you please tell me what setting? I get great service where I work and haven't had a problem with any other phone. I even went to Verizon and got a new SIM card. I've tried everything, starting with factory resets and clearing the cache. I have sleep mode off, app data sync on, mobile data is not restricted or limited, I've tried with and without beats audio enabled. The audio cuts out about every 5 minutes for 5-10 seconds and comes back on, just to cut out again for 5-10 seconds every 5 or so minutes. It's very annoying. The only thing that really helps is the data connection fix app, but that's not 100% reliable. I even called HTC and Verizon about the issue and they are looking into it. I would have normally just tried a different ROM, but I'm unable to unlock/s-off/root my phone because I'm on 4.4.2(3.11.605.1). That's the only reason I even called them. I currently have my phone up for sale and I'm seriously thinking about switching my service to sprint. I'm tired of paying top dollar for used phones to keep my unlimited data on Verizon. For all I know, there could be a problem with the phone, but it seems like a software issue to me. Everything else works and runs great. It's just that streaming Internet Radio is the thing I use most.

Have you tried this?
http://androidforums.com/htc-one/732481-beats-audio-setting-interrupts-streaming-audio.html

https://twitter.com/TeamAndIRC/status/443850349678321664
Sent from my HTC6500LVW using Tapatalk

BhRaElEfD said:
Have you tried this?
Yes I've tried. It has nothing to do with beats audio. For some reason it just drops the data connection for like 5-10 seconds with the screen off every 5 minutes or so. I don't know if it's incompatible apps with 4.4.2 or 4.4.2 itself. It could also have something to do with the HTC sense software. It could just be the way this phone communicates with the Verizon towers. I have no idea and it's very frustrating. The last time I had a problem similar to this was when I had an LG Optimus V on Virgin Mobile and it would lose 3g and I would have to turn off the data connection and turn it back on. This is different, though, because I have 4G LTE all the time. There just seems to be a delay in receiving my data to where the Internet Radio cuts out before it signals for more data. Then by the time I receive more data, it's too late and the sound has already cut out. I did a speed test and I'm getting about 30mbps download and around 15mbps upload so I know I'm not being throttled. The only thing that helps is the data connection fix app.
Click to expand...
Click to collapse

I did some more testing and I don't have any issues on WiFi and I don't have any issues if the screen stays on. It's only on cellular data with the screen off when I'm having issues. I noticed the Power Saving feature was removed in 4.4.2 and instead there's a sleep mode option. I have the sleep mode option off, but I'm thinking my issue might be because of a power saving bug in the HTC software for 4.4.2. If anybody knows anything about this, please post. Thanks

Think it will ever be unlocked?
I would SO much love to have airplay enabled on my HTC One. I came from iPhone, and have a full home surround sound based on Airplay, which I now can't use. Airplay is available only through a root application, although i have my phone on 4.4.2. Any thoughts on if and when this will ever be unlocked? Otherwise it's a huge reason for me to not have this phone...

BBooch said:
I would SO much love to have airplay enabled on my HTC One. I came from iPhone, and have a full home surround sound based on Airplay, which I now can't use. Airplay is available only through a root application, although i have my phone on 4.4.2. Any thoughts on if and when this will ever be unlocked? Otherwise it's a huge reason for me to not have this phone...
Click to expand...
Click to collapse
Well it took beaups and crew about 1 month + to get 4.3 unlocked. Plus it seems more devs are having issues with 4.4.2 so it could be longer. At this point hope for the best and expect the worse.

I seriously don't know why all of these companies continue to try and lock out everyone's phones (and spend unnecessary money doing so) when someone will just outwit them almost every time. If a dev REALLY wanted this done right away it would be done! Point blank... It's a cat n mouse game and Verizon will lose. I just purchased an HTC One on 4.4.2 and have full faith that it will be cracked wide open anytime now. No one can stop somebody that is determined and smarter than the person who created the bottleneck. Here's hoping to a quick S-off method soon :victory:

shojus said:
I seriously don't know why all of these companies continue to try and lock out everyone's phones (and spend unnecessary money doing so) when someone will just outwit them almost every time. If a dev REALLY wanted this done right away it would be done! Point blank... It's a cat n mouse game and Verizon will lose. I just purchased an HTC One on 4.4.2 and have full faith that it will be cracked wide open anytime now. No one can stop somebody that is determined and smarter than the person who created the bottleneck. Here's hoping to a quick S-off method soon :victory:
Click to expand...
Click to collapse
It's not unnecessary money to them honestly. In Samsung's case they are trying to prove that their devices are secure enough to use for government agencies. Do you think they care that a few rogue hackers find exploits from time to time? No, they just need to convince some corporate goon that his e-mails to his mistress won't get intercepted. Speaking of the S4, it's been locked down now for about 8 months so I'd say they're getting pretty damn good at it. They have root I believe, but the bootloader is locked down tight on every S4 other than the very first firmware that came with the phone. I'm not sure what HTC's motivations are but I'm guessing they need to play ball with companies like Verizon in order to be able to sell their devices in the future.
Another thing that is hurting us is that Android itself is getting more secure. They are adding features that prevent exploits so it makes it harder for your average dev to find a way in. In the future we may be forced to buy developer editions to be able to do anything. That's worse case, but you never know.
Just like you I had "faith" that a developer would crack the S4 and I could finally have freedom. It never happened. It still hasn't happened. That's the main reason I switched to HTC. I'm not saying you should give up hope, but if you can't stand a phone to be locked down you should be looking into buying a different phone just in case...

Crawshayi said:
It's not unnecessary money to them honestly. In Samsung's case they are trying to prove that their devices are secure enough to use for government agencies. Do you think they care that a few rogue hackers find exploits from time to time? No, they just need to convince some corporate goon that his e-mails to his mistress won't get intercepted. Speaking of the S4, it's been locked down now for about 8 months so I'd say they're getting pretty damn good at it. They have root I believe, but the bootloader is locked down tight on every S4 other than the very first firmware that came with the phone. I'm not sure what HTC's motivations are but I'm guessing they need to play ball with companies like Verizon in order to be able to sell their devices in the future.
Another thing that is hurting us is that Android itself is getting more secure. They are adding features that prevent exploits so it makes it harder for your average dev to find a way in. In the future we may be forced to buy developer editions to be able to do anything. That's worse case, but you never know.
Just like you I had "faith" that a developer would crack the S4 and I could finally have freedom. It never happened. It still hasn't happened. That's the main reason I switched to HTC. I'm not saying you should give up hope, but if you can't stand a phone to be locked down you should be looking into buying a different phone just in case...
Click to expand...
Click to collapse
Valid points! That's why I said "almost every time"... I really just need root and I would be happy but I switch devices so much that I probably won't even have the One (my 3rd HTC One) by the time it gets exploited (if) it does. And I do understand that Google has to close a lot of security holes so that they don't look like they are such a terrible company by allowing all of these terrible "viruses" into our phones which I have never had any issues with. I do agree with you though that we will probably all be buying dev phones sooner than later. Thanks for the insight!

Just another reason to leave Verizon and go get a Nexus device.

For thouse, who run stock 5.0.x-5.1.x, why to risk the device?

I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk

The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.

5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.

OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?

I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.

donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.

^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.

I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.

Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...

I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk

donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.

Android phone choice - no auto or forced updates

I hope this is the best place to ask this question since it's largely concerned with "upgrading".
Earlier this year I'd had enough of my Apple iPhone and its endless buggy updates which the phone would railroad you into installing and had no way to disable that. I elected to go for an Android phone. After spending a while looking I went for a Samsung Galaxy S8 which came with Android 7 and was literally flawless, the first such phone I'd had since iOS 8.6. Hurrah
However the phone has a major fault confirmed by the manufacturer. One key thing I checked was that I wouldn't be in the same position as with Apple, forced into installing updates. I am actually a software developer and one with a very limited tolerance of buggy things. I also understood that with Android you can't undo updates without invalidating the warranty. I have no problem with being informed they're available. Once. I can then review whether I want to risk it or not. I don't want to risk Oreo since there are plenty of reports of reduced battery life among other things and it brings nothing new of any significance and once it's on there it can't be taken off again.
So I checked the features and menus on the S8 before I bought it and went ahead.
This phone was great for about 3 months until the Oreo update was released. At which point the device began nagging. There are various settings which should, among other things, stop it downloading updates automatically and a developer mode option that should stop it updating. However as confirmed by Samsung these options simply do not work, it is a defect out-of-the-box and they are ignored. The phone will do what it wants not what you want.
So I'm now back where I was with Apple albeit the device is otherwise bug-free and superb. I have an uncancellable dialog box coming up repeatedly trying to railroad me into installing the Oreo update it should not have downloaded anyway. This is destroying what was a superb device. I've expended ages resetting it already. There aren't enough hours in the day. Android 7 is great. It isn't my primary device, that being my PC. I just want something that runs a few apps and checks email and that's about all. I don't want a "Samsung Experience"
Samsung refuse to fix this, but as they've confirmed it's a fault I can get a refund from the retailer now. However I still need a phone. My question is:
Is it absolutely necessary to invalidate the warranty on a brand new phone out-of-the-box to stop this behaviour since they're all like it? (e.g. "rooting" is the only option)
Or, does anyone know more than Samsung do about their phones and can advise how the phone can be repaired by me (have done factory reset, denied internet, set not to update etc., as Samsung confirm, this part is broken and doesn't work). I could for instance block Samsung's IPs if I knew what they were but that will only work on WiFi here, not on mobile data. As I understand it the package that needs disabling is called "Software Update" but that isn't possible (again without invalidating the warranty which I'd rather not do since it's almost new).
I know how to scupper Microsoft's Windows Updates but that's because that's what I work with and I know the OS quite well and what they're up to. But I don't know how the Android OS works nor should I need to, really. Another reason for my reluctance to forcibly replace the OS.
Don't mind a pop-up box informing me updates are available with a button "Do Not Install" coming up when the update is released. What I don't want is what this phone and Apple phones do which is to suggest they know better than you do and eventually force you into installing them.
Or, which Android phones behave properly and don't have this sort of fault? That respect the user's settings and do not do whatever they like? I'll need to choose a new one anyway so this would be really useful.
Thanks for reading all that

No wifi calling because my phone is from Verizon?

I am having an issue where my phone cannot do Wifi calling, or Samsung Visual Voicemail. So I did some digging and found out that my gf's phone (which I flashed unlocked U1 firmware on) now has the service provider software information (SPS) of AIO/AIO/XAA, even though when I got her phone, it was designated to T-Mobile. However, for MY phone, even though I used the same exact firmware flash, my SPS is VZW/VZW/VZW.
Could this be the cause of my issue? Is there anyway to fix this? I flashed the phone using this firmware: https://samfw.com/firmware/SM-G986U1/XAA/G986U1UES2DUD4
I will provide more info if anyone asks for it, I just don't know what other info to provide as of now.

Here is one thing I know for certain, Verizon's Wifi calling uses an IPSEC tunnel that connects to them when turned on from your phone.
From this we can possibly assume that wifi calling is carrier specific. I am sure voicemail is the same.
So if your phone is technically on one carrier but the firmware thinks it's another, it would be mismatched so to speak.
I know this does not solve your issue but it might explain why those things do not work.

DarkQuark said:
Here is one thing I know for certain, Verizon's Wifi calling uses an IPSEC tunnel that connects to them when turned on from your phone.
From this we can possibly assume that wifi calling is carrier specific. I am sure voicemail is the same.
So if your phone is technically on one carrier but the firmware thinks it's another, it would be mismatched so to speak.
I know this does not solve your issue but it might explain why those things do not work.
Click to expand...
Click to collapse
Right, I figured it would be something like that. The problem, at least I think, is that the phone still thinks it's a Verizon phone, even though it has U1 firmware. I tried flashing the firmware again, and putting in the SIM after I factory reset it, and nothing changed. I truly do need to change the SPS. I'm not sure if that's possible, but hopefully someone can shed more light on this problem.

guyguyguy1 said:
Right, I figured it would be something like that. The problem, at least I think, is that the phone still thinks it's a Verizon phone, even though it has U1 firmware. I tried flashing the firmware again, and putting in the SIM after I factory reset it, and nothing changed. I truly do need to change the SPS. I'm not sure if that's possible, but hopefully someone can shed more light on this problem.
Click to expand...
Click to collapse
Here is just my 2 cents on it. For years I used to buy unlocked phones specifically so I could put custom firmwares on them. I had 3 reasons for doing so at the time. Get rid of the trash, custom firmwares were often updated more frequently and longer than manufacturer "official", and for root.
As it sits today, root is handy but not required like it used to be. Manufacturers now update their firmware FAR better and there are ways to debloat an official phone.
What I am getting at is this. Dinking with the firmware (IE changing away from official) is not worth it in my opinion today for most folks. Especially if you really depend on your device,, as I do for work.
However with all that said, if I did not depend on mine for work I would customize it anyway because while the processes for doing so are tedious, I find them fun.
Just my take on it. I wish you luck with your issue.

DarkQuark said:
Here is just my 2 cents on it. For years I used to buy unlocked phones specifically so I could put custom firmwares on them. I had 3 reasons for doing so at the time. Get rid of the trash, custom firmwares were often updated more frequently and longer than manufacturer "official", and for root.
As it sits today, root is handy but not required like it used to be. Manufacturers now update their firmware FAR better and there are ways to debloat an official phone.
What I am getting at is this. Dinking with the firmware (IE changing away from official) is not worth it in my opinion today for most folks. Especially if you really depend on your device,, as I do for work.
However with all that said, if I did not depend on mine for work I would customize it anyway because while the processes for doing so are tedious, I find them fun.
Just my take on it. I wish you luck with your issue.
Click to expand...
Click to collapse
Thank you! My understanding is that if your phone is protected by Knox, if you root the phone, it would break the chip on the logic board, and it would either brick the phone, or totally disable all protections on the phone, so you would HAVE to do custom firmware and security. Which simply isn't worth it to me. I just think it's annoying that a phone that SHOULD have the built in compatibility, just simply doesn't because the company that commissioned the phone felt like being a ****. Worst case scenario, I just suck it up and deal with it, it's not a huge deal. But, if someone eventually comes along and offers a fix for it, I'll jump on it!

S9 help needed

So, this is a friend's phone...
I know, whenever I hear someone say that I think to myself "sure buddy". But seriously, it's true, this is not my phone but I have taken on the task of repairing it. My personal phone is actually a Pixel 2 XL, which I chose so I would never have to deal with a phone that had a locked bootloader or a strict root policy; forcing me to scour through forums for solutions to problems that are created by the cell phone manufacturers and carriers.
Moving along, my friend's phone is a Tmobile Galaxy S9 (g960usqs6csgb) (SM-G960U)
I believe it has the Snapdragon CPU (qualcomm and qual was littered all over the bootloader logs) but I don't know what Android version it's on. Because I can't get past the initial setup screens... because, you guessed it, the device was factory reset and now it's locked because he doesn't have the previous owner's google account credentials and it won't allow further progress. A message is displayed at the wifi setup screen stating as much, and at this point the unit is entirely useless.
When I first saw him with the phone in hand, wrestling to get it to work, I proclaimed "I can fix it!! Not to worry!! After all, I used to root and ROM and ADB with the best of 'em !! Going back to the early days of android, cracking open the incredible, galaxy nexus, HTC 9, nexus 5, note 5, etc etc. My Pixel 2 XL was the first phone I didn't root, simply because it already had all the features I wanted, right out of the box! But this phone wasn't cooperating like the old devices. Apparently the carriers and manufacturers have incorporated new ways to deter nefarious activities and squeeze out every bit of money from us hapless technology addicts.
I digress. Is there any way to get past this? I've already downloaded Odin 3 and I believe I'm hot on the trail of this model's firmware:
https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960U/TMB/download/G960USQS6CSGB/283293/
But is this even possible? Will rooting and flashing a new ROM remove the unauthorized factory reset lockdown? Will the device even let me get that far? I don't know anything about rooting the S9 but it's all here in the forums, I just wanted to know if there's anything I should be aware of in advance. I'm not too concerned with bootlooping/bricking or losing google pay or something similar because it's basically a paperweight already. But if there's a way to do this properly, I certainly don't want to mess it up irreparably by charging headlong into the fire when I might patiently tiptoe and emerge unscathed instead. I appreciate any help you might offer.
Thanks!!

Yikes, not a single reply.
No one's gonna touch this one, a?
At least I got a like. Thank you to the brave individual willing to sit back and watch the trainwreck go its course.
TLDR: Can I get past the Google lockout on a TMobile s9? Is it possible to unlock, root, and flash a ROM on an otherwise locked s9?

If your stuck on FRP lock then maybe this thread may help.
[CLOSED]S21+ (GM-996B) FRP Bypass
Hello everybody, I hope it fits in here. I forgot the pattern on my S21 + after resetting the phone, my phone still wanted the pattern or a Google account. He doesn't take my Google account and after a long back and forth with the Samsung...
forum.xda-developers.com

spawnlives said:
If your stuck on FRP lock then maybe this thread may help.
[CLOSED]S21+ (GM-996B) FRP Bypass
Hello everybody, I hope it fits in here. I forgot the pattern on my S21 + after resetting the phone, my phone still wanted the pattern or a Google account. He doesn't take my Google account and after a long back and forth with the Samsung...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much. Didn't even know what to call it so search wasn't very helpful.