Database Users

Questions About the Dev Editon VZW S5

I was thinking of going ahead an ordering the Dev S5, but how easy is it to root a dev edition phone.
I've never owned a dev edition phone, so would it be as simple as downloading something from the app store or adb fastboot a custom recovery, then flash a root zip? Also is the bootloader already unlocked or do they just make it where you can unlock it, but it still comes locked at first? I'm just trying to figure out what the steps would be when the phone arrives to get it rooted.
Does the anyone know if Asurion would cover the phone? When you activate it, does it just show up as a Galaxy S5 or something different?
Also for anyone wanting to buy the Dev S5, you can just sell your normal S5 on ebay, and the get the Dev S5 for like $50 more, at least that's what I did.

clemson91 said:
I was thinking of going ahead an ordering the Dev S5, but how easy is it to root a dev edition phone.
I've never owned a dev edition phone, so would it be as simple as downloading something from the app store or adb fastboot a custom recovery, then flash a root zip? Also is the bootloader already unlocked or do they just make it where you can unlock it, but it still comes locked at first? I'm just trying to figure out what the steps would be when the phone arrives to get it rooted.
Does the anyone know if Asurion would cover the phone? When you activate it, does it just show up as a Galaxy S5 or something different?
Also for anyone wanting to buy the Dev S5, you can just sell your normal S5 on ebay, and the get the Dev S5 for like $50 more, at least that's what I did.
Click to expand...
Click to collapse
Root is easy as it comes already bootloader unlocked. It is unlocked at the factory. To root, basically flash Odin image of a supported custom recovery (you can try Philz Touch recovery - as long as it supports the S5) or download an app from the play store which can flash a custom recovery as long as the S5 is supported. Then reboot into your Custom recovery and flash this zip: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Bingo, you are now rooted!!!
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!! There are no official ODIN images available for the DevS4 or DevS5 - all images have come from the community. We have rooted our devices and backed up the partitions in case something goes wrong and we need to recover. Again, back up system, cache, radio, modem, aboot, recovery, etc etc etc....all!

Request: Once the Developer Editions are in hand and rooted. Would someone be willing to dd all of the partitions and host them? I have a DevS4 and being that I will never see an update to KitKat, I would be interested in seeing if I can upgrade using the partitions from the DevS5 (all but ABOOT).

[Q] not sure if root worked right. can install eclipse, but not cm12

Hello all, I come asking for help. I recently had an issue with my note 3. I tried to update my twrp with the twrp manager, I had safestrap 3.75 and then used the twrp manager to try and flash the new 3.8.4.0 twrp, but after it flashed I went to recovery and tried to install cm12 but kept getting the error "this build is for hltevzw, you have a ." When trying to install. So I went full stock, flashed the new stock stuff via odin. Then rerooted with towelroot, installed superSU, then the safestrap 3.75. Now I can get to safestrap recovery, but if I try to install cm12, I will follow directions, flash rom, flash gapps, then I've tried flashing superSU as some have suggested, and tried not flashing superSU, but then my phone reboots, goes past the splash screen showing the unlock and says custom, sits at a black screen for a while, then reboots. Only when it reboots, at the splash screen it says loafing recovery in red at the top, then I get a screen saying that custom software has been detected and I need to take the phone in to Verizon or something like that. The only way to get out of it is to shut down, boot into download, and then hit volume down to cancel. It just keeps doing that same thing over and over. I was able to get eclipse rom installed, but cm12 always does the same thing. I've also gone into the safestrap 3.75 recovery and flashed the twrp 3.8.4.0, it says it was successful, but then I'll reboot, get to the safestrap screen, hit recovery, and it is still the older one with safestrap 3.75, not the updated one I just flashed. If I try to shut down my phone and power on using volume up, home, and power, I get the stock recovery saying that it has detected custom software and blah blah blah. So, I have a bunch of problems and honestly I am not sure what is going on. I have scoured the Web for 3 days now trying to find instructions on updating the recovery, every single one is the same as I described above with the same outcome. I've also been searching for how to install cm12, with the same results. Can anyone help me, I am so annoyed, lost, confused, and just.... please help. Thank you.
Tldr; recovery stuck on safestrap 3.75 regardless of flashing the newer twrp 3.8.4.0, and when trying to reboot into recovery using volume up, home, and power, I get the stock recovery with a message saying custom software detected. Please help.... please. I am on hltevzw with nc4. Rooted with towelroot, and safestrap 3.75.

