Well i have tried almost everyway to lock my bootloader and i failed miserably...I have a motorolo G 2014 XT1068 model..Whenever i try to fastboot.exe oem lock i get a error in cmd that "Please flash valid signed images first" nd in my mobile it shows "Version downgraded for boot failed to validate boot image" I can't understand the error..Well any suggestions or help will be highly appreciated.
While downgrading from 5.0.2 to android 4.4.4 i unlocked my bootloader so now i am on 4.4.4 and lock the bootloader is not working nd giving me those errors....
abhirockz said:
lock my bootloader
Click to expand...
Click to collapse
There is no benefit in locking the bootloader. Absolutely none.
doppelhelix said:
There is no benefit in locking the bootloader. Absolutely none.
Click to expand...
Click to collapse
Well Thank you for the info..I will stick with it.
Related
How can I relock my bootloader (XT1092) please? I know how it is done in theory ("fastboot oem lock begin" + flashing the factory image + erasing user data/cache + ending with "fastboot oem lock"), but it just does not work - I am getting a "not signed system error" with the stock firmware for the XT1092 which I grabbed from a link in the xda forums.
Motorola published only the factory image for the XT1095, I know that too. So is this the problem, that the captured firmware (not from the Motorola website) of the XT1092 is not validated for the procedure to relock the bootloader of the XT1092?
Thanks in advance for any tip!
same problem here, Ive tried flashing the lollipop firmware but I couldnt relock. I get this problem
SST lock failure!
Now Im downloading, RETEUALL_XT1092_4.4.4_KXE21.187-42_cid7_CFC.xml.zip
and Ill try with it... no idea...
any help?
it's very important because I need to give the phone back to amazon.
What do you suggest, give it back with unlocked bootloader?
I can put the stock logo bin so they cant see the logo that tells that the phone is unlocked, hoping the man doesnt watch the bootloader screen
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
tbiwalkar said:
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
Click to expand...
Click to collapse
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
doppelhelix said:
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
Click to expand...
Click to collapse
I understand but then how am i able to flash logo.bin?
tbiwalkar said:
I understand but then how am i able to flash logo.bin?
Click to expand...
Click to collapse
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
doppelhelix said:
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
Click to expand...
Click to collapse
I am locked and still i am able to flash various logo.bin files using mfastboot
tbiwalkar said:
I am locked and still i am able to flash various logo.bin files using mfastboot
Click to expand...
Click to collapse
Interesting. Thanks for the input. learned somthing new..[emoji4]
hello guys ) i just wanna ask if its possible to flash android m with nexus root toolkit or no ??
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
jj14 said:
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
Click to expand...
Click to collapse
thank you for the fast reply
Yes I followed those steps and flashed it perfectly.
BossJ said:
Yes I followed those steps and flashed it perfectly.
Click to expand...
Click to collapse
yeah same here, everything went more then well.
Should I relock the bootloader after flashing M ?
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
NOOO!!!!
To many folks have encountered an issue that soft-bricked their device afterwards.
You will still receive OTA with an unlocked bootloader.
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
stricker said:
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
Click to expand...
Click to collapse
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
danarama said:
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
Click to expand...
Click to collapse
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
danarama said:
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
Click to expand...
Click to collapse
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you like.
I have a moto x 2014 xt1097 phone and i like to gift it to someone so i wanted to relock the bootloader. but i am unable to relock the bootloader by the following cmd
fastboot oem lock
and i am getting some errors like
[ bootloader ] fastboot oem lock begin
[ bootloader ] flash signed images
can anyone suggest what is the proper procedure to relock the bootloader?
Bump. I'd like to know the same.
maninder.email said:
I have a moto x 2014 xt1097 phone and i like to gift it to someone so i wanted to relock the bootloader. but i am unable to relock the bootloader by the following cmd
fastboot oem lock
and i am getting some errors like
[ bootloader ] fastboot oem lock begin
[ bootloader ] flash signed images
can anyone suggest what is the proper procedure to relock the bootloader?
Click to expand...
Click to collapse
I recently installed official marshmallow 6.0 on my verizon XT1096 from other variant like xt1092 after unlocking bootloader and now I also getting same error to re lock it. I was irritating by bootloader unlocked warning screen. If anyone knows please tell me also. But anyhow I got rid from that warning screen by installing logo.bin file in fastboot. By following this link.
http://forum.xda-developers.com/moto-x-2014/general/warning-message-unlocked-bootloader-t2871478
abrarakram19 said:
I recently installed official marshmallow 6.0 on my verizon XT1096 from other variant like xt1092 after unlocking bootloader and now I also getting same error to re lock it. I was irritating by bootloader unlocked warning screen. If anyone knows please tell me also. But anyhow I got rid from that warning screen by installing logo.bin file in fastboot. By following this link.
http://forum.xda-developers.com/moto-x-2014/general/warning-message-unlocked-bootloader-t2871478
Click to expand...
Click to collapse
To be able to relock it, you must be 100% stock. For example you would have to flash back the full 5.1verizon firmware.
But there is no point in locking it. Locking it does not restore the warrany, it was voided when you unlocked it.
Also it does not make the warning bootloader unlocked message disappear. That message will only disappear if you flash a different boot logo.
Honestly, there is not much point to relocking it.
Sent from my XT1095 using Tapatalk
Thanks Sir, I understood the point. But one thing to ask, can I flash back the stock 5.1 factory images of XT 1095 instead of Verizon. By following the factory restore instructions. Actually I want it be 100% pure stock XT1095, just like convert it and get clean OTA of 6.0 stock without any issue.
Because when I was installing 6.0 xt1092 stock on it I got some errors
Like failed check boot & recovery
shown in image below and I am doubtful it is not 100% pure because now when I connect it to my PC it still detect it as xt1096.
I am not rooted or custom recovery.
Please sir little bit more help.
abrarakram19 said:
Thanks Sir, I understood the point. But one thing to ask, can I flash back the stock 5.1 factory images of XT 1095 instead of Verizon. By following the factory restore instructions. Actually I want it be 100% pure stock XT1095, just like convert it and get clean OTA of 6.0 stock without any issue.
Because when I was installing 6.0 xt1092 stock on it I got some errors
Like failed check boot & recovery
shown in image below and I am doubtful it is not 100% pure because now when I connect it to my PC it still detect it as xt1096.
I am not rooted or custom recovery.
Please sir little bit more help.
Click to expand...
Click to collapse
No. It has to be the xt1096 firmware to lock the bootloader.
Sent from my XT1095 using Tapatalk
Ok thanks sir.
How to unlock bootloader without sunshine T.T, xt1097 at&t 5.1
xsoftdesigner said:
How to unlock bootloader without sunshine T.T, xt1097 at&t 5.1
Click to expand...
Click to collapse
Sunshine is the ONLY way.
Sent from my XT1095 using Tapatalk
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 ?