Database Develop

re-lock bootloader?

is there anyone out there found out if its possible in any way to unroot and relock the bootloader???

*sigh*
ibtl

i know this has probrably been answered alot of times but i figured ask and see how e are on this? any new updates on this??

xghostyxjokerx said:
i know this has probrably been answered alot of times but i figured ask and see how e are on this? any new updates on this??
Click to expand...
Click to collapse
would like to see this happen to.
Not "ok" that it voids the warranty.

xghostyxjokerx said:
i know this has probrably been answered alot of times but i figured ask and see how e are on this? any new updates on this??
Click to expand...
Click to collapse
You figured wrong.

uansari1 said:
You figured wrong.
Click to expand...
Click to collapse
He figured people wouldn't act like trolls?

http://lmgtfy.com/?q=Relock+Nexus+One+Bootloader

kobecamp2009 said:
http://lmgtfy.com/?q=Relock+Nexus+One+Bootloader
Click to expand...
Click to collapse
And .... [drumroll] .... that does not answer the question.

I can. Not many others with the same luck though.

jesus. Nobody gave this poor guy a direct answer?
Very few, and I mean probably like 5% of all nexus one's can relock their bootloader. It's some special Holiday edition or something.
But as of right now, no you can't relock it.

stuff said:
jesus. Nobody gave this poor guy a direct answer?
Very few, and I mean probably like 5% of all nexus one's can relock their bootloader. It's some special Holiday edition or something.
But as of right now, no you can't relock it.
Click to expand...
Click to collapse
thank you!!! at least some help and some dont...i thought this was a q/a section..thanks again!

stuff said:
jesus. Nobody gave this poor guy a direct answer?
Very few, and I mean probably like 5% of all nexus one's can relock their bootloader. It's some special Holiday edition or something.
But as of right now, no you can't relock it.
Click to expand...
Click to collapse
Just out of curiousity, when you say "holiday edition", are you referring to the N1s given to Google employees before the phone was released, or is this just a clever way of acknowledging the good luck of those who got a re-lockable phone?
If the latter, is there any pattern by which one can recognise these phones (serial number, manufacturing date/facility, etc.), or is it just luck of the draw?

kobecamp2009 said:
http://lmgtfy.com/?q=Relock+Nexus+One+Bootloader
Click to expand...
Click to collapse
Ironically, that leads to the search results where I found the link to this page. lol
Penguissimo said:
Just out of curiousity, when you say "holiday edition", are you referring to the N1s given to Google employees before the phone was released, or is this just a clever way of acknowledging the good luck of those who got a re-lockable phone?
If the latter, is there any pattern by which one can recognise these phones (serial number, manufacturing date/facility, etc.), or is it just luck of the draw?
Click to expand...
Click to collapse
I'm not 100% sure but I believe "Holiday edition" refers to the special versions of the phones that have the battery cover with a QR code in it, as said QR code leads to a special holiday game when scanned on the Nexus One. Serial number can't be used to determine which Nexii (Nexuses?) can be relocked and which can't. The easiest way to tell if a Nexus One can be relocked is to power it off, hold the track ball, and power it on again. This boots into the bootloader where you will see on the second line something like "NEXUSONE PVT SHIP S-ON." 'S-ON' means that the bootloader can not be relocked while 'S-OFF' indicates a device can be easily be relocked by running a simple fastboot command from your computer, ''fastboot oem lock." I hope this answers your question.
I know the Nexus One has already been successfully rooted without unlocking the bootloader, but I still hope we can figure out a method for relocking the bootloader. I don't mean to scam warranty, I just hate that awful lock icon on the boot screen.

crawler9 said:
Ironically, that leads to the search results where I found the link to this page. lol
I'm not 100% sure but I believe "Holiday edition" refers to the special versions of the phones that have the battery cover with a QR code in it, as said QR code leads to a special holiday game when scanned on the Nexus One. Serial number can't be used to determine which Nexii (Nexuses?) can be relocked and which can't. The easiest way to tell if a Nexus One can be relocked is to power it off, hold the track ball, and power it on again. This boots into the bootloader where you will see on the second line something like "NEXUSONE PVT SHIP S-ON." 'S-ON' means that the bootloader can not be relocked while 'S-OFF' indicates a device can be easily be relocked by running a simple fastboot command from your computer, ''fastboot oem lock." I hope this answers your question.
I know the Nexus One has already been successfully rooted without unlocking the bootloader, but I still hope we can figure out a method for relocking the bootloader. I don't mean to scam warranty, I just hate that awful lock icon on the boot screen.
Click to expand...
Click to collapse
Shouldn't it be possible to simply flash the SPL from a re-lockable phone onto a phone that (before) couldn't?