you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...

mirrin said:
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
Click to expand...
Click to collapse
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.

danwguy said:
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
Click to expand...
Click to collapse
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...

mirrin said:
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
Click to expand...
Click to collapse
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.

danwguy said:
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
Click to expand...
Click to collapse
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk

donc113 said:
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
They exist in different areas of memory safe strap essentially hijacks the boot process before the phone can boot and tells it to instead boot this way if you want to update the version of twrp it us using you need to update safestrap it is what is holding us back from 4.4.4 and it will be what slows 5.0 unless someone updates safestrap or comes up with something new. All I know is I'm going to get a nexus next time I'm done with this locked bootloader bull****.

Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?

danwguy said:
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
Click to expand...
Click to collapse
Not necessarily the developers working on jasmine have been claiming to be working on a replacement for safestrap.
Verizon will eventually push out 5.0 but I doubt it will be anytime soon even then if I don't have root I don't want so I am not sure what I'll end up doing I'll try to wait it out maybe a mistake will happen and 5.0 will have some thing that leads to a bl unlock. If only they would make root an option like the dev menu...
and my prediction for when verizon will put out 5.0 I would say October is not out of range. Also it will likely be the note 3's last update that Verizon gives.

NO OEM unlocking with S off

I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.

anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.

Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.

anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.

Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve

anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.

OK will give that a shot tomorrow thanks

If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.

Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.

anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.

no oem unlock area in the dev tab

hello all,
im currently working on a samsung S4 (GT-I9515) and i ran into a small problem.
i have rooted phones more then ones and i know the drill more or less.
but when i tried to sellect the unlock oem option in the dev options it was not there.
normally it is located under bluetooth HCI-snooplog and above Process stats but the oem unlock option seems to be non existing on this phone
can someone tell me whats wrong or is it not needed ? Because i did get a message when i tried to install something trough the default recovery menu that the system was still locked. (also it runs android 5.0.1(lolipop))
Best regards,
Darkdevel

You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.

Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
true i also tried using twrp but when in boot twrp i cant swipe/select anything of the first screen do you have another idea what i can use ?

What are you trying to unlock with "unlock OEM option"?

audit13 said:
What are you trying to unlock with "unlock OEM option"?
Click to expand...
Click to collapse
well as far as i know i need it so i can try to flash a new android version on it im trying force 6.0 on it and yes i know there is no S4 (i9515) android 6.0 version but i still want to try and do it its a old phone anyway

ppl you can forget about this post i found the problem more or less first off i had the wrong twrp version that caused the bug on twrp afterward it was all smooth sailing
for all the other ppl who want a non official android 6.0
go to youtube and look for:
install Android 6.0.1 Marshmallow Galaxy S4 GT-I9515
posted by ما لا تعلم ?
all the files you need are in the discription
Best regards,
Darkdevel

Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.

FurySh0ck said:
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
Click to expand...
Click to collapse
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.

Pwnycorn said:
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Click to expand...
Click to collapse
It's very strange then. When I had a root (same device gt-i9515 for SURE), I managed to flash TWRP on my first try, no mistakes.
I recently flashed a firmware (from sammobile. I9515XXU1BOE3_I9515DBT1BOE1_DBT, because my PDA is i9515xxu1boe3) and wiped everything. It's like a new device now.
In it's current state (non-root) I couldn't install TWRP via the same method I did before (ODIN + TWRP.tar).
About the comment on the other thread, yes, I am sure it's gt-i9515 and I know that if the USB is getting disconnected, ODIN writes it on screen, so I could see it.
Here's the guide that told me about OEM: http://www.theandroidsoul.com/how-to...ry-using-odin/ (I understand that it's a trash guide lol)
Update:
I finally did it, explained here: https://forum.xda-developers.com/ga...p-cr-galaxy-s4-gt-i9515-t3668461#post73680660
Thanks for your help!

