Currently my wife's phone is unlocked. I am a noob and I am just getting into the flash/root android community so I upgraded her stock phone to JI6 on Eclair. As a result, her unlocking codes are not easily accessible anymore but the phone is unlocked. I'm wondering if I need to risk going through the steps in this thread:
http://forum.xda-developers.com/showthread.php?t=822008&page=11 (under Helroz) to find the unlock codes for the phone or I can just continue flash in Roms and kernels on her phone.
I guess the real question is: how important is it to have the unlocking codes if your phone is already unlocked and under what circumstances would the phone relock itself?
Thank you in advance for all replies.
Unlocked as in.... you can change out the sd card? Otherwise, if you have already flashed a differnet ROM, kernel, or modem or whatever, I don't think it would be different if you did it again.
But I would assume once you're unlocked...well you're unlocked, right?
Lol I am unlocked...I'm using the t mobile phone on the wind network I
n toronto so I can say with certainty that I'm unlocked. The reason why I'm asking is because we have two viberants (one that I have the unlock code and one that I don't ). being the noob that I am, I retired to manualy root my phone (the one I have the unlock code) using the update.zip file found in the sticky noob guideline.that one somehow re-locked my phone but I had the unlock codes so out was no problem. That's why I'm paranoid now about the phone relocking itself and I won't have the unlock codes.
Your right about it not asking for the unlock codes after rom and kernel updates.I'm hoping the situation where I re-locked the phone is a special, rare, and unique case. I'm going for some confirmation on this.
Hi, I saw the news (on july) that the bootloader was cracked but then the posts about it's a lie and then the custom kernels appear and I don't know if the bootloader is unlocked or not.
My question is if there will be a way to free unlock the phone (sim unlock) shortly or better go paying an unlock code.
Thank you.
The custom kernels are here because some clever devs figured out how to bypass the bootloader to load unsigned kernels.
Apparently, Zdzihu is working with a mystery dev about unlocking the bootloader, and apparently, they have done it. Nothing has been released to us about it yet however.
Regarding your question, until the bootloader is unlocked, you will need to pay an unlocking service to sim unlock your phone. If the bootloader is unlocked, you might still need to pay an unlocking service.
Sent from my X10i using XDA Premium App
Yum, no matter the bootloader is unlocked, the SIM unclocking is different and not relate to bootloader.
silveraero said:
Yum, no matter the bootloader is unlocked, the SIM unclocking is different and not relate to bootloader.
Click to expand...
Click to collapse
Actually, If you remember back to the flame war between Max and the_laser, much of the hype was about SIM unlock, as unlocking the bootloader would give us direct access to where SIM lock information is stored. I believe this is one of the reasons that SE will not unlock the bootloader, as they are in agreement with various carriers to keep it locked. The carriers obviously don't want people ditching them whenever they feel like it.
Edit:
I might have misunderstood your post. Sorry about that. But the bootloader is directly related to the SIM lock, on this phone at least, hence why I stated "If the bootloader is unlocked, you might still need to pay an unlocking service."
Hi guys, i recently got a legend with hboot 1.01.0000 and s-on. From what i understand after looking through the forum, s-on shows that the phone is "attached" to a certain wireless carrier and is only compatible with that carrier's SIM card, and that hboot 1.01 can't be reversed and thus can't be s-off except with xta clip or an unlock code.
However, just out of my curiosity, i borrowed my cousin's active t-mobile SIM card (prepared) and plugged into my htc...here the strange part, instead of having "no-signal/service," the phone was getting t-mobile services and I was able to make calls & texts! So can anyone tell me why is that because i want to understand the situation before i run off to get a t-mobile or at&t SIM card for it seems to work even with s-on.
Thanks!
(The phone was previously using SIM card from Taiwan mobile if thats any help.)
PSHSU said:
... s-on shows that the phone is "attached" to a certain wireless carrier and is only compatible with that carrier's SIM card ... can't be s-off
Click to expand...
Click to collapse
No, that is not correct. S-ON just means that you do not have write access to system partition even on a rooted device. That is the default state of all HTC devices. Not to be mixed up with a sim-lock as you wrote above.
In case you want to get rid of the write protection, you can easily update the bootloader via HTCdev. Once updated, bootloader can be unlocked so that you can get write access to system partition. That's comparable to S-OFF (even if it is not the same, as it does not allow e.g. to remove sim-locks).
Hope that helped.
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Famous22 said:
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Click to expand...
Click to collapse
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
TheEmpyre said:
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
Click to expand...
Click to collapse
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
brianray14 said:
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
Click to expand...
Click to collapse
Unlocking the bootloader trips a flag. When you relock it gets rid of one flag but trips the relocked flag. Soff can get rid of all flags but you have to leave it soff. Turning it back on throws a security flag.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
redpoint73 said:
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
Click to expand...
Click to collapse
I can second this. I just had to replace my m8 because the speakers were crackling like crazy, my bootloader showed relocked and they told me straight up that they didn't care about that as long as it was a hardware problem and not a software problem and replaced it on the spot.
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
brianray14 said:
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
Click to expand...
Click to collapse
Looking at the return info, I can see where the confusion might come from. It says "Return directly to manufacturer" for 15 days or more:
http://www.att.com/shop/wireless/returnpolicy.html#fbid=KMGdewZyG_f
But AFAIK, all warranty returns go to AT&T when you work through their warranty department. You send them your defective phone, and they send you a refurb. I haven't had to go through this process myself, but this is what has been reported many times on XDA and other forums.
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
im2c0ol said:
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
Click to expand...
Click to collapse
No "update" on this issue is required. The process has been the same for a couple years or more. Further, you've posted the same/similar question to multiple places, and its been answered already in multiple places.
Connect phone to computer in fastboot mode.
Open command prompt, and type: fastboot OEM lock
From there, you can run the RUU.
I'm trying to unlock my HTC One from the AT&T network. I'm currently waiting for them to get back to me with my unlock request. Shouldn't be a problem, I hope.
I'm S-On, and running Dirty Unicorns on my phone. From reading around, I've seen that the unlock code will only work if I'm "stock." However, I have no idea how "stock" I have to be. I've been reading around to find a stock ROM I can flash but everything I see is in the context of going 100% back to stock, flashing RUUs, etc. I currently don't have a USB cable to connect it to my computer so this might prove difficult.
Question: What do I NEED to do to my phone to ensure that I can network unlock it when I have the code from AT&T? (stock rom, stock bootloader, etc)
Bonus questions:
Can I unlock the phone without physically inserting a new SIM? (my friend isn't going to buy one until she gets to China and I don't want to buy one just for this purpose)
AT&T is acting sort of sketchy. If they fail to get me an unlock code in time, can I hack one together or are the services noted in this thread my best bet? http://forum.xda-developers.com/showthread.php?t=2242473