nexusdue said:
Shouldn't it be possible to simply flash the SPL from a re-lockable phone onto a phone that (before) couldn't?
Click to expand...
Click to collapse
Unfortunately, no this is not possible. Trying to do so would most likely lead to a bricked handset as the retail devices have a 512k spl and the engineering spl from holiday phones is 768k in size.

Is this working?
http://www.machackpc.com/headline/restore-your-nexus-one-to-its-original-shipping-image/
Will it brick the phone ?

nomedor said:
Is this working?
http://www.machackpc.com/headline/restore-your-nexus-one-to-its-original-shipping-image/
Will it brick the phone ?
Click to expand...
Click to collapse
It will not brick the phone. It will work fine for what it's meant to do. Here's a quote from the page
What will be the end result of your Nexus One:
It will reset your system files to the original System Files
It will reset your kernel/boot image to the original shipping boot image
It will reset your recovery to original recovery
The only thing we will not be able to do at this time is to RE-LOCK your Nexus One.
Click to expand...
Click to collapse
Note that this does not re-lock the device which is what this thread is about. As of right now, there is no way that has been made publicly visible to relock the bootloader of an unlocked S-ON Nexus One. Maybe in the future there will be a way. I hope so, but for now, we're stuck. The method from the link can be used only to restore your phone to the stock ROM, so that you can once again receive OTA updates. It will take away your root priveleges, which I'd assume is the reason you've unlocked your device in the first place. So unless you're tired of being in control of your device, it's pointless.

crawler9 said:
I hope this answers your question.
Click to expand...
Click to collapse
It does, thanks Very informative!

crawler9 said:
Unfortunately, no this is not possible. Trying to do so would most likely lead to a bricked handset as the retail devices have a 512k spl and the engineering spl from holiday phones is 768k in size.
Click to expand...
Click to collapse
I have a shipping S-OFF SPL, but apparently nothing can be done with it.

would be nice to see team unrevoked work on this......

[Q] Any reason to re-lock & unroot, plus couple of noob questions

Hi - so I recently installed AR HD 11.5, but I'm wondering now that I've done that is there any compelling reason to re-lock the bootloader? What about un-rooting... any reason to do that after I've done what I needed to whilst being rooted?
Finally, a couple of noobish questions... 1) what's the difference between unlocking the bootloader & S-ON/S-OFF? I guess I was thinking they were one and the same thing, but some of the reading I've done imply they are in fact different things. If someone could please provide a brief explanation I would appreciate it. 2) why are some people concerned about being able to flash the latest OTA update if they have a custom ROM installed? I mean, won't any custom ROM pretty quickly catch up or even surpass the latest available OTA update? For example, that's one of the reasons I chose to go with AR HD because it's already using 4.2.2 instead of 4.1.2 that came with my phone.
Thanks in advance

Drvylyne said:
Hi - so I recently installed AR HD 11.5, but I'm wondering now that I've done that is there any compelling reason to re-lock the bootloader? What about un-rooting... any reason to do that after I've done what I needed to whilst being rooted?
Finally, a couple of noobish questions... 1) what's the difference between unlocking the bootloader & S-ON/S-OFF? I guess I was thinking they were one and the same thing, but some of the reading I've done imply they are in fact different things. If someone could please provide a brief explanation I would appreciate it. 2) why are some people concerned about being able to flash the latest OTA update if they have a custom ROM installed? I mean, won't any custom ROM pretty quickly catch up or even surpass the latest available OTA update? For example, that's one of the reasons I chose to go with AR HD because it's already using 4.2.2 instead of 4.1.2 that came with my phone.
Thanks in advance
Click to expand...
Click to collapse
1. sOFF permits various additional commands like fastboot flash etc.
In short you get even more freedom
Search on google :- ''why do we need to sOFF'' there is a link on ARHD blog that explains this in detail
2. The answer to your 2nd question is very simple.
To get back to full stock- as if you havent done anything to it(no root sOFF unlock etc.) So as to gain warrenty
Hit thanks if i helped you
Sent from my HTC One using xda app-developers app

