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.
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
droidfun1 said:
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
Click to expand...
Click to collapse
This might not work with a locked bootloader, but you can give it a shot.
Download the boot logo from this thread that looks like the original one: https://forum.xda-developers.com/mo...o-maxx-droid-turbo-x-style-logos-bin-t3407046
Double click on the .exe file while your phone is in bootloader mode and plugged into your computer.
Thanks ya, I have seen that logo fix floating around for the Droid Turbo but I didn't want to try until I had at least one confirmation that it could work on a relocked bootloader. Anyone have a guess/idea/or success story?
After unlocking Z2 Plus bootloader, started to showing up on boot before logo splash:
"Your device has been unlocker and can't be trusted
To learn more, visit:
g.com/placeholder
If no key pressed:
You device will boot in 5 seconds"
Anyone knows how can I get rid of this message?
Already tried to flash factory splash.img with no success!
Thanks in advance!
there is no way you can get rid of this warning because i think it's deeply written in the kernel or your phone
I remember removing that screen on my old Moto G by flashing a custom boot image, I don't know if it's possible with this device as well, gotta do some research I guess.
ruhanboom said:
Actually you can get rid of it but you'd end up losing your unlocked bootloader
Click to expand...
Click to collapse
I locked my bootloader again, but it is still there. Not sure if it really can be removed.
ruhanboom said:
Well then you still have a unlocked bootloader how did you lock your bootloader anyway?
Click to expand...
Click to collapse
You are right mate...
I checked it this morning by connecting it to the PC and see there the state was still unlocked. Now I have locked it again to get the latest update.
Thanks
Anyone checked if there is /logo partition? That way it was possible to "hide" this message on Moto X Play (and probably other Lenovo-Motorola devices).
Hello Modders,
I was wondering if it was possible to relock bootloader + FRP to get rid of the screen "your device has been unlocked and can't be trusted" at boot, while keeping LineageOS (I don't really care of TWRP though).
Reason is the phone is for a rookie user that stress when she sees this screen.
From what I've read it seems to be a bad idea and that creates more problems if done without stock rom, is that true?
Petronius42 said:
Hello Modders,
I was wondering if it was possible to relock bootloader + FRP to get rid of the screen "your device has been unlocked and can't be trusted" at boot, while keeping LineageOS (I don't really care of TWRP though).
Reason is the phone is for a rookie user that stress when she sees this screen.
From what I've read it seems to be a bad idea and that creates more problems if done without stock rom, is that true?
Click to expand...
Click to collapse
Bad idea bro, bad idea
:laugh:
i have bough a x4 from ebay without warranty or anyting, the problem that i have. my phone says at the begining your device has loaded another operating system and then just a line of code says verity mode is set to disabled.
but after that the device starts normally, i have tried to lock the device again, but it doesn't work , maybe you have a solution for this problem :the model is XT1900-1 Type:M2997
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
cango123 said:
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
Click to expand...
Click to collapse
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
doksch84 said:
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
Click to expand...
Click to collapse
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
another problem
jhedfors said:
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
Click to expand...
Click to collapse
thank you guys, i just try to flash TWRP image, but it hangs with bootloader logs
getvar is-logical recove
getvar:has-slot:recovery
getvar_maxdown
Sending ....... in the command line? did anyone faces that problem ?