Database Develop

[Q] Strange thing happened ! (Dev- XT1068 Indian)

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]

How to remove device unlocked screen (before logo splash)

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

device has loaded a different operating system

I had a rooted (magisk) X4 (google_fi) with twrp 3.2.1. I removed root and reflashed the stock rom (OPW27.1) and relocked the bootloader.
Everything works fine even the OTA updates (I OTA'd back up to OPWS27.1.3, but there is an annoying yellow startup screen that displays "My device has loaded a different operating system." From what I read it's because the ROM isn't digitally signed? Is that correct?
Any way to remove this screen on startup?
**FYI this is not the unlocked bootloader screen this is something else.
Thanks.

Ok so google pay won't work. It says I have an unlocked bootloader and/or custom software. I have a stock rom, recovery, bootloader, and the bootloader is locked. Shouldn't it work? I never had this problem after flashing stock and relocking my old Moto X Pure.

ptn107 said:
reflashed the stock rom (OPW27.1)
Click to expand...
Click to collapse
I am not able to help with removing the boot message you're seeing, but is that copy of the stock rom you flashed still available and is it for Android One/Fi?

Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

did you managed to remove the message? I'm having the same problem

My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.

CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.

ptn107 said:
Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Does this help?

jsis83 said:
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.
Click to expand...
Click to collapse
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?

CypherPotato said:
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-x4/

CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
How to solve this?

so are we all mad? I've googled for hours, it seems to be you need a factory image of our phones to correct this problem.

figured it out, you need to supply your own keystore to remove the message in fastboot
https://youtu.be/OfWFmhucWlg?t=15m33s

how do you match rom to the correct bootloader? I've installed the 8.0.0 rom I get the same boot error as stated above. I'm trying to get everything back to stock to get the 8.1 update

we would need a factory image, that Motorola never will provide..

squanchy said:
we would need a factory image, that Motorola never will provide..
Click to expand...
Click to collapse
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750

jhedfors said:
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Click to expand...
Click to collapse
if it was a real factory image it would contain a developer keystore in the image, and people wouldn't get the yellow bootloader warning message..
Like I get from all these images posted on this Forum.
If the Keystore doesn't match your original phones Hardware Keystore, it uses the Image's keystore instead. A factory Image, has no keystore or sometimes a universal keystore, and you won't get the mentioned error.
I obtained all this information just watching a Android Developer talk about Verified Booting, but it never goes into detail how to remedy this issue. So unless I spend hours and hours learning how to re-compile an image from source, or figure out where my keystore is located, I'll be stuck with this message.
Because each manufacturer is different, they don't always follow the same Practices.

Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything

PlaviiCZ said:
Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything
Click to expand...
Click to collapse
You can't just ignore it? It does not affect functionality.

ptn107 said:
You can't just ignore it? It does not affect functionality.
Click to expand...
Click to collapse
I think it does, Google Pay cannot add my debet card cause it says "Your device is rooted or customized".

STILL cant get rid of N/A or bad key message!!! grrr

Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!

OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help

Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked

biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?

Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!

I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;

The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao

w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same

madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.

biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning

jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631

My Bootloader isn't unlocking

I tried to unlock my moto g5s plus bootloader with unlock code but it is showing me "invalid boot state". It is not unlocking. And it is showing an error when I turn on the device "Your device has loaded a different operating system". And I am facing many problems including my sim isn't supporting.
At first, my bootloader was unlocked and I was using a custom room. Then I wanted to lock my bootloader and flash stock rom. So I did flash stock ROM (maybe I flashed wrong stock firmware) and then I locked my bootloader with the simple code "fastboot oem lock". After that my device has this problem. Now I can't flash anything else.
Please help me with this situation. How can I unlock my bootloader and fix my phone?
Warning Screenshot -> https://imgur.com/a/QZjNAio
Invalid boot state error in cmd screenshot -> https://imgur.com/a/vijKUxw
Fastboot mode screenshot -> https://imgur.com/a/og17n7j

akibahmed2011 said:
I did what you told me. It says " Unable to match appropriate firmware. Some key information cannot be read from the device"
Screenshot: http://prntscr.com/u45a8v
Click to expand...
Click to collapse
If that doesn't help the devices is in bad shape. Try a service center.

You loaded wrong firmware - not good.
Moto has an app that'll download and install the correct firmware, get it, let it do it's thing and keep the fingers crossed.

Phazmos said:
You loaded wrong firmware - not good.
Moto has an app that'll download and install the correct firmware, get it, let it do it's thing and keep the fingers crossed.
Click to expand...
Click to collapse
Thankyou so much for your reply. Can you give me the name of that app or download link.

Phazmos said:
You loaded wrong firmware - not good.
Moto has an app that'll download and install the correct firmware, get it, let it do it's thing and keep the fingers crossed.
Click to expand...
Click to collapse
I did what you told me. It says " Unable to match appropriate firmware. Some key information cannot be read from the device"
Screenshot: http://prntscr.com/u45a8v