Not sure if T-mobile follows the same procedure but I find the original solution here for S3 Frontier (AT&T). It apparently works for S2 also. I have no idea why AT&T does not release this and claims they cannot unlock wearables (in 2016).
Here is a log of the procedure, verified by both XDA folks and me.
First, you need to get the unlock code (from here at AT&T). If you are not the account holder, ask them to follow the procedure for you. To get the unlock code, you need to find out your smartwatch's IMEI number at
Settings > Gear Info > About Device. For me, the request takes about 2 business days. Some people did not get it in couple days and pinged at the customer service and went it through.
Anyway, suppose you have the 8-digit unlock code now. You get it from the email asking you to follow the procedure by first "power off the device and remove the SIM card". Yea, you can never do that for Gear S2/S3 because they use eSIM.
slapshot2286, we can unlock the device by doing the following.
- Go to
Settings > Gear Info > About Device and scroll down to
Software Version 5 times and a keyboard will show up
#7465625*638*# and another dialog shows up, which says "Personalisation" followed by "Enter NCK"
- Enter the unlock code you get from AT&T and tap
You will then see
SUCCESS indicating you have unlocked your Gear S2/S3. Period.
This is awesome. Vultr recently upgraded the $5/month plan so that I now have 1GB memory with 25GB storage! YAY!
And what is more fun is there is $2.5/month option, which has less bandwidth, storage, and memory. The only thing is there is no possibility to downgrade a plan, otherwise I might just go for this one (since my old plan was 768MB memory and 15GB SSD).
Here is the referral link if you are interested in it. I'll answer any questions if you get any.
NLP: Natural Language Processing
Just show you a photo you'll understand.
hmm... see here http://www.sony.jp/digital-paper/lineup/
Last year I was suggesting to use StartSSL/StartCom to get free SSL certificates and easily enable HTTPS for websites. Apparently now Chrome and Firefox have distrusted their certificates and considered my site as a "malicious" site after then. I went online and looked for alternatives and Let's Encrypt is a really great service (free & more freedom). Here I log the process how did I switch to certificates with Let's Encrypt.
In this log/tutorial, I assume websites have already enabled SSL (e.g., using
httpd as demonstrated in this earlier post) and are using Apache version less than 2.4.8. Also, I'm using Debian 7. Otherwise, try to follow instruction here. Continue reading Switch From StartSSL/StartCom To Let's Encrypt (Enable HTTPS For Websites)
Finally get some time to fix the certificate issue. Long story short, I was using StartCom's StartSSL Class 1 as my root certificate authority. It is free and easy to use (until recently). Chrome had decided not to trust this company due to some issues a while ago but I never paid attention to it. And recently the update of Chrome browser had decided to not trust my website due to this and said
Your connection is not private
Blah blah blah. In short, that treated my site as a potential malicious site.
But my stuff are all legit and do no harm to anyone.
So I now switched to Certbot. I will write some details about switching to Certbot shortly.