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] 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.

[Q] Best way to get off of 5.1 LMY47D?

Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!

you can always use fastboot to go back to 5.0.1

stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?

i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.

simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.

gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.

EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.

EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.

Sweet, successful downgrade!

I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!

Disregard! Got it handled. Thanks guys!

Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1

EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??

Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!

H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.

Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?

H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.

you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.

simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.

danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.

Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6

Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.

H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.

cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.

-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.

Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6

Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?

H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.

Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?

alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Question Help, i did something stupid.

Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?

Can't you fix stuff by using https://flash.android.com/ ?

No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.

Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me

If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.

Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..

JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.

Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works

Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD

JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.

Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.

Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for

Delete

If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware

DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.

Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.

DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please

DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.

Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening