Related
Hey forumers I'm a little new here so sorry if this is a huge noob question
Yesterday I bought a Sony Z5 outright from a local provider here in Canada and I had gotten it unlocked and such but it doesn't seem like I'm able to find my local WIND network.. after some research i found that this phone might not be compatible at all
I had gotten a couple hints that maybe if I root I can unlock the band or something... I don't know.. if anyone knows what I can do please let me know.. I rather like this phone aha
TLDR/ Looking for a way to get Sony Z5 Compatible with WIND
If you already unlocked the sim and it doesn't work then it doesn't work. Should have checked the network bands before purchasing. If you don't know you can ask one of the wind representative. Also, if I remember correctly you might need root or worst you need to unlock the bootloader (which you can't because it is from bell), to unlock the other bands. All I know is that unlocking bands require alot of coding and complicated procedures. Gl bud, return it if you can if it doesn't work out.
LitoNi said:
If you already unlocked the sim and it doesn't work then it doesn't work. Should have checked the network bands before purchasing. If you don't know you can ask one of the wind representative. Also, if I remember correctly you might need root or worst you need to unlock the bootloader (which you can't because it is from bell), to unlock the other bands. All I know is that unlocking bands require alot of coding and complicated procedures. Gl bud, return it if you can if it doesn't work out.
Click to expand...
Click to collapse
Is there a reason why BELL cannot unlock the bootloader? I've been doing a lot of research since I posted this thread (im becoming obsessed even as a noob) and I'll need to root the phone, install custom kernel/ROM and edit 6 values into the non volatile memory in order to gain access to add additional bands. The Chipset in the Z5 should in theory allow AWS bands..
Make sure your APN is correct before going through all that trouble. Unlocking bootloader on Sony phones renders some special features useless.
augie7107 said:
Make sure your APN is correct before going through all that trouble. Unlocking bootloader on Sony phones renders some special features useless.
Click to expand...
Click to collapse
Thank you!
I have triple checked the APN settings to be perfectly compatible with WIND and that is not the issue.
So pretty much either i lose out on features in order to root - unlock the radios
or I return it and somehow get the Z5 DUAL.
I really love this phone and can't think of any others to get if I return it and don't go for the dual lol.
GearshiftJB said:
Is there a reason why BELL cannot unlock the bootloader? I've been doing a lot of research since I posted this thread (im becoming obsessed even as a noob) and I'll need to root the phone, install custom kernel/ROM and edit 6 values into the non volatile memory in order to gain access to add additional bands. The Chipset in the Z5 should in theory allow AWS bands..
Click to expand...
Click to collapse
As far as I know, here in Canada when ever you get a phone from a carrier the bootloader is locked forever. Blame the carriers not sony. And from my years in XDA - sony in particular I don't think I have met a developer skilled enough to get the bootloader unlocked on non unlockable devices, maybe Samsung devices yea but not sony.
Installing custom roms and kernels would require you to unlock the bootloader which you can't do so with carrier phones. This is the down side when you get carrier phones. Always get international phones because they are not locked forever.
I have the international version so I don't know about the bell one. Go to dial pad and input *#*#service#*#*
From there navigate to service info / configuration. Under rooting status, if it states "yes" next to bootloader unlock allowed then you can unlock it if it states "no" then it means no
LitoNi said:
As far as I know, here in Canada when ever you get a phone from a carrier the bootloader is locked forever. Blame the carriers not sony. And from my years in XDA - sony in particular I don't think I have met a developer skilled enough to get the bootloader unlocked on non unlockable devices, maybe Samsung devices yea but not sony.
Installing custom roms and kernels would require you to unlock the bootloader which you can't do so with carrier phones. This is the down side when you get carrier phones. Always get international phones because they are not locked forever.
I have the international version so I don't know about the bell one. Go to dial pad and input *#*#service#*#*
From there navigate to service info / configuration. Under rooting status, if it states "yes" next to bootloader unlock allowed then you can unlock it if it states "no" then it means no
Click to expand...
Click to collapse
Thank you for that.
I went through the directions and the bootloader says no. Looks like I'm heading to return it later today as I'm not interested in losing out on features if I was to root etc...
dang, I feel like I was so close to, but after reading on everything for a few hours, I must hang up the towel. I will probably try and buy the Sony Z5 Dual in green now from Ebay (the color I wanted anyways)
Thanks everyone for the assistance even though we came up short!
GearshiftJB said:
Thank you for that.
I went through the directions and the bootloader says no. Looks like I'm heading to return it later today as I'm not interested in losing out on features if I was to root etc...
dang, I feel like I was so close to, but after reading on everything for a few hours, I must hang up the towel. I will probably try and buy the Sony Z5 Dual in green now from Ebay (the color I wanted anyways)
Thanks everyone for the assistance even though we came up short!
Click to expand...
Click to collapse
No worries, at least its not too late to return it. You can still root the device but just can't unlock the bootloader.
Just curious, how much did you pay in total for the phone outright?
LitoNi said:
No worries, at least its not too late to return it. You can still root the device but just can't unlock the bootloader.
Just curious, how much did you pay in total for the phone outright?
Click to expand...
Click to collapse
$649.99 + tax so $734.48 which I totally didn't mind, I was due for an upgrade and was able to sell off my previous phone...
I'm looking into the Z5 Dual and it's showing me $854 for it... on ebay at least http://www.ebay.ca/itm/Sony-Xperia-...903367?hash=item419df43c47:g:86QAAOSwo0JWF52C
that jump though..
GearshiftJB said:
Thank you!
I have triple checked the APN settings to be perfectly compatible with WIND and that is not the issue.
So pretty much either i lose out on features in order to root - unlock the radios
or I return it and somehow get the Z5 DUAL.
I really love this phone and can't think of any others to get if I return it and don't go for the dual lol.
Click to expand...
Click to collapse
That sucks, sorry you are having difficulty. As an FYI, I made multiple edits on a coupe Xiaomi Qualcomm devices with a NV editor and the changes stuck but it never enabled any additional bands. I see that neither model on the Z5 Compact is compatible with Wind on any band by plugging in values here:
http://www.willmyphonework.net/
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
hackel said:
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Click to expand...
Click to collapse
I can't answer the main part of the question, but you can skip adding a google account and still enable OEM unlock ability in dev options.
EDIT: regarding your edit, hackel, that is frustrating they make you "activate" it on a carrier or via google before allowing OEM unlock. Very Apple-ish.
hackel said:
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
Click to expand...
Click to collapse
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
dmbfan36_23 said:
[snip]
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Do you have confirmation of this? We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
dmbfan36_23 said:
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
Click to expand...
Click to collapse
Did you have your phone connected to the internet and/or have a SIM in it when you enabled OEM unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
efrant said:
Do you have confirmation of this. We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
Click to expand...
Click to collapse
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
dispatch said:
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
Click to expand...
Click to collapse
Where did they say that? Everything I've seen says it's not unlockable:
http://www.androidpolice.com/2016/10/04/confirmed-verizon-pixels-bootloader-will-not-unlockable/
All of the phones ship locked, but on non-Google versions the option to enable OEM unlocking remains greyed out.
All phones, including those sold by Vz, are carrier unlocked though.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
You're absolutely right. I must've read that the Verizon variant will be carrier unlocked and interpreted that as BL.
Still garbage that you have to phone home before the google variant will allow an OEM unlock.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
efrant said:
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Click to expand...
Click to collapse
Please let us know when you do especially if you're on Bell. Thanks!
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
Click to expand...
Click to collapse
Does anyone know for sure that the phones from best buy are locked and have a locked bootloader? I contacted best buy and they said the phones are locked but when I contacted Google support, they said those phones along with the Google store phones are unlocked with a unlocked bootloader. Don't know who to believe? I would like to buy the phone from best buy only if it's unlocked with a unlocked bootloader because the Google stores shipping and logistics are all screwed up. Ordered placed later are getting shipped before earlier orders. Not happy with Google.
Sent from my LGLS990 using Tapatalk
hackel said:
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
Click to expand...
Click to collapse
Hackel, you don't need to enter your google account info or insert your sim. Just connect to wifi and then go to developer settings to disable OEM unlock.
Source: Me cause I did it, duh
tjarvis said:
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
Click to expand...
Click to collapse
That's a no go, the VZW model has a different CID.
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
dbrohrer said:
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
Click to expand...
Click to collapse
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
Ok. That sounds correct. I nevered tried to unlock out of the box. I assumed it was the same as after the first boot.
Thanks for the clarification.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
It hinders someone from loading malware before the phone is booted. It also makes you clearly aware of the "risks".
Sent from my Pixel using XDA Labs
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Cares said:
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Click to expand...
Click to collapse
Well, there are other reasons for wanting to be able to unlock the bootloader without ever having booted into Android, so I wouldn't call this a complaint thread. For example, getting a complete backup of all the partitions in a (mostly) untouched condition (e.g., partitions like frp, persist, etc.).
Calling someone's question/observation a "dumbest complain thread" isn't really contributing to the discussion.
efrant
Senior Moderator
So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
About a year ago, I bought a Samsung Galaxy S7 from a 'rebuilder' (my term) who mentioned at the time "... it was ATT phone..", and, yes, when I turn it on it does the ATT circle jerk logo and has an ATT logo on the back of the phone. This was of no real concern to me, because my service purveyor uses the ATT system (Consumer Cellular), so it's worked well enough. But unfortunately, it also has a boatload of 'semi-proprietary' ATT trash in the phone which I'd like to get rid of. To confuse the matter even more, it appears that I cannot 'unlock' the phone because it has not been associated with an actual active ATT account for close to two years, and it APPEARS that now they refuse to accommodate an unlock code for this phone.
So... according to my friend (Mr. Android Phone), I can 'root' this phone to 'factory original firmware' and make it (in essence) just a plain-old-vanilla Samsung S7 without this rather bogus ATT firmware and the myriad of craplets I'd like to get rid of..
So, I'm here looking for "expertise" in such things because I certainly don't want to 'brick' this pretty nice phone, but I also want to get this to a point where there is no association with ATT in any manner. So my question sorta comes down to: "can I root this and be rid of all things ATT?", and "will this allow me to achieve an 'unlock' without having to play ATT's games? (I had QUITE the discussion with an ATT 'support' dude a couple of hours ago when he flatly refused to give me an unlock code so I could simply ATTEMPT to see if Consumer Cellular's T-Mobile service might work better at my home, since CC tells me I'm right in the center of a brand new rebuilt 4G service area).
Does any of this make any sense to anyone? Pardon my ignorance, but if the IMEI # is somehow 'tethered' to ATT and they won't "release" it, how does rooting help with this? - or is this something more like an 'association' of the IMEI # AND the ATT firmware...? GAH!! I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.
CentennialMan said:
So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.
Click to expand...
Click to collapse
Hi There that's a lot of words partner! I'll try make the answer easy to understand and I've cut out much of the post so my reply isn't huge.
1. Yes you can install vanilla firmware which will remove all branding from AT&T and you don't need to root the phone to do this. here is the firmware for your device >>here<< You can also use XAS or XAA. You will see the guide and the Odin you need to flash this firmware.
2. This is another version of Odin on this website if you have any issues with the one on Sammobile. >>here<<
3. Unfortunately you cannot unlock the phone unless the original cell phone provider gives you their half of the unlock key as a code to input to the phone. In the UK once a phone is out of the initial contract period it is illegal for the provider to refuse to give you this code whether your still with them or not. I know in the USA you guys gets ****ed over. The original account holder of the phone can ask for the unlock code but not you.
4. Changing the firmware and unlocking the phone to any network are two different things, flashing unbranded firmware will not unlock the phone the network is tied to. They don't make it that easy!
5. As far as i know T Mobile (USA) has also moved to G930U firmware so you could be lucky with a T Mobile SIM working once the phone is flashed with this firmware but don't hold your breath. Check Sammobile for the T Mobile firmware too.
6. IMEI number is tied to the phone so in theory it can be changed after the phone is rooted and you are able to modify the EFS partition but it is extremely difficult even for veterans like me and it causes lots of problems with cell network registration. Leave well alone if you don't want a completely useless device.
Things to make flashing go easier
1. Turn off FRP lock or sign out of the Google account on the phone or delete it before you do anything, you can put that account back on the phone after flashing.
2. If you enable Developer options make sure " usb debugging" is enabled and OEM unlock, not essential but can help when things go wrong.
3. Anything you want to keep, pics media etc back up or move to SD card, the SD card won't be touched when flashing firmware.
4. Please follow the guides on how to flash correctly.
Any other questions please ask.
It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.
Beanvee7 said:
It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.
Click to expand...
Click to collapse
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.
cooltt said:
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.
Click to expand...
Click to collapse
Source?
Beanvee7 said:
Source?
Click to expand...
Click to collapse
Don't be smart you know how to use Google?
I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.
Beanvee7 said:
I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.
Click to expand...
Click to collapse
lol ok.
i have no OEM unlock on my A53U T-Mobile Variant, i have tried the date trick, the factory reset trick and still not working.
Any ideas?
You probabaly have US devices and this is why u cant unlock
I don't know enough here but my last Samsung is unlocked US device and it has custom roms available for it without needing anything.
The carrier Samsung devices can have a missing oem unlock that supposedly will show up under the correct situation.
So I'd expect that it can be unlocked. But, I don't buy carrier versions so don't know if its correct that you cannot or not. I just feels incorrect to think that you can't at all and it feels more like its not understood how to get it unlocked.
But, if you can't, you can't. At least it has more updates than Samsung has ever had so far. So you should be happy anyway about that more so than other brands.
Not long ago I bought this model of the S22 ultra and I wanted to know if it is possible that it can be rooted
No it cannot be rooted. The bootloader needs to be unlocked, and that is not possible to do either.
i dont understand on how come samsung always do this with new S series until next model comes out and a dev comes in understands that all the lights are shyning on the phone so it should be way esier to get around the OEM toogle missing from developers tab....i would be happy runninh simple but effects very strong to just be able to control whats running and wahts not,use shizuku for highger APis previleges,ice box is great to frezze in case you cant remove via ADB ,Nevo great as well,greniffy,etc....but come one someone find the solution to root the american vertion variant and ill pay whoever can do this favor,on any network in the US im on t-mobile....but willing to witch if is t-mobile the problem ill switch, its unlocked
bresk said:
i dont understand on how come samsung always do this with new S series until next model comes out and a dev comes in understands that all the lights are shyning on the phone so it should be way esier to get around the OEM toogle missing from developers tab....i would be happy runninh simple but effects very strong to just be able to control whats running and wahts not,use shizuku for highger APis previleges,ice box is great to frezze in case you cant remove via ADB ,Nevo great as well,greniffy,etc....but come one someone find the solution to root the american vertion variant and ill pay whoever can do this favor,on any network in the US im on t-mobile....but willing to witch if is t-mobile the problem ill switch, its unlocked
Click to expand...
Click to collapse
Why not switch to a pixel then? The issue isn't you or your phone the issue is Samsung deciding that what you paid for the phone wasn't enough to allow you to do what you want to a device you supposedly own.. The response you received here is disappointing. I dont own this phone but I was thinking about it until finding this out.
talksickisil said:
Why not switch to a pixel then? The issue isn't you or your phone the issue is Samsung deciding that what you paid for the phone wasn't enough to allow you to do what you want to a device you supposedly own.. The response you received here is disappointing. I dont own this phone but I was thinking about it until finding this out.
Click to expand...
Click to collapse
My phone is full paid, network unlocked but still no OEM toogle for unlock the bootloader
talksickisil said:
Why not switch to a pixel then? The issue isn't you or your phone the issue is Samsung deciding that what you paid for the phone wasn't enough to allow you to do what you want to a device you supposedly own.. The response you received here is disappointing. I dont own this phone but I was thinking about it until finding this out.
Click to expand...
Click to collapse
So you can buy a Pixel in the US on any carrier with an unlockable bootloader?
I live in the UK and don't buy new phones very often and have a Samsung S4 mini, S7 and S9 which I still use.
The S4 mini came with an unlocked bootloader out of the box, so no toggle needed in dev options. The S7 and S9 have the toggle.
Regarding the S4 mini, I read a post from 2019 that stated Verizon and AT&T were the only US carriers that locked the bootloader, so I don't know what is going on
bresk said:
My phone is full paid, network unlocked but still no OEM toogle for unlock the bootloader
Click to expand...
Click to collapse
Qualcomm is the one to blame. You need an exynos version to unlock BL
Ryu--X said:
Qualcomm is the one to blame. You need an exynos version to unlock BL
Click to expand...
Click to collapse
Well I've seen some threads about this, but mine is a snapdragon so far i have been searching and hoping that with the s23 series maybe someone would have a answer for the issue
Ryu--X said:
Qualcomm is the one to blame. You need an exynos version to unlock BL
Click to expand...
Click to collapse
Not true. The non-US Snap Dragon variants are rootable. Qualcomm had nothing to do with the bootloader being locked down. That was because North American (primarily US) carriers required it.
Samsung's US and Canadian Snapdragon phones do not allow unlocks regardless if the phone was bought from a carrier or not.
Source : https://en.wikipedia.org/wiki/Bootloader_unlocking#
I honestly didn't realize that was even a thing. No surprise. We don't own our devices Any more. The 1000+ dollars you pay for a phone is just to use it. I've been using an iphone as my primary device since early 2018 which is how I didn't realize this bootloader f#ckery.
Putting on my tinfoil cap: do the US carriers collude with the government to put some type of backdoor in the stock OS that you just won't find in a custom roms source code?
talksickisil said:
Putting on my tinfoil cap: do the US carriers collude with the government to put some type of backdoor in the stock OS that you just won't find in a custom roms source code?
Click to expand...
Click to collapse
Ummm... Go ahead and take off that tinfoil hat and read the 4th, 5th, and 14th Amendments. You should also cut back on the Dan Brown books.