prunzzz said:
1. sOFF permits various additional commands like fastboot flash etc.
In short you get even more freedom
Search on google :- ''why do we need to sOFF'' there is a link on ARHD blog that explains this in detail
2. The answer to your 2nd question is very simple.
To get back to full stock- as if you havent done anything to it(no root sOFF unlock etc.) So as to gain warrenty
Hit thanks if i helped you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did some more reading on S-Off as you suggested and it doesn't sound necessary or really worthwhile to me. As long as I can put a custom ROM on, as I've already done, then I don't see the need for S-Off as it sounds like it's just inviting trouble if you don't know what you're doing (which I admittedly don't).
Also, I don't see why anyone would ever want to go back to full stock. I read that even if you unlock and put a custom ROM on your phone that it is still covered under warranty and that it's up to the manufacturer and/or carrier to prove that the act of doing one of those things is what actually caused the phone to malfunction thus requiring warranty repair.

Drvylyne said:
I did some more reading on S-Off as you suggested and it doesn't sound necessary or really worthwhile to me. As long as I can put a custom ROM on, as I've already done, then I don't see the need for S-Off as it sounds like it's just inviting trouble if you don't know what you're doing (which I admittedly don't).
Also, I don't see why anyone would ever want to go back to full stock. I read that even if you unlock and put a custom ROM on your phone that it is still covered under warranty and that it's up to the manufacturer and/or carrier to prove that the act of doing one of those things is what actually caused the phone to malfunction thus requiring warranty repair.
Click to expand...
Click to collapse
90% of people have no need for s off...since HTC let us install kernels via recovery ...now barely any people need s off... I think in Europe it doesn't matter if you unlocked and etc..you're still covered... Here in the states ...they can be a holes

I used S-Off to convert my AT&T One software to Developer edition software, then returned it to S-On. Now running totally stock developer version software, eliminates AT&T bloat and hoping I get updates a bit sooner than I would have with AT&T version.

With S-OFF you can flash kernels from the phone. S-ON you would have to do it maunally via fastboot.
Sent from my HTC One using Tapatalk 4 Beta

Drvylyne said:
I did some more reading on S-Off as you suggested and it doesn't sound necessary or really worthwhile to me. As long as I can put a custom ROM on, as I've already done, then I don't see the need for S-Off as it sounds like it's just inviting trouble if you don't know what you're doing (which I admittedly don't).
Also, I don't see why anyone would ever want to go back to full stock. I read that even if you unlock and put a custom ROM on your phone that it is still covered under warranty and that it's up to the manufacturer and/or carrier to prove that the act of doing one of those things is what actually caused the phone to malfunction thus requiring warranty repair.
Click to expand...
Click to collapse
So you got the answer of your 1st question
Now the answer for 2nd one is very simple, though what you said about warrenty is right,
But still many times its always better to have a full stock for warrenty or replacement (by "better" i mean you dont have to prove anything to the service center)
Hit THANKS if i helped you
Sent from my HTC One using xda app-developers app

squabbi said:
With S-OFF you can flash kernels from the phone. S-ON you would have to do it maunally via fastboot.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Wrong I believe with updated HTC dev for the one...HTC unlocked that for us

Basically don't S off if you don't know what it does. It bypasses security checks and allows access to all phone partitions that if applyed wrong could brick your phone. Just flashing roms doesn't require s off
Example of mistake
Fastboot flash hboot recovery.img
This would brick your phone if you had s off, s on would deny write access!!
IF YOUR recive HELP FROM SOMEONE BE GRATEFUL AND HIT THANKS!!!
Sent from my HTC One using xda app-developers app

a box of kittens said:
Wrong I believe with updated HTC dev for the one...HTC unlocked that for us
Click to expand...
Click to collapse
Oh sorry. I was basing that off the One X. I S-OFF'd my One because I thought that without S-OFF I couldn't flash a kernel.
Sent from my HTC One using Tapatalk 4 Beta

[Q] Need help to Sim Unlock AT&T HTC One

Looking to unlock an AT&T version of the HTC One to T-Mobile. I do have an unlock code but it's not working. The phone is rooted and running ARHD 51. I just flashed a different stock rom, tried the code once again but still no luck.

Any suggestions?

WreakerofHavoc said:
Any suggestions?
Click to expand...
Click to collapse
I heard you need to be stock to use a sim-unlock code so you might want to try back to 100% stock then use the code. If it still don't work then maybe you could purchase a new code.

WreakerofHavoc said:
Looking to unlock an AT&T version of the HTC One to T-Mobile. I do have an unlock code but it's not working. The phone is rooted and running ARHD 51. I just flashed a different stock rom, tried the code once again but still no luck.
Click to expand...
Click to collapse
Check your IMEI number and cross reference it with your original to make sure they match. My phone is doing the same thing and it came back from mobile tech videos jtag repair and my numbers are all wrong. Looking for a solution now but my serial number and IMEI numbers are different.
Just a thought, Shot in the dark

alray said:
I heard you need to be stock to use a sim-unlock code so you might want to try back to 100% stock then use the code. If it still don't work then maybe you could purchase a new code.
Click to expand...
Click to collapse
I thought the Rom I used was stock, will try again. Thanks.
cannonofcourse said:
Check your IMEI number and cross reference it with your original to make sure they match. My phone is doing the same thing and it came back from mobile tech videos jtag repair and my numbers are all wrong. Looking for a solution now but my serial number and IMEI numbers are different.
Just a thought, Shot in the dark
Click to expand...
Click to collapse
Will check it out, Thanks.

WreakerofHavoc said:
I thought the Rom I used was stock, will try again. Thanks.
Click to expand...
Click to collapse
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.

nkk71 said:
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
Click to expand...
Click to collapse
Ok. Thanks.

restored the original rom, still no luck.
Any suggestions?

Returned to stock rom and recovery, still no luck.

WreakerofHavoc said:
Returned to stock rom and recovery, still no luck.
Click to expand...
Click to collapse
Are you RUU'ing back to stock ?
if your 4.3 try this
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
if your 4.4 try this
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe

clsA said:
Are you RUU'ing back to stock ?
if your 4.3 try this
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
if your 4.4 try this
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Haven't RUU'ed to stock yet. S-Off is need for RUU right? Going to S-Off and then try this. Thanks.

WreakerofHavoc said:
Haven't RUU'ed to stock yet. S-Off is need for RUU right? Going to S-Off and then try this. Thanks.
Click to expand...
Click to collapse
you don't need s-off, you just need to relock the bootloader

Hmmm still no luck. Been working at this for a while now, not sure what the problem is. Selling it is the only solution I can think of right now, but there must be a way to unlock this for my carrier.

Hello. I have a similar issue, so I don't think I should create another topic.
I just purchased a 64gb HTC One and purchased the unlock code from the same vendor as always. I was always able to unlock other devices (One XL, One X+, Windows phone 8X) easily, and even other Ones, since this is my fouth (first one I gave to my brother, second slipped off my pocket while in a tunnel riding my motorcycle and the third is 32gb, so I decided to sell it and buy a 64gb).
This one is used like new, everything stock, s-on, nothing unusual. Well, except the led seems to be smaller (very hard to see the red dot while charging) and the system may be newer, since it doens't find any update available.
But the code doesn't work. I tried twice thinking I could be misspelling the numbers, but returned wrong anyway.
So...
1-What happens if I try again and it returns wrong, since it's showing it's my last try?
2-Any clue?
Thanks in advance.

Does your phone work on any network? What carrier is it branded?
Best thing is to email (carrier) support and get a code from them.
This thread is for devices that have a security cross reference back end problems.
Does your phone say it accepts the code then restarts then asks for the code again?
Sent from my unknown using xda app-developers app

mefxes said:
Hello. I have a similar issue, so I don't think I should create another topic.
I just purchased a 64gb HTC One and purchased the unlock code from the same vendor as always. I was always able to unlock other devices (One XL, One X+, Windows phone 8X) easily, and even other Ones, since this is my fouth (first one I gave to my brother, second slipped off my pocket while in a tunnel riding my motorcycle and the third is 32gb, so I decided to sell it and buy a 64gb).
This one is used like new, everything stock, s-on, nothing unusual. Well, except the led seems to be smaller (very hard to see the red dot while charging) and the system may be newer, since it doens't find any update available.
But the code doesn't work. I tried twice thinking I could be misspelling the numbers, but returned wrong anyway.
So...
1-What happens if I try again and it returns wrong, since it's showing it's my last try?
2-Any clue?
Thanks in advance.
Click to expand...
Click to collapse
In my experience, I'm not getting anything showing my number of attempts or last attempt. I've tried the unlock code about 8-10 times on different roms stock and non stock and stock recovery. I really have no idea.

WreakerofHavoc said:
In my experience, I'm not getting anything showing my number of attempts or last attempt. I've tried the unlock code about 8-10 times on different roms stock and non stock and stock recovery. I really have no idea.
Click to expand...
Click to collapse
Thanks for your answer.
All my HTCs always shown a counter.
Today, after restoring the phone to stock ruu, it wasn't showing any counter anymore, so I decided to try again the code I purchased (and other code sellers confirmed) and it worked.
Very strange... but now it's unlocked.

mefxes said:
Thanks for your answer.
All my HTCs always shown a counter.
Today, after restoring the phone to stock ruu, it wasn't showing any counter anymore, so I decided to try again the code I purchased (and other code sellers confirmed) and it worked.
Very strange... but now it's unlocked.
Click to expand...
Click to collapse
You have the at&t version too? Can you link me to the ruu you used?

nkk71 said:
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
Click to expand...
Click to collapse
After a lot of painstaking effort, I managed to flash a stock RUU, got back to a stock recovery, and locked the bootloader. Got the same unlock code from two separate vendors. No dice. Incredibly frustrating, don't know what's wrong with my phone but now I have to sell it.

850csi said:
After a lot of painstaking effort, I managed to flash a stock RUU, got back to a stock recovery, and locked the bootloader. Got the same unlock code from two separate vendors. No dice. Incredibly frustrating, don't know what's wrong with my phone but now I have to sell it.
Click to expand...
Click to collapse
well you can sim-unlock using the sieempi method instead of the unlock code, like many others successfully did
http://forum.xda-developers.com/showpost.php?p=53043418&postcount=601

[Guide?] Returning to factory from S-OFF and need to go back to stock everything.

Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.

did you use htcdev to unlock?
Sent from my 831C using Tapatalk

Zzz73 said:
did you use htcdev to unlock?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Yes, I initially used the HTCDEV to unlock which voids the warranty. There are ways to revert from that though and that is what I am trying to accomplish by going back to stock everything.
I don't know if I need to flash the full firmware or not after I installed the stock nandroid backup from step 4).
Thank you for the reply.

oh OK. of you know a way around. i thought it registered your serial with HTC...
Sent from my 831C using Tapatalk

murf43143 said:
Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.
Click to expand...
Click to collapse
I would put it back to s-on as well.

FlowingAway said:
I would put it back to s-on as well.
Click to expand...
Click to collapse
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.

murf43143 said:
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.
Click to expand...
Click to collapse
The only reason I say that is because I had a bad experience last year with my M7 being sent back to HTC.
If I was confident I could get s-off again when the phone cane back I would do it just to make sure it wouldn't be denied. Of course that's just me. Definitely try and find some more people's experience before you do anything.

I don't think anyone here can give you a definitive answer to your question because people have all had different experiences when it comes to HTC's warranty department. Some get denied for tampering and voiding the warranty while another customer with almost an almost identical issue breezes through without even un-rooting.....
It is very likely they have some other means of telling whether the stock firmware/software has been replaced at some point that we have no clue about. If they wanted to be hardarses about this kind of thing I'm sure they are quite capable of doing so but I do not think it is in their best interest as a company to get that kind of PR when you have Google and Motorola offering warranties (guaranteed or something like that I read somewhere?) despite tampering. 'Power users' like most of the members on XDA, are a huge market who often have multiple devices and a high level of influence with friends, relatives, coworkers etc when it comes time for their upgrades...You can see where that train of thought ends up I hope.^^
Anyway, sorry for the ranting, haha. My point is that you should take every precaution you can including going back to S-On, "Locking" the bootloader again, and ensuring your device is as exactly like it was when you first got it if you want to minimize your chances of getting denied your warranty. You can always look back on it and go, well maybe I didn't have to go through all that trouble but sure glad it got fixed! That's a much better alternative than the regret you'd have if something as simple as S-Off is to fix(or faux fix) resulted in your claim getting denied.^^
Best of luck, whatever you decide!

[Q] Can't boot into android, or flash anything

Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)

Welcome to the club!

necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.

wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.

necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.

AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.

Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....

wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.

necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.

the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.

AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.

AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.

rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.

AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.

AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.

the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.

AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.