From 6d7bdc69c0dfa492d25ba7d79b583932b75ae941 Mon Sep 17 00:00:00 2001
From: Ivy <78825510+Lost-Entrepreneur439@users.noreply.github.com>
Date: Tue, 3 Dec 2024 10:51:36 -0330
Subject: [PATCH 1/5] Add carriers
---
carriers/README.md | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 carriers/README.md
diff --git a/carriers/README.md b/carriers/README.md
new file mode 100644
index 0000000..694a3b4
--- /dev/null
+++ b/carriers/README.md
@@ -0,0 +1,42 @@
+Carrier locked devices are the ones you get after making a commitment with a carrier of your choice. This is quite common in North America and (supposedly) allows you to save some money on your device.
+
+As a rule, almost all carrier locked devices do not allow the bootloader to be unlocked. This usually makes sense, as it would allow you to completely bypass the contract. The problem is that many devices still do not allow you to unlock the bootloader even after the carrier lock has been lifted. This page is keeping track of those carriers.
+
+> [!NOTE]
+> This page is a WIP! If you have any details about a carrier who isn't here, please open a pull request!
+
+## United States
+Land of the free... unless you want your phone to be free. American carriers have been historically bad with bootloader unlocks.
+
+### AT&T/Cricket
+AT&T does not allow you to unlock your bootloader until your phone is network unlocked, and AT&T has a history of refusing to network unlock phones for zero reason. However, some recent posts on XDA have claimed the AT&T Pixel 9's bootloader can be unlocked if you set up the phone [without an AT&T SIM inserted](https://xdaforums.com/t/at-t-pixel-9-pro-xl-bootloader-unlockable.4689083/). AT&T also has an artifical blacklist, meaning you are limited only to the devices they officially support. You're best off avoiding AT&T.
+
+### Verizon/Visible
+Verizon has always been infamously bad for force locking the bootloader. Even dating back to their exclusive DROID series of phones (made by HTC and Motorola) in the late 2000s and early 2010s, you had to use things like SafeStrap to get custom ROMs. Verizon hasn't changed, being very clear that they will not unlock your bootloader, no matter what. In some very very rare cases, people have reported they were able to [unlock their Verizon Pixel's bootloader](https://xdaforums.com/t/just-unlocked-my-vzw-bootloader.4500027/), but this is extremely rare (I can only find one case of this happening).
+
+### T-Mobile/Metro
+In general, T-Mobile generally lets you unlock your bootloader, even if your phone is still carrier locked, likely related to the fact T-Mobile has always supported Android (they were the first carrier in the world to sell an Android device), way back in 2011, T-Mobile said on Twitter that CyanogenMod (a very popular custom ROM, now known as LineageOS) was great, and they were excited to see what Cyanogen would do [for T-Mobile's new phone](https://x.com/TMobile/status/60111542494048256). T-Mobile has also seemingly forced certain manufacturers to make their bootloaders unlockable, as phones like the LG G6 (normally not unlockable), is unlockable via the [standard unlock procedure](/misc/general-unlock.md) for T-Mobile models.
+Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
+
+### Boost
+Boost doesn't have a wide choice of Android phones, they only have Samsung, Motorola, and phones made by Boost (likely made by a different OEM, similar to T-Mobile, I can't find which OEM though). I can't find anything for Boost-made phones, but their Motorola devices are unlockable via [standard Motorola procedure](/brands/motorola/README.md]
+
+## Canada
+All devices sold in Canada after December 1, 2017 are sold unlocked, and any devices sold before then legally have to be unlocked for free, thanks to [the Wireless Code](https://crtc.gc.ca/eng/archive/2017/2017-200.htm). For devices sold before then however..
+
+### Bell/Virgin/Lucky
+Bootloaders are unlockable, although I'd recommend avoiding Bell due to their virtually non-existent LTE and 5G network if you live outside of Ontario, Quebec or BC.
+
+### Telus/Koodo/Public
+Bootloaders are unlockable, nothing to report.
+
+### Rogers/Fido/Chatr
+Bootloaders are unlockable, however for devices sold before December 1, 2017, network unlocking is a problem. Rogers directly violates the Wireless Code, forcing you to be a Rogers customer to unlock your phone. If you have a Rogers device and need it to be unlocked, [file a complaint](https://crtc.gc.ca/eng/contact/question.htm) with the CRTC. This is illegal, Rogers legally has to unlock your phone unless it's reported as lost or stolen. Even with modern devices, I'd avoid Rogers because they've shown they have no problem breaking laws.
+
+## Japan
+If you buy a Sony or Sharp phone used, high chance it's going to be locked to a Japanese carrier as that's just where Sony and Sharp are popular.
+
+### NTT Docomo
+NTT Docomo does not allow you to unlock your bootloader, the OEM unlock option is greyed out.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
From a0a8cd3dcebfb3941dcfd5d9273b6aa2129f50e6 Mon Sep 17 00:00:00 2001
From: Ivy <78825510+Lost-Entrepreneur439@users.noreply.github.com>
Date: Tue, 3 Dec 2024 10:53:33 -0330
Subject: [PATCH 2/5] README: add carriers
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 3f7e949..2658fc2 100644
--- a/README.md
+++ b/README.md
@@ -69,7 +69,7 @@ If you know of specific details/unlocking methods, please PR them or drop them i
Carrier locked devices are the ones you get after making a commitment with a carrier of your choice. This is quite common in North America and (supposedly) allows you to save some money on your device.
-As a rule, almost all carrier locked devices do not allow the bootloader to be unlocked. This usually makes sense, as it would allow you to completely bypass the contract. The problem is that many devices still do not allow you to unlock the bootloader even after the carrier lock has been lifted.
+As a rule, almost all carrier locked devices do not allow the bootloader to be unlocked. This usually makes sense, as it would allow you to completely bypass the contract. The problem is that many devices still do not allow you to unlock the bootloader even after the carrier lock has been lifted. For more details, see the [carriers page](/carriers/README.md).
## ⚠️ Proceed with caution!
From a4c097a9260e80d3142e7b0439f79ac4327051e9 Mon Sep 17 00:00:00 2001
From: Ivy <78825510+Lost-Entrepreneur439@users.noreply.github.com>
Date: Wed, 15 Jan 2025 11:00:55 -0330
Subject: [PATCH 3/5] Carriers: split pages
---
carriers/README.md | 27 ++++++++-------------------
carriers/brands/att/README.md | 3 +++
carriers/brands/bell/README.md | 3 +++
carriers/brands/boost/README.md | 3 +++
carriers/brands/nttdocomo/README.md | 3 +++
carriers/brands/rogers/README.md | 3 +++
carriers/brands/telus/README.md | 3 +++
carriers/brands/tmobile/README.md | 2 ++
carriers/brands/verizon/README.md | 3 +++
9 files changed, 31 insertions(+), 19 deletions(-)
create mode 100644 carriers/brands/att/README.md
create mode 100644 carriers/brands/bell/README.md
create mode 100644 carriers/brands/boost/README.md
create mode 100644 carriers/brands/nttdocomo/README.md
create mode 100644 carriers/brands/rogers/README.md
create mode 100644 carriers/brands/telus/README.md
create mode 100644 carriers/brands/tmobile/README.md
create mode 100644 carriers/brands/verizon/README.md
diff --git a/carriers/README.md b/carriers/README.md
index 694a3b4..c4ad1a0 100644
--- a/carriers/README.md
+++ b/carriers/README.md
@@ -8,35 +8,24 @@ As a rule, almost all carrier locked devices do not allow the bootloader to be u
## United States
Land of the free... unless you want your phone to be free. American carriers have been historically bad with bootloader unlocks.
-### AT&T/Cricket
-AT&T does not allow you to unlock your bootloader until your phone is network unlocked, and AT&T has a history of refusing to network unlock phones for zero reason. However, some recent posts on XDA have claimed the AT&T Pixel 9's bootloader can be unlocked if you set up the phone [without an AT&T SIM inserted](https://xdaforums.com/t/at-t-pixel-9-pro-xl-bootloader-unlockable.4689083/). AT&T also has an artifical blacklist, meaning you are limited only to the devices they officially support. You're best off avoiding AT&T.
+### [AT&T/Cricket](/carriers/brands/att/README.md)
-### Verizon/Visible
-Verizon has always been infamously bad for force locking the bootloader. Even dating back to their exclusive DROID series of phones (made by HTC and Motorola) in the late 2000s and early 2010s, you had to use things like SafeStrap to get custom ROMs. Verizon hasn't changed, being very clear that they will not unlock your bootloader, no matter what. In some very very rare cases, people have reported they were able to [unlock their Verizon Pixel's bootloader](https://xdaforums.com/t/just-unlocked-my-vzw-bootloader.4500027/), but this is extremely rare (I can only find one case of this happening).
+### [Verizon/Visible](/carriers/brands/verizon/README.md)
-### T-Mobile/Metro
-In general, T-Mobile generally lets you unlock your bootloader, even if your phone is still carrier locked, likely related to the fact T-Mobile has always supported Android (they were the first carrier in the world to sell an Android device), way back in 2011, T-Mobile said on Twitter that CyanogenMod (a very popular custom ROM, now known as LineageOS) was great, and they were excited to see what Cyanogen would do [for T-Mobile's new phone](https://x.com/TMobile/status/60111542494048256). T-Mobile has also seemingly forced certain manufacturers to make their bootloaders unlockable, as phones like the LG G6 (normally not unlockable), is unlockable via the [standard unlock procedure](/misc/general-unlock.md) for T-Mobile models.
-Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
+### [T-Mobile/Metro](/carriers/brands/tmobile/README.md)
-### Boost
-Boost doesn't have a wide choice of Android phones, they only have Samsung, Motorola, and phones made by Boost (likely made by a different OEM, similar to T-Mobile, I can't find which OEM though). I can't find anything for Boost-made phones, but their Motorola devices are unlockable via [standard Motorola procedure](/brands/motorola/README.md]
+### [Boost](/carriers/brands/boost/README.md)
## Canada
All devices sold in Canada after December 1, 2017 are sold unlocked, and any devices sold before then legally have to be unlocked for free, thanks to [the Wireless Code](https://crtc.gc.ca/eng/archive/2017/2017-200.htm). For devices sold before then however..
-### Bell/Virgin/Lucky
-Bootloaders are unlockable, although I'd recommend avoiding Bell due to their virtually non-existent LTE and 5G network if you live outside of Ontario, Quebec or BC.
+### [Bell/Virgin/Lucky](/carriers/brands/bell/README.md)
-### Telus/Koodo/Public
-Bootloaders are unlockable, nothing to report.
+### [Telus/Koodo/Public](/carriers/brands/telus/README.md)
-### Rogers/Fido/Chatr
-Bootloaders are unlockable, however for devices sold before December 1, 2017, network unlocking is a problem. Rogers directly violates the Wireless Code, forcing you to be a Rogers customer to unlock your phone. If you have a Rogers device and need it to be unlocked, [file a complaint](https://crtc.gc.ca/eng/contact/question.htm) with the CRTC. This is illegal, Rogers legally has to unlock your phone unless it's reported as lost or stolen. Even with modern devices, I'd avoid Rogers because they've shown they have no problem breaking laws.
+### [Rogers/Fido/Chatr](/carriers/brands/rogers/README.md)
## Japan
If you buy a Sony or Sharp phone used, high chance it's going to be locked to a Japanese carrier as that's just where Sony and Sharp are popular.
-### NTT Docomo
-NTT Docomo does not allow you to unlock your bootloader, the OEM unlock option is greyed out.
-***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+### [NTT Docomo](/carriers/brands/nttdocomo/README.md)
diff --git a/carriers/brands/att/README.md b/carriers/brands/att/README.md
new file mode 100644
index 0000000..966b9a9
--- /dev/null
+++ b/carriers/brands/att/README.md
@@ -0,0 +1,3 @@
+AT&T does not allow you to unlock your bootloader until your phone is network unlocked, and AT&T has a history of refusing to network unlock phones for zero reason. However, some recent posts on XDA have claimed the AT&T Pixel 9's bootloader can be unlocked if you set up the phone [without an AT&T SIM inserted](https://xdaforums.com/t/at-t-pixel-9-pro-xl-bootloader-unlockable.4689083/). AT&T also has an artifical blacklist, meaning you are limited only to the devices they officially support. You're best off avoiding AT&T.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/bell/README.md b/carriers/brands/bell/README.md
new file mode 100644
index 0000000..ae38c09
--- /dev/null
+++ b/carriers/brands/bell/README.md
@@ -0,0 +1,3 @@
+Bootloaders are unlockable, although I'd recommend avoiding Bell due to their virtually non-existent LTE and 5G network if you live outside of Ontario, Quebec or BC.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/boost/README.md b/carriers/brands/boost/README.md
new file mode 100644
index 0000000..93f3581
--- /dev/null
+++ b/carriers/brands/boost/README.md
@@ -0,0 +1,3 @@
+Boost doesn't have a wide choice of Android phones, they only have Samsung, Motorola, and phones made by Boost (likely made by a different OEM, similar to T-Mobile, I can't find which OEM though). I can't find anything for Boost-made phones, but their Motorola devices are unlockable via [standard Motorola procedure](/brands/motorola/README.md]
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/nttdocomo/README.md b/carriers/brands/nttdocomo/README.md
new file mode 100644
index 0000000..ed1c446
--- /dev/null
+++ b/carriers/brands/nttdocomo/README.md
@@ -0,0 +1,3 @@
+NTT Docomo does not allow you to unlock your bootloader, the OEM unlock option is greyed out.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/rogers/README.md b/carriers/brands/rogers/README.md
new file mode 100644
index 0000000..ce1d4b2
--- /dev/null
+++ b/carriers/brands/rogers/README.md
@@ -0,0 +1,3 @@
+Bootloaders are unlockable, however for devices sold before December 1, 2017, network unlocking is a problem. Rogers directly violates the Wireless Code, forcing you to be a Rogers customer to unlock your phone. If you have a Rogers device and need it to be unlocked, [file a complaint](https://crtc.gc.ca/eng/contact/question.htm) with the CRTC. This is illegal, Rogers legally has to unlock your phone unless it's reported as lost or stolen. Even with modern devices, I'd avoid Rogers because they've shown they have no problem breaking laws.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/telus/README.md b/carriers/brands/telus/README.md
new file mode 100644
index 0000000..8c851f4
--- /dev/null
+++ b/carriers/brands/telus/README.md
@@ -0,0 +1,3 @@
+Bootloaders are unlockable, nothing to report.
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/tmobile/README.md b/carriers/brands/tmobile/README.md
new file mode 100644
index 0000000..77870ea
--- /dev/null
+++ b/carriers/brands/tmobile/README.md
@@ -0,0 +1,2 @@
+In general, T-Mobile generally lets you unlock your bootloader, even if your phone is still carrier locked, likely related to the fact T-Mobile has always supported Android (they were the first carrier in the world to sell an Android device), way back in 2011, T-Mobile said on Twitter that CyanogenMod (a very popular custom ROM, now known as LineageOS) was great, and they were excited to see what Cyanogen would do [for T-Mobile's new phone](https://x.com/TMobile/status/60111542494048256). T-Mobile has also seemingly forced certain manufacturers to make their bootloaders unlockable, as phones like the LG G6 (normally not unlockable), is unlockable via the [standard unlock procedure](/misc/general-unlock.md) for T-Mobile models.
+Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
\ No newline at end of file
diff --git a/carriers/brands/verizon/README.md b/carriers/brands/verizon/README.md
new file mode 100644
index 0000000..2dc8cf3
--- /dev/null
+++ b/carriers/brands/verizon/README.md
@@ -0,0 +1,3 @@
+Verizon has always been infamously bad for force locking the bootloader. Even dating back to their exclusive DROID series of phones (made by HTC and Motorola) in the late 2000s and early 2010s, you had to use things like SafeStrap to get custom ROMs. Verizon hasn't changed, being very clear that they will not unlock your bootloader, no matter what. In some very very rare cases, people have reported they were able to [unlock their Verizon Pixel's bootloader](https://xdaforums.com/t/just-unlocked-my-vzw-bootloader.4500027/), but this is extremely rare (I can only find one case of this happening).
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
From 90718be103356f4331f90e9b29c7e441ca38e8ab Mon Sep 17 00:00:00 2001
From: Ivy <78825510+Lost-Entrepreneur439@users.noreply.github.com>
Date: Mon, 20 Jan 2025 14:34:17 -0330
Subject: [PATCH 4/5] Add headers and verdicts, and fix broken Boost link.
---
carriers/brands/att/README.md | 4 ++++
carriers/brands/bell/README.md | 6 +++++-
carriers/brands/boost/README.md | 4 ++++
carriers/brands/nttdocomo/README.md | 4 ++++
carriers/brands/rogers/README.md | 4 ++++
carriers/brands/telus/README.md | 4 ++++
carriers/brands/tmobile/README.md | 6 +++++-
carriers/brands/verizon/README.md | 4 ++++
8 files changed, 34 insertions(+), 2 deletions(-)
diff --git a/carriers/brands/att/README.md b/carriers/brands/att/README.md
index 966b9a9..2dfd4a4 100644
--- a/carriers/brands/att/README.md
+++ b/carriers/brands/att/README.md
@@ -1,3 +1,7 @@
+# AT&T/Cricket
+
+- Verdict: **⛔ Avoid!**
+
AT&T does not allow you to unlock your bootloader until your phone is network unlocked, and AT&T has a history of refusing to network unlock phones for zero reason. However, some recent posts on XDA have claimed the AT&T Pixel 9's bootloader can be unlocked if you set up the phone [without an AT&T SIM inserted](https://xdaforums.com/t/at-t-pixel-9-pro-xl-bootloader-unlockable.4689083/). AT&T also has an artifical blacklist, meaning you are limited only to the devices they officially support. You're best off avoiding AT&T.
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/bell/README.md b/carriers/brands/bell/README.md
index ae38c09..1dbe3dc 100644
--- a/carriers/brands/bell/README.md
+++ b/carriers/brands/bell/README.md
@@ -1,3 +1,7 @@
-Bootloaders are unlockable, although I'd recommend avoiding Bell due to their virtually non-existent LTE and 5G network if you live outside of Ontario, Quebec or BC.
+# Bell/Virgin Canada/Lucky
+
+* Verdict **ℹ️ "Safe for now" :trollface:**
+
+Bell's bootloaders are unlockable, nothing to report.
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/boost/README.md b/carriers/brands/boost/README.md
index 93f3581..ee70cb3 100644
--- a/carriers/brands/boost/README.md
+++ b/carriers/brands/boost/README.md
@@ -1,3 +1,7 @@
+# Boost
+
+* Verdict **ℹ️ "Safe for now" :trollface:**
+
Boost doesn't have a wide choice of Android phones, they only have Samsung, Motorola, and phones made by Boost (likely made by a different OEM, similar to T-Mobile, I can't find which OEM though). I can't find anything for Boost-made phones, but their Motorola devices are unlockable via [standard Motorola procedure](/brands/motorola/README.md]
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/nttdocomo/README.md b/carriers/brands/nttdocomo/README.md
index ed1c446..44218c8 100644
--- a/carriers/brands/nttdocomo/README.md
+++ b/carriers/brands/nttdocomo/README.md
@@ -1,3 +1,7 @@
+# NTT Docomo
+
+- Verdict: **🍅 Terrible!**
+
NTT Docomo does not allow you to unlock your bootloader, the OEM unlock option is greyed out.
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/rogers/README.md b/carriers/brands/rogers/README.md
index ce1d4b2..ebbfed1 100644
--- a/carriers/brands/rogers/README.md
+++ b/carriers/brands/rogers/README.md
@@ -1,3 +1,7 @@
+# Rogers/Fido/Chatr
+
+- Verdict: **⚠️ Proceed with caution!**
+
Bootloaders are unlockable, however for devices sold before December 1, 2017, network unlocking is a problem. Rogers directly violates the Wireless Code, forcing you to be a Rogers customer to unlock your phone. If you have a Rogers device and need it to be unlocked, [file a complaint](https://crtc.gc.ca/eng/contact/question.htm) with the CRTC. This is illegal, Rogers legally has to unlock your phone unless it's reported as lost or stolen. Even with modern devices, I'd avoid Rogers because they've shown they have no problem breaking laws.
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/telus/README.md b/carriers/brands/telus/README.md
index 8c851f4..be21e17 100644
--- a/carriers/brands/telus/README.md
+++ b/carriers/brands/telus/README.md
@@ -1,3 +1,7 @@
+# Telus
+
+* Verdict **ℹ️ "Safe for now" :trollface:**
+
Bootloaders are unlockable, nothing to report.
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/carriers/brands/tmobile/README.md b/carriers/brands/tmobile/README.md
index 77870ea..9d55095 100644
--- a/carriers/brands/tmobile/README.md
+++ b/carriers/brands/tmobile/README.md
@@ -1,2 +1,6 @@
+# T-Mobile/Metro
+
+* Verdict **ℹ️ "Safe for now" :trollface:**
+
In general, T-Mobile generally lets you unlock your bootloader, even if your phone is still carrier locked, likely related to the fact T-Mobile has always supported Android (they were the first carrier in the world to sell an Android device), way back in 2011, T-Mobile said on Twitter that CyanogenMod (a very popular custom ROM, now known as LineageOS) was great, and they were excited to see what Cyanogen would do [for T-Mobile's new phone](https://x.com/TMobile/status/60111542494048256). T-Mobile has also seemingly forced certain manufacturers to make their bootloaders unlockable, as phones like the LG G6 (normally not unlockable), is unlockable via the [standard unlock procedure](/misc/general-unlock.md) for T-Mobile models.
-Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
\ No newline at end of file
+Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
diff --git a/carriers/brands/verizon/README.md b/carriers/brands/verizon/README.md
index 2dc8cf3..396b475 100644
--- a/carriers/brands/verizon/README.md
+++ b/carriers/brands/verizon/README.md
@@ -1,3 +1,7 @@
+# Verizon/Visible
+
+- Verdict: **🍅 Terrible!**
+
Verizon has always been infamously bad for force locking the bootloader. Even dating back to their exclusive DROID series of phones (made by HTC and Motorola) in the late 2000s and early 2010s, you had to use things like SafeStrap to get custom ROMs. Verizon hasn't changed, being very clear that they will not unlock your bootloader, no matter what. In some very very rare cases, people have reported they were able to [unlock their Verizon Pixel's bootloader](https://xdaforums.com/t/just-unlocked-my-vzw-bootloader.4500027/), but this is extremely rare (I can only find one case of this happening).
***
Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
From 45e75d623bb762f46f610708f1a5fabfe9edab36 Mon Sep 17 00:00:00 2001
From: Ivy <78825510+Lost-Entrepreneur439@users.noreply.github.com>
Date: Mon, 20 Jan 2025 14:35:57 -0330
Subject: [PATCH 5/5] tmobile: add footer
---
carriers/brands/tmobile/README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/carriers/brands/tmobile/README.md b/carriers/brands/tmobile/README.md
index 9d55095..6b51d60 100644
--- a/carriers/brands/tmobile/README.md
+++ b/carriers/brands/tmobile/README.md
@@ -4,3 +4,5 @@
In general, T-Mobile generally lets you unlock your bootloader, even if your phone is still carrier locked, likely related to the fact T-Mobile has always supported Android (they were the first carrier in the world to sell an Android device), way back in 2011, T-Mobile said on Twitter that CyanogenMod (a very popular custom ROM, now known as LineageOS) was great, and they were excited to see what Cyanogen would do [for T-Mobile's new phone](https://x.com/TMobile/status/60111542494048256). T-Mobile has also seemingly forced certain manufacturers to make their bootloaders unlockable, as phones like the LG G6 (normally not unlockable), is unlockable via the [standard unlock procedure](/misc/general-unlock.md) for T-Mobile models.
Do note that this does *not* account for phones made by T-Mobile, these phones have a number of different OEMs, usually Wingtech for newer models, and [HTC](/brands/htc/README.md) for older models, however they've been made by a varity of different OEMs, including [TCL](/brands/tcl/README.md), [Samsung](/brands/samsung/README.md), [Sharp](/brands/sharp/README.md), Danger, [LG](/brands/lg/README.md) and [Huawei](/brands/huawei/README.md).
+***
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).