[SM-G950W] Running official Android 9 on Samsung S8, help me understand my options (root, custom ROM)

Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!

temuri said:
Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
Click to expand...
Click to collapse
Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
temuri said:
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
Click to expand...
Click to collapse
Depends on the binary version, the screen text in Download Mode should tell you. You can't downgrade the binary, so if it changed from 3 to 4 (for example) and is currently on 4, you can only flash binary 4 firmware, but you can't downgrade to 3.
temuri said:
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!
Click to expand...
Click to collapse
I'll try to put this simply:
Enable OEM unlocking in developer options
Unlock bootloader (wipes data)
Boot device, set up Google/Samsung account, connect to the Internet
Perform a manual update check, do not download update
Check to ensure OEM Unlocking is still visible
Put device in download mode and flash TWRP; immediately boot TWRP, do not allow device to reboot into system, otherwise it will restore the stock recovery
Make sure you flash the Multidisabler in TWRP to disable encryption and recovery restoration
Flash Magisk in TWRP to gain root
Boot into system and set up device, install the Magisk app to manage root.

I would leave it on Pie. Anything below that has nasty vulnerabilities like X helper.
If you want more performance optimize it with Package Disabler or adb edits.
If that doesn't get it, get a N10+, a huge performance and cam increase.
How to read Samsung build numbers

@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
I heard that Extreme Syndicate for S9 series may seem nice. (OUDATED THOUGH TAKE EVERYTHING NOT FOR THE FAINT OF HEART.)

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
Click to expand...
Click to collapse
Are you saying it can't be unlocked? Or simply that it is not unlocked?
The bootloader unlock has nothing to do with the Android version. Whether you can unlock it might though.
temuri said:
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
Blackhawk is a cranky old curmodgeon, don't listen to him. Totally kidding, he's a smart guy.
So let's focus on Step 1. Enable Developer Options, do you see the OEM Unlocking toggle?

@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.

temuri said:
@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.
Click to expand...
Click to collapse
Your device is set up, you have a Google account added, and you're connected to the Internet?

V0latyle said:
Your device is set up, you have a Google account added, and you're connected to the Internet?
Click to expand...
Click to collapse
that's correct.

temuri said:
that's correct.
Click to expand...
Click to collapse
Okay. Current firmware version?
Settings > About phone > Software information

Baseband version: G950WVLU8CUF3

temuri said:
Baseband version: G950WVLU8CUF3
Click to expand...
Click to collapse
Okay, so you're on the latest update. See if you can download and flash CSL1
If that works try AQD9
Next time you're in download mode, either take a picture of your screen or post what it says for SW REV or RP REV

consider downloaded - 6min left.

should I use standard ODIN to flash it?

Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh92 for US/Canada Samsung BL unlocking

webhook said:
Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh62 for US/Canada Samsung BL unlocking
Click to expand...
Click to collapse
uh-oh... can you please explain the "low bit" part and how do I check it?

@V0latyle
An attempt to flash CSL1 failed with:
FAIL! (Auth)
Complete(Write) operation failed

Disregard message

ouchies. was too quick and contacted the guy already

temuri said:
ouchies. was too quick and contacted the guy already
Click to expand...
Click to collapse
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected] Before Starting...
forum.xda-developers.com
I've tried this with my T-Mobile US GS8+. Works like a charm. Since you are on Bit 8 the stuff there is compatible with your phone. However you may brick stuff so be careful
You can join their Telegram chat for